Skip to content
English
Contact us Sign in
  • There are no suggestions because the search field is empty.

Connections' execution order

Learn how module and global connections are executed

It is important to know the connection execution order to understand how the bot decides what to do next.

There are 2 types of connections:

  • Module connections – defined inside individual modules. They handle context‑specific logic
  • Global connections – defined at the bot level (Bot Settings). They catch universal intents or conditions and provide cross‑module behavior.

Connection Execution Rules

  • All connections are evaluated one by one
  • Execution stops immediately when a matching connection with the action “Go to” is found
  • If no “Go to” action matches in a module connections:
    • The bot may proceed to global connections (depending on settings)
    • Or go directly to fallback.

See the diagram below that illustrates this process.

Skip global connections

When checked, the execution goes directly to the fallback.

Don’t wait for user’s input

When a module has “Don’t wait for user’s input” checked and the module does not have any set variable or webhook connections, the global connections are skipped. This is an optimization to avoid unnecessary global connections runs when the bot state hasn’t changed. 

Fallback

  • Fallback can be:

    • Module‑specific, or
    • Default fallback defined in Bot Settings
  • Module‑specific fallback overrides the default fallback when defined.