Zapier
Push Waitlyze events into Zaps via webhooks.
There is no native Waitlyze Zapier app. The supported path is a Waitlyze webhook connected to Zapier's Webhooks by Zapier trigger. Treat this as a recipe built on signed event delivery, not a direct app connection.
Recipe: new signup → your Zap
Add a webhook endpoint in Waitlyze
In waitlist settings → Webhooks, add your Zapier webhook URL (new endpoints receive all four events: signup.created, signup.verified, referral.completed, milestone.reached). Enable Include subscriber data to map email, phone, custom fields, and referral details directly in later Zap steps; leave it off if you want ID-only events. Copy the signing secret.
Catch the hook in Zapier
Create a Zap with a Webhooks by Zapier → Catch Raw Hook trigger and paste the URL back in Waitlyze. The raw variant preserves the exact request body and the x-waitlyze-signature header, both of which signature verification needs. Send a test from Waitlyze ({ "test": true } in data) and confirm the Zap fires.
Verify the signature in a Code step (recommended)
Before any later Zap action runs, verify the event in a Code step: pass the Catch Raw Hook's request body, the x-waitlyze-signature header value, and your signing secret to the verifier from Webhooks, and stop the Zap if verification fails.
Map the subscriber fields
With enrichment enabled, map fields from data.subscriber directly into Sheets, Slack, or your CRM; the test hook includes realistic sample values for setup. Without enrichment, use signupId in a follow-up lookup against your subscriber read path or the Signup API. Always check for data.test before creating real contacts.
Tips: dedupe on the event id (retries redeliver), return success only after your Zap's side effects are durable, and keep one Zap per event type so failures stay isolated. Pause the Waitlyze endpoint while editing the Zap to avoid queueing noise.