Workflows

Build automations on a visual canvas or with chat-to-workflow, then save, test, activate, and operate them.

Workflows are step-by-step automations that run in Automate. Each workflow starts with a trigger, then runs actions (apps, Flow Control, agents, and more) in order. Open the list at Workflows.

In this guide

Build

TopicStart here
Create a workflow and assemble steps with clicksBuild on the canvas
Describe a process and let AI draft the graphChat to workflow
What Build with AI can do vs the agent builderBuilder tools
Choose how a run startsTriggers
Approvals, branches, waits, and other built-in logicFlow Control
Name, description, tags, metrics, and ActiveSettings

Operate

TopicStart here
Save a graph as a reusable pattern, or start from oneTemplates
Share a workflow file between workspaces or environmentsExport and import
Find runs, open details, and clean up historyMonitor executions

What a workflow is made of

PieceRole
TriggerHow the run starts (for example Manually Run, Recurring Schedule, or an app event). See Triggers.
ActionsWhat happens next: call apps, Flow Control (branches, waits, approvals), talk to agents, write knowledge, and more
ConnectionsCredentials many actions need before they can run
ActiveWhen on (and saved), the workflow can run according to its trigger

Every workflow belongs to a project. Creating from the global Workflows list asks you to pick a project first.

Canvas at a glance

You do not drag steps from a left palette. You build by:

  1. Choosing a trigger on the empty canvas (Select a trigger...).
  2. Adding the next action with the + on a node or on a connection line.
  3. Clicking a node to configure fields, connections, and Save & Test.
  4. Turning Active on and clicking Save in the header when you are ready for real runs.

The right-hand Build with AI panel is the chat-to-workflow path. See Chat to workflow.

After you build

JobWhere
Keep the workflow findable and readySettings (Active, name, tags, metrics)
Reuse the pattern in another projectTemplates
Move the graph to another workspaceExport and import
Check whether runs succeeded or failedMonitor executions (under Observability → Executions)

Related