Integrations

Vicket includes an integration engine for external communication and automation.

Connector families currently implemented

• Slack
• Microsoft Teams
• Discord
• Email
• Webhook

Scope model

Integrations are organization-scoped and can be tested, updated, and executed through integration services.

Current dashboard availability

In the current web dashboard build, the integrations section is present but marked as coming soon in the sidebar.

This means backend capability exists while full dashboard UX rollout is still in progress.

Recommendation

Plan your integration architecture early, then enable production usage when your dashboard release includes the integration management UI.

Connector details

Slack

Sends ticket notifications to a designated Slack channel. Supports new ticket alerts, status changes, and assignment updates. Configure with an incoming webhook URL from your Slack workspace.

Microsoft Teams

Delivers ticket notifications to a Teams channel via incoming webhook. Covers the same event types as Slack -- new tickets, status transitions, and assignment changes.

Discord

Posts ticket updates to a Discord channel using a webhook URL. Useful for developer-facing support teams that already use Discord for internal communication.

Email

Configures outbound email delivery for ticket notifications. Set a custom sender address, reply-to header, and delivery preferences. Email integration is essential for notifying end users about ticket status changes and agent replies.

Webhook

Sends raw HTTP POST payloads to any endpoint you control. This is the most flexible connector -- use it to trigger custom automation, sync data to external systems, or integrate with tools that Vicket does not have a native connector for.

Webhook payloads include the full event context (ticket ID, status, priority, assigned user, timestamps).

Configuring an integration

1. Navigate to Settings > Integrations
2. Select the connector type
3. Provide the required credentials (webhook URL, API key, or SMTP settings depending on the connector)
4. Save and send a test event to verify connectivity

Each integration can be toggled on or off without deleting its configuration.

Testing integrations

After configuration, use the Send test button to push a sample event. Verify that:

• The payload reaches the target system
• The event format matches your expectations
• Any downstream automation triggers correctly

Test events are clearly marked so they can be distinguished from production data.

Security considerations

• Webhook URLs should use HTTPS to encrypt data in transit
• Rotate webhook tokens periodically, especially if team membership changes
• Limit the events sent to each connector to reduce exposure of sensitive ticket data
• Review connected integrations during your regular organization access audits