How to Link Outbound Webhooks on Telvoip
Outbound Webhooks allow Telvoip to automatically send ticket events to external applications and systems in real time. This enables teams to automate workflows, synchronize data across platforms, and trigger actions whenever important ticket activities occur.
Follow the steps below to configure a new outbound webhook:
From the Admin Panel, click Tickets, then navigate to Outbound Webhooks and click NEW WEBHOOK to create a new webhook configuration.

In the Endpoint URL field, enter the destination URL that will receive webhook payloads from Telvoip. Eg, https://example-endpoint/webhook-receiver
Enter a Signing Secret to secure webhook communications and enable your receiving application to verify that incoming requests originated from Telvoip.

Under Events, select the ticket activities that should trigger the webhook. Available events include: for example, ticket.created, ticket.status_changed, e.t.c

Review the selected events and webhook details to ensure they align with your integration requirements.
Click CREATE to activate the webhook. Telvoip will begin sending notifications to the specified endpoint whenever the selected events occur.
Ticket Events
Ticket events determine which actions within the ticketing system will trigger outbound webhook notifications. Select the events that are relevant to your integration requirements to ensure external systems receive updates at the appropriate stages of the ticket lifecycle.
- ticket.created – Sends a notification when a new ticket is created.
- ticket.updated – Triggers when ticket details are modified.
- ticket.status_changed – Sends updates whenever a ticket's status changes.
- ticket.assigned – Notifies external systems when a ticket is assigned to an agent.
- ticket.unassigned – Triggers when a ticket assignment is removed.
- ticket.comment_added – Sends updates when a new comment is added to a ticket.
- ticket.closed – Notifies connected systems when a ticket is closed.
- ticket.sla_warning – Triggers when a ticket is approaching its SLA target.
- ticket.sla_breached – Sends an alert when an SLA target has been exceeded.
- ticket.tag_added – Notifies external systems when a tag is applied to a ticket.
- ticket.tag_removed – Triggers when a tag is removed from a ticket.
By selecting the appropriate events, you can automate workflows, synchronize ticket activity with external platforms, and maintain real-time visibility across your support ecosystem.
Was this helpful?