Agents work with you. Work keeps moving.
Flow is the automation builder inside ViviScape Work. Draw how a piece of work should move — what starts it, what happens next, and where a person signs off — and Flow runs it, with your AI agents doing the legwork and your team making the calls.
Part of Premium and Enterprise · See pricing
Not a robot in a back room
Flow puts your agents and your people in the same process — the agent does the busywork, a person decides what matters, and every run is written down.
What can start a flow?
Six kinds of trigger, all live today. Every request that starts a flow is kept in that flow’s request log.
Something happens in Work
A task or ticket is created, changes status, gets a comment, or is assigned.
Mail sent to the flow’s own address, filtered by sender address or domain.
Webhook
Another system posts to the flow’s own URL — an order, a form, an alert.
Schedule
As often as every 5 minutes, or daily or weekly at the time you pick.
Agent request
One of your AI agents asks the flow to handle something — only if you let it.
Run by hand
Someone on the team sends it a request straight from the flow’s page.
What can a flow do?
Drag steps onto the canvas and connect them. Each step can use what the trigger or an earlier step produced, so the work carries its context the whole way.
Agent
Hand a step to one of your AI agents. It works under its own sign-in and permissions, the same as everywhere else in Work.
Classifier
Sort what came in — billing, technical, sales, or your own labels — with a confidence score and the reason it chose.
Human approval
Pause for a person. Approved, rejected and timed out each lead where you want, and their note goes along.
Action
Get something done in Work — create the task, comment on it, send the notification, email the report.
Condition
Branch on a value: the amount, the priority, the customer, a date. Yes goes one way, no goes the other.
Wait & Handoff
Pause until the right moment, or hand the work to another of your agents to carry it on.
Start from a template, or just describe it.
Pick a starting point, choose which of your agents does each step, and you’re most of the way there. Or type what should happen in your own words — Flow drafts the flow for you to check and edit.
Request to an agent
A request arrives and one of your agents handles it.
Ticket triage
A new ticket is sorted into billing, technical or sales, and the right people hear about it. Unsure ones go to a person.
Inbound order to task
Another system sends an order; it becomes a task, and a repeat of the same order is spotted.
Weekly report
Every Monday at 9:00, the open tasks are emailed as one report.
Automation you can actually let run.
Flow is careful in the places automation usually isn’t, so you can hand it real work.
Test before it’s live
Edits save as a draft. A test run treats steps that reach outside systems as dry runs, so nothing is sent by accident.
Publish on purpose
Real requests run the published version until you publish again — editing never changes a flow mid-week.
Every run on the record
Each request is kept in the flow’s log with the status of every step, and can be replayed.
Agents stay in their lane
An agent can start a flow only when the flow accepts agent requests and the agent has permission to run flows.
No runaway loops
Flows set off by events in Work can chain only three deep, so one flow can’t keep setting off another forever.
Start it from anywhere
Claude, ChatGPT or Codex can start a published flow through the ViviScape MCP server and follow its run.
ViviScape Flow questions
What is ViviScape Flow?
ViviScape Flow is the automation builder inside ViviScape Work. You draw how a piece of work should move — what starts it, which steps follow, and where a person signs off — and Flow runs it, with your AI agents doing steps and every run recorded.
What can start a flow?
Six things: a webhook from another system, an email sent to the flow's own address, a schedule (as often as every 5 minutes, or daily or weekly), something happening in ViviScape Work such as a task or ticket being created, changing status, getting a comment or being assigned, a request from one of your AI agents, or a person running it by hand.
Can a person approve steps in a flow?
Yes. A Human approval step pauses the flow until a person approves or rejects it, or until it times out, and each outcome can lead somewhere different. The person's note is passed on to the steps that follow.
Do I have to build a flow from scratch?
No. Start from a template — Request to an agent, Ticket triage, Inbound order to task or Weekly report — or use Describe it: say what should happen in your own words and Flow drafts the flow for you to check and edit.
How do I test a flow before it goes live?
Flows are saved as drafts, and a test run of a draft treats steps that reach outside systems as dry runs. Publishing makes the saved draft the version that real requests run, and every request is kept in the flow's request log, where it can be replayed.
Which plan includes ViviScape Flow?
ViviScape Flow is part of the Premium and Enterprise plans, and flows are built by account admins. AI agents can start a published flow when the flow allows agent requests and the agent has been given permission to run flows.
Let the work move on its own.
Set up your agents, pick a template, and publish your first flow this afternoon.