Create and Configure

Create a Work Queue and define its identity, properties, statuses, transitions, agents, and Resource Group.

6 min read

Select New Queue from the Work Queues list to open the queue editor.

The Work Queue editor showing identity and Resource Group settings

The editor is organized into Information, Properties, Status, and Agents. You can move between sections before saving.

Information

Setting	What it does
Work Queue Name	Labels the queue in the list, breadcrumbs, item details, and selectors. Use a name that describes the process, not a single item.
Description	Explains the queue's purpose and operating boundary. Include the intended outcome and important safety constraints.
Resource Group	Chooses the execution pool and guardrails used when an agent works an item.
Edit Resource Group	Opens concurrency, circuit-breaker, and cost-window settings for the selected group.

The Resource Group card summarizes its current state, maximum concurrent requests, circuit breaker, cost window, and last start time. A queue can still hold and organize human work while its Resource Group is paused.

Create from existing data

Use Create from Data instead of New Queue when a spreadsheet or file already describes the items.

The Create Work Queue wizard with paste-data and file-upload choices

The wizard has four stages:

Paste rows from Excel or Google Sheets, or upload CSV, JSON, or Excel.
Review the detected columns and their types.
Configure the queue name, properties, and lifecycle.
Create the queue and its initial items.

Review generated property keys before creating the queue. Stable, machine-readable keys are harder to change safely after agents, views, or imports depend on them.

Properties

Properties define the structured data stored on every item.

Setting	What it does
Name	Sets the stable property key used by agents, imports, filters, and APIs. Prefer `snake_case`, such as `target_timezone`.
Required	Requires a value when a form or transition validates this property.
Label	Sets the human-readable column and form label.
Type	Controls the editor, validation, sorting, and filtering behavior.
Description	Explains the value to people and agents. Describe format and intent.
Multiline	Gives text a larger editor for notes or longer responses.
Markdown	Treats text as Markdown and provides rendered and raw views where supported.

Use Add Property to append a field. Select a property in the left column to edit, reorder, or delete it. Copy JSON Schema copies the current property model for use in a Flow, tool, or external producer.

Property types can include text, numbers, booleans, date and time values, options, structured data, and BotDojo resource references. A resource reference can link an item to a document, Flow Request, recording, or another BotDojo resource without copying the resource into a text field.

Status workflow

Statuses model the business lifecycle. Open Status, then Layout, to review the whole workflow.

The status layout for the fictional outbound review queue

Layout control	What it does
Start Status	Sets the status assigned to newly created items.
Add Status	Adds another business stage.
Auto Arrange	Places status cards into a readable workflow layout.
Status cards	Show the label, assignment type, start/end markers, and transition count.

Select a status card or its name in the left column to edit it.

Status settings

Setting	What it does
Color	Sets the status chip and workflow-card color.
Status Name	Sets the human-readable label.
Key	Sets the stable value stored on items and used by tools. Prefer a short `snake_case` key.
End Status	Marks the status as complete for summary and Completed views. A queue can have more than one complete outcome.
Description	Explains what the status means.
Assignment	Chooses human ownership or one of the queue's registered agents.
Human Instructions	Tells a person what to do before moving the item forward.
Agent Instructions	Tells the assigned agent how to process the item. This appears for agent-assigned statuses.
Layout	Chooses which properties appear in the left and right sides of the item page for this status.
Agents With Access	Allows selected queue agents to work with this status even when they are not its default assignment.
Property access	Sets each property to Read, Write, or Hide for the status.
Agent Starts When Assigned	Makes an eligible agent assignment start work automatically when the Resource Group allows it. Leave it off when another event or operator should start the work.
Work Queue Item MCP	Chooses the item-tool interface exposed to the agent. Use Core Item Tools v2 for new queue agents; Legacy v1 remains for older Flows that depend on that contract.

Transitions

The Transitions section lists every possible target status.

Transition setting	What it does
Enabled target	Allows the current status to move to that target status. Disabled targets are not offered on the item.
Transition Name	Replaces the generated button label with an operator-friendly action such as `Approve` or `Request clarification`.
Validation properties	Shows selected fields in the transition dialog so the operator can confirm or edit them.
Required properties	Blocks the transition until every selected field has a value.
Next assignment	Changes who owns the item after the transition when the workflow calls for an explicit handoff.

Required properties block an incomplete transition. Validation properties are shown in the transition dialog so the operator can confirm or update them without reopening the entire item.

Agents

The Agents section registers the Flows that can work queue items. Only Flows configured as Work Queue Agents appear in the selector.

Select Add Agent.
Enter an Agent Name, or use the selected Flow's name.
Under Flow Configuration, choose a Flow configured as a Work Queue Agent.
Save the queue, then assign the registered agent to a status or transition.

Registering a Flow does not start it. Agent work begins only when an item is assigned to that agent, its action state is eligible to run, and the selected Resource Group permits execution.

An agent receives item-scoped context, including the queue item tools and any allowed resource references. Its instructions should tell it which status it may process, what to validate, how to update fields, when to snooze, and which outcomes require human review.

Save, duplicate, or cancel

Save writes the current queue definition.
Duplicate creates another queue from the current definition so you can adapt a proven schema and lifecycle.
Cancel closes the editor. BotDojo asks before discarding unsaved changes.