Beex icon

Beex

Beex Contact Center API Interaction and Consumption

Queue → Create One

AI-generated

Overview

This node interacts with the Beex Contact Center API to create a new queue on the platform. It is useful in scenarios where you need to programmatically set up queues for managing customer service or support tickets, specifying details such as queue name, customer channels, users, waiting thresholds, service levels, distribution types, maximum tickets per agent, and associated portfolios.

Use Case Examples

  1. Creating a new customer support queue with specific agents and channels.
  2. Setting up a queue with defined service levels and ticket distribution rules for a campaign.

Properties

Name Meaning
Name The name of the queue to be created.
Customer Channels Comma-separated list of customer channel IDs associated with the queue, without spaces.
Users Comma-separated list of user IDs assigned to the queue, without spaces.
Waiting Threshold Numeric value defining the waiting threshold for the queue.
Service Level Numeric value indicating the selected service level for the queue.
Distribution Type Numeric value representing the distribution type for the queue.
Maximum Tickets Per Agent Numeric value specifying the maximum number of tickets an agent can handle in the queue.
Portfolios Comma-separated list of portfolio IDs associated with the queue, without spaces.

Output

JSON

  • json - The JSON response from the Beex API representing the created queue details.

Dependencies

  • Beex Contact Center API with an API key credential

Troubleshooting

  • Common issues include invalid or missing parameters, which result in error messages from the API. Ensure all required fields are correctly filled and formatted, especially comma-separated lists without spaces.
  • API authentication errors may occur if the API key credential is missing or invalid. Verify the API key is correctly configured in the node credentials.
  • Rate limiting or request throttling might happen due to the 1-second delay between requests; adjust usage accordingly.

Discussion