For the complete documentation index, see llms.txt. This page is also available as Markdown.

Queue distributor

Overview

The Queue Distribution Component is an action node focused on the distribution, consumption, and ordered processing of records. Its main function is to perform the search and selection of a data item (such as users and departments). By extracting this record from the queue, the component consumes the item and injects all of its information and variables directly into the current execution scope of the automation flow.

Configuration Parameters

The component's configuration connects the node to the platform's global data structure through the following criterion:

  • _Queue ( Required Field):_* Dropdown used to choose which data queue will be consumed by this automation block. The component does not create or store record lists locally; it performs a real-time query and inherits the record queues previously structured in the workspace settings of the platform.

Visual Builder

The builder has a streamlined design focused on inheritance and secure coupling of structured data:

  • Synchronization with the Workspace: The selector displays only the registered and active queues in the user's workspace. Any new record added to the workspace queue becomes eligible to be captured by this node automatically.

  • Return Mapping (Output Data): In the flow architecture, executing this component changes the state of the available variables. It creates an output data object containing all the custom properties of the item that was selected in the queue so that the next nodes can read this information (e.g., phone number, contact name, or task data).

Special Operators

The logical properties of this component handle concurrency control, ordering, and batch data integrity:

  • FIFO (First In, First Out) Consumption Logic or Priority: When executed, the component engine accesses the selected queue and consumes the next available item according to the order of arrival or priority rules configured in the workspace, ensuring that no record is processed twice by concurrent instances of the automation.

Practical Examples

The table below shows classic application scenarios for this component to manage automated data distribution:

Selected Queue (Workspace)

Immediate Action of the Component

Next Connected Node

Practical Use Case

Agents

Captures the next agent in the queue

Service Transfer Component

Sends the service to a specific agent.

Departments

Captures the next department in the queue

Hablla Component (Create or update card)

Sends the service to a department according to the queue's distribution rule.

Last updated

Was this helpful?