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 users to interact with the PortaOne Call Control API, specifically to perform actions such as unholding a call. This is useful in telephony automation scenarios where you need to programmatically manage call states—such as resuming a call that was previously put on hold.
Common use cases:
- Automating customer support workflows by unholding calls based on business logic.
- Integrating with CRM or helpdesk systems to control call flow.
- Building custom dashboards or triggers for call management.
Example:
A support agent puts a customer on hold while checking information. Once ready, an automated workflow can use this node to unhold the call and resume the conversation.
Properties
| Name | Meaning |
|---|---|
| Authentication | The authentication method to use. Options: Token Authentication, Basic Authentication. |
| Call → Id | The unique identifier of the call to be unheld. |
| Call → Tag | An optional tag associated with the call. |
Output
The node outputs a json field containing the result of the "Unhold Call" operation from the PortaOne Call Control API. The exact structure depends on the API response, but typically includes status information about the call after the unhold action.
Note: If the API returns binary data (unlikely for this operation), it would be included as a binary output, representing the raw response.
Dependencies
- External Services: Requires access to the PortaOne Call Control API.
- API Credentials:
- For Token Authentication: portaOneCallControlTokenApi credentials.
- For Basic Authentication: portaOneCallControlBasicApi credentials.
- n8n Configuration: Ensure the appropriate credentials are set up in n8n under the node's credential options.
Troubleshooting
Common Issues:
- Invalid Credentials: If authentication fails, ensure the correct credentials are selected and valid.
- Missing Call ID: The "Id" property is required; omitting it will likely cause the API to reject the request.
- API Connectivity: Network issues or incorrect API endpoints may prevent successful execution.
Error Messages:
- "Authentication failed" – Check your credentials and authentication method.
- "Call not found" – Verify the provided Call Id is correct and active.
- "Missing required parameter: id" – Ensure the Call Id is specified in the input properties.