Actions9
Overview
This node integrates with the Beex Contact Center API to retrieve data about sequences. The "Obtener" (Get) operation for the "Sequence" resource fetches multiple sequence records from the API, supporting pagination through limit and offset parameters.
Typical use cases include:
- Retrieving a list of sequences for reporting or analysis.
- Fetching sequences in batches to process or synchronize with other systems.
- Automating workflows that depend on sequence data from the Beex platform.
For example, a user might want to get the first 10 sequences or all sequences available, depending on their needs.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all results or only up to a given limit. Options: true or false. |
| Limit | Number of sequence records to return when not returning all. Example: "10". |
| Offset | Number of sequence records to skip before starting to return results. Example: "0". |
Output
The node outputs JSON data containing the retrieved sequences from the Beex API. The structure corresponds directly to the API response for the /sequences endpoint, typically an array of sequence objects with their details.
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. - The node uses HTTP GET requests to the
/sequencesendpoint with query parameters for pagination (limitandoffset).
Troubleshooting
- Empty Results: If no sequences are returned, verify that the Beex account has sequences created and that pagination parameters are correct.
- Authentication Errors: Ensure the API key credential is correctly configured and valid.
- Invalid Parameter Values: Passing non-numeric or negative values for
limitoroffsetmay cause errors; use positive integers as strings. - API Rate Limits: Excessive requests may be throttled by the API; consider using the
Return Alloption carefully.
Links and References
- Beex Contact Center API Documentation (assumed URL based on baseURL)
- n8n documentation on HTTP Request Node for understanding API integrations