Skip to main content
Workflows are the automations Upsun Dispatch runs after your organization connects an integration and stores the required AI model key. A workflow listens for supported activity, creates a run, executes the work, and publishes results back to the relevant integration and the Upsun Dispatch console. Upsun Dispatch currently provides two built-in workflows:
  • Issue to code starts when an issue body or comment is exactly @upsun-dispatch implement, with an optional trailing !, ., or ?, and turns the issue request into code work.
  • Code review reviews GitHub pull requests and GitLab merge requests, then publishes review feedback such as checks, statuses, comments, notes, and summaries.
For a compact list of built-in workflows and their supported triggers, see Built-in workflows.

​
How workflows start

Workflows can start from integration events or from a manual action, depending on the workflow and your settings.

​
Automatic triggers

Trigger mode applies to Code review only. Its default is automatic, which means supported events can start Code review runs without a separate action from you. For Code review, this includes changes to connected GitHub pull requests and GitLab merge requests. Code review uses wait behavior for rapid updates: if a new push arrives while a review is already running, Upsun Dispatch holds the new delivery and runs one fresh review after the active review finishes. This prevents a burst of pushes from creating redundant reviews. Issue to code does not have an automatic or manual trigger mode. It starts only when the entire trimmed issue body or a comment is exactly @upsun-dispatch implement, with an optional trailing !, ., or ?.

​
Manual triggers

Some workflows can be started manually from comments. For Code review, users can request a review, force a full review, or request cancellation of an active review from the pull or merge request conversation:
  • On GitHub pull requests, use whole-message commands addressed to the Upsun Dispatch bot, such as @upsun-dispatch review, @upsun-dispatch full review, or @upsun-dispatch cancel.
  • On GitLab merge requests, use the bot username configured for that GitLab connection, such as @<configured-bot-username> review, @<configured-bot-username> full review, or @<configured-bot-username> cancel.
For Issue to code, the whole trimmed issue body or comment must be exactly @upsun-dispatch implement, with an optional trailing !, ., or ?. Issue to code has no automatic or manual mode of its own. This exact issue command is the trigger. See Issue to code for examples and non-matching command behavior. Use @upsun-dispatch help to post command help. Ordinary comments that do not match a supported command are ignored. You can observe runs in the Upsun Dispatch console, including viewing run details, following logs, and rerunning eligible terminal runs. See Use the Upsun Dispatch console for those actions.

​
Workflow settings

Workflow settings control how Upsun Dispatch behaves for a workflow across your organization. Settings are available per configurable workflow and integration. In Organization Settings > Workflows, use Model integration to choose which stored AI model key a workflow uses. Use Quality level to set the model effort level for that workflow. To add or manage stored model keys, see AI models. Available settings include:
Turning summary mode off stops Upsun Dispatch from publishing future summary content. It does not delete summaries that were already posted.
The Plan approval gate setting does not make Issue to code automatic. Issue to code still starts only from its exact trigger phrase. The gate only controls whether eligible Jira-triggered Issue to code runs pause at the plan step before continuing.

​
Repository overrides

Organization-level workflow settings act as defaults. You can also create repository overrides for individual repositories when one repository needs different behavior from the rest of the organization. Repository overrides pin selected settings for that repository independently from the organization default. For example, you can keep Code review automatic for most repositories while making one repository manual-only, or pin a repository to a specific stored AI model key. Manage organization workflow settings and repository overrides in the Upsun Dispatch console. See Use the Upsun Dispatch console for where to change these settings.

​
Where results appear

Each workflow run is visible in the Upsun Dispatch console with status, steps, timeline events, logs, and usage information. Code review also publishes results back to GitHub and GitLab, such as GitHub checks and review comments or GitLab progress notes, commit statuses, and merge request notes. To inspect a run, follow logs, or rerun an eligible completed, failed, or canceled run, use the Upsun Dispatch console.
Last modified on September 17, 2026