AutomationBeta
Workflows that live where your work does.
Build a flow on the canvas or describe it. It starts when a form comes in, a table row changes or a meeting is transcribed. Your agents take the steps that need judgment, a named person approves what matters, and the result lands in the docs and tables your team already edits.
It starts from your team's work.
Triggers are things your team already does in Dokki: a form submitted, a row added or changed, an agent assigned in a table, a call transcribed, a message received, a doc updated. There are no webhooks to wire and no credentials to paste. For anything outside, there is a webhook.
Forms, tables and docs
A submission, a changed row or an edited doc starts a run on its own.
Meetings and messages
A transcribed call or a new message can start one too.
Outside, when you need it
A webhook starts a run from anywhere, and connected apps can be called as steps.
Your agents do the work. Your people make the calls.
An Agent task hands a step to one of your own agents with a brief, then waits for the result it returns, checked against the fields you asked for and capped in steps and credits. A Human review stops the run for one named teammate, who approves, rejects or answers your questions, in Dokki or by email.
Your agents, not a prompt box
The same agents your team works with. Organization admins turn Agent tasks on.
A person where it matters
One named member decides, with the questions and the deadline you set.
Results where people work
Approved output goes into your docs and tables, or to a channel.
Describe it. Review it. Turn it on.
Tell Automation Builder what should happen. It drafts the steps, the connections and the data mapping, and nothing runs or turns on until you have reviewed it. Change it later by asking, or by hand on the canvas.
A draft from a sentence
Builder lays out the nodes and maps the data between them.
Nothing runs by surprise
You review the draft, test a step, then turn it on.
Change it by asking
Select nodes on the canvas and tell Builder what to change.
Every run leaves a trail you can replay.
Runs are durable: a run picks up where it stopped after a restart, flaky steps retry, and branches run in parallel. Every save is a version you can restore, and any past run replays on the canvas it ran on, step by step.
Durable by default
A run survives a restart and continues from its last finished step.
Versions you can restore
Each save is a new version. Go back to any earlier one.
Replay any run
Step through what happened, event by event, on the canvas.
Start your company of agents
today.
Free to start. Your first team is one sentence away.