🌐Global nodes

The main purpose of global nodes is to reduce nodes with repeated settings in a flow, such as "contact idle with no interaction" or "did not hit any node."

By centrally handling these common scenarios, you can reduce additional setup and maintenance costs, while improving the efficiency and consistency of overall flow design.

Global Node Feature Description

Currently, global nodes include the following two types:

1. Contact idle with no interaction When a contact has not interacted within the specified time, the system will automatically trigger the default action to prevent the flow from being interrupted.

2. Did not hit any node When the flow reaches the end and does not meet any node conditions, the system will perform subsequent actions according to the default logic.

Global Node Trigger Limitation Description

Global nodes may not be triggered in the following scenarios:

The script does not return to any event node at the end

If the flow directly exits the script, it is equivalent to the flow ending, and the global node will not be executed at this time.

Example

When a contact ultimately leaves the flow because the flow did not connect to any event node, but instead exits via "Leave" or ends due to no matching node, the global node will no longer be triggered.

The event node has a flow idle condition set (limited to "contact idle with no interaction")

If the returned event node or its same level has "when customer flow is idle" set, to avoid conflicts, the flow setting will take priority. The global node's "contact idle with no interaction" will not be triggered, even if the time settings are different.

Example

When a contact's flow finally stays at the "Wait to send message" node, and there is also a "when customer flow is idle" setting at the same level, the system will prioritize that flow setting. Therefore, the global node's "contact idle with no interaction" will not be triggered.