---
title: Workflow
description: Create, test, deploy, and review reusable project workflows when the builder is available.
---

Workflow turns a repeatable process into connected steps that Runner can run with the same inputs and rules again.

> **Conditional:** The Workflow interface exists, but the current standard project navigation does not expose a Workflow entry. Use it only when Runner displays an approved Workflow entry for your workspace or Runner support provides an approved path. Do not guess or edit a URL to reach it. If your plan allows only a preview, Runner can show the page while keeping its controls blocked.

## Entry path

Open the **Workflow** entry only when Runner presents it in your workspace. The page lists workflows for the current project. If no entry is present, use [Feature availability](./feature-availability) or contact support instead of trying a direct URL.

## Before you start

- Workflow access depends on the current feature rollout and plan.
- Confirm the project and connected services before testing or deploying a workflow.
- A preview or saved draft is not active; deployment and activation are separate consequential actions.

## Workflow list

When there are no workflows, select **Create Workflow**. When the list already has items, use **New Workflow**.

| Control | What happens after you select it |
| --- | --- |
| **Create Workflow** or **New Workflow** | Opens **Create a Workflow**. |
| **Blank** | Creates an **Untitled Workflow** and opens its builder. |
| Template card | Creates a workflow from that template and opens its builder. If templates fail to load, **Retry** requests them again. |
| Workflow name | Opens that workflow in the builder. |
| **Rename** | Makes the name editable. Enter or clicking away saves it; Escape cancels the edit. |
| **Pin to top** / **Unpin** | Moves the workflow into or out of the pinned group. It does not run the workflow. |
| **Duplicate** | Creates a copy and opens the copy in the builder. |
| **Export** | Downloads the workflow as a JSON file. It does not deploy or run anything. |
| **Delete** | Opens a confirmation. Confirming permanently removes that workflow and cannot be undone. |

Use each row's More menu to find **Rename**, **Pin to top** or **Unpin**, **Duplicate**, **Export**, and **Delete**.

Row labels can also show whether a version is **Live**, has a **Draft ahead**, exposes an Endpoint, or is bound to a Schedule or Event. A paused or plan-blocked label means automatic triggering is not currently active.

### Work with several workflows

Select the checkbox beside one or more rows. The selection bar shows how many are selected and offers:

- **Export** to download the selected workflows.
- **Delete** to open a bulk confirmation. Confirming permanently removes every selected workflow.
- **Clear** to remove the selection without changing any workflows.

**Select all** selects the workflows shown in the current list. Always recheck the count before bulk deletion.

## Build and save

The builder canvas is where you add steps, connect them, and configure what each step receives and does. **Add component** opens the searchable component library. Canvas controls zoom in, zoom out, fit the workflow on screen, and automatically arrange connected steps.

Changes save automatically; there is no separate Save button. The Back arrow finishes a pending save before returning to the workflow list.

| Save state | What to do |
| --- | --- |
| **Saving…** | Wait before closing the page or deploying. |
| **Saved** | The latest canvas change is stored. |
| **Save failed** | Select **Retry** after checking the connection. |
| **Conflict — your changes were not saved** | Another saved version is newer. **Reload** discards the conflicting local edits and loads the saved version. |

The lower panel contains **Playground** and **History**. In Playground, complete the required text, product, or media inputs before running. The run control stays unavailable while required inputs are missing. Results appear in the output area.

The builder's More menu also provides **Export JSON** and **Import JSON…**. Export downloads the current canvas. Import immediately replaces the current canvas and triggers autosave without a confirmation, so export a backup and check the selected file before importing.

## Choose the right test

Testing can have very different consequences.

| Control | What happens after you select it |
| --- | --- |
| **Simulate without calling APIs** | Opens a simulation dialog. Use generated sample data or paste JSON, then select **Run Simulate**. Write-side actions such as emails, Slack posts, and store changes are stubbed. |
| **Live Test — real side effects, marked isTest** | Opens a live-test dialog. Use generated data, pasted JSON, or a recent event when available. **Run Live Test** makes real API calls and can send messages or change connected services. The run is marked as a test in history. |
| **Skip waits** | During a live test, skips configured wait periods so the test can continue sooner. It does not remove other real effects. |
| **Run workflow** | Starts the configured workflow immediately and opens History. Its steps may have real effects; review every step and input first. |
| **Stop execution** | Requests that the current run stop. Work already completed is not reversed. |
| **Cache** | On a rerun, skips eligible nodes whose inputs have not changed so you can focus on changed downstream work. |

Use Simulation to check branching and data flow. Use Live Test only when real side effects are acceptable in the connected accounts.

## Review run history

Open **History** in the lower panel to see previous runs. Filter the list with **Live**, **Test**, or **All**, then select a run to inspect its node results, output, timing, and errors. Statuses include Completed, Failed, Running, and Cancelled.

If the list says **No runs yet**, the current workflow has no recorded execution. Starting another run is not a fix for a failed one; open the failed run first and read its error.

Some eligible failed nodes offer **Retry from “node”**. This starts a new attempt immediately, without another confirmation. Downstream actions can run again, so check for messages or store changes already produced by the failed run first.

## Deploy and activate

Select **Deploy** to open **Deploy Workflow**. Review the change summary, API-contract compatibility, validation results, and optional changelog before continuing.

You can optionally bind the deployed workflow to a schedule or an event. Only one of those trigger types can be selected at a time.

- **Deploy** publishes a version with the selected settings.
- **Activate & Deploy** appears when a new schedule or event binding would make the automation active. Confirming it publishes the version and allows future triggers to run automatically with real effects.

A save error, unresolved conflict, or validation problem can block deployment. Resolve it instead of repeatedly selecting Deploy.

After deployment, the production status can show **Not deployed**, **Draft ahead**, or **Live**, plus **No trigger**, **Active**, or **Paused** for the binding. Opening an existing binding offers consequential controls:

- **Pause** stops automatic triggers but keeps the workflow and binding.
- **Resume** allows the retained binding to trigger again.
- **Remove** permanently deletes the binding but does not delete the workflow.

Each action opens a confirmation and can include a reason. Removing the check from an existing binding during deployment pauses that binding rather than permanently removing it.

## Version history and rollback

Select **Version history** to open the **Version History** panel.

| Action | Result |
| --- | --- |
| **Rollback** | Opens **Rollback to this version?**. **Confirm** makes the selected deployed version supersede the current deployed version. This can change what future runs do, but it does not replace the current draft canvas. |
| **Restore** in Draft History | Replaces the current canvas with the selected saved draft after confirmation. Unsaved or newer canvas changes can be lost. |

Add an optional rollback reason so other workspace members understand the change. Review the restored canvas and deployment state before starting another run.

## Safe operating checklist

1. Confirm you are in the correct project and workflow.
2. Wait for **Saved** before testing or deploying.
3. Complete and review every required input.
4. Start with **Run Simulate** when possible.
5. Use Live Test or Run workflow only when their connected-service effects are acceptable.
6. Inspect **History** and outputs before deploying.
7. Treat **Activate & Deploy**, rollback, restore, and deletion as consequential actions that require a final review.

## Troubleshooting

| Problem | Next step |
| --- | --- |
| No **Workflow** entry is visible | This is expected in the standard navigation. Do not guess a URL; see [Feature availability](./feature-availability) or ask Runner support whether your workspace has an approved entry. |
| Controls are blocked by a plan preview | Follow the plan message on screen or ask a workspace owner about access. |
| Template list fails | Select **Retry**, or create a **Blank** workflow. |
| Run button is unavailable | Complete every required input and fix any invalid value. |
| Save conflict appears | Decide whether the saved version should win before selecting **Reload**, because local conflicting edits are discarded. |
| Run fails | Open it in **History**, keep the visible error and inputs, and avoid starting identical runs repeatedly. |
| Deploy is blocked | Resolve save, conflict, contract, or validation messages shown in the deploy dialog. |

## Related guides

- [Automations](../automate-test-and-create/automations)
- [Task states and details](../work-with-runner/task-states-and-details)
- [Troubleshoot Runner tasks](../help-and-reference/troubleshoot-runner-tasks)
- [Feature availability](./feature-availability)