Workflows
Path: Workflows (/workflows).
Visual automations: triggers, employees, APIs, approvals, connectors. This is different from Job workflows (a fixed job-application pipeline).
Lifecycle
- Create blank or from a template.
- Edit — drag nodes, connect edges, set attributes and Input / Output.
- Save draft → Publish (required before Run).
- Run with optional input. Watch the runs panel or fullscreen run audit. Each run has a numeric WF run id (searchable from Ctrl+K).
- On audit: Retry from this step, retry stuck/failed, or Retry from start (new run).
- Optional: Publish as A2A, Download for Windows, import/export JSON.
Chat with Workflow Builder in everyday language (“look this up and send me a recap”, “promote this product on Medium and Hacker News with blogs”, “generate story scenes, review them, and upload to YouTube”, “scrape IMDb and Rotten Tomatoes for reviews”). Any create/build-a-workflow ask creates a real graph and opens the editor (not a chat-only plan). With a graph open, “add a GitHub connector” updates the canvas (the builder looks up Connectors / content tools / employees / MCP, then adds the node). The builder gives the model the node catalog (purpose, inputs, outputs, config) plus your employees, tools, MCP, and connectors, and the model chooses the nodes — it does not pick ERP Checker because you said “reviews”. Designer chat uses your Profile model (BYOK or platform primary). After a build it lists any Settings → API Keys names to store — never paste secrets into the chat. Brain steps use free Ollama and an installed local model (not the platform’s paid/cloud model name). Public posts and uploads wait for your approval. Medium binds MEDIUM_INTEGRATION_TOKEN; Hacker News uses Connectors; sites without a Connector (YouTube, TikTok, …) use Browser Session. Then: take it live, put it back in draft, share so other companies can call it (A2A), or delete this workflow.
Use Platform Help to explain a node; use Workflow Builder to change the graph.
Triggers
| Mode | When it fires |
|---|---|
| Manual | You click Run |
| Schedule | A cron expression you set on the trigger |
| Chat | Phrase match (COO and others can trigger) |
| Event | Webhook after save (secret header required) |
Mapping values
Each node has Input / Output:
- Static — a value you type (may include
{{…}}templates) - From previous step — pick source node and output key
- Workflow variable — shared config for this graph (budgets, base URLs)
Examples: {{brain-1.text}}, {{trigger-1.trigger_input}}, {{var.budget_usd}}.
Prefer API Keys vault names for long-lived secrets. Connector nodes need a saved Connector first.
Filesystem, FTP, and SFTP
A Filesystem node can read/write a local path (including the Windows desktop package) or talk to FTP / FTPS / SFTP. Put passwords in API Keys, not in the node or in chat. Pair with a schedule trigger to poll a folder.
Optional input JSON Schema on the Trigger validates Run / webhook / A2A payloads.
Maker / Checker certify
Some packs ship Maker and Checker graphs (for example run crm maker checker). High-risk steps can pause for CEO approval on Kanban. See Maker and Checker.
Website copilot targets
A Connector node can send governed instructions to authorized Digital Adoption website panels. A saved target group persists across runs; individual panels are authorized separately, and peer pairing is optional. See Website copilot workflow connectors for linking, website selection, approvals and save verification.