HTTP tools with Make, n8n and Zapier
If your software has no API, or only OAuth2, you can put one of these services in between. The HTTP tool calls a webhook of the service, the service talks to your software and answers the agent. This page explains what each one returns and what Atendia does with it.
Make: tested on a real call on 2026-11-02, with an HTTP tool. n8n: tested on a real call on 2026-11-02, with an HTTP tool and the end-of-call webhook, without a signature; the verification code was tested outside n8n. Zapier: according to the documentation of 2026-10-30. We have not tested it.
Atendia's templates
- When the Builder prepares a lookup tool or the post-call webhook for Make or n8n, the card comes with a ready-made template. The card recognises Make by the
x-make-apikeyheader or ahook.….make.comaddress, and n8n by thex-n8n-keyheader or a….n8n.cloudaddress. - Make: press «Open template in Make». The scenario opens in a new tab and already has the right reply for the agent.
- n8n: press «Copy workflow for n8n». In n8n, open a new workflow and paste (Ctrl+V; on Mac, Cmd+V). If a window opens, click «Skip». Then follow the workflow's «Como usar» note.
- The n8n key: press «Copy key for n8n». The console makes a key, puts it in the card, in the
x-n8n-keyheader, and copies it. In n8n, in the «Webhook» node, create the credential with «Name»x-n8n-keyand paste the key in «Value». You can also write your own. - In n8n, click «Publish», then «Publish» again in the window. Then copy the «Production URL» and paste it in the card, in «Destination address».
- For the post-call webhook, before you press «Send example and turn on»: in Make, the webhook must show «Listening for data»; in n8n, the workflow must be published. Without that, the example does not arrive.
Timeout
- The agent waits for the answer during the conversation. People on the phone do not wait long: set the tool timeout to a few seconds (for example, 10) at most.
- The tool timeout has to be below the platform one. If the platform takes longer than the tool, Atendia gives up first and the agent says the confirmation is pending.
- Do the slow work after answering, or in another flow. Answer the agent only with what it needs.
- A tool that writes (POST, PUT, PATCH, DELETE) and gets no answer in time leaves the result unconfirmed. The agent does not repeat it on its own.
Make
- Create a scenario that starts with «Custom webhook» and copy the address into the tool. In «Advanced settings», turn on «Get request headers» if you want to read the headers.
- End the scenario with the «Webhook Response» module. You set the status (200), the body and the header
Content-Type: application/json. What you put in the body is what the agent receives. - Make waits up to 180 seconds for the answer. After that, it returns
200 Acceptedwithout your data. This is why the tool timeout has to be well below it. - If the scenario fails, return an error status (for example 500) in the «Webhook Response». Atendia turns the code into a fixed sentence for the agent.
- Make only returns the data when the scenario is on and set to «Immediately as data arrives». When it is off, or scheduled at intervals (for example «Every 15 minutes»), it answers
200with the text «Accepted» straight away, queues the request and does not run the scenario. A scenario that is off leaves no history: with no runs to look at, turn it on first. Choose the response fields in the tool, so that this «Accepted» counts as a failure, in the tool test too. 410: the webhook address no longer has a scenario (more than 5 days went by without one). Create the scenario again and write the new address in the tool.400«Queue is full.»: the webhook queue is full because the scenario is not processing the requests. Set the scenario to «Immediately» or wait for the queue to empty.429: too many requests; wait and try again.
n8n
- Create a workflow with the «Webhook» node, with the same method as the tool, and copy the production address into the tool. Publish the workflow («Publish»): otherwise the tool gets a 404 error.
- In the «Webhook» node, set «Respond» to «Using 'Respond to Webhook' Node». End the workflow with the «Respond to Webhook» node, with «Respond With» set to «JSON» or «First Incoming Item». What it answers is what the agent receives.
- To verify the signature, turn on the «Raw Body» option of the «Webhook» node (the exact body) and put a Code node after it with the example below. Check in the output panel where n8n stores the body: the example reads it from the binary field
data. - The Code node needs
crypto: n8n only lets it be used if the variableNODE_FUNCTION_ALLOW_BUILTIN=cryptois set (with task runners, set it on the runners). Store thewhsec_secret in an n8n environment variable and read it as in the example; if your installation blocks variable access in the Code node, store it in another way it allows.
The logic is that of the «Node, by hand» example on the HTTP tools page. Replace YOUR_TOOL_ID with your tool id:
// Code node, "Run Once for All Items".
// The Webhook node needs the option "Raw Body" (the exact body is then in the binary field "data").
// n8n must allow crypto in the Code node: NODE_FUNCTION_ALLOW_BUILTIN=crypto.
const { createHmac, timingSafeEqual } = require("crypto");
function verifyAtendia(secret, rawBody, headers, idPrefix) {
const id = headers["webhook-id"];
const timestamp = headers["webhook-timestamp"];
const signatures = headers["webhook-signature"];
if (!id || !timestamp || !signatures) return false;
// 5 minutes either way. "!(x <= 300)" also refuses a timestamp that is not a number.
if (!(Math.abs(Date.now() / 1000 - Number(timestamp)) <= 300)) return false;
// Tool: "atd_tool_<your tool id>_". Post-call webhook: "atd_postcall_<your agent id>_".
if (!id.startsWith(idPrefix)) return false;
const key = Buffer.from(secret.slice("whsec_".length), "base64");
const expected = createHmac("sha256", key).update(`${id}.${timestamp}.${rawBody}`).digest();
// During a rotation there are two entries; one match is enough.
return signatures.split(" ").some((entry) => {
const [version, value] = entry.split(",");
if (version !== "v1" || !value) return false;
const received = Buffer.from(value, "base64");
return received.length === expected.length && timingSafeEqual(received, expected);
});
}
const rawBody = (await this.helpers.getBinaryDataBuffer(0, "data")).toString("utf8");
const headers = $input.first().json.headers;
const ok = verifyAtendia($env.ATENDIA_SIGNING_SECRET, rawBody, headers, "atd_tool_YOUR_TOOL_ID_");
if (!ok) throw new Error("Invalid Atendia signature");
return [{ json: rawBody ? JSON.parse(rawBody) : {} }]; // a GET has no body
Zapier
- «Webhooks by Zapier» (Catch Hook) answers as soon as it receives the request, before the Zap runs. The answer does not carry the result of the Zap.
- So Zapier is only for sending data (for example the post-call webhook). Do not use it in a tool where the agent needs an answer with data.
- In a writing tool, the Zapier 200 means «received», not «done». The agent may tell the customer it is done when it is not.
Verifying the signature
- n8n verifies the signature in a Code node, with the example above.
- Make and Zapier have no HMAC verification of their own. The honest alternative is a fixed, secret header: in the tool, add a header (for example
X-Atendia-Key) of type «Secret» with a long random value, and in the scenario or the Zap refuse requests where the header does not match. - A fixed header is weaker than the signature: it proves the caller knows the value, it does not tie the request to the body or the time. Change it if you think it was exposed.
- The signature is still sent with the requests if the organization has a secret. You can ignore it in these services.
- In Make, a filter that stops the scenario is not an error: a request with the wrong key gets
200and the text «Accepted», and the run counts towards the account's credits. The data stays protected. Choose the response fields in the tool: without them, the agent reads «Accepted» as a result; with them, that200counts as a failure, in the tool test too. - Make offers its own key when you create the webhook: in «API Key authentication» › «Add API key» › «Create a keychain», make up a key in «API key value». In the tool, add the header
x-make-apikeyof type «Secret» with the same key. It replaces the fixed header with a filter.
For the rest of the tool (data, errors, signing), see the HTTP tools page.