# How do I connect EnableCalls to n8n, Make or Zapier?

Every automation tool can call the API with an HTTP step and receive results with a webhook trigger. No code needed.

## How do I place a call from an automation?

1. Create a full-access key on **Developers** and store it in the tool's credentials (n8n Header Auth, Make keychain, Zapier secret), not in the step text.
2. Add an HTTP request step: method POST, URL `https://api.enablecalls.com/v1/calls`, header `Authorization: Bearer <your key>`, body type JSON.
3. Map the body: `employee_id`, `phone` from your trigger, `name`, and any `details` the employee's script uses.
4. Add the header `Idempotency-Key` with the trigger's own id, so a retried step never calls twice.

| Tool | Good Idempotency-Key |
| --- | --- |
| n8n | `{{ $execution.id }}-{{ $itemIndex }}` |
| Make | The trigger bundle's id, e.g. `{{1.id}}` |
| Zapier | The id field from your trigger (form submission or row id) |
| Pabbly Connect | The trigger's unique id field |

## How do I receive results in the same tool?

1. Add a webhook trigger in your tool and copy its URL.
2. Create an endpoint with that URL: in the dashboard under Integrations, or with `POST /webhook-endpoints`, subscribed to `call.completed` and `call.not_connected`.
3. Use `data.call.external_id` (or `data.lead_id`) to update the right row in your CRM or sheet.

> Only need leads to be called, without results back? A lead source's private link in Instant leads needs no key at all: any form or tool can post to it.

## How do I avoid hitting limits in a loop?

When looping over many rows, send them as one campaign (`POST /campaigns` with up to 1,000 contacts) instead of one call each, or add a short wait between batches. Writes are limited to 60 a minute per key.

## More EnableCalls API docs

- [Overview](https://enablecalls.com/developers.md): Place AI phone calls, run calling campaigns and get every conversation's outcome, summary and transcript from your CRM, website, n8n, Make or Zapier.
- [Authentication](https://enablecalls.com/developers/authentication.md): Create EnableCalls API keys on the Developers page, choose full or read-only access, and send them as a Bearer token. Keys are shown once and can be revoked at once.
- [Calls and retries](https://enablecalls.com/developers/calls.md): How EnableCalls API calls move from queued to completed: calling hours, do-not-call, coins, the 30-minute cooldown, automatic retries for unanswered calls and every status.
- [Webhooks and events](https://enablecalls.com/developers/webhooks.md): Receive call.completed, call.not_connected, lead and appointment events on your URL, verify the HMAC-SHA256 signature, and understand retries and the event log.
- [Errors and limits](https://enablecalls.com/developers/errors.md): The EnableCalls API error format, rate limits per key, Idempotency-Key for safe retries, dry runs and starting_after pagination.
- [API reference](https://enablecalls.com/developers/reference.md): Every EnableCalls API endpoint: calls, leads, campaigns, contacts, appointments, do-not-call, webhooks, events, employees and phone numbers, with parameters and fields.

Canonical page: https://enablecalls.com/developers/no-code
