Actions23
- Call Control Actions
- Answer Call
- Convert To On Spot Conference
- Delete On Spot Conference Participant
- Disable Api Notifications
- Enable Api Notifications
- Get On Spot Conference List
- Get On Spot Conference Participant List
- Get Sip Calls List
- Hold Call
- Join Calls
- Join On Spot Conference
- Join To Active Call
- Originate Advanced Call
- Play Prompt
- Progress Call
- Ring Call
- Start DTMF Detect
- Stop DTMF Detect
- Stop Play Prompt
- Terminate Call
- Transfer Call
- Unhold Call
- Update On Spot Conference Participant
Overview
The PortaOneCallControl node for n8n allows you to interact with the PortaOne Call Control API, specifically enabling you to perform the "Join Calls" operation. This operation is useful in scenarios where you need to merge or join two separate calls programmatically, such as in call center applications, conferencing solutions, or automated telephony workflows.
Practical examples:
- Automatically merging an incoming support call with a supervisor's line.
- Creating conference bridges by joining multiple ongoing calls.
- Automating escalation processes by joining a customer call with a specialist.
Properties
| Name | Meaning |
|---|---|
| Authentication | The authentication method to use. Options: Token Authentication, Basic Authentication. |
| Call | Details of the first call to be joined. Includes: Id (string), Tag (string). |
| To Call | Details of the second call to be joined. Includes: Id (string), Tag (string). |
Output
The output will be a JSON object containing the result of the "Join Calls" operation from the PortaOne Call Control API. The exact structure depends on the API response, but typically includes information about the joined calls, their status, and any relevant identifiers.
If binary data is returned (unlikely for this operation), it would represent call-related media or logs.
Dependencies
- External Services: Requires access to the PortaOne Call Control API.
- API Credentials:
- For Token Authentication:
portaOneCallControlTokenApicredentials must be configured in n8n. - For Basic Authentication:
portaOneCallControlBasicApicredentials must be configured in n8n.
- For Token Authentication:
- n8n Configuration: Ensure the correct authentication method is selected and corresponding credentials are set up.
Troubleshooting
Common Issues:
- Invalid Credentials: If the provided API credentials are incorrect or missing, authentication will fail.
- Missing Required Fields: Both "Call" and "To Call" collections require valid Ids; missing these may cause errors.
- API Connectivity: Network issues or incorrect API endpoints can prevent successful operation.
Error Messages and Resolutions:
- "Authentication failed" – Check that the correct authentication method and credentials are used.
- "Missing required parameter: id" – Ensure both "Call" and "To Call" have valid Id fields filled.
- "API request failed" – Verify network connectivity and API endpoint configuration.