Zapier
Automate on referral lifecycle events, or qualify referrals on events from the tools you already use — no code
Zapier connects Invitebase to thousands of apps without writing a webhook handler. Both directions use Zapier's built-in Webhooks by Zapier app — no Invitebase-specific Zapier app to install:
- Out: referral lifecycle events trigger Zaps — post to Slack when a referral validates, log rewards to a sheet, alert the team on
balance.low. - In: events from other tools flow into qualification gates — a demo booked in Calendly or a deal won in your CRM can validate a referral.
Webhooks notify — they don't fulfill
Rewards fulfill automatically once a referral validates; webhooks are notifications, not commands. Use Zaps to announce, mirror, and alert — never as a step rewards depend on.
Trigger Zaps from Invitebase
In Zapier, create a Zap with the trigger Webhooks by Zapier → Catch Hook and copy the generated URL (https://hooks.zapier.com/hooks/catch/…).
In the dashboard, open Developer tools → Webhooks, add the Zapier URL as an endpoint, and subscribe it to just the event types the Zap handles — say referral.validated and balance.low. Start with a test-mode endpoint while you build.
Use the dashboard's test-fire button to send a sample event — Zapier catches it and uses it as the sample record for mapping fields in your action steps. The useful fields live under data (the event's payload — see the delivery envelope).
Add your action steps — a Slack message, a Google Sheets row, a CRM update — and publish. Flip the endpoint to live mode (or add a second, live-mode endpoint) when you're ready.
Two delivery details worth knowing:
- Deliveries are at-least-once. If a duplicate Slack message is merely annoying, ignore this; if the action must not repeat, add a Zapier Filter or Storage step keyed on the event
id. - Catch Hook URLs are unguessable but unauthenticated. That's fine for notification-grade automations. If a Zap gates on payload contents, verify the
Invitebase-Signatureheader in a Code by Zapier step — the verification recipe ports directly.
Send events into gates
To qualify referrals on something that happens in another tool, have the Zap call POST /v1/events:
Start a Zap from the source app's trigger — Calendly → Invitee Created, HubSpot → Deal Won, whatever marks real activation for you.
Add the action Webhooks by Zapier → Custom Request:
- Method:
POST, URL:https://api.invitebase.com/v1/events - Headers:
Authorization: Bearer sk_…,Content-Type: application/json, andIdempotency-Keymapped from the trigger's record ID so Zap replays never double-count. - Data:
{
"name": "demo_booked",
"referred_user_id": "<mapped from the trigger>",
"properties": { "source_app": "calendly" }
}Run the Zap's test. The event lands in Developer tools → Events with source: api, and demo_booked becomes selectable in the gate builder.
The catch to plan for: referred_user_id must be the same ID you pass to the SDK's identify(), and most third-party triggers only carry an email. Close the gap at the source — put your user ID in a hidden field (Calendly, Typeform) or a CRM property — or add a lookup step in the Zap that resolves email → user ID against your backend.
Your secret key lives in the Zap
Secret keys have full API access, and pasting one into the Custom Request step stores it in your Zapier account. Anyone who can edit your Zaps can read it — restrict Zap editing accordingly, and if the key leaks, revoke it immediately.