Get Queue Agent
Get Queue Agent is one of the Internal Data Ops operations. Point it at a queue, choose which agent statuses you care about, and it returns the matching agents as a list you can use later in the flow.
What it does
Section titled “What it does”The component looks inside a single queue and hands back every agent whose status matches the one(s) you asked for. You can name the queue outright or build an expression so the target is decided while the call is running. Whatever comes back is written to variables, ready to be passed into a following component or evaluated in a Condition.
Configure the component
Section titled “Configure the component”-
Drag the Internal Data Ops component onto the canvas, then click it to open its settings.

-
In the Component Type drop-down list, choose Get Queue Agent.

-
Point the component at a queue using one of these methods:

-
Queue: pick a queue from the drop-down list.
-
Expression: click the fx icon and enter an expression to resolve the queue at runtime.

For example,
$UserInput1.userInputuses the queue number the caller keyed in.
-
-
In the Agent Status drop-down list, select one or more statuses to filter the agents by.

-
Click Confirm in the bottom-right corner.
Variables
Section titled “Variables”Adding a Get Queue Agent component writes the matching agents into the variables below. Read them from any expression-aware component, Condition, for instance, to branch on what the lookup returned.
| Variable | Type | Description | Example |
|---|---|---|---|
$GetQueueAgent{index}.agentList | Object | The matching agents in the queue, each returned as its extension number paired with its current status. | "1001,Log Out;1003,Log Out;1004,Log Out" |
$GetQueueAgent{index}.agentNumberList | Object | The matching agents in the queue, returned as extension numbers only. | "1001,1003,1004" |
What it can connect to
Section titled “What it can connect to”A Get Queue Agent component leads to exactly one downstream component. Any of the following can follow it:
| Component | Purpose |
|---|---|
| Prompt | Play an audio file or a text-to-speech message to the caller. |
| Business Hours | Route the call to different destinations depending on the time of day. |
| Menu | Offer callers a set of options and route them by the DTMF (Dual-Tone Multi-Frequency, the touch-tone signal a phone keypad sends) key they press. |
| User Input | Collect DTMF digits from the caller, usually paired with Condition to act on what was entered. |
| Language | Change the system prompt language for the rest of the flow. |
| Record | Start recording once the caller connects to another party, with optional notification prompts, or turn recording off for a call that would otherwise be recorded. |
| Dial by Number | Let callers dial a number directly to reach their destination. |
| Dial by Name | An end component that lets callers reach a user by typing the first three letters of their name. |
| Transfer | An end component that sends the caller to a chosen destination, with optional prompts announcing the transfer. |
| Hang Up Call | An end component that disconnects the call. |
| Condition | Route the call based on logical expressions. |
| Loop | Repeat a group of components a set number of times or until a condition is met. |
| Internal Data Ops | Read from and write to the Cloud Voice system’s own database. See Get Extension Presence Status, Set Extension Presence Status, Get Queue Agent, Get Queue Info, Get Agent Status, Set Agent Status, Get System Info, Get System Capacity, Get Extension Info, and Get Company Contact Info. |
| Email Sender | Send an email for real-time notifications, alerts, or user-specific information. |
| Database Access | Run a SQL (Structured Query Language) operation against an external database during the call flow. |
| HTTP Request | Send an HTTP (Hypertext Transfer Protocol) request to an external server to exchange data with a third-party service. |