Wait for reply
Wait for reply lets a queue-backed bot ask a question, pause durably, and continue when that same conversation sends its next message. The answer is stored in the variable you name and the waking message is consumed by the suspended run.
Connect both outcomes
Connect Reply to the steps that use the saved answer. Connect Timeout to a reminder, cleanup, or stop step. The pending-wait row is the race arbiter, so reply and timeout cannot both run. A second message after a reply starts a normal fresh execution.
Choose a variable and timeout
Variable names start with a letter or underscore and contain only letters, numbers, and underscores. Timeouts must be longer than five seconds and no more than 30 days. Flow variables are snapshotted at suspension with the same 256 KB cap as a long Delay.
Supported channels
Telegram, Discord, Slack, WhatsApp, Messenger, and Instagram use the durable inbound-wake rail. Website bots reject this node because webchat returns each response synchronously in one HTTP request. Wait for reply is also rejected inside For Each branches.
Meta and WhatsApp windows
Keep timeouts under 24 hours on WhatsApp, Messenger, and Instagram. A user reply reopens the customer-service window, but sends attempted outside an open window still fail with the channel's normal window-closed error.
Test and monitor
Test chat pauses locally at the node. Send the next message to exercise Reply or choose Skip to timeout. Live Runs show system.wait_started, system.wait_resumed, and honest cancellation traces after replacement or redeploy.