When it acts
- Incoming webhook from Make scenario
- Intake ticket updated
Connect Make and feed the agent the context it lacks
With Make, you can send agent events, account fields, and state changes that help the agent resolve repetitive tickets.
What it solves
Every loose tool stops being a blind spot
An account state is rarely in one place: one fact in the billing panel, another in a sheet, another in an internal tool. What the agent cannot see, a person has to look up. With Make those facts reach the agent and those questions stop escalating.
What it solves
Scenarios that do something when something happens
Not everything ends when the agent replies: sometimes a record must be created, someone told or a status updated in another system. Make triggers that work from what happened in the conversation, so the administrative half of the ticket also stops being done by hand.
What it solves
Without waiting for integrations to exist
No support tool is going to integrate the internal system you built yourselves. Make covers exactly that gap: the agent works with your system without anyone having to build a custom integration and maintain it afterwards.
What it does
What the connection triggers and what the agent does with it
An integration is not useful for being on the list: it is useful for what it lets the agent do. This is what Make puts on the table, and what the agent does with it without anyone watching.
What it can do
- Trigger Make scenario
- Receive variables and execute AI decision
How Make helps the agent resolve with context
Three concrete things that change the team day, not a feature list.
More product state
Sync plan, configuration, usage, or key events from tools without a native integration.
Automate handoffs
Create tasks, alerts, or updates when the support workspace detects that human intervention is needed.
Light setup
Connect flows without asking for a custom integration for every data point the agent needs.
How it works
Three steps, and only the first needs a Make admin. The rest you change later without reconnecting anything.
Authorise the connection
You open the integrations panel, pick Make and authorise access with the account your team already uses. You need to be an admin in Make, so if you are not, this is the only step you will have to ask someone for.
You choose what the agent sees
You tick the channels, events and account fields it can reach. What you do not tick does not exist for it, and you can change that whenever you want without reconnecting anything.
It answers with that context
From the first conversation the agent looks that data up before replying, resolves what it can close on its own and passes to a person what it cannot, with the case already assembled.
Frequently asked questions
How long does connecting Make take?
Minutes, not an afternoon. You authorise access and choose what it can see; nothing needs rewriting and no development work is needed to start.
Can I revoke access later?
Yes, and from either side: revoking the connection in Intake or withdrawing the permission from Make. The agent stops reading that data immediately and keeps answering with the rest.
Does using Make cost extra?
No. Every integration sits inside the per-resolved-conversation price: 0.41 EUR on annual billing. There is no add-on to buy and no call meter.
What happens if Make stops responding?
The agent answers with what it does have and, if the question depended on that data, hands off to a person explaining why. It never invents the value it could not look up.
Do I need to know how to code?
No. Make lets you build visual scenarios to pass useful data into the agent.
Which events can I use?
New conversation, resolved ticket, tag added, account changes, or product events you want to connect.
