Connect Cinch to Zapier

Cinch does not have a Zapier app, and does not need one. Zapier can start a Zap from a web address you give it. Cinch can send every completed response to a web address. So the two join up with nothing but that address, 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 and scroll to Where leads go. Press Webhook, paste the address in, and click away from the box. It saves on its own.

3. Send a real response

Zapier works out what your data looks like from a real example. Click Test trigger, then go and answer your own funnel from start to finish. A moment later Zapier shows the response, and you can match its fields to whatever comes next.

Answer it properly rather than clicking through. Zapier only offers you fields it has actually seen. Skip the email question in your test and the email field will not be there to use.

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.score and response.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, straight after the trigger. Set it to carry on only when response.score is above whatever you count as 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.