Signal · Connect

Your event data,
in whatever tool comes next.

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".

POST · hooks.n8n.yourco.in
registration.created
Delivery #4821 · attempt 1 · 200 OK
X-SignupDesk-Signature:
t=1763179805,v1=9f3a…c21e
{ "id": 4821,
  "event": "registration.created",
  "data": { "name": "Priya Sharma",
    "seat_number": "V-14",
    "category": "vip" } }

Ten events. Each one a webhook.

Subscribe to any mix per endpoint. Every payload carries a stable delivery id, a timestamp and an HMAC signature.

📝
registration.created · approved
Fires when a seat is confirmed, including auto-approved and accreditation-approved registrations. Name, email, mobile, seat, category, event.
✅
checkin.completed
Gate scan, kiosk, or manual check-in. Timestamp and seat, so your "who is in the room" board updates live.
💳
order.paid · refund.issued
Order number, buyer email, amount in INR, gateway, registration ids. Push to Zoho Books, Tally via a connector, or a finance sheet.
⏳
waitlist.joined
Position and tier. Trigger a "we will let you know" message from your own tool, or alert sales that demand exceeds seats.
🤝
lead.captured
A sponsor scans a badge at their booth. Lead goes to the exhibitor's CRM through your automation, with priority and remarks.
💬
rsvp.accepted · declined · registration.deleted
WhatsApp RSVP replies and deletions, so your headcount sheet stays honest without anyone exporting it.

Four things other tools can do inside SignupDesk.

➕
Create registration
A row lands in your Google Sheet, a form fires in Typeform, a deal closes in HubSpot: create the attendee, allocate the seat, send the QR pass. Duplicate emails are refused unless the event allows them.
🔍
Find attendee
Look up by email. Get seat, category, check-in status and QR token back. The step every multi-step automation needs before it does anything else.
🎫
Check in
Mark an attendee present from outside SignupDesk. Useful when a venue's own turnstile system is the source of truth.
⭐
Tag VIP
Flip the VIP flag on the attendee's profile across all your events. Feeds the Attendee CRM and the VIP filter in Campaigns.

Signed, retried, logged. The boring parts done properly.

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.

Open source, on your own server, your attendee data stays yours.

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.

What usually sits on the other end.

🔌
HubSpot, Zoho CRM and Mailchimp have direct connectors. Hooks cover everything else, including the CRM your client insists on.
🤝
lead.captured is the trigger exhibitors ask for. Each sponsor's leads can flow into their own pipeline the moment the badge is scanned.
📣
Tag VIP from an automation, then target VIPs from Campaigns. The two features share the same attendee profile.

Questions developers ask us

Is SignupDesk listed in the Zapier app directory?
Not yet. Today you connect through Zapier's Webhooks by Zapier app, or through n8n and Make's native webhook nodes, using our REST hooks API. It is the same mechanism a listed Zapier app uses under the hood. We publish a private Zapier app when a customer needs one.
Why do you recommend n8n first?
n8n is open source and can run on your own server, so the attendee data you route through it never passes a third-party automation cloud. That matters for DPDP and for clients with data-residency clauses. Make and Zapier work exactly the same way if you prefer them.
How do I verify a webhook is really from SignupDesk?
Every delivery carries 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.
What happens when my endpoint is down?
We retry at 1 minute, 5 minutes, 15 minutes, 1 hour and 6 hours. Six attempts in all over about seven hours. Each retry carries the same delivery id so you can deduplicate. After the last attempt the delivery is marked failed and stays visible in Admin → Webhooks → Logs.
Where do I get an API token?
Admin → Workspace → API Keys. Create a key, copy it once, send it as 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.
Stop waiting for "the integration".
Subscribe a hook, fire a test registration, watch it land in your tool. Ten minutes on a call.