Advanced and visual flows

simple automation rules run one action when one trigger matches use advanced or visual flows when the automation needs more structure when to use the visual editor use the visual editor when the rule needs multiple steps branching waits more than one message ai handoff plus follow up actions data updates after a message or template a custom sequence that should be easier to inspect visually from the automation builder, choose build a visual flow or use save and open editor what changes after opening the visual editor after a rule uses the visual editor, the simple form shows it as a visual editor flow the rule can still be edited, but the flow steps are managed in the visual editor the simple form summarizes the starting step and the number of runnable steps advanced triggers advanced triggers are useful when a rule needs more than the simple trigger picker can express use advanced triggers for multiple start triggers exit triggers custom data mappings more control over event payloads when advanced triggers are managing a rule, the simple form shows a manage triggers action instead of replacing the trigger configuration inline keep flows understandable give every advanced automation a plain language name and note use names that describe the outcome, not the internal mechanism good examples assign enterprise leads to sales move read reminders to follow up send payment confirmation from api onboarding drop off recovery avoid names that only describe implementation details, such as “webhook rule 3” or “template automation ”