Add a Note action

Add a Note action when you want to document the workflow design for other Experience Designers.

A Note sits on the canvas as documentation only. Notes never execute, aren't visible to employees, and don't produce runtime output. Use them to explain decisions, constraints, or handoff instructions that might otherwise be difficult to understand in a complex workflow.

For an overview of all workflow actions, including Note, see Understand workflow actions. For a summary of Note behavior, see Workflow actions reference.

Before you begin

Make sure you have:

A workflow open in the designer.
The Experience Designer or Tenant administrator role.
The guidance you want other designers to see, such as why a Condition exists or which system owns a downstream event.

When to use a Note action

Use Note when you need to:

Document design decisions next to the relevant actions.
Explain complex Condition or Process List logic.
Leave implementation or ownership notes for maintainers.
Capture assumptions that aren't obvious from the canvas alone.

Open the workflow in the workflow designer.
From the Actions palette, add a Note action.
Place the Note on the canvas near the actions it describes.
Select the Note to open the editor.
In Note text, enter the documentation other designers should read.

For example:

Default branch skips Create Job Profile when the item is not an executive profile.

Changes save automatically.

What Notes do not do

Expectation	Behavior
Run during a workflow	Notes never execute
Appear to employees	Notes aren't employee-visible
Produce outputs	Notes have no runtime output
Replace Agent messages	Use Agent for employee conversations
Store runtime data	Use Set State or action outputs

Writing tips

Keep each Note short and specific to the nearby actions.
Refer to concrete Names, branch names, and event names rather than using vague reminders.
Explain why a design decision was made when that isn't obvious from the workflow.
Update or remove Notes when the design changes so the documentation stays accurate.

Next steps

Test the workflow. Notes don't affect employee-facing run behavior.
Publish the workflow when the design is ready.

Related to