Overview
This node establishes a phone connection between an agent and a customer using the IVRAPI service, which is specialized for Polish phone numbers. It enables automated call bridging by dialing two parties in a specified order and connecting them once both have answered. This is useful in scenarios such as customer support callbacks, sales calls, or any situation where an agent needs to be connected to a customer via phone without manual dialing.
Practical examples:
- A call center automatically connects an available agent to a customer who requested a callback.
- Sales teams initiate outbound calls where the system first calls the agent, then the customer, or vice versa.
- Automated telephony workflows that require controlled call sequencing and caller ID management.
Properties
| Name | Meaning |
|---|---|
| Target Number (Customer) | Polish 9-digit phone number of the customer to be called. Numbers cannot start with 30, 40, 70, or 80. Service only available in Poland. |
| Agent Number | Polish 9-digit phone number of the agent to be called. Numbers cannot start with 30, 40, 70, or 80. Service only available in Poland. |
| Call Order | The order in which calls are placed: either "Agent first → then Customer" or "Customer first → then Agent". |
| Outbound Caller ID / Virtual Number (for Customer) | The caller ID number shown to the customer when receiving the call. Must be a valid Polish 9-digit virtual number not starting with 30, 40, 70, or 80. Can be selected from a list or specified via expression. |
| Outbound Caller ID / Virtual Number (for Agent) | The caller ID number shown to the agent when receiving the call. Must be a valid Polish 9-digit virtual number not starting with 30, 40, 70, or 80. Can be selected from a list or specified via expression. |
| Max Connection Retries | Number of times to retry connecting if the call fails, between 0 and 10 inclusive. Default is 1. |
Output
The node outputs JSON data containing the response from the IVRAPI service after attempting to create the connection. The structure reflects the API's response and typically includes details about the created call connection, such as identifiers, status, and metadata.
If the call connection is successful, the output JSON confirms the connection setup. If there is an error, the node throws an error instead of returning output.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for the IVRAPI service to authenticate HTTP requests.
- The node makes HTTP POST requests to
https://api.ivrapi.com/api/connectionsto create call connections. - To load available virtual numbers for caller ID selection, it performs GET requests to
https://api.ivrapi.com/api/vnumbers. - The node expects all phone numbers to be valid Polish 9-digit numbers excluding those starting with 30, 40, 70, or 80.
- Proper n8n credentials configuration with the IVRAPI API key is mandatory.
Troubleshooting
- Invalid Phone Number Format: The node validates that phone numbers are exactly 9 digits and do not start with disallowed prefixes (30, 40, 70, 80). Errors will specify which number is invalid. Ensure numbers meet these criteria.
- Max Connection Retries Out of Range: The retries count must be between 0 and 10. Setting a value outside this range causes an error.
- Missing or Invalid API Key: If the API key credential is missing or invalid, the node will throw an error indicating the absence of the API key.
- Failed to Load Virtual Numbers: When loading virtual numbers for caller ID selection, network issues or invalid credentials can cause failure. The error message will indicate failure to load virtual numbers.
- HTTP Request Failures: Any network or API errors during the connection creation will result in an error with details from the HTTP request.
To resolve errors:
- Verify phone numbers conform to format rules.
- Check that the API key credential is correctly set up and valid.
- Ensure network connectivity to the IVRAPI endpoints.
- Adjust max connection retries within allowed limits.
Links and References
- IVRAPI Call Connect Documentation
- n8n Expressions Documentation (for specifying dynamic values in properties)