Easily Integrate the BusyConf ticket.updated Webhook into your application using Javascript, Ruby, and other frameworks.
Occurs whenever an existing ticket is successfully updated (The cancelled_at will be set for cancelled tickets. It will be null for active or reinstated tickets).
Steps to receive the Busyconf ticket.updated Webhook
- Sign up for your free Hooky account.
- Create a new Webhook Source, and select busyconf. This will be the endpoint that receives the Busyconf ticket.updated webhook on behalf of your application, and forwards them using the unified SDK.
- Once the ticket.updated webhook is received from Busyconf, you'll see the payload under the Live Logs section of your webhook source.
- Next, follow the examples below to integrate the Hooky SDK in Ruby or Javascript, and start receiving webhooks.
- Sign up for your free Hooky account.
- Create a new Webhook Source, and select busyconf. This will be the endpoint that receives the Busyconf ticket.updated webhook on behalf of your application, and forwards them using the unified SDK.
- Once the ticket.updated webhook is received from Busyconf, you'll see the payload under the Live Logs section of your webhook source.
- Next, follow the examples below to integrate the Hooky SDK in Ruby or Javascript, and start receiving webhooks.