Wait for data: the flow resumes when an external service sends an event

The block connects a flow to the outside world: the bot has issued an invoice or submitted a request — and waits until a third-party service (a payment provider, a CRM, your website) posts an HTTP request to a receiver from the "Data intake" section. For the event to find this exact conversation, the block and the receiver compute the same key — for example, the order number. The customer sees nothing meanwhile: the bot simply stays quiet and continues on its own once the data arrives or the deadline passes.

Data receiver

Which receiver from the "Data intake" section to listen to. The external service must post the event to that receiver's URL. If you have no receivers yet, create one in "Data intake" first.

Wait key (template)

A template for the value that matches the event to this conversation — usually a variable holding the order or invoice number, e.g. {{invoice_id}}. At pause time the template renders into a concrete value; the receiver computes the same key from the incoming data, and a match resumes the flow. Up to 255 characters; the key must be unique per run.

How long to wait

The maximum waiting time — a number plus a unit (minutes, hours or days), from 1 minute to 30 days. If the event never arrives, the flow takes the "timeout" branch — typically a "payment not received" message or a reminder.

The bot issues an invoice and reaches a "Wait for data" block: receiver — "Payments", key — {{invoice_id}}, limit — 7 days. After the payment, the provider posts an event with that invoice number to the receiver — the flow instantly continues down the "received" branch and sends a link to the private channel. If a week passes with no payment, the "timeout" branch politely reminds about the invoice.