Make a phone call from Zapier or Make
Zapier and Make can move data between apps, but they cannot phone a business. With HumanCalls, one HTTP step sends a call request and a real person makes the call. A later step fetches the typed answers.
How a call fits into a Zap or scenario
HumanCalls has a plain REST API, so you do not need a dedicated app. Any step that can send an HTTP request with headers and a JSON body will work. In Zapier that is usually the Webhooks step with a custom request. In Make it is the HTTP module's request action.
- A trigger fires, such as a new spreadsheet row or form entry.
- An HTTP step sends
POST /v1/callswith the business, number and goal. HumanCalls saves the task and returns itsid. - A delay step waits while a person at HumanCalls makes the call.
- A second HTTP step sends
GET /v1/calls/:idand reads the status. - Once the status is final, later steps use the answers.
Calls are placed during the business's local hours, so a result can take anywhere from minutes to the next time the business is open. Plan your delays with that in mind.
Start the call with an HTTP POST
Get an API key first, either from your dashboard or with POST /v1/signup. The key is shown once, so store it in your tool's secure connection or credential field. The workspace owner must verify their email before calls can be created. Then set up the request:
- Method
POST, URLhttps://humancalls.ai/v1/calls. - Header
Authorization: Bearer <your api_key>. - Header
Content-Type: application/json. - Header
Idempotency-Keyset to something unique to this task, such as the trigger's record ID. If the step retries with the same key and body, you get the same task back with a 200, not a second call.
{
"to": "+12125550100",
"business": "Harbor Supply Co.",
"on_behalf_of": "Lakeside Hardware",
"goal": "Confirm stock and earliest delivery for SKU 7712",
"max_minutes": 10,
"collect": {
"in_stock": { "type": "boolean", "required": true },
"delivery_date": { "type": "date", "description": "Earliest delivery date" }
},
"metadata": { "source_row": "row-118" },
"delivery": { "mode": "polling" }
}Keep delivery set to polling. New keys must say how results are delivered, and polling is the simplest choice for a no-code workflow. The collect fields become typed answers you can map later. Field names are lower_snake_case, with types string, number, boolean or date. All inputs are listed in the API docs.
Wait, then check the call
A 202 response means the task was created. Save its id. Add a delay step, then an HTTP GET to https://humancalls.ai/v1/calls/<id> with the same Authorization header. Read the status field.
| Status | What to do |
|---|---|
| queued, assigned, dialing, in_progress | Not finished. Wait and check again. |
| completed | Read the answers and continue. |
| failed, no_answer, declined, canceled | Final. Route to a fallback branch. |
Zapier and Make handle repeats differently, so keep the logic simple. One pattern is a single long delay followed by one check. Another is a separate scheduled workflow that looks up open call IDs and checks each one. Before the first dial, check intake_status too. A task marked review_required waits before dialing, and a prohibited request is declined without charge.
Use the answers in later steps
A completed call returns outcome with one typed value per collect field, or null when an optional answer was not available. You also get outcome_notes, a summary, billed_minutes, cost_usd and your metadata, so you can match the result to the row that started it.
recording_url and transcript_url can appear a little after the call completes. If you need them, check again later until they are present. Fetching those URLs also needs your bearer key.
Limits and costs to plan for
- Each call costs $1 per connected minute, rounded up. Unanswered, declined and canceled calls cost $0. A new workspace gets 10 free minutes. See pricing.
- A 402
insufficient_creditsmeans no call was queued. Lowermax_minutesor have the owner add credit. Your workflow cannot buy credit. - A 403 means the owner has not verified the account yet.
- A 429 means you hit a creation limit: ten new tasks a minute, and three open tasks per phone number. Wait for the time in
Retry-After. - You can cancel with
POST /v1/calls/:id/cancelwhile the task is queued or assigned.
Write the goal as an information request. Callers do not buy, book or agree to anything you did not authorize. Read how our callers work.
Questions
- Can I use a webhook instead of polling?
- Yes, but webhook delivery needs a verified receiver that answers a signed challenge. A plain catch hook that returns 200 does not pass. For most Zaps and scenarios, polling with a delay is simpler.
- What if my Zap or scenario runs twice?
- Send the same Idempotency-Key and body. HumanCalls returns the existing task instead of placing a second call. Reusing a key with a different body returns 409.
- Is the caller an AI voice?
- No. A real, trained person makes every call. They say who they are and who they are calling for, and tell the business the call is recorded.
- Which numbers can a workflow call?
- Businesses in the United States and Canada. Sales, debt collection, political calls and cold calls to consumers are not accepted.
Related
- Add a phone call step to an n8n workflowUse HumanCalls from n8n: one HTTP Request node asks a real person to phone a business, and a second reads back typed answers your workflow can branch on.
- A phone call API with a human callerCreate phone calls by REST: POST /v1/calls with typed collect fields, and a real person calls the US or Canadian business. Poll or use a signed webhook.
- Call a supplier to check order statusHave a real person phone a supplier about an order or delivery and bring back the status, the expected date and the name of who they spoke to.
Try it with 10 free minutes
$1 per connected minute after that, and nothing when nobody picks up.