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 to perform actions such as answering a call. This node is useful in automated workflows where you need to programmatically control telephony operations, such as automatically answering incoming calls based on business logic or integrating call handling into broader automation processes.
Practical examples:
- Automatically answer support hotline calls during business hours.
- Integrate with CRM systems to pop up customer information when a call is answered.
- Trigger downstream automations (e.g., logging, notifications) upon answering a call.
Properties
| Name | Meaning |
|---|---|
| Authentication | The authentication method to use. Options: Token Authentication, Basic Authentication. |
| Call | Collection of call-specific parameters: - Id: The unique identifier of the call. - Tag: An optional tag associated with the call. |
| AdditionalFields | Collection of additional options: - Callee Answer Mode: Specifies how the callee should answer the call. |
Output
The node outputs a json field containing the result of the "Answer Call" operation from the PortaOne Call Control API. The exact structure depends on the API response, but typically includes details about the call status after the answer action is performed.
Note: If the node supports binary data output, it would represent call-related media or logs, but this is not indicated in the provided code.
Dependencies
- External Services: Requires access to the PortaOne Call Control API.
- API Credentials:
- For Token Authentication:
portaOneCallControlTokenApicredentials. - For Basic Authentication:
portaOneCallControlBasicApicredentials.
- For Token Authentication:
- n8n Configuration: Ensure the appropriate credentials are set up in n8n under the node's credential options.
Troubleshooting
Common Issues:
- Invalid Credentials: If the provided API credentials are incorrect or missing, authentication will fail.
- Missing Required Fields: Not providing the required call ID may result in errors from the API.
- Network Errors: Connectivity issues between n8n and the PortaOne API endpoint can cause failures.
Error Messages & Resolutions:
- "Authentication failed" – Check that the correct authentication method and valid credentials are used.
- "Missing call ID" – Ensure the "Id" field in the Call collection is populated.
- "API request failed" – Verify network connectivity and API endpoint configuration.