Integrations
Can I connect Roccai to Zapier or my own webhook?
Yes, two ways. Zapier gives Roccai a new-lead trigger that can start a Zap into any app Zapier supports, including Make and Google Sheets. Or point Roccai at your own endpoint: it POSTs the full JSON payload the moment an enriched lead is captured, with an optional signing secret you can verify.
How the Zapier & custom webhook connection works
Anything the native connectors don't cover, these two do — Zapier when you want no code, a webhook when you want the raw payload.
Zapier is the no-code route. Create a Zap with a webhook trigger, paste its URL into the Zapier integration in Roccai, and select the campaigns that should fire it. Every captured lead starts the Zap, which can then reach any app in Zapier's catalogue — including Make, Google Sheets and any CRM without a native Roccai connector.
The custom webhook is the direct route. Give Roccai your endpoint URL and it POSTs the full payload as JSON the moment an enriched lead is captured. You can also set a signing secret, which Roccai sends with every request so your endpoint can verify it came from us. Use this when you already have a system that can receive data and you would rather not route it through a third party.
Zapier & custom webhook integration at a glance
| How it works | |
|---|---|
| Zapier — what you need | A Zapier webhook URL from a Zap you have created |
| Zapier — best for | Reaching a tool with no native connector, without writing code |
| Webhook — what you need | Your endpoint URL, plus an optional signing secret |
| Webhook — best for | Sending the raw payload straight into a system you control |
| Both — scoping | Per campaign — you pick which campaigns fire it |
| Both — timing | On guide submission, in real time |
What you can do with it
Reach a CRM or email tool with no native Roccai connector, by letting Zapier bridge the two.
Run Make scenarios from an enriched lead — Make connects through the webhook or through Zapier, the same way any other automation platform does.
Drop leads into a Google Sheet for a campaign you want to watch manually before wiring anything permanent.
Post straight into your own data warehouse, internal app or lead router, with the decisions and AI summary layers included or switched off as you prefer.
What the payload contains
| Field | What it holds |
|---|---|
| companyId | Your Roccai company ID — constant across all your guides |
| moduleId | Which guide was completed |
| sessionId | The individual run of the guide, for tying a lead back to its session |
| campaignId | The campaign the guide was shared under, so you can route or attribute by channel |
| submittedAt | ISO 8601 timestamp with timezone offset, e.g. 2026-09-04T12:34:56.789012+00:00 |
| data | The contact fields the person entered, keyed by your own field names — e.g. email |
| aiSummary | Optional plain-language summary of the session, e.g. "Customer compared pension plans and leans toward balanced growth; wants advisor contact by email." |
| decisions | Optional. One entry per card, keyed by card ID, each holding the question text, every option with whether it was selected or unselected, the selected answer, and a timestamp |
Frequently asked questions
How do I connect Roccai to Zapier?
Create a Zap with a webhook trigger, copy the webhook URL Zapier gives you into the Zapier integration in Roccai, and choose which campaigns should fire it. Each captured lead then starts the Zap, which can route the data into any app Zapier supports.
Does Roccai work with Make?
Yes. Make connects either through the custom webhook — point Roccai at a Make webhook URL — or via Zapier. There is no separate native Make connector; it uses the same webhook route as any other automation platform.
What does the Roccai webhook payload look like?
A single JSON POST with Content-Type: application/json. It carries companyId, moduleId, sessionId, campaignId and submittedAt, a data object with the contact fields the person entered, and optionally aiSummary and a decisions object holding every question, the options chosen and the options rejected.
How do I verify a Roccai webhook came from Roccai?
Set a signing secret on the webhook integration. Roccai then sends it with every request, so your endpoint can verify the call came from Roccai before accepting the payload. The setup screen in Roccai shows you exactly what to check for.
Can I turn off the AI summary or the decisions data?
Yes, both are toggles. Switch them off and the payload carries contact data only — useful when the receiving system does not need the preference detail or you would rather not store it.
Can I send Roccai data to Google Sheets?
Yes, through Zapier. Point a Zap's Google Sheets action at the Roccai trigger and every captured lead becomes a row — a quick way to watch a campaign before committing to a permanent integration.
Other Roccai integrations
Roccai also connects natively to HubSpot, Ortto, Mailchimp, Klaviyo and ActiveCampaign. For the full list, the data that flows and the payload reference, see all Roccai integrations.
Talk through your setup