Automation settings

A flow can be drawn correctly and still behave wrongly: the same campaign goes to one person five times, or a customer gets cut off mid-answer. The cure for those is not on the canvas but on the Settings tab. This article covers the four fields on that tab and the deletion section, one by one.

⚠️ Note: Anyone can view this tab, but the fields are only editable for roles with edit rights. On an automation sitting in the trash the fields are disabled too.

Where the Settings tab is

Open the automation and switch to Settings in the tab row. You will see two sections: Settings (name and folder) and Behaviour. If you have the rights, a Delete automation section sits at the bottom of the page.

Your changes are not saved automatically: after editing the fields you have to press Save at the bottom. Saving shows a Settings saved. notice.

💡 The settings on this tab are not part of the flow graph. Changing the name, folder, re-entry rule or interruptibility needs no Publish; it takes effect the moment you save. The version number does not increase either.

Name

The name that appears in the list, in the logs, in the target list of the Another flow step, in the Also start field of global rules and in the Start an automation field of sequences. It can be 80 characters at most.

A naming pattern that works: topic — channel — state. "Price question — Instagram", "Comment to DM — summer campaign". In the Logs screen, a good name is the only way to find the right automation among dozens of rows.

Folder

The dropdown where you pick which folder the automation sits in. No folder is the first option. A folder only organises the view in the list; it has no effect on how the flow runs.

You can do the same from the row menu in the automations list (Folders, bulk actions and the trash).

Can the same person enter again?

This is the most important setting on the tab: it decides how often a person can enter this automation. There are four options:

• Every time — The flow restarts whenever a trigger matches. Correct for ordinary question-and-answer flows.