What happens when you generate
The prompt is assembled
EDGR gives the model the catalog of available nodes with their fields, the customer fields you can reference with
{{customer.*}}, and the workflow currently on the canvas.The graph is compiled
A graph with a cycle, a missing field or a bad node reference is rejected and nothing is applied.
Writing the prompt
State the goal, then number the steps, then say what each branch does. The model follows an explicit sequence far better than it infers one.Name the goal
“3-step cold outreach for fintech leads, aiming at a 5% reply rate.”
Number the steps
One step per line, in order, including the waits.
Spell out the branches
“If they reply, hand off. If they clicked but did not reply, wait 5 days then follow up. If no opens after 7 days, cooldown.”
Point at variables
“Personalize the subject by industry. Mention a use case for
{{customer.country}}.”Example prompts
Steering the generator
The instructions the model receives come from a prompt template namedflow-generator. Create a template with that name under Templates and it overrides the default — which is how you push the generator toward short flows, email-only designs, or your own house style.
After generating
The output is a skeleton. Before activating:- Read the subject and body on every messaging node and rewrite them in your own voice.
- Swap inline bodies for template references wherever the content is reused.
- Replace the placeholder credentials with real ones.
- Adjust the Wait durations for the audience’s timezone.
- Clear the compile errors.
- Run it against one or two customers.