Works with Zapier
Registrations to any app with Zapier, and registrations from any form.
Every registration, cancellation and check-in can go to a Zapier webhook as it happens, signed so you know it came from us, with where the person came from. The other way, any Zap can register someone by posting their email and name to an incoming address made for your event. There isn't a Programmable Talk app in Zapier's directory yet, so this uses Zapier's own Webhooks by Zapier steps, which work the same in Make and n8n.
Try it: write your event in a sentence
What you get
On top of Zapier
Every change, as it happens
New registrations, people moved up from the waitlist, cancellations, check-ins and no-shows, questions, and events published or cancelled. Every type goes to your address; a Filter step in the Zap keeps the ones you want.
Signed, and sent again if missed
Each request carries an X-Programmable-Signature to check and an ID that stays the same on retries. A failed delivery is tried again for about a day, and you can send it again from Developers → Webhooks.
Register people from anything
An incoming address registers whoever a Zap posts to it, through the same path as every other way in: the same confirmation, reminders and waitlist.
Counted as its own way in
Each incoming address is a way in, named "Webhook: <name>", so the registrations it brings are counted like a QR code's.
The API, for the rest
Create events, read and export registrants, and send invitations from any tool with an API key.
What you can catch
| Type | When |
|---|---|
| registration.created | Someone registered, by any way in. |
| registration.promoted | Someone moved up from the waitlist. |
| registration.cancelled | A registration was cancelled, here or on Luma, Zoom, Eventbrite or Meetup. |
| registration.attended, registration.no_show | Marked as came or didn't, by you, the door, the live room or the platform. |
| question.created | A registrant asked a question. |
| event.published, event.cancelled | An event went live or was published to a platform, or was cancelled. |
How it works
- 1
Start a Zap with Webhooks by Zapier
Trigger: Catch Hook. Copy the address Zapier gives you.
- 2
Add it in Developers → Webhooks
Paste the address as your webhook and send a test, so Zapier has a sample to map. Keep the signing secret it shows you.
- 3
Map it to your app
A row in a sheet, a contact in your CRM, a message, anything Zapier connects to.
- 4
Or register people from a Zap
In Developers → Webhooks, make an incoming address for the event. In your Zap, add Webhooks by Zapier → POST to it, with email, first_name, last_name and company.
Good to know
- No app in Zapier's directory yet
- You won't find Programmable Talk in Zapier's app search. Use Webhooks by Zapier, as above; the deliveries and the incoming address are the same ones an app would use.
- Webhooks by Zapier is a paid Zapier feature
- Zapier lists it on its Professional, Team and Enterprise plans, not Free. Make and n8n have webhook steps of their own.
- No personal links in the payload
- A registrant's personal page link is never sent to a webhook: it's emailed to them only.
Questions
How do I check that a request came from you?
Compute an HMAC-SHA256 of "<t>.<raw body>" with your signing secret and compare it with v1 in the X-Programmable-Signature header. In a Zap you can skip this; in your own code you shouldn't.
Can I send registrations to a partner's CRM?
Yes: filter on the way in in your Zap and send those registrations on to wherever your partner wants them.
Does Make or n8n work the same way?
Yes. Point the outgoing webhook at a Make or n8n webhook, and post to the incoming address with Make's HTTP module or n8n's HTTP Request node.