Dispatch from Slack

A connected Slack workspace can dispatch runs without leaving the conversation: mention the bot with a task, and it replies in a thread with the run link once the run is queued.

Connect your workspace

An organization owner or admin installs the app from Credentials → Slack → Add to Slack in the dashboard. Slack shows its consent screen, and after approval the workspace is connected — one Slack workspace maps to exactly one Devboxes organization.

Uninstalling the app from Slack deactivates the connection and revokes the bot's access. Linked accounts are kept, so reinstalling from the same place restores dispatching without re-linking anyone.

Link your Slack account

Runs are attributed to a Devboxes account, so link your Slack account once with Sign in with Slack — from the Slack tab in the dashboard, or straight from the bot's reply when it does not know you yet. If you have no Devboxes account, the link flow sends you through the normal sign-in or sign-up first and finishes the link afterwards.

Mention the bot

In any channel the Devboxes app has been added to:

@Devboxes fix the flaky login test in the auth suite

Everything after the mention is the task. The bot replies in a thread — Dispatched. Follow the run here: … — with a link to the run in the dashboard. Slack's retried deliveries never double-dispatch: each mention creates at most one run.

The slash command

/devboxes dispatch <task>

Does the same from anywhere in the workspace. Errors — an unlinked account, a missing project — are shown only to you; a successful dispatch posts the run link to the channel.

Picking the project

An organization with a single project needs nothing: every task targets it. With several projects, start the task with a project token:

@Devboxes project:"Dashboard" migrate the settings page to the new form kit

project:<name> (or project:"A Name" with spaces) pins the project by its name. Without it, the bot replies with the tokens to choose from. Slack dispatches use the default model and the same blueprint defaulting as an unnamed API dispatch.

Who can dispatch

The dispatch policy in the Slack tab decides, per organization:

Linked users with an owner or admin role always dispatch as their own Devboxes account. Under Any workspace member, everyone else's runs are attributed to the owner or admin who installed the app. Under the default policy, an unlinked account gets a reply with a Sign in with Slack link to fix it in one click; an unconnected workspace gets This Slack workspace is not connected to a Devboxes organization.

Next: Repository connections — the connections every project imports from.