Work Queues
Coordinate structured work across people and agents with queue-defined fields, statuses, assignments, views, history, and resource guardrails.
Work Queues turn a repeatable process into structured items that people and agents can share. A queue defines what every item contains, how it moves, who can work it, and which resource limits apply.
Use this section to:
- Create and configure a queue
- Add, import, filter, assign, and update items
- Open and work an item
- Use saved views, the summary, and analytics
- Control execution with Resource Groups
How Work Queues fit together
Work Queue
properties • statuses • transitions • agents • Resource Group
│
├── Work Queue Item
│ data • status • assignment • action state • snooze
│ notes • transition history • linked runs and resources
│
└── Views and analytics
filters • columns • grouping • saved views • metrics
- A Work Queue is the process definition. It owns the item schema, lifecycle, available agents, and Resource Group.
- A Work Queue Item is one unit of work. Its custom data follows the queue's properties.
- A Status is the business stage, such as
Ready for Review,Review Required, orCompleted. Transitions determine which moves are allowed. - An Assignment identifies the agent, person, or group responsible for the item.
- The Action state describes operational state independently from the
business status. It can be
ready,waiting,running,snoozed,completed,needs_attention,error, orcancelled. - A Resource Group controls whether agent work can run and applies concurrency, per-request, and time-window cost guardrails.
The status and action state answer different questions. Status says where the
item is in your process; action state says what the execution system is doing
with it. For example, an item can remain in Ready for Outreach while its
action state is snoozed.
Open Work Queues
In a project, select Work Queues under Developer.
The list shows each queue's name and created and modified times. Select a queue name to open it. Use the row checkbox with Archive Work Queue to remove an inactive queue from the current list.
The page also provides three entry points:
| Action | Use it for |
|---|---|
| New Queue | Build a queue manually, starting with its identity, properties, statuses, and agents. |
| Create from Data | Paste spreadsheet data or upload CSV, JSON, or Excel, then turn the columns into queue properties and items. |
| View Resource Groups | Review and configure the execution controls shared by one or more queues. |
A safe operating model
Start with a human-owned status and a paused Resource Group while you build and review the schema. Add an agent only after its Flow, instructions, Connections, allowed transitions, and cost limits are ready.
For scheduling, use an item's native Snooze Until value. Keep the item in its meaningful business status instead of creating a separate status only to represent time. When the time arrives, BotDojo can return the item to its normal ready state.