// Guide

Run workflows

A workflow repeats a defined task. Use it for a daily brief, a weekly project summary, or a review that should start when a document enters a folder.

Create a workflow

1. Open Settings → Workflows and select New workflow.
2. Give it a name that describes the output.
3. Select an instruction document, or choose to enter the instructions directly.
4. Open the advanced options to set the trigger and output destination.
5. Create the workflow, inspect its status, and activate it when it is ready.

A workflow drafted by the agent remains inactive until a person activates it. Check the status after creation rather than assuming that a schedule means it is running.

Write complete instructions

Name the source material, expected output, checks, and what to do if information is missing. An instruction document lets the team maintain the task alongside its other knowledge. Inline instructions suit a short task with a stable definition.

Choose when it runs

• On demand: runs when you select Run now.
• Daily: runs at the selected hour.
• Weekdays: runs at the selected hour on weekdays.
• Weekly: runs on the selected day and hour.
• When a document is filed into…: starts from a filing event in the selected trigger folders.

For scheduled work, choose the time zone and inspect the next-run preview. The hour and weekly day follow that time zone. A folder trigger reacts to filing; it is not a promise to rerun on every edit of a document already in the folder.

Choose the output destination

Select an optional Target folder. With no folder selected, the resulting document remains unfiled. If Slack is connected and available, select the optional channel for the run output. Check the channel carefully before enabling delivery; leaving it empty means nothing is posted to Slack.

Run, edit, or disable

The settings list shows your own workflows, with their status, trigger or schedule, and next run. Members can manage their workflows without being company owners. Use the row’s actions to Activate, Disable, or Edit. Run now runs with the workflow owner’s credentials and requires the matching permission.

Disable a workflow when you want future runs to stop. Read any displayed disabled reason, including plan restrictions. Editing instructions or a destination changes future work, so review the next run after a significant change.

Check run history

Open Run history on the row. Check whether each run succeeded, failed, or was blocked, and open the output document when available. A successful start is not the same as a completed result. For a failure, inspect the reason, source access, connector state, and limits before retrying.

External execution

Advanced agent integrations can execute workflows assigned to an external executor. The agent must claim a due run, carry out the instructions, create the output, and report the result. A scheduled external workflow still needs an available connected agent to claim it; the schedule alone does not start an arbitrary local process.