⌘ K

Search

Search portal content

AI customer support in one tabAI customer support in one tab
⌘ K

Search

Search portal content

AI customer support in one tabAI customer support in one tab
  • Use the initdesk API
  • Set up webhooks
  • Use the MCP server
  1. Home
  2. Integrations

Set up webhooks

Have initdesk send a JSON message to your URL when a ticket is created, replied to, assigned, or resolved. Set it up and check each delivery.

On this page
  • Set up webhooks
  • Before you start
  • Add a webhook
  • Events you can choose
  • What initdesk sends
  • How delivery works
  • Check deliveries
  • Edit or delete a webhook
  • If something's not working
  • If you don't get any requests
  • If you see "Enter a valid endpoint URL."
  • If deliveries fail and your server looks fine
  • Related

Set up webhooks

Have initdesk send a JSON message to your URL when a ticket is created, replied to, assigned, or resolved. Set it up and check each delivery.

A webhook sends a message to a URL you control each time something happens to a ticket in your organization. Use it to log events, update another system, or start an automation. initdesk pushes events to you. To read or change initdesk data on demand, use the API instead.

Before you start

  • You need to be an account owner or admin. Other roles don't see Webhooks in Settings.
  • You need an HTTPS URL on your side that accepts a POST with a JSON body.
  • Have a way to see incoming requests, such as your server logs or a request-inspection service.

Add a webhook

  1. Open Settings > Webhooks.
  2. Select Add webhook.
  3. Under Endpoint, paste the full URL that should receive the events.
  4. Optionally, add a Description so your team knows what the webhook is for.
  5. Choose a Template: Default sends JSON for your own systems. Slack sends a message formatted for Slack.
  6. Under Events, select the events you want.
  7. Select Save.
A webhook form with the endpoint, description, template, and events
Choose the events and the payload format.

To test it, do something that triggers one of your events, such as creating a ticket, and check that your server got the request.

Events you can choose

Event in the app Name in the payload When it fires
Ticket created ticket.created A new ticket is created.
Ticket status changed ticket.changed_status A ticket's status changes.
Ticket assignee changed ticket.changed_assignee A ticket is assigned, reassigned, or unassigned.
Customer replied ticket.customer_replied A customer sends a message.
Teammate replied ticket.associate_replied Someone on your team replies to the customer.
System replied ticket.system_replied initdesk posts a message that the customer can see.
Internal note added ticket.internal_note_created Someone adds an internal note.
Ticket resolved ticket.resolved A ticket is resolved.

Pick only the events you need. If your receiver shouldn't see private notes, leave Internal note added off.

What initdesk sends

With the Default template, the request is a POST with Content-Type: application/json and this shape:

1
2
3
4{
  "event": "ticket.created",
  "data": { }
}

event is the name of the event. data holds the ticket's details at the moment the event fired. Read event first, then use data. New fields can appear over time, so ignore the ones you don't know.

The Slack template sends a Slack-formatted message instead of this shape. To post ticket activity to a Slack channel with inbox routing, use the Slack plugin.

How delivery works

  • Each webhook that includes the event gets its own request.
  • Your server has 15 seconds to answer. Respond with a 2xx status as soon as you accept the event, and do slow work afterward.
  • An answer of 400 or higher, a timeout, or a network error counts as a failed delivery. initdesk tries again with growing waits, up to 10 more times.
  • The same event can arrive more than once, for example if your server did the work but answered too slowly. Make your handler safe to run twice.

initdesk doesn't sign webhook requests, and there is no signing secret in Settings. Protect your endpoint yourself: use HTTPS, and put a long, hard-to-guess token in the URL that your server checks.

Check deliveries

Open Settings > Webhooks, then open the webhook. Delivery attempts lists what initdesk sent in the last 24 hours. Each row shows the time, the event, and the outcome: Success, Failed with the status code, or No response when your server didn't answer.

The Delivery attempts table with successful and failed rows
Delivery attempts show what initdesk sent and what your server answered.
  • Use the filters to show Failed only or a single event.
  • Select Inspect on a row to see the Endpoint used, the Payload, and the Response body or Error.

initdesk keeps delivery attempts for about 24 hours. They aren't a long-term log, so store what you need on your side. Query parameters in the endpoint URL can hold secrets, so don't share a screen that shows them.

Edit or delete a webhook

Open the webhook from Settings > Webhooks, change what you need, and select Save. To remove it, select Delete, then confirm with Delete webhook. You can't undo it, and events stop going to that URL right away.

If something's not working

If you don't get any requests

Check that the webhook has the event you expect ticked under Events. Then open Delivery attempts. If a row shows Failed or No response, your server rejected or missed the request. Check your firewall and your URL. If there are no rows, the event may not have fired, or the attempt is older than 24 hours.

If you see "Enter a valid endpoint URL."

The URL is missing or malformed. Paste the full URL. It can be up to 2,048 characters.

If deliveries fail and your server looks fine

Check status.initdesk.com for an incident.

Related

  • Use the initdesk API
  • Connect Slack
  • Use the MCP server
Use the initdesk API

Create an integration token, find your organization ID, and send your first request. The full endpoint reference is on developers.initdesk.com.

Use the MCP server

Add the initdesk MCP server to Claude, ChatGPT, or another assistant to search tickets, draft replies, and edit help center articles by chat.

Powered by initdesk