Action

Wait for reply

Pause for missing info, resume on reply

The Wait-for-reply node pauses a job when something's missing, waits for the customer to send it, and then picks the same job back up where it left off — no new submission, no lost context.

How it works

Sometimes a job can't finish because a piece is missing: a statement, a signature, one more month of records. Wait-for-reply handles that gap. It parks the job in a 'needs info' state and produces a unique reply address, so whatever you send the customer next can invite them to respond with what's missing.

It doesn't send the message itself — you wire a notifier after it (an email, an SMS, a WhatsApp) and point that message's reply-to (or a link) at the address this node hands you. That keeps the choice of channel yours: the same pause works whether you're chasing documents by email or by text. When the customer replies with the file attached, it's added to the very same job and the workflow resumes from the top, re-reads the now-complete set, and carries on.

Pair it with a Validate or File router step that detects the gap, and you have a hands-off follow-up loop: the system asks for exactly what's short, waits, and finishes the moment it arrives — instead of a person noticing, emailing, and re-keying a fresh submission.

Common use cases

Real situations where this node earns its place in a flow.

Chase a missing statement automatically

When a validation step finds a gap, park the job and email the applicant for exactly what's short; their reply resumes the same job.

Collect a signature page later

Pause a job that's ready except for one missing page, ask for it, and finish the moment it arrives — no re-submission.

Follow up over any channel

Wire the pause to an SMS or WhatsApp instead of email when that's how your customers actually respond.

Wait for reply in a workflow

A simple example of where this node sits in a flow.

Application Arrives by email Extract PDFs into structured data Validate Complete? valid / missing Wait for reply Park until docs arrive Ask for documents Reply resumes the job

What you set up

  • Put it on the 'missing' path of a Validate or File router step that detected the gap.
  • Wire a notifier after it (Email, SMS, WhatsApp) and set that message's reply-to or link to the resume address this node emits.
  • Optionally set how many times to re-ask before giving up, and a note describing what you're waiting for.

Common questions

Does it send the request email itself?

No — on purpose. You wire a notifier (email, SMS, WhatsApp) after it and point that message's reply-to or link at the resume address this node gives you. That way the pause works for any channel, not just email.

Does the customer's reply start a new job?

No. The reply attaches to the same job that was waiting and resumes it from the start, so all the earlier context and files are kept — no duplicate submission to reconcile.

What if they never reply?

You can cap how many times it re-asks, and abandoned parks are settled automatically after the reply window closes, so nothing sits waiting forever.