Automations · Nodes · action

Send In-App Chat interactive

action.appchat_send_interactive · action

Send reply buttons or a list (same shapes as chat).

When to use

  • Send reply buttons or a list without waiting (advanced graphs).
  • Pair with Wait for interactive reply when you need a customer tap next.

Configuration

FieldRequiredNotes
accountIdnoChannel account; leave empty to use context when available
interactiveTypenobutton (reply buttons) or list
bodyTextnoMessage body; expressions allowed
headerTextnoOptional header (list); expressions allowed
footerTextnoOptional footer (list); expressions allowed
listButtonLabelnoCTA label on the list message
buttonsnoReply buttons: id (static) + title (max 3)
sectionsnoList sections with rows: id (static), title, optional description
interactivenoOptional power override — prefer buttons/sections in the portal

Inputs

Upstream node output and execution context (contact, account, variables).

Outputs

messageId, interactiveType, optionIds, bodyText, account/contact fields for downstream Wait or expressions.

Execute step (editor)

Eligible?Notes
LimitedDry-run only — no live send. Use Test run / Run now for delivery.

See Test, Execute, debug, listen and limitations.

Common errors

SymptomCauseFix
Interactive wait never resumesCustomer sent free text, or wrong contact/outbound correlationOnly button_reply / list_reply resume; set expected outbound message id when using wait-only.
INTERACTIVE_WAIT_CONFLICTAnother interactive wait is already open for this contactWait for the other run to finish or time out before opening another Ask/wait.
Send failed on Test/RunOutside window, bad template, or missing contactUse template outside window; ensure contact/account in context.
Execute succeeds but nothing deliveredExecute is dry-run for channel sendsUse full Test run / Run now.

Example

Message-received trigger → Send interactive → optional Wait for interactive reply → Test with a contact inside the WhatsApp window.

Related