Workflows

What is a Workflow?

A workflow is an automated sequence of actions that executes when triggered. Workflows are built visually by connecting nodes together in the drag and drop editor.

Workflow Structure

Every workflow consists of:

1. Trigger — The starting point that initiates execution. Add additional triggers directly; existing drafts switch to independent execution automatically when the second trigger saves. See adding another trigger.
2. Nodes — Individual actions or operations (AI generation, sending emails, data lookups, etc.)
3. Connections — Links between nodes that define the execution order
4. Context — Shared data passed between nodes via template variables

The Visual Editor

The editor is a canvas where you build workflows by placing and connecting nodes. Key interactions:

• Add nodes — Use the node picker, universal search, or the canvas context menu
• Connect nodes — Drag from an output handle to an input handle
• Configure nodes — Click or double click a node to open its settings panel on the right
• Move nodes — Drag nodes to rearrange the layout
• Delete nodes — Select a node and press Delete, or use the context menu
• Undo and redo — Reverse or restore editor changes
• Copy and paste — Reuse nodes or sections of a workflow
• Lock the canvas — Prevent accidental movement while reviewing
• Add sticky notes — Document the workflow directly on the canvas

Node settings and canvas changes can save while you work. Check the toolbar's save state before leaving; use Save workflow when changes remain. Use Copilot to add, configure, explain, test, or repair a workflow through conversation.

Canvas layout

Workflows flow left to right: inputs are on the left of each node card, and outputs are on the right. Branching nodes show separate output rows. Follow the labeled connection for the intended branch; moving a node does not change execution order.

Older workflows are arranged once when first opened in an editable canvas. This changes positions, not configuration, connections, or deployment state. You can undo the arrangement as one change and continue positioning nodes yourself. Read-only previews do not initiate this conversion. If arranging fails, the editor releases the canvas and offers Retry; wait for pending edits or connection problems to clear before retrying.

Saving and conflicts

A successful save covers the changes submitted with that save. New edits made while saving can still leave the workflow marked unsaved. Saving a draft is separate from deploying or running it.

If saving reports that the workflow changed, preserve your unsaved work before reloading. Another tab or collaborator may have changed the stored workflow; repeating the same save does not merge conflicting edits. Review the latest version and reconcile your changes instead of overwriting it.

If Copilot finishes but the workflow cannot be saved, use the separate save recovery controls.

Execution Flow

When a workflow runs:

1. The trigger node activates
2. Execution follows the selected trigger’s connected path; unrelated roots do not run
3. Output from each node is added to the workflow context
4. Subsequent nodes can access previous outputs via variables
5. Branching nodes select the connected paths according to their configured rules

Workflow States

Deploying or undeploying from the workflow library requires confirmation. A draft can still be tested manually from the editor; service triggers, public forms, schedules, and API execution require the appropriate deployed state.

Organize the workflow library

The Workflows page supports:

• Search by workflow name
• Create colored folders
• Drag workflows between folders or move them from the item menu
• Rename, duplicate, or delete a workflow
• Import a workflow JSON definition
• Publish a workflow as a reusable template
• See and change draft/deployed state

Execution History

Each workflow run is logged with the status of every node. Click on a completed execution to see what each node produced. Execution history retention depends on your plan:

• Free: 1 day
• Pro: 30 days
• Business / Enterprise: 90 days

For workspace-wide logs, live status, debugging, and notifications, see Executions and Inbox.

Using the Copilot

The Copilot can build and modify workflows using natural language. Open it from the sidebar sparkles icon.

Best Practices

• Keep workflows focused — Each workflow should do one thing well
• Use descriptive names — Name nodes clearly so variables are easy to understand
• Test incrementally — Run and verify after adding each node
• Use environment variables — Store secrets in environment variables instead of hardcoding them