Send a Freshdesk Ticket Status Change to a Webhook

A ticket escalated to another team can update an internal queue through a webhook. Start with one status transition and a test endpoint your organization owns.

Worked example

Expected request body for a synthetic escalation

{"ticket_id":6402,"state":"escalated"}

Expected destination row = Ticket 6402 in the internal escalation queue.

Steps

  1. Write the exact ticket update event you want, such as a transition to a configured Escalated status. Decide the minimum fields the receiver needs and choose a test ticket.
  2. Create a ticket-update automation with the transition as its condition and Trigger Webhook as its action. Use HTTPS and your test endpoint's approved authentication.
  3. Map the ticket identifier and status using the available placeholders. Inspect the received body and confirm the rule left out subject, message text and customer details.
  4. Send a duplicate fixture to the receiver. Upsert an escalation status by ticket ID so the repeated notification updates the same row.

What to check

  • Edit an unrelated field after the status change. Verify that this update does not enqueue a second escalation.
  • Use the destination logs to distinguish an unmatched rule from a delivery failure. Review the webhook's error history before enabling it on live tickets.

View Freshdesk

References