Connect a customer event to a system your team owns. Gleap’s webhook integration sends ticket events to a callback URL, giving your application the input for a custom notification, record, or follow-up workflow.
Choose what your endpoint receives
The native integration supports ticket creation, updates, deletion, messages, and assignee-change events. Set the events and ticket types your receiver needs, then decide what your application should do with them.
For example, your backend could use an incoming bug report to create an entry in an internal triage system. Your code defines the mapping and the downstream behavior.
Configure the receiver
Set the callback URL in the webhook configuration. Custom header fields let you provide the authentication information expected by your endpoint.
Send a sample event and inspect the payload your service receives before connecting it to a production action. Build the receiver around that event data and the behavior your workflow requires.
The integration guide explains where native connections are configured. To work with Gleap through its API, start with the developer documentation.
If your destination already has the required action in Zapier, the Zapier integration offers a route without writing the receiver yourself.
