Connect Cinch to Slack

There is no Slack app to install. Slack accepts an incoming webhook — a URL that turns an HTTP POST into a message in a channel — and Cinch posts every completed response to a webhook. So the two connect directly, with no Zapier in the middle.

A caveat worth having up front: what lands in the channel is the raw response as JSON, not a tidy summary. That is genuinely useful for a small team who want a ping and a name, and it is not a formatted card. If you want it pretty, send it through Zapier and use its Slack action instead.

1. Create the incoming webhook

1. Go to api.slack.com/apps and create an app, choosing From scratch. Pick the workspace it belongs to.
2. Open Incoming Webhooks and turn it on.
3. Click Add New Webhook to Workspace and choose the channel the leads should land in. A private channel is a reasonable choice — these are people’s contact details.
4. Copy the URL Slack gives you. It starts with https://hooks.slack.com/services/.

2. Paste it into your funnel

In Cinch, open the funnel, expand Also send it somewhere else, and paste the URL into the webhook field.

3. Answer your own funnel

Publish it if you have not already, then run through it yourself. The message should appear in the channel within a second or two of you finishing.

Keep it to the leads worth interrupting for

A channel that pings on every response gets muted within a week, and a muted channel is worse than no channel. Two ways to keep it useful:

• Point Slack at a funnel that is already qualifying — a scored one where finishing means something — rather than at everything you publish.
• Or route through Zapier with a filter on response.score, so only the ones above your threshold reach the channel.

If nothing arrives

• Slack webhook URLs are tied to one channel. If you picked the wrong one, make another.
• Only completed responses are delivered — an abandoned one is stored and counted in drop-off, but does not post.
• Check the response in Cinch: it shows whether the delivery was sent, is retrying, or failed with whatever Slack said. A revoked webhook usually shows up as a plain 404 there.