Skip to Content
CraftBot Docs v1 — internal preview
Recipes & Bot EngineNode referenceQuick Links

Quick Links

The Quick Links node sends a message with one or more tap-to-select quick-reply buttons. Unlike a URL-link button, tapping one of these advances the flow down that button’s port — Quick Links is a branching node, not an informational link list.

Heads-up on the name. “Quick Links” describes the WhatsApp / channel primitive these render as (a short row of tap-to-select buttons). They aren’t web URLs — see Button for the full-fat branching button variant and Message when you want to send a clickable URL alongside text.

Configuring the node

  1. Drop the Quick Links node from the Messaging category onto the canvas.
  2. Open the configuration drawer:
    • Prompt (EN / AR) — bilingual message body shown above the button row.
    • Links — repeater of buttons. Per row:
      • Key — short identifier (e.g. track, contact). This is the port name on the canvas; wire each port to its downstream branch.
      • EN label / AR label — bilingual button text shown to the customer.

Output ports

  • One port per configured link, with the port name equal to the link’s key.
  • fallback — fires when the customer’s reply doesn’t match any button’s key, English label, or Arabic label (e.g. they typed free-text instead of tapping a button).

How the reply is matched

The runtime matches the customer’s inbound message against each button in order:

  1. Key match (lowercased, exact).
  2. English label match (lowercased, exact).
  3. Arabic label match (exact match, RTL-aware).

The first button that matches wins. If nothing matches, the session falls to the fallback port; if that port is unwired, the session escalates.

When to use it

  • Top-of-conversation menus with a handful of common choices (“Track order”, “Talk to an agent”, “Change plan”).
  • Quick yes/no decisions where the customer should tap rather than type.
  • Three-option follow-ups after a Message node.

When not to use it

  • You want to send a clickable URL the customer opens in their browser — use a Message node with a URL in the body instead.
  • You have more than a small handful of options — use List instead. WhatsApp’s quick-reply primitive caps the row at a small number of buttons; List handles longer menus.
  • The options come from a backend lookup at runtime — Quick Links button labels are static. For dynamic options, use a List node populated from a previous API call’s response.

Notes

  • The customer’s reply must be a tap or an exact label match. Free-text variants (“track my order plz”) fall through to fallback; if you expect that traffic, follow this node with an Intent Route on the fallback branch.
  • Channels surface the buttons differently — WhatsApp renders them as quick-reply chips, web widgets render them as inline buttons. Behavior on each channel follows that channel’s button limits.
Last updated on
MessageQuestion