Skip to main content
You run a workflow by filling in the inputs it asks for. The run then follows the workflow’s steps and stops where a person must approve. Every run you start appears in Tasks.
Who: Admins and Members (Viewers cannot run workflows) · Where: New task, or Workflows › a workflow › Runs · Works on: Enterprise and SaaS
Admins and members can run every workflow they can see. A run uses the workflow’s published revision, unless its owner or an admin chooses another one.

Run from New task

1

Pick the workflow

On New task, open the worker picker at the bottom of the message box. Workflows are listed under Workflows, after the agents, with their published version (for example v3 · published). Only published workflows that are not archived are offered. Type to search, and click the star to keep a workflow at the top.
2

Fill in the inputs

The message box turns into the workflow’s input form. Fields marked optional can stay empty, and some workflows group them under Optional inputs. Below the form, a badge says how many required inputs are still empty, or Ready.
  • Use last inputs fills the form with the inputs of the workflow’s last run. Files are not kept with a run, so you pick them again.
  • Fill example fills the form with example values, where the workflow defines them.
New task with the Expense approval workflow picked: its form with Employee, Amount and Purpose filled in, the Ready badge, and the run button.
3

Run

Click the run button (the play icon), or press Ctrl+Enter (⌘+Enter on a Mac). The run starts on the published revision and its task page opens.
Steps that pause for a decision appear in the Inbox of the people who may decide them.

Run from the workflow page

Open the workflow from Workflows (or choose Run in its row menu), then open the Runs tab.
1

Fill in the inputs

Under What to run it on, fill in the inputs. Required ones are marked with an asterisk. When the workflow has no inputs, the page says there is nothing to fill in, and you go straight to Run.
2

Run

Click Run in the header. If a required input is empty, the run does not start and the missing fields are listed.
3

Follow the run

The run’s steps appear on the right as they run. While it runs, the inputs it uses stay visible, greyed out. New run clears them for the next run.
Beside Current, the Executions tab lists the workflow’s most recent runs (Run history) with their status, start time, duration, cost and first inputs. Click one to show it on the right. Everyone who can open the workflow sees its runs, whoever started them.
  • Members the workflow is shared with always run the published revision.
  • The owner and admins run the revision chosen in the header’s revision picker: Published by default, Draft, or an earlier revision. More actions › Test run (draft) runs the latest saved draft. A workflow that has never been published runs its draft.
Run is disabled while the workflow has unsaved changes (Save changes before running), a pending proposal (Resolve the pending proposal before running) or issues to fix (Fix blueprint validation issues before running).

Decide an approval

When a run reaches an Approval step, it pauses with the status Waiting for approval. The request appears:
  • in the Inbox, under Waiting for you, for every admin and member who can see the workflow and matches the step’s approver role or groups;
  • on the run page and on the workflow page’s Runs tab;
  • by email to the addresses the step lists, when your installation has email set up.
Under Your approval is needed, the request names the paused step. Below that come the step’s prompt (when the step sets one), when it was requested and when it expires, and what happens if nobody decides in time. It also shows the main facts of the run and the content to approve.
1

Review

Read the request. Technical details shows the full data the step received.
2

Add a comment and evidence

Comment and Evidence (for example a ticket link or the document you reviewed) are optional. Both are recorded on the audit trail with your decision.
3

Decide

Click Approve & resume run or Reject. Rejecting without a comment asks you to confirm (Reject anyway) or to Add a note.
The run then continues on the approval or the rejection path that the step defines. With no rejection path set, a rejection stops the workflow. Decided requests are listed under Decided in the Inbox.

The run page

A run started from New task, or opened from Tasks, has its own task page. The top shows the Worker (the workflow and its version), when it Started, its Status, its Duration and its Cost. When the run waited for an approval, the duration is split into time active and time waiting. The page then shows the sections that apply to the run.

Cancel a run

The person who started a run, or an admin, can cancel it while it is running or waiting for an approval. Click Cancel run next to the run (on the Runs tab or under a pending approval) and confirm, or choose Stop in the task page’s actions menu.
Cancelling cannot be undone, and the run cannot be resumed. Anything its completed steps already did, such as a message sent or a record written, stays done. Cancelling a run that waits for an approval closes the request undecided.

Schedule a workflow

The owner of a workflow and admins can run it on a schedule. Each scheduled run starts a fresh run and appears in Tasks.
  • From New task or a run page: fill in the inputs, then click Schedule (or Schedule this on a run). The schedule sheet opens with those inputs. See Schedules.
  • From the workflow page: More actions › Schedule automatic runs opens Schedules. Enter a Cron expression (or click a preset such as Every day at 09:00), a Timezone, an optional Name, the Revision to run (Published or Draft (head)) and the Default inputs (JSON), then click Add schedule. Each schedule shows its next and last run and its last error. Turn it off with its switch, or delete it.
An archived workflow cannot be scheduled, and its schedules do not run. On SaaS, your plan limits how many schedules you can have (see Plans and limits).

Other ways a workflow runs

A workflow can also be started through the API with an API key (see API keys and the API reference), or by an agent that was given the workflow to run (see Configuring agents). More actions › Run analytics on the workflow page counts runs by how they were started: Manual, API, Schedule or Agent.

When a run does not start

When a run starts but fails, open it and read Error on the run page. The step that failed is marked under Step Execution.