In Freshdesk Admin, navigate to Settings > Automations > Ticket Creation or Ticket Update rules, and add a new rule with an action of type 'Trigger Webhook'.
Set the webhook URL to your publicly reachable HTTPS endpoint, choose the HTTP method (POST), and select 'JSON' as the content type.
Configure the 'Custom Headers' section if your receiver requires signature verification — Freshdesk supports custom headers but does not send a built-in HMAC signature, so implement shared-secret verification via a custom header value you define.
In the 'Content' section, use Freshdesk placeholder variables (e.g., {{ticket.id}}, {{ticket.status}}, {{ticket.requester.email}}) to compose the JSON payload your endpoint will receive.
Save and activate the automation rule, then create a test ticket that satisfies the rule's conditions and inspect your endpoint's received payload.
Handle retries on your receiver side — Freshdesk retries failed webhook deliveries a limited number of times; implement idempotent processing keyed on ticket ID and event timestamp.
Known gotchas
Freshdesk webhooks are configured through the Automations UI, not via a dedicated webhooks REST API endpoint — there is no programmatic webhook registration API as of the current API version.
The webhook payload is fully custom-templated via placeholders; if you omit a field from the template, it will not appear in the payload — design the template to include all fields your downstream system needs.
Freshdesk does not guarantee exactly-once delivery — design your receiver to be idempotent and deduplicate on ticket ID plus event type.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp