Back to Integrations
Logic

Wait

The Wait node introduces intentional pauses into your workflow. Sometimes you need to give an external API time to process a file, or you want to delay an automated follow-up email by 3 days. This node suspends execution efficiently and resumes exactly when instructed.

Wait
Core / Logic

What can you do with Wait?

Hard Resumed Delays

Pause the execution for a set duration (e.g., exactly 5 minutes, or up to 30 days) allowing external systems to process data before safely resuming the sequence.

Database Throttling

Implement micro-delays (e.g., 500ms) between loop executions to throttle outbound HTTP traffic and meticulously respect strict 3rd-party API rate limits.

Webhook Callbacks

Suspend execution indefinitely until a specific asynchronous Webhook callback is received, perfectly syncing with slow external human-approval systems.

Detailed Usage & Configuration

The Wait Node operates entirely on backend orchestration, halting your active workflow sequence deliberately and precisely. It supports both set time durations and advanced asynchronous callbacks.

1. Static Time Delays

The most common usage incorporates a Set Duration. For example, after sending an automated "Welcome" email, you can configure the Wait Node to pause for exactly "3 Days" before dispatching the follow-up email. The execution sleeps seamlessly in the database without consuming precious RAM or CPU threads.

2. Human-in-the-Loop (Webhook Approval)

For operations requiring manual oversight (e.g., a manager approving a high-value purchase or reviewing a generated document before sending), the Wait node excels via its Webhook Approval mode.

  • How it works: The node pauses the workflow indefinitely and exposes a unique, secure Resume URL dynamically generated for that specific run.
  • Routing the Approval: You map this dynamic {{ $execution.resumeUrl }} variable into an upstream notification node (like Slack, Discord, or Gmail). The manager receives a message like: "New Purchase Request: Click here to Approve".
  • Seamless Resumption: The moment the manager clicks that link, the nLink core engine intercepts the Webhook, validates the secure token, wakes up the sleeping workflow, and instantly resumes execution down the subsequent nodes in the graph.
đź’ˇ Enterprise Trick: You can pass custom form data (e.g., ?decision=rejected) through the Resume URL click. The workflow wakes up carrying this query parameter in its payload, allowing you to attach an If/Else Node immediately after the Wait node to create dynamic "Approved" vs "Rejected" pathways based entirely on the manager's click!