Connect Cinch to Zapier
Send every quiz response into Zapier, and from there into a CRM, a spreadsheet, or any of the several thousand apps it reaches.
Cinch does not have a separate Zapier app, and does not need one. Zapier starts a Zap from an incoming webhook, and Cinch posts every completed response to a webhook — so the two connect with a URL and no code. The same steps work for Make, which calls the same thing a Custom Webhook.
Once a response is in Zapier it can go anywhere Zapier goes: HubSpot, Pipedrive, Mailchimp, Notion, Airtable, Google Sheets, a text message. You are wiring up one connection, not one per tool.
What you need
- A published Cinch funnel.
- A Zapier account. The free plan is enough to test this.
1. Create the Zap
In Zapier, make a new Zap and choose Webhooks by Zapier as the trigger, with the event Catch Hook. Zapier gives you a URL that looks like this:
https://hooks.zapier.com/hooks/catch/1234567/abcdefg/Copy it. In Make, start a scenario with a Custom Webhook module and copy that URL instead.
2. Paste it into your funnel
Open your funnel in Cinch, expand Also send it somewhere else under the lead settings, and paste the URL into the webhook field. It saves as you leave the box.
3. Send a real response
Zapier learns the shape of your data from a real example, so click Test trigger and then go and answer your own funnel from start to finish. A moment later Zapier will show the response, and you can map its fields to whatever comes next.
Answer it properly rather than clicking through. Zapier only offers you fields it has actually seen — if you skip the email step in your test, the email field will not be there to map.
What arrives
Each response comes through as JSON. The parts you will map most often:
response.contact— name, email and phone, whichever your funnel asked for.response.scoreandresponse.band— how they scored, and which band that put them in. This is what you filter on to treat a hot lead differently.response.answers— every question and the answer they picked, written the way they read it, in the order they were asked.response.fields— the same answers keyed by field name, for when you want to map one specific question rather than a readable list.
The webhook reference has the full payload, and it is worth a look before you build anything complicated on top.
Only send the good ones
Add a Filter step in Zapier after the trigger, and set it to continue only when response.score is greater than whatever you consider worth chasing. Everyone still lands in your Cinch dashboard; only the ones you care about reach your CRM or your phone.
If nothing arrives
- Check the funnel is published. A draft does not deliver, because nobody can answer it.
- Only completed responses are sent. Somebody who abandons halfway is stored and counted in your drop-off view, but they do not fire the webhook.
- Look at the response in Cinch. Each one shows how its deliveries went — sent, retrying, or failed with the error Zapier returned.
Cinch retries a failed delivery eight times over about two hours before giving up, and emails you if it does. So a Zap that was briefly turned off usually catches up on its own.
Read next
Build one yourself
Free, unlimited responses, no card.