Build a flow
1
Describe it
Open Flows > All flows. Under “Describe the flow you want to build”, type what you want. For example: “When a deal moves to Negotiation, check that we have an economic buyer, and tell me if we do not.”
2
Choose the trigger
Starts sets the trigger. Leave it on Let Doris choose, or select a trigger.
3
Choose who it runs for
Admins also see for. Just me builds a personal flow. Whole company builds a company flow. Members always build personal flows.
4
Start the build
Select Build flow. The canvas opens.
5
Work with Doris
The conversation with Doris is on the left. The flow diagram is on the right. Doris proposes steps. Accept, change or reject each proposal. Continue until the diagram does what you want.
6
Review it
Select Review & test flow in the conversation, or Review flow at the top of the canvas. Doris checks the flow and opens the review.
7
Test it
Select Test flow. Doris runs the saved flow against real data. “No notifications will be sent and no records will be changed.”
8
Activate it
Select Activate for me or Activate for workspace. The flow runs on the next matching trigger.
The canvas
The canvas has two parts:- The conversation is on the left. This is where you edit the flow. Tell Doris what to change. You do not drag steps or fill in forms.
- The diagram is on the right. It shows the trigger and then each step in order. Select a step to see what it does. Doris then shows “Selected:” and the step name in the conversation.
- Apply proposal saves the change to your draft.
- Revise proposal lets you say what is wrong. Select Send revision to get a new proposal.
- Discard proposal removes the proposal. Your draft does not change.
Steps
Doris builds a flow from a fixed set of steps. Each step does one job.Read
Find record loads one deal, person or meeting with related data. List records and Count and group records work across many records. Format results turns results into a table, stat tiles or key points.
Reason
Compose text writes from the data the flow already has. Analyse records looks further into your Doris data. It can only read.
Decide
Continue if stops the flow when a condition is false. It can also send the flow down one of two named paths.
Write and notify
Notify person alerts the record owner, or the owner and their managers. Other steps save an output inside Doris, write to your CRM, or read from or act on a connected account.
Connected accounts
Some steps read from or act on an account outside Doris. Above the composer on All flows, a control shows how many integrations are connected. Select it to open Flow integrations. Select Connect to connect an account. Then any flow can use it. If an integration is not ready yet, select Request sooner. A Slack or Teams channel is different. It is where a Notify person step sends its alert, so you add it on that step. If you ask Doris to notify a channel that is not set up, a field above the message box asks you to “Paste the webhook URL”. See Slack & Teams notifications.The review
The review shows “Ready to activate?” and three sections:- Who it runs for
- When it starts
- What it does, with a label for each effect the flow has
Human approval
A step that writes to your CRM or acts on a connected account needs approval. The review then shows “Human approval stays in control”. Doris prepares the change, and a person approves it before Doris writes it. Notify person alerts only people in your workspace: the record owner, or the owner and their managers.Who can activate
- Any member can activate a personal flow.
- Only an admin can activate a company flow. A member sees “A workspace admin must publish this flow.”
Testing
Test flow runs the saved version of your draft. The dialog shows “Test only”: no notifications are sent and no records change.- For an event trigger, “Choose a recent example” lists recent matching events. Select one, then select Start test.
- For a schedule trigger, Doris tests as you, with today’s data.