Workflows
Automation on a visual canvas.
Every event in your workspace is a starting point.
Tasks, messages, tables, email, calendar, webhooks, cron
Because everything lives in one platform, everything can trigger a flow: a task changes status, a message arrives, a table row is created, an email lands in the channel inbox, a meeting is scheduled, a webhook fires from GitHub or HubSpot — or simply on a schedule.
- Task, message, table & email triggers
- Calendar & document events
- Webhooks (GitHub, HubSpot) & scheduled runs
- Run manually anytime
Flows that branch, loop and wait.
A node-graph canvas with an AI step built in
Build on a visual canvas, not a wall of settings: conditions with named branches, for-each loops, delays, and variables like {{trigger.title}} flowing between steps. Drop in an AI step to summarize, extract structured fields or make a call mid-flow — with an explicit tool policy you control.
- Node-graph canvas, multiple triggers per flow
- Branching, for-each loops, delays
- Built-in AI step with structured output
- Variables & tokens between steps
Try it first, then let it run.
Test runs, per-node traces, HTTP to anywhere
Test run executes the whole flow without persisting anything, so you see exactly what would happen. Every run keeps a per-node trace — inputs, outputs, warnings. Actions cover the platform (send messages and email, create and update tasks, write table rows) plus an HTTP request node for any external API.
- Dry-run test mode — nothing persisted
- Run history with per-node traces
- Message, email, task & table actions
- HTTP request node for external APIs
output: { "urgency": "high", "topic": "billing" }502 Bad Gateway — POST /tickets
Automation
Leave the busywork to the flows.
Get started
Build your first flow.
Automation that lives where the work happens — triggered by your tasks, messages and tables, running on your own infrastructure if you want.