How to define global actions in Builder

An action represents a task that must be performed on any block of the Builder, either before sending the contents of a block (input action), or immediately after sending the contents (exit action). There are several actions available in the Builder, such as HTTP Request, Event Log, JS Scripts among many others.

Actions can be defined locally, within the scope of a Builder block or globally. A global action will be performed in conjunction with the user inputs present in your bot's flow.

Global input actions are performed immediately after the state machine (Builder) resumes execution because it has received input from the user. Global exit actions are performed immediately before the state machine stops executing to wait for new user input.

To define a global action, access your bot's Builder Settings and choose the Global Actions option.

When to use global action?

Think about using global actions for tasks that need to be performed at each interaction (entries responsible for receiving messages) from your users.

An example of using this type of action is the event registration for each of the blocks responsible for receiving content from users. In this scenario, it is possible to use the {{state.name}} variable to ensure that all events take into account the name of the block associated with the entry.