When it acts
- When a conversation is resolved or handed to a person
- When a Zap sends a webhook
Connect Zapier and bring the agent to the tools you already use
With Zapier, the agent receives events and account data from any of your tools, and you trigger whatever you need when a conversation is resolved or handed to a person.
What it solves
The missing data, without a development request
The data the agent needs to close a question often exists, but in a tool with no dedicated integration. Asking for that connection puts it in the product queue, which takes months. With Zapier, the same data arrives this afternoon and nobody writes code.
What it solves
Alerts where your team already looks
Every team has its place: a sheet, a channel or a board. Make them check a new one and they’ll stop checking it. When the agent hands a conversation to a person or spots something, the Zap sends it where you already are, in the format you choose.
What it solves
Test before you ask for a dedicated integration
A Zap takes an afternoon to build and five minutes to remove. It’s the cheap way to find out whether that data improves the answers before you request a dedicated integration. If it works, you know it’s worth it; if not, you haven’t spent a sprint finding out.
What it does
What the connection gives the agent and what it does with it
What counts in an integration is what it lets the agent do. This is the data Zapier brings and what the agent does with it on its own.
What it can do
- Trigger a Zap with the conversation details
- Receive account data and answer with it
How Zapier helps the AI agent
Three concrete things that change your team’s day.
No custom development
If the tool is on Zapier, the agent can read from it or write to it without anyone writing code.
Alerts where you already look
When the agent hands a conversation to a person, the Zap posts it to the channel, sheet or task your team already checks.
Start today
A Zap takes an afternoon to set up, so you have the data before deciding whether it deserves a dedicated integration.
How it works
Three steps, and only the first needs a Zapier admin. You can change the rest later without reconnecting anything.
Authorize the connection
Open the integrations panel, pick Zapier and authorize access with the account your team already uses. You need admin rights in Zapier, so if you don’t have them, this is the only step you’ll have to ask someone for.
Choose what the agent sees
Select the channels, events and account fields it can access. Anything you don’t select stays hidden from it, and you can change it anytime without reconnecting.
The agent answers with that data
From the first conversation, the agent checks that data before replying, resolves what it can close on its own and hands the rest to a person, with the case already prepared.
Frequently asked questions
How long does it take to connect Zapier?
A few minutes. You authorize access and choose what it can see; nothing needs rewriting and no development work is needed to start.
Can I revoke access later?
Yes, from either side: by revoking the connection in Intake or removing the permission in Zapier. The agent stops reading that data right away and keeps answering with everything else.
Does using Zapier cost extra?
No. Every integration is included in the plan, from €49 a month. There are no add-ons to buy and no per-call charges.
What happens if Zapier stops responding?
The agent answers with what it does have and, if the question depended on that data, hands the conversation to a person and explains why. It never makes up data it couldn’t look up.
Do I need a paid Zapier plan?
Not for a one-step Zap; multi-step flows need one of their paid plans. That cost is Zapier’s, not Intake’s.
What data is sent in the Zap?
Whatever you choose when you build it. The agent sends the conversation details and you decide which fields go out.
