Actions9
Overview
This node interacts with the Beex Contact Center API to retrieve information about queues. Specifically, the "Queue - Obtener" operation fetches details of queues, optionally filtered by a campaign ID (portfolio). It supports pagination and can return either all results or a limited subset.
Common scenarios where this node is useful include:
- Retrieving queue data for reporting or analytics.
- Filtering queues by campaign to monitor specific campaigns' performance.
- Integrating queue information into workflows that automate contact center management.
Example use case: A user wants to get all queues related to a particular campaign to analyze their status or load, so they configure the node with the campaign's portfolio ID and set it to return all results.
Properties
| Name | Meaning |
|---|---|
| ID Portfolio | Campaign ID to filter queues by the campaign they belong to. |
| Return All | Whether to return all results or only up to a given limit. |
| Limit | Page size to retrieve, from 1 up to any number. Only used if "Return All" is false. |
| Offset | Page number to retrieve, descending by creation date starting at 0. |
Output
The node outputs JSON data containing the retrieved queue details from the Beex API. The structure corresponds to the API response for the /queues endpoint, including fields describing each queue's attributes.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Beex Contact Center API.
- The base URL for API requests is
https://api.beexcontact.com/api/v1. - Proper configuration of the API key credential in n8n is necessary.
Troubleshooting
- Empty or no results: Verify that the provided campaign ID (portfolio) is correct and that there are queues associated with it.
- Authentication errors: Ensure the API key credential is valid and has sufficient permissions.
- Pagination issues: If not all expected data is returned, check the "Return All" setting and adjust "Limit" and "Offset" accordingly.
- API rate limits or connectivity problems: Confirm network access to the Beex API and review any rate limiting policies.
Links and References
- Beex Contact Center API Documentation (assumed URL based on baseURL)
- n8n documentation on HTTP Request Node for understanding API calls in workflows