IVRAPI Call Connect (BETA) icon

IVRAPI Call Connect (BETA)

Establish a phone connection between an agent and a customer via IVRAPI

IVRAPI Call Connect (BETA)

AI-generated

Overview

This node establishes a phone connection between an agent and a customer using the IVRAPI service, specifically designed for Polish phone numbers. It enables automated call bridging where the system calls one participant first and then connects to the other, facilitating scenarios such as customer support callbacks, sales calls, or any situation requiring a controlled two-party phone connection.

Typical use cases include:

  • A call center automatically connecting an available agent to a waiting customer.
  • Automated outbound calls where the order of calling agent and customer can be configured.
  • Ensuring calls originate from specific virtual numbers (caller IDs) compliant with Polish telephony regulations.

Properties

Name Meaning
Target Number (Customer) The 9-digit Polish phone number of the customer to be called. Numbers cannot start with 30, 40, 70, or 80.
Agent Number The 9-digit Polish phone number of the agent to be called. Numbers cannot start with 30, 40, 70, or 80.
Call Order Defines which party is called first: either "Agent first → then Customer" or "Customer first → then Agent".
Outbound Caller ID / Virtual Number (for Customer) The 9-digit Polish caller ID number shown to the customer when receiving the call. Must not start with 30, 40, 70, or 80. Can be selected from a list or specified via expression.
Outbound Caller ID / Virtual Number (for Agent) The 9-digit Polish caller ID number shown to the agent when receiving the call. Must not start with 30, 40, 70, or 80. Can be selected from a list or specified via expression.
Max Connection Retries Number of times the system will retry connecting the call if it fails, ranging from 0 to 10.

Output

The node outputs JSON data containing the response from the IVRAPI service after attempting to establish the call connection. This typically includes details about the created connection such as connection status, identifiers, and any relevant metadata returned by the API.

No binary data output is produced by this node.

Example output structure (simplified):

{
  "connectionId": "string",
  "status": "string",
  "details": { /* additional info from IVRAPI */ }
}

Dependencies

  • Requires an API key credential for the IVRAPI service to authenticate requests.
  • The node makes HTTP POST requests to https://api.ivrapi.com/api/connections to create call connections.
  • To populate the caller ID options, it fetches virtual numbers from https://api.ivrapi.com/api/vnumbers.
  • The service and all phone numbers must comply with Polish telephony rules (9-digit numbers, restricted prefixes).

Troubleshooting

  • Invalid Phone Number Format: If any phone number is not exactly 9 digits or starts with forbidden prefixes (30, 40, 70, 80), the node throws an error specifying which number is invalid. Ensure numbers meet these criteria.
  • Max Connection Retries Out of Range: Setting retries below 0 or above 10 results in an error. Use values within the allowed range.
  • Missing or Invalid API Key: If the API key credential is missing or invalid, the node will fail to load virtual numbers or create connections. Verify that the API key is correctly configured.
  • No Virtual Numbers Available: If no virtual numbers are registered for the account, loading caller ID options will fail. Add virtual numbers in the IVRAPI account before using the node.
  • HTTP Request Failures: Network issues or API errors during requests to IVRAPI endpoints will cause the node to throw errors with messages indicating failure reasons. Check network connectivity and API key validity.

Links and References

Discussion