Actions21
Overview
This node integrates with the RetellAI API to manage phone number data. Specifically, the "Phone Number" resource with the "Get Many" operation allows users to retrieve multiple phone numbers from their RetellAI account. It supports filtering by area code and agent IDs, and can return either all matching results or a limited subset.
Common scenarios include:
- Fetching a list of phone numbers assigned to specific inbound or outbound agents.
- Retrieving phone numbers filtered by geographic area codes for reporting or management.
- Bulk exporting phone number data for synchronization with other systems.
Example: A user wants to get up to 50 phone numbers associated with a particular outbound agent to audit call routing configurations.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching phone numbers or only up to a specified limit. |
| Limit | Maximum number of phone numbers to return if not returning all (minimum 1). |
| Filters | Collection of filters to narrow down results: |
| - Area Code | Filter phone numbers by their area code (numeric). |
| - Inbound Agent ID | Filter phone numbers assigned to a specific inbound agent (string identifier). |
| - Outbound Agent ID | Filter phone numbers assigned to a specific outbound agent (string identifier). |
Output
The node outputs an array of JSON objects representing phone numbers that match the query criteria. Each object contains details about a phone number as returned by the RetellAI API. The exact structure depends on the API response but typically includes fields such as the phone number itself, associated agent IDs, area code, and possibly status or configuration metadata.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the RetellAI API.
- The node uses the base URL
https://api.retellai.comfor requests. - Proper configuration of the API authentication token in n8n credentials is necessary.
Troubleshooting
- Authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions.
- Empty results: Check filter values; incorrect agent IDs or area codes may yield no matches.
- Limit vs Return All: If
Return Allis false but the limit is set too low, you might miss some data. Increase the limit or enableReturn All. - API rate limits: Excessive requests may be throttled by the RetellAI API; consider adding delays or handling retries.
- Error messages from API: These will be surfaced in the node's output if
Continue On Failis enabled; otherwise, they will stop execution.
Links and References
- RetellAI API Documentation (for detailed API endpoints and data structures)
- n8n documentation on creating custom nodes