Send events to RAVE™ with Zapier

Zapier connects RAVE™ to thousands of tools that don't have a direct webhook, such as Stripe, Shopify, Typeform, Zoom or your course platform. Any Zapier trigger can create a RAVE™ event with the Webhooks by Zapier action.

Create the Zap

1. 1

   Pick a trigger

   Start a Zap with any trigger: a new order, new subscriber, new form entry, new row and so on.

2. 2

   Add the action

   Choose Webhooks by Zapier as the action app and POST as the event.

3. 3

   Paste your RAVE™ URL

   Use your campaign's webhook URL with labels, for example https://rave.cxformula.com/api/ingest/YOUR_CAMPAIGN_KEY?source=zapier&event=purchase&product=Ultimate%20Pack.

4. 4

   Set the payload type

   Choose JSON.

5. 5

   Map the data

   Add first_name, last_name, email, city, state, country and product, mapped from your trigger. Send whichever you have.

6. 6

   Test and publish

   Test the step, check RAVE™, then publish the Zap.

Get the webhook URL from the campaign's Sources tab in RAVE™. Under Setup guides, pick Zapier and fill in event, product and step to build the full URL.

Ready-made recipes

Add source=zapier to any of them so you can tell where events came from. The exact trigger names depend on each app in Zapier.

Test it

1. Click Test step in Zapier. RAVE™ replies with {"ok":true} when it records the event.
2. If the campaign is live, the person appears on your site within about a minute.
3. Check the campaign's Analytics to see the event counted.

Prefer an API key?

If your plan includes API access, you can instead POST JSON to https://rave.cxformula.com/api/v1/events with the header Authorization: Bearer rave_live_…. Create the key in Settings → API keys in your workspace. See the REST API guide.

Troubleshooting

• Zapier says it worked, but RAVE™ shows nothing. Look at the response: skipped means the campaign is paused or the data had no first name and no email; deduped means the same email already did the same thing within the campaign's duplicate window.
• Wrong event type. Set event= in the URL rather than relying on the trigger data.
• The payload is nested. That's fine. RAVE™ looks for common field names at any depth, but mapping flat fields like first_name is the most reliable.

More detail on labels and event types: How webhooks work.