Build workflows

Workflows chain multiple steps together. Use them when a task needs planning, multiple model calls, branching, exports, or integration actions.

The callouts identify the view switcher, workflow name, workflow goal, canvas, step settings, and run control.

Before you begin

• Run the task manually once before turning it into a workflow.
• Identify the input, review point, output, and export destination.
• Confirm that required integrations are configured.
• Decide whether the workflow may pause for follow-up questions.

Workflow and task comparison

Step types

Create a workflow

1. Open Agent Mode.
2. Select the workflow view.
3. Create a workflow or open an existing one.
4. Add steps to the canvas.
5. Configure each step.
6. Connect steps or use the automatic sequential flow.
7. Save the workflow.
8. Run the workflow manually before scheduling it.

Expected result: the workflow is saved and has at least one successful manual run before it is shared or scheduled.

Configure a step

Common step settings include:

• Name - A readable label for the step.
• Prompt - A step-specific instruction, or blank to use the workflow goal.
• Outputs - One or more outputs for model comparison.
• Models - The model used by that step.
• Synthesize - Combine multiple outputs into one result.
• Topic - Inherit from the workflow or override for the step.
• Attachments - Inherit workflow attachments or use step-specific documents, files, or images.
• Diagrams - Allow diagram generation when it helps the answer.
• Skip follow-ups - Continue with reasonable assumptions instead of pausing for clarifying questions.

Use document packs

For Agent steps, enable Generate separate documents when the workflow should produce a pack of documents instead of one combined answer.

This is useful for:

• policy packs;
• control-by-control documents;
• project document sets;
• troubleshooting bundles.

Action steps can then export the pack, including ZIP/DOCX pack downloads where supported.

Add branching

Use a Condition step to route a workflow.

1. Add a Condition step after the step that produces the decision input.
2. Describe the condition clearly.
3. Connect Yes, No, and optional default paths.
4. Add a Join step if branches need to merge before continuing.

Keep conditions specific. For example, use "Does the draft include a rollback plan?" rather than "Is this good?"

Action steps

Action steps use a source step output or the latest prior output.

Supported action categories include:

Available actions depend on tenant configuration and permissions.

Add an export action

1. Add an Action step after the step that creates the output.
2. Select the export action.
3. Choose the file format.
4. Select the source step output.
5. Run the workflow.
6. Download the generated artifact from the run output.

Expected result: the workflow produces the export during the run, so users do not need to manually format the result in the browser.

Run and monitor a workflow

1. Save the workflow.
2. Select Run.
3. Watch progress in Running status.
4. Answer follow-up questions if the workflow pauses.
5. Review per-step outputs and artifacts.
6. Use Run history to review previous executions.

Workflow states can include queued, running, waiting for follow-up, paused by quota, completed, failed, or cancelled.

Manage workflows

Depending on your role, you can:

• save workflow changes;
• branch or version a workflow;
• share a workflow with selected users;
• rerun previous runs;
• cancel active runs;
• delete workflows that are no longer needed.

Shared workflows are visible to selected users. Editing is limited to the owner or administrators.

Example workflow

1. Plan - Create the policy outline.
2. Ask - Gather missing assumptions.
3. Agent - Draft the policy.
4. Condition - Check whether rollback and evidence sections are present.
5. Agent - Revise if the condition fails.
6. Action - Export DOCX and save the final output.

Troubleshooting

Tips

• Keep each step responsible for one outcome.
• Name steps with verbs, such as Draft policy, Check gaps, or Export pack.
• Put review or decision points before Action steps.
• Use a Join step when branches must come back together before export.
• Keep workflow prompts reusable; put one-off context in attachments or run input.

Next steps

• Create agent tasks
• Schedule automation
• Monitor runs