Integrations / Make
Make.com AI voice agents that run a scenario from a call
The agent calls a Make custom webhook as a tool during the call and reads back what the scenario returns, or Cartesia sends it the finished call.
Request intake agent
Collects requests and starts a scenario.
Instructions
Ask what the caller needs, collect name and phone, send the request to the scenario, and read back the reference it returns. Transfer to the office line if the caller asks for a person.
- Handoff
- Office
Connected tools
- Start scenarioWebhook
- Transfer to officeTransfer
What a Make AI voice agent can do
Open one to watch a call. The grey lines are the tools the agent calls mid-sentence.
Make's routers send urgent requests down one path and routine ones down another, inside the same scenario the tool calls.
A webhook response module sends a value back, such as a reference number, for the agent to read aloud on the call.
Register a call-events webhook, and a second scenario can log the finished call, send a summary or update a sheet.
Tool definitions
Webhook tools go to POST /v1/agents/tools. Transfers are a system tool on the agent. Replace the placeholder values in capitals with your own.
Start scenario
Posts the request to a custom webhook.
Show the JSON definition
Transfer to office
Cold transfer to your office.
Show the JSON definition
Set it up
Through Make's custom webhook module. The agent has no Make-specific app. A webhook tool posts to your scenario's URL. Vendor details read in October 2026.
Create a scenario with a custom webhook
Add the Webhooks module's Custom webhook as the trigger and copy its address.
Add the webhook tool
Paste the address and define the fields.
Add a response
Use a Webhook response module if the agent should read something back.
Run once and map the fields
Make learns the data structure from the first call.
Documentation
Before you build
Respond in time
The tool times out after 20 seconds by default. Keep the scenario's response path short, or set execution_mode to async so the turn doesn't wait.
Secrets in URLs
Make's webhook address contains a key. Treat the tool definition, which holds that address, as a secret.
Use cases for teams on Make
More integrations
Enterprise-grade security
HIPAA compliant

SOC 2 Type 2

GDPR
Make AI voice agent FAQs
How do I connect an AI voice agent to Make.com?
Start a scenario with Make's custom webhook module and paste its address into a Cartesia webhook tool. The agent posts the caller's details to the scenario during the call, and Make learns the data structure from the first run. There is no Cartesia module in Make.
Can a Make scenario answer the agent during the call?
Yes. Add a webhook response module, and the value it returns, such as a reference number, is what the agent reads to the caller. The tool times out after 20 seconds by default, so keep the path to the response short.
Can I run the scenario without waiting?
Yes. Set the tool's execution_mode to async when the agent does not need an answer. Cartesia runs an async tool separately, so the current turn can finish without waiting on the scenario.
Is the Make webhook address a secret?
Yes. Make's webhook address contains a key, so anyone with it can start your scenario. Treat the Cartesia tool definition that holds the address as a secret too. If it leaks, create a new webhook in Make and update the tool.
Who bills what on a Make setup?
Cartesia bills the call and Make bills the scenario. Agents run at $0.03/min, plus LLM usage and telephony, and the scenario's usage counts against your Make plan, including any post-call scenario that call events start.
Get started today
Talk to an expert.
Connect with a member of our team and learn how Cartesia can help you build world-class voice experiences.
Start building.
Access our models via API and bring a voice agent into production in minutes.