Send events to RAVE™ with Make
Add an HTTP "Make a request" module to your Make scenario to send opt-ins and purchases to your RAVE™ campaign.
2 min read · Updated Oct 5, 2026
In Make (formerly Integromat), an HTTP → Make a request module sends data from any trigger to your RAVE™ campaign's webhook URL.
Build the scenario
Start with your trigger
Any module that produces a new contact, order or entry.
Add an HTTP module
Add HTTP → Make a request after the trigger.
Set the URL and method
Paste your campaign's webhook URL with labels, for example
https://rave.cxformula.com/api/ingest/YOUR_CAMPAIGN_KEY?source=make&event=signup, and set the method to POST.Set the body
Body type Raw, content type JSON.
Map the request content
Add the fields below, mapped from your trigger.
Run once, then schedule
Click Run once to test, check RAVE™, then turn the scenario on.
Get the webhook URL from the campaign's Sources tab in RAVE™. Under Setup guides, pick Make and fill in event, product and step to build the full URL.
Request content
Map these from your trigger. Send whichever you have; RAVE™ needs at least a first name or an email.
{
"first_name": "{{1.first_name}}",
"last_name": "{{1.last_name}}",
"email": "{{1.email}}",
"city": "{{1.city}}",
"state": "{{1.state}}",
"country": "{{1.country}}",
"product": "{{1.product}}"
}
{{1.first_name}} stands for the field from module 1 in your scenario; pick the real fields from Make's mapping panel.
Labels for different signals
- Opt-in:
?source=make&event=signup - Purchase:
?source=make&event=purchase&product=Ultimate%20Pack - Webinar attendance:
?source=make&event=attended&product=Live%20Workshop
Use one HTTP module per signal, or a router with one HTTP module per branch.
Test it
- Click Run once and trigger the event. The HTTP module's output should show
{"ok":true}. - Check the campaign's Analytics in RAVE™.
- If the campaign is live, the person appears on your site within about a minute.
Troubleshooting
- The response says
skipped. The campaign is paused, or the body had no first name and no email. - The response says
deduped. The same email already did the same thing within the campaign's duplicate window. - An "unreadable body" error. Check the body type is Raw with content type JSON and that the JSON is valid (watch for missing commas or quotes).
- Names show as merge text. Make sure each value is a mapped field, not typed text.
More detail on labels and event types: How webhooks work.
Related articles
- Send events to RAVE™ with ZapierUse Webhooks by Zapier to send purchases, sign-ups and engagement from any Zapier trigger to your RAVE™ campaign.
- Send ClickFunnels opt-ins and purchases to RAVE™Create one ClickFunnels 2.0 webhook endpoint per signal (opt-in, order, upsell) pointed at your RAVE™ campaign's webhook URL.
- Send HighLevel (GoHighLevel) opt-ins and orders to RAVE™Add a Webhook action to a HighLevel workflow so form submissions and orders show up in your RAVE™ cards.
Can't find it?
Send us a question, a bug or an idea. It goes straight to the RAVE™ team, and you can follow its status.