WHDeveloper · Outbound

Webhook integration

Send ticket events to any URL the moment they happen.

What it does

Outbound webhooks for everything else.

Leodesk POSTs a JSON payload to a URL you control whenever something happens on a ticket. Point it at a webhook endpoint, a Zapier or Make hook, or your own service — and react to support events in real time without polling the API.

Fire on ticket created, status change, customer reply, agent reply, internal note or macro applied
Deliver to any HTTPS URL — Zapier, Make, n8n or a service you wrote
Every request is HMAC-signed so you can verify it really came from us
Pick exactly which events each endpoint receives — no firehose

Webhooks pair well with automation rules: trigger an external workflow the same way you would route a ticket internally.

app.leodesk.io/settings/integrations/webhooks

Webhook

Active · POST · signed

ticket.created

ticket.status_changed

customer.replied

agent.replied

How it works

Paste a URL, pick events, verify the signature.

Open Integrations → Webhooks, paste an endpoint URL, and choose the events it should receive. Add an optional signing secret and Leodesk will POST JSON to it as events happen. Each request carries an X-Leodesk-Signature: sha256=<HMAC-SHA256 of the request body> header — recompute it with your secret to confirm the payload is genuine and untampered. The full event reference lives in the docs.

POST https://hooks.example.com/leodesk
Content-Type: application/json
X-Leodesk-Signature: sha256=9f86d0818...

{
  "event": "customer.replied",
  "ticket": {
    "id": "T-4821",
    "subject": "Refund for order #1043",
    "status": "open",
    "priority": "normal",
    "url": "https://app.leodesk.io/tickets/T-4821"
  },
  "customer": {
    "name": "Dana Okafor",
    "email": "[email protected]"
  }
}

No-code

Connect it with Zapier, Make or n8n.

You don’t need to host anything. Create a "Catch Hook" trigger in Zapier, Make or n8n, copy the URL it gives you, and paste it into Leodesk. From there, fan a ticket event out to 6,000+ apps — log replies to a sheet, ping a channel, or open a row in your CRM. For deeper, two-way connections, see Slack and Shopify instead.

zapier.com/app/editor

1Leodesk · ticket.created

2Zapier · Catch Hook

3Google Sheets · Add row

Integration FAQ

Setting up webhooks.

The quick questions before you point one at your service.

Read the docs

How do I verify a webhook came from Leodesk?

Each request includes an X-Leodesk-Signature header in the form sha256=<hex>. Compute an HMAC-SHA256 of the raw request body using your signing secret and compare it to that value. If they match, the payload is genuine and unmodified.

What happens if my endpoint is down?

A non-2xx response is treated as a failure and retried with backoff over the following hours. You can see recent deliveries, their status codes and responses in the webhook log, and replay any of them by hand.

Are these inbound or outbound webhooks?

Outbound. Leodesk POSTs ticket events to a URL you provide. To push data the other way — creating or updating tickets from your own systems — use the REST API documented in the docs.

Run support like an engineering team.

Free for 14 days. No card, no sales call to get started.

Try Leodesk