Automations · Nodes · logic

Wait for interactive reply

logic.wait_for_interactive_reply · logic

Pause until the contact taps a reply button or list row. Free text does not resume.

When to use

  • Pause until the contact taps a button or list row (not free text).
  • Use after a send interactive node, or prefer Ask for send+wait+branch.

Configuration

FieldRequiredNotes
channelTypenowhatsapp or appchat
accountIdnoChannel account; leave empty to use context when available
timeoutSecondsnoWait timeout in seconds (default 86400)
expectedOutboundMessageIdnoOptional Engagive outbound message id to correlate the reply

Inputs

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

Outputs

After the customer taps (or timeout): replyId, replyTitle, interactiveType, inboundMessageId, outboundMessageId / messageId, timedOut. Insert value paths use nodes.{id}.*.

Execute step (editor)

Eligible?Notes
DisabledNeeds multi-branch or wait/resume context — use a full Test run.

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

Send interactive → Wait for interactive reply → If / else on replyId (or use Ask for built-in ports).

Related