A registration lands, a ticket is paid, a badge is scanned at the gate. Each one can fire a signed webhook into n8n, Make or Zapier, and from there into your CRM, your Google Sheet, your Slack channel or your accounts team's inbox. Ten triggers, four actions, retries you do not have to think about. No "contact sales for the integration".
Subscribe to any mix per endpoint. Every payload carries a stable delivery id, a timestamp and an HMAC signature.
Signature. Every delivery carries X-SignupDesk-Signature: t=<unix>,v1=<hex>. Compute HMAC-SHA256 over <unix>.<raw body> with your endpoint's secret and compare. Reject timestamps older than five minutes and replays are dead.
Retries. A non-2xx or a timeout is retried at 1 minute, 5 minutes, 15 minutes, 1 hour and 6 hours. Six attempts over about seven hours, long enough to ride out a deploy or a DNS hiccup on your side. The delivery id stays the same every time, so deduplicating on your end is one line.
Dead letters. When the sixth attempt fails, the delivery is marked failed and stays in Admin → Signal → Webhooks → Logs with the last HTTP status and response body. You see what broke. Nothing disappears into a void.
REST hooks. Automation tools subscribe and unsubscribe through the API themselves: POST /api/v1/hooks/subscribe, DELETE /api/v1/hooks/{id}, and GET /api/v1/hooks/sample/{event} for test data. That is the contract Zapier's REST Hook triggers and n8n's webhook node expect.
Zapier and Make are fine tools and they work with these hooks out of the box. But every attendee record you route through them passes a third-party cloud, usually outside India. For a corporate client with a data-residency clause, or an organiser who takes DPDP seriously, that is a conversation you would rather not have.
n8n is open source and runs on a ₹500-a-month VPS. Point its webhook node at our hooks, build the flow, and the data goes from our server to yours and nowhere else. The same is true of Activepieces. We built the hooks to the REST-hook standard so you can pick whichever tool fits the client, not whichever one we happened to list with.
We are honest about one thing: SignupDesk is not in the Zapier app directory yet. Use Webhooks by Zapier today. When a customer needs a private Zapier app, we publish one.
X-SignupDesk-Signature: t=<unix time>,v1=<hex>. Compute HMAC-SHA256 over <unix time>.<raw body> with the secret you set when subscribing and compare with v1. Reject anything older than five minutes to stop replays.Authorization: Bearer. Keys can be scoped and expire on a date you set. GET /api/v1/hooks/events returns every trigger with a sample payload.