Beex icon

Beex

Interacción y Consumo de la API Beex Contact Center.

Actions9

Overview

This node interacts with the Beex Contact Center API to retrieve ticket data filtered by creation date. It is designed to fetch multiple tickets within a specified date range, supporting pagination and the option to return all results or limit the number of returned tickets.

Common scenarios where this node is beneficial include:

  • Extracting tickets created within a specific timeframe for reporting or analysis.
  • Integrating ticket data into workflows that require up-to-date ticket information.
  • Automating monitoring or auditing processes based on ticket creation dates.

For example, a user might configure the node to get all tickets created between January 1, 2025, and January 31, 2025, limiting the results to 50 per page, or retrieving all tickets without pagination.

Properties

Name Meaning
Fecha Inicio Start date for filtering tickets based on their creation date. Format: AAAA-MM-DD HH:MM:SS. Required.
Fecha Fin End date for filtering tickets based on their creation date. Format: AAAA-MM-DD HH:MM:SS. Required.
Return All Boolean flag indicating whether to return all matching tickets or only up to a specified limit.
Limit Number of tickets to return per page when not returning all. Range: from 1 up to any number.
Offset Page number to retrieve, starting at 0, ordered descending by creation date.

Output

The node outputs JSON data containing an array of ticket objects retrieved from the Beex API. Each ticket object includes details as provided by the API about individual tickets created within the specified date range.

If binary data were involved (e.g., attachments), it would be summarized here, but this node focuses on JSON ticket data only.

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 for successful requests.

Troubleshooting

  • Invalid Date Format: Ensure that the "Fecha Inicio" and "Fecha Fin" fields use the exact format YYYY-MM-DD HH:MM:SS. Incorrect formats may cause API errors or no results.
  • Empty Results: If no tickets are returned, verify that the date range actually contains tickets and that pagination parameters (Limit and Offset) are set correctly.
  • Authentication Errors: Confirm that the API key credential is valid and has sufficient permissions to access ticket data.
  • Rate Limits or API Errors: If the API returns rate limit errors or other HTTP errors, consider adding delays between requests or checking API status.

Links and References

Discussion