Skip to main content
Flows are the automations Doris runs in your account. A flow starts on a trigger, works through a sequence of steps, and produces something: a CRM update, a brief, a notification, a report. The Flows page is where you build new ones and manage the ones already running.

​
When to use Flows

  • You want Doris to do something repeatable that you currently do by hand
  • You want to know what automations are running in your workspace
  • You need to check whether a flow is on, when it last ran, and what it produced
  • You want to control which flow alerts reach you
  • You want to roll a flow back to an earlier version

​
How to use Flows

1

Build a flow

Describe what you want in the composer at the top of the page. Doris builds it with you on the canvas. See Flow builder for the full walkthrough.
2

Browse what is running

The three cards below the composer split your flows into Personal, Company, and System. Open one to see the flows in that scope.
3

Find a specific flow

Use search and the filters for scope, status, trigger, and output type. This is how you find the automation responsible for a particular email, brief, CRM update, or report.
4

Open a flow

A flow’s page shows its trigger and its step diagram, so you can read what starts it and what each step does.
5

Check its runs

Open Flow runs to review recent executions. Filter by flow or status, then expand a run to see each step and what it produced.
6

Control your alerts

Use the alerts control on a flow row to choose whether its notifications reach you, whether they arrive by email, and which chat channels it posts into.

​
Flow scopes

Personal

Runs for one person, over their own records. Any member can build and activate one.

Company

Runs across the workspace. Admins build, activate, and turn these off.

System

Doris-managed flows that work the same way for every customer. You turn them on and off; you do not edit them.
If a company flow covers the same ground as your personal one, the company version wins. Your personal flow is kept but stops running, and Doris tells you when that happens.

​
Flow concepts

  • Trigger — The event or schedule that starts the flow. See Triggers
  • Steps — The sequence Doris works through after the trigger fires
  • Effects — What the flow changes outside itself: CRM writes, notifications, documents. Anything that writes outside Doris sits behind a human approval boundary
  • Output — The email, brief, CRM update, or document a run produced
  • Run — One execution of a flow, with its status and per-step detail
  • Version — A published revision of a flow. Republishing creates a new one, and you can roll back to any earlier version

​
Alerts

Flows that notify people give you control over how those notifications reach you:
  • My alerts — Notifications about your own records
  • Team alerts — Notifications about your team’s records, for managers
  • Email — Whether the alert also arrives by email
  • Chat channels — Which Slack or Teams channels the flow posts into. Shown here rather than changed here: a channel belongs to the notify step that sends to it, so that is where it is added, renamed or removed

​
Versions and rollback

Every activation publishes a version. A flow’s version history shows what was published and when, and lets you roll back to an earlier version. Rolling back changes what runs from that point on; it does not undo anything past runs produced.

​
Requesting a flow

If you want an automation you would rather not build yourself, use Request a flow. Describe what you want and the Doris team picks it up.
Use Catalog to see the flow templates available. Use the composer on this page to build something specific to how your team sells.