GetMyBot Knowledge Base

Reaction Links

How reactions call each other: 12 link mechanisms, incoming and outgoing transitions.

On this page

Reactions rarely work in isolation: they call each other through buttons, chains, "else" branches, dialog replies, and more. Reaction links show this transition graph: for any reaction you can see where it leads (outgoing links) and where it is reached from (incoming links). This helps you navigate large scenarios and safely delete reactions.

What a link is

A link is a directed transition from one reaction to another, tagged with the mechanism that produced it. The platform traverses the full reaction and collects all outgoing transitions, discarding self-references and empty targets and collapsing identical transitions. The link list is available from the reaction editor and via API: GET /api/bots/{id}/reactions/{id}/links.

Incoming and outgoing

  • Outgoing: which reactions the current one references (its buttons, chains, "else" branch, etc.).
  • Incoming: which reactions reference the current one. Useful before deletion: if something links to this reaction, deleting it will break the scenario.

12 link mechanisms

  • Button (button): an inline button of type "Trigger reaction" opens another reaction when tapped.
  • Button replace (button_replace): a button with "replace message" behavior substitutes the content of the linked reaction.
  • Dynamic button (dynamic_button): a button from a "Dynamic buttons from list" block leads to a reaction. See Dynamic buttons and parameters.
  • Reaction block (block): a message block that calls another reaction during sending.
  • Chain reaction (chain): the "Chain reaction" action launches another reaction.
  • Else branch (else): if conditions are not met, control passes to the specified reaction.
  • Web request: success (web_success): the reaction triggered on a successful web request.
  • Web request: error (web_error): the reaction triggered on a web request error.
  • Expected answer (expected_answer): the reaction that fires on a user's reply in a dialog step.
  • Answer timeout (expected_timeout): the reaction that fires if no reply was received before the timeout.
  • Next reaction (goto_next): the "Next reaction" action passes control to the next matching reaction in the list.
  • Scenario (flow): a reaction linked to the completion of a scenario (flow).

Why to look at the graph

  • Scenario navigation: quickly jump to a linked reaction without searching the list.
  • Safe deletion: see incoming links and avoid breaking transitions.
  • Audit: verify that all scenario branches lead where expected and there are no "dangling" transitions.

What's next