Connect an eflow to Zapier

You do not need anything from us to use Zapier, and there is nothing to install. Zapier’s own Webhooks by Zapier trigger hands you a URL; you paste it into your eflow’s Integrations tab and every completed conversation arrives in Zapier from then on, ready to go to any of the apps Zapier connects to.

Make and n8n work the same way. Anything with a “receive a webhook” trigger does.

Set it up

1. In Zapier, create a Zap. Trigger: Webhooks by Zapier, event Catch Hook. Leave Pick off a child key empty — you want the whole body. Continue, and copy the custom webhook URL Zapier shows you.
2. In Acquainto, open the eflow, go to its Integrations tab, and paste that URL into Webhook URL on the Webhook card. Save.
3. Back in Zapier, click Test trigger. It waits for a request, so send one: open your eflow’s link and answer it through to the end. Zapier picks that up as the sample you will map fields from.
4. Map from values. Zapier shows nested fields joined with a double underscore, so the field key monthly_budget reads as values__monthly_budget. Each answer arrives in its real type — a rating as the number 9, a date as 2026-10-01 — so Zapier filters like “rating is above 7” work without converting anything first.

Your test conversation is a real response. It appears under Feedback and counts toward this month’s usage like any other.

Before you build anything on it

Add a filter on event as your first step. Three kinds of event arrive at the same URL: response.completed when someone finishes, and response.abandoned / eflow.partial when someone stops partway. Without a filter, an abandoned conversation creates a half-empty record in whatever you connected.

Do not map the numbered answers list. answers.2.value is the third question on that response, and because eflows branch, the third question is not the same question on the next one. That is the whole reason values exists. A field key is fixed when a question is created and does not change when you reword the question.

One URL per eflow. An eflow has a single Webhook URL, so pointing it at Zapier means your own endpoint cannot also have it. If you need both, let Zapier forward.

Keep the URL private. We sign every delivery with an Acquainto-Signature header, but Catch Hook does not check signatures — so anyone who learns that URL can post invented responses into your Zap. Treat it like a password, and regenerate it in Zapier if it gets out.

Failed deliveries are visible. Recent Deliveries on the Integrations tab shows what we sent and what came back, and we retry a failed delivery for about a day. If a Zap was off, you can see what it missed rather than guessing.

Why there is no Acquainto app in Zapier’s directory

Because it would not give you anything this does not. The connection above is the same data, at the same moment, with the same reliability — a listed app would mainly make us findable by people browsing Zapier’s directory, which is our marketing problem rather than your integration problem. Zapier also requires a 90-day public beta before any listing goes live, and the listing needs permanent upkeep after that.

If a directory listing would genuinely change how you work — your team only installs apps from it, say — tell us through Help & support. That is the argument that would change our mind, and we have not heard it yet.