Overview
This node, named "AI Calls," is designed to initiate outbound calls by activating an agent through an API. It is useful in scenarios where automated or semi-automated calling is required, such as customer support callbacks, telemarketing campaigns, or appointment reminders. The node allows specifying the phone number to call, the agent who will handle the call, and additional caller information.
For example, a business could use this node to automatically start a call to a customer with a selected agent when a new support ticket is created, passing along the customer's contact details and optionally receiving webhook notifications about call status.
Properties
| Name | Meaning |
|---|---|
| Phone | The phone number to call. |
| Name | The full name of the person being called (optional). |
| The email address of the person being called (optional). | |
| Agent Name or ID | Select an outbound agent from a dynamically loaded list or specify an agent ID directly. This agent will handle the call. |
| Webhook Url(optional) | Optional URL to receive webhook callbacks related to the call's progress or result. |
| Additional Fields | A collection of custom key-value pairs to send as dynamic data alongside the call request. |
Output
The node outputs a JSON object representing the response from the API after initiating the call. This typically includes details about the call initiation status, any identifiers for tracking the call, and possibly error messages if the call could not be started.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential to authenticate requests to the external AI Calls service.
- The base URL for the API is expected to be set in the environment variable
BASE_URL. - The node makes HTTP requests to endpoints under this base URL:
/userAgentsto load available agents./webhookto start the call.
Troubleshooting
Common issues:
- Missing or invalid API key credential will cause authentication failures.
- Incorrect or missing
BASE_URLenvironment variable will prevent API communication. - Providing an invalid phone number or agent ID may result in API errors.
- If the webhook URL is incorrect or unreachable, webhook callbacks may fail silently.
Error messages:
- Authentication errors usually indicate problems with the API key; verify the credential setup.
- HTTP 4xx or 5xx responses from the API suggest issues with input parameters or server-side problems; check the phone number format, agent selection, and network connectivity.
- Timeout or network errors imply connectivity issues between n8n and the external API endpoint.
Links and References
- n8n Expressions Documentation — for using expressions in property fields like Agent ID.
- Refer to your AI Calls service API documentation for detailed information on request and response formats, webhook handling, and agent management.