A visual + agentic automation layer: define a trigger, build the flow, and let the agent do the work — with durable human-in-the-loop steps, connected accounts, and delivery back into chat.
Our first shipping version: create a workflow from a trigger, author it two ways, and run it with interactive steps and delivery.
The end-to-end foundation of Workflows: a user can pick a trigger, build the automation either by describing it to the agent or assembling typed steps in the flow builder, collect input via forms, gate on human approval or button choices, call APIs and connected accounts, and deliver results back into chat — all running durably with live progress.
Ship the first usable version to production so early users can create and run real workflows end-to-end. Live in prod Tue 11 Aug.
Describe the goal in one line of plain language. The agent decides how to accomplish it at run time — the fastest path from intent to a working automation.
Assemble the workflow step by step from typed blocks — add, edit, reorder — then choose how the result is delivered back to a channel or person. Deterministic and reviewable.
What starts a workflow.
The typed steps you assemble a flow from.
Getting results and questions into chat.
Interactive steps that pause and wait for a person.
Connected accounts wired end-to-end for v1.
Watching a workflow execute.
Guardrails so automations stay safe.
An agent that keeps growing the catalog — always on.
Where interactive workflows run in our own chat.
choice() posts a tappable card right in the room; a tap resumes the runAny step can pause and wait for a person to allow or deny before it continues — durably, so the run survives a restart and picks up exactly where it paused.
approval() gate — e.g. before sending an external message or calling a write API.Allow once / Allow always / Deny — from the card or with /approve <id>.Assembled in the flow builder from typed blocks — trigger, an AI step, an API call, an approval gate, then delivery. Each block is added, edited, and reordered; the run executes them top-to-bottom.
#bugs#bugs Matrix room · fires on any new report.#engAdd / remove / reorder blocks freely — the flow compiles deterministically to a runnable script. Preview each step before publishing with a Test run (writes stubbed).
Broaden how workflows are triggered and where they run, and stand the service up on its own footing.
Expand reach and robustness: add webhook triggers and let assistant (AIC) messages drive steps, bring workflows into Slack as an app, let users trigger agent actions directly, and broaden the connector catalog (including Google Workspace). Under the hood, move workflow data into a database and split workflows into their own service.
Make workflows reachable from more places and ready to scale independently, with a wider set of integrations. Delivered before 21 Aug.
Let any external service kick off a workflow.
Use an assistant message as a signal inside a workflow.
Run and interact with workflows natively in Slack.
Let a person pick up and run a workflow's action.
Persist workflow data properly.
Give workflows their own service boundary.
Broaden the integration catalog.
An agent that keeps growing the catalog — always on.
Bring team bots and shared credentials into workflows, safely.
Take workflows from individual to team scale: integrate team bots / bot services so automations run on behalf of a team, and let a workflow securely borrow the permissions and secrets held by the team bot — governed, delegated access instead of per-user credentials.
Enable shared, team-level automation with delegated, governed access to team-owned permissions and secrets. Early September.
Workflows that work hand-in-hand with team bots.
Run workflows with the team bot's access.
An agent that keeps growing the catalog — always on.