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, the Terminate Call operation enables users to programmatically end an active call by specifying either its unique ID or tag. This is useful in automated workflows where calls need to be managed or terminated based on business logic, such as disconnecting calls after a certain duration, handling fraud detection, or integrating with customer support systems.
Example scenarios:
- Automatically terminate calls that exceed a predefined time limit.
- End calls associated with specific tags (e.g., flagged for review).
- Integrate with CRM or ticketing systems to hang up calls when a case is closed.
Properties
| Name | Meaning |
|---|---|
| Authentication | The authentication method to use. Options: Token Authentication, Basic Authentication. |
| Call → Id | The unique identifier of the call to terminate. |
| Call → Tag | A tag associated with the call to identify which call to terminate. |
Output
The output will contain a json field reflecting the result of the terminate call operation. The structure typically includes:
- Confirmation of termination (success/failure)
- Details about the terminated call (such as id or tag if provided)
- Any error messages or status codes from the API
Note: The exact fields depend on the response from the PortaOne Call Control API.
Dependencies
- External Service: PortaOne Call Control API
- Authentication: Requires either Token Authentication or Basic Authentication credentials configured in n8n.
- n8n Credentials:
portaOneCallControlTokenApi(for token-based auth)portaOneCallControlBasicApi(for basic auth)
Troubleshooting
Common Issues:
- Invalid Credentials: If authentication fails, ensure the correct credentials are set up in n8n and have sufficient permissions.
- Missing Call Identifier: At least one of "Id" or "Tag" must be provided; otherwise, the API may return an error indicating insufficient information to terminate a call.
- API Errors: If the PortaOne API returns errors (e.g., call not found, already terminated), check the input values and the current state of the call.
Error Messages:
- "Authentication failed" – Check your credentials and authentication method.
- "Call not found" – Verify the Id or Tag matches an active call.
- "Insufficient parameters" – Ensure at least one of Id or Tag is provided.