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, the Get On Spot Conference List operation retrieves a list of on-the-spot conferences based on provided filtering criteria. This node is useful in scenarios where you need to automate the retrieval and processing of conference data from your PortaOne system, such as reporting, monitoring, or integrating conference information into other workflows.
Practical examples:
- Automatically fetching all active conferences for a given customer.
- Integrating conference lists into dashboards or notification systems.
- Filtering conferences by owner or name for audit or management purposes.
Properties
| Name | Meaning |
|---|---|
| Authentication | The authentication method to use. Options: Token Authentication, Basic Authentication. |
| Conference Info | A collection of filters for the conference list: |
| - I Customer: Numeric ID of the customer. | |
| - Name: Name of the conference. | |
| - Owner Id: Identifier of the conference owner. |
Output
The output will be a JSON array containing the details of the conferences that match the specified filters. Each item in the array represents a conference and includes its relevant properties as returned by the PortaOne API.
Note: The exact structure of each conference object depends on the API response, but typically includes fields like conference ID, name, owner, participants, etc.
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 credentials are incorrect or missing, the node will fail to authenticate. Make sure the right authentication method and credentials are used.
- Missing Required Fields: If required filter fields are not provided, the API may return an error or an empty result.
- API Connectivity: Network issues or incorrect API endpoint configuration can lead to connection errors.
Error Messages:
- "Authentication failed" – Check your credentials and authentication method.
- "Resource not found" – Verify the resource and operation names.
- "Invalid parameter" – Ensure all input fields are correctly filled and formatted.