Platform — Workflows
Repeatable work,on the record.
Turn multi-step processes into governed workflows a person or an agent can run — with approvals where you want them and a complete trace of every run.
Overview
A workflow turns a process you keep re-explaining into a definition you run. Steps, inputs, branching and human approval gates are set once; every execution becomes a durable run with snapshots and a full audit trace. A person or an agent can start it, and you can watch all of it move on one Kanban-style control plane.
Feature
Steps, branches, approvals
Define inputs, multi-step logic, branching and human approval gates once. Put a person in the loop exactly where judgment is needed, and let the rest run.
Feature
Runs you can replay
Every execution is a durable run with status, snapshots and a full audit trace. You can see what happened at each step and reconstruct any run after the fact.
Feature
Start from anywhere
Kick off a run from a Space, a document, chat, the API or a schedule — the workflow is the same however it starts.
Feature
A control plane for AI work
One Kanban-style Control Plane surfaces agent work, reviews and scheduled activity across the org, so the state of automated work is visible in one place instead of scattered.
Feature
Start from a template
Workflow starters give you a ready-made definition to adapt, so a common process doesn't have to be built from a blank canvas.
Feature
Connect to your channels
Blinkin's chat surfaces reach Microsoft Teams and external channels, so the work a run produces can be discussed where your team already talks.
Feature
Real example: field inspection
A workflow running today in industrial inspection takes field photos in and produces a structured safety-checklist review out — a person signs off, and every step is on the record.
Feature
Blinkwoot: your service inbox, governed
Blinkwoot binds a customer-service inbox to a Space and its agents, so inbound conversations run through the same governed runtime as everything else — drafts proposed, humans deciding, every step on the record.
Feature
Workflow packs
Early accessPackaged workflows for a recurring job — first up: inbound press. A pack classifies what arrives and proposes governed next actions; your team stays the one that acts.
How it works
How it works
Define once
Set inputs, steps, branches and approval gates.
Start a run
Trigger from a Space, document, chat, API or schedule.
Approve where needed
The run pauses at your gates for a human decision.
Trace and replay
Track it on the Control Plane; every run keeps snapshots and an audit trace.
In practice
In practice
An EHS manager runs the field-photo inspection workflow: submissions come in, an agent drafts the checklist assessment, and an inspector signs off before anything is final.
An operations lead watches the Control Plane like a Kanban board, seeing which agent runs are waiting on a human approval.
A team scheduler sets a workflow to run on a schedule, so the recurring report is drafted and waiting for review every Monday morning instead of being assembled by hand.
Questions
FAQ
Do I need to build every workflow from scratch?
No — workflow starters give you templates to adapt for common processes.
Can an agent run a workflow, or only a person?
Both. A person or an agent can start a run, and the approval gates apply either way.
How do I know what happened in a past run?
Each run is durable, with status, snapshots and a full audit trace — you can replay exactly what occurred at each step.
Where can a workflow start from?
A Space, a document, chat, the API or a schedule. The definition is the same regardless of trigger.
Is the inspection example real?
Yes — the field-photo safety-checklist workflow is deployed and running today in industrial inspection.
Governance
Governed by design
EU hosting
Per-organization data isolation
Full audit trail
Review-gated knowledge
Works with any AI model
Next step