Wait for Events and Approvals

Use a Wait node when progression depends on an outcome. Use a Delay when only elapsed time matters.

Choose the wait

• Something happens waits for an event such as a form submission, paid invoice, signed document, booked appointment, or completed task.
• Team approval waits for an approval or rejection.
• Client completes portal step waits for the configured client step.

Choose the matching event or preset, then configure the relevant record or correlation value. This connects the incoming event to the correct waiting run. For example, an invoice wait must match the intended invoice, not any invoice in the workspace.

Configure the outcome paths

Connect the available result paths and configure a timeout when the process needs a follow-up if no response arrives. Review both the successful outcome and timeout or rejection path in the builder.

Sending a form or document and waiting for its response are separate actions. Preserve the response reference provided by the preceding action when configuring the wait.

Review a waiting run

Open run detail to identify the waiting step and required outcome. Check that the associated form, document, invoice, or client step produced the expected event before retrying or starting another run.

A simulation checks configuration; it does not obtain a real approval, signature, submission, or payment.

See Connect Workflows and client flows for starting a flow or releasing a held step.