How it differs from Zapier
The Zapier trigger sends data and that is the end of it: a Catch Hook does not answer. A Make scenario that ends with a Webhook response module does, and whatever it answers reaches the agent as the tool’s result. So the agent can not only push something into your systems but ask them something while the caller is still on the line: an order’s status in the shop, a free slot in the booking system, a customer record in an app Make has a module for and we have no integration with. A scenario without a Webhook response module works too: Make answersAccepted, the agent gets “sent” and carries on.
Connecting
1
The scenario in Make
New scenario → Webhooks → Custom webhook module → Add, give it a
name. If the scenario should answer the agent, end it with a
Webhooks → Webhook response module with a JSON body (example below).Recommended: in the webhook’s Show advanced settings switch on
Get request headers, and after the first module add a filter: the
x-brosbots-secret header equal to your secret. You enter the same
secret on our side.2
Copy the address and switch the scenario on
The address is in the webhook module (Copy address to clipboard),
of the form
https://hook.eu1.make.com/…. The toggle in the bottom left
of the editor has to be on; with a webhook trigger the schedule is
Immediately.Make only learns the data structure from the first request. Click
Redetermine data structure, save the connection on our side (saving
delivers a test message) and only then map the fields in the modules
that follow.
3
The connection in BrosBots
Integrations → Make. Paste the address and the secret, if you
set one. Saving delivers a test message, so the scenario runs once with
"event": "test" in the body.4
Switch the tool on in the agent
Agent editor → Integrations → Make scenario. Pick the connection
and fill in When to use it, and what to say and Phrases that should
trigger it. Without those fields the agent has the tool but no idea
what it is for - and usually leaves it alone. Details in Slack, email,
Zapier and the calendar during the
call.
The Make integration is available from the Start plan, like Zapier, n8n
and the webhooks. Make’s Webhooks module is available on its free plan too.
What reaches the scenario
The agent sends aPOST with JSON. It chooses event and data itself,
following what you wrote in When to use it, and what to say; the other
two fields are added by us, so the agent cannot invent them.
In Make the fields are
{{1.event}}, {{1.data}}, {{1.caller_phone}}.
With the X-Brosbots-Secret header when the connection has a secret.
What the scenario can answer
The Webhook response module: Status200, under Custom headers
add Content-Type: application/json, and in Body one sentence the agent
should pass on:
The agent waits for the answer for up to 15 seconds. The call is live, so
if the scenario does something slow, put Webhook response early in the chain
and the heavy modules after it. Make runs them after the response is sent.
A
4xx/5xx code is a tool error: the agent gets “Make failed (code)” and
tells the caller it could not check. Make also returns 400 when the filter
rejects a request without the secret.
Post-call events in Make
That is a separate integration, Post-call webhook in the catalogue, and a separate scenario: a Custom webhook module whose address you paste into the webhook wizard.call.completed arrives with the transcript, summary and
outcome, and on request SMS, campaign and balance.low events too; the
format and the list of events are in Webhooks.
Troubleshooting
Every run shows up in Make under History, with the body the agent sent.