Skip to main content
Flows are the automated workflows Doris runs in your account. A flow fires when something happens — a meeting is processed, a deal changes, a schedule comes around — and then carries out a sequence of steps: pulling context, running an agent, composing a brief, sending an email, or updating a CRM field. The Console shows you every flow as a clear trigger-to-steps diagram, so the machine work happening behind your deals is never a black box.
Flows are configured and built together with the Doris team. Today you can view your flows, toggle them on or off (company admins), and inspect their execution history and outputs in the Console. Building new flows and forking templates is done with your Doris contact — there’s no self-serve builder yet. To get a flow set up or changed, reach out and the team will configure it for you.

​
What a Flow Is

Every flow has two parts:
  • A trigger — the thing that starts it. Triggers come in three kinds: an event (a meeting is processed, a deal review completes, a deal closes), a schedule (daily or weekly at a set time), or a manual run.
  • Steps — what runs after the trigger fires, in order. Each step does one job: resolve context from the ontology, run an agent, branch on a condition, compose text, send an email, or write a field back to your CRM. Steps chain together so the output of one feeds the next.
The result is a single automated path from “something happened” to “the work got done.”

​
Viewing Your Flows

Open Console › Flows to see every flow configured for your account. The list is grouped into Company-wide flows and per-person flows, and for each one you can see its trigger, output type, schedule, and whether it’s active. Click any flow to open its diagram. The flow is laid out left to right: the trigger on the left, then each step as a labelled node connected by arrows. Branch steps fork the path so you can see exactly how the automation decides what to do. The footer shows how many steps the flow has.

​
Turning Flows On and Off

Company admins can toggle any flow on or off directly from the list or the flow’s detail page. When a flow is disabled it stops firing but stays configured, so it can be switched back on at any time. Everyone else sees the current status (Active or Disabled) as read-only.

​
Execution History & Outputs

Every time a flow runs, it’s logged. Open the Executions tab in Console › Flows (or the Outputs page) to see the full run history:
  • Status — completed, running, pending, or failed for each run
  • What it touched — the deal a run was about, when it ran, and how many outputs it produced
  • Step-by-step detail — expand any run to see each step, its status, and what it actually produced: the email subject and recipient, the brief preview, the CRM fields written, the context resolved, or the branch taken
Filter the log by flow or by status to find a specific run. The view refreshes automatically, so a flow that’s running right now updates in place.

​
The Catalog

Console › Catalog › Flows is where you browse the available automation templates. It’s organized around a simple question — when do you want Doris to act? — with templates grouped by trigger:
  • After a meeting — flows that fire once a call is processed
  • When a deal changes — react to stage changes, updates, and outcomes
  • On a schedule — recurring flows that run daily, weekly, or before an event
  • When overdue — act on missed deadlines, overdue commitments, and stale deals
Click any template to preview its full workflow diagram before it’s set up — the same trigger-to-steps view you see for your live flows — along with its step count and intended audience (reps or managers). To put a template to work, request setup and the Doris team configures it for your account.
Flows always do the machine work and stop short of the buyer. A flow can draft a follow-up, assemble a brief, or flag a slipping deal for a rep — but reconnecting with the customer stays human.