Docs

The four actions

A new chat shows the four actions as cards. The same actions, plus two more pictures, are in the Actions menu at the bottom left of the message box. You can also type any question. Every action sends the flow as last saved and asks for a particular kind of answer.

Overview

A summary of 200 to 400 words: what the flow is for, what triggers it, the main paths named by their outcome, which objects it writes to, what it calls outside Salesforce, and anything worth knowing before you change it.

Draw this flow

A flowchart of the main paths, with steps merged and labeled in everyday words. In the Actions menu, this picture is Draw main paths, and there are two more:

• Draw one element: pick an element to see what leads into it and where each of its outcomes goes.
• Draw every element: every element, labeled by its API name. On a flow with more than 100 elements, the panel asks first. Drawing every one can take a couple of minutes.

Open in Excalidraw opens excalidraw.com with the picture on your clipboard; paste it there to edit it. You can also copy the Mermaid text to use the picture in another tool. A picture shows this flow only. What happens inside its subflows or other automation isn't drawn. Check the details in Flow Builder before you rely on a picture.

Document this flow

A full write-up: a metadata table, purpose, trigger, resources, a walkthrough in the order the flow runs, a decision matrix, a table of data operations, fault handling, and assumptions and unknowns. Under the answer, you can copy it or download it as a Markdown file. On a large flow, it can take a couple of minutes.

To save the flow's metadata as a JSON file, choose Download JSON from the ⋮ menu at the top of the panel.

Explain an element

Choose Explain an element and pick from the list, or pick an element from the Outline on a new chat. The explanation starts at once. It gives the element's type, label, and API name, what leads into it, the inputs it reads, its logic with every condition and formula quoted exactly as saved, where each outcome goes, and its fault path, or that it has none.

What it won't do

It never edits your flow. Ask what you'd change, and it describes the change and the element it belongs in. It sees the saved flow and nothing else in your org. Check any suggestion against the rest of your org before you make the change.

Previous: Getting started · Next: How answers stay grounded · All docs