Wait & Resume Node

Overview

The Wait & Resume node allows a workflow to pause execution and resume later based on time-based or event-based conditions. It succeeds the earlier Delay node and introduces the ability to wait for an external webhook or API signal before continuing.

This makes it suitable for building long-running or asynchronous workflows such as drip marketing, job scheduling, or integrations with third-party systems. It is also commonly used in scenarios that require manual intervention, such as approvals or user actions, where the workflow must pause until a person completes a required step.

It is typically placed after a trigger or a processing node to insert a controlled pause.

When to Use

• Pause execution for a set duration (minutes, hours, or days).

• Schedule workflow continuation at a specific date and time.

• Wait indefinitely until a webhook/API call signals the workflow to continue.

• Handle asynchronous processes like approvals, external responses, or user actions.

How to Add the Node?

1. Open the Workflow Editor in your Nected dashboard.

2. Click the “+” icon below or after any existing node.

3. From the Control Nodes category, choose Wait & Resume.

4. Select the Action type: Immediately, After Time Interval, At Specific Time, or On Webhook Call.

5. Configure the required fields for the chosen action type.

6. (Optional) Set advanced options such as custom parameters or auto-resume timeout.

7. Save the node and connect it to the next node in the workflow.

Input Parameters

Action

Determines how the node decides when to resume. Supported options:

• Immediately

• After Time Interval

• At Specific Time

• On Webhook Call

Action = Immediately

• The workflow does not pause and continues execution instantly.

• This option is used when you want the workflow to switch into asynchronous execution mode after this point.

• The workflow responds immediately to the trigger or API caller, while the subsequent nodes continue running in the background.

• No resumeId is involved in this mode since the workflow does not wait for any external signal.

Action = After Time Interval

• Pauses the workflow for a relative period before resuming.

• Fields:

  • Delay Unit – Minutes, Hours, or Days (Weeks are no longer supported).

  • Delay Amount – Numeric value of how many units to wait. Supports tokens from earlier nodes.

• Once the time has passed, the workflow automatically resumes from the next node.

Action = At Specific Time

• Resumes the workflow at a fixed date and time.

• Opens a date-time picker.

• Value can be hard-coded (e.g., 2025-09-03 14:30 IST) or constructed dynamically from previous variables.

Action = On Webhook Call

The On Webhook Call option pauses the workflow until an external request signals it to resume. This mode is used when the workflow must wait for user actions, approvals, or third-party system events.

API Tab

When using the API tab, you are responsible for calling Nected’s resume endpoint.

• Base URL – Pre-filled with Nected’s resume endpoint (e.g., https://nected-59.nected.io/nected/workflow/resume). This is the URL you must call to resume the paused execution.

• Authentication – Inherits the workflow’s API authentication (typically via the nected-api-key header).

• System Parameters – A resumeId is automatically generated. This value uniquely identifies the paused execution and must be included in the resume request.

• Custom Parameters – Optional. Any additional parameters you define here will be injected into the workflow context once it resumes.

• Resume on Value(s) – Optional condition. If specified, the workflow resumes only when the incoming request contains a parameter with the expected key and value.

  • Example:

    • Key: status

    • Resume on Value: approved

    • Result: The workflow resumes only if the request includes "status": "approved".

• Auto Resume Timeout – Defines what happens if no valid webhook arrives within the timeout period. You can configure:

  • Auto-resume after the timeout.

  • Close the execution after the timeout. By default, a timeout value can be set in minutes, hours, or days.

Sample request:

curl -X POST "https://nected-59.nected.io/nected/workflow/resume" \
  -H 'Content-Type: application/json' \
  -H 'nected-api-key: XXXX-XXXX-XXXX-XXXX' \
  -d '{
    "environment": "staging",
    "params": {},
    "resumeId": "{{.systemVar.resumeId}}"
}'

• resumeId is mandatory and identifies the paused workflow execution.

• environment is optional and can be used to indicate staging or production.

• params can include any custom parameters you have configured.

Webhook Tab

When using the Webhook tab, Nected provisions the webhook endpoint for you.

• You define the expected payload schema.

• Fields in the payload can be mapped to resume conditions.

• Use this option when you only need to resume the workflow without expecting a response payload.

• Use the API tab if you require a response back after the workflow continues execution.

Behaviour and Output

• State Persistence – Nected saves the current state and issues a resumeId. Time-based actions are scheduled, and webhook actions wait until a valid POST request with the resumeId is received.

• Custom Parameters – Injected into workflow context upon resumption if defined.

• Error Handling – If no webhook arrives and no auto-resume timeout is set, the workflow remains suspended indefinitely. Always configure a fallback timeout.

Comparison with Delay Node

Best Practices

• Use Webhook Resumption for Long Processes – e.g., approvals, API responses, or batch jobs.

• Set Fallback Timeouts – Always configure auto-resume to prevent workflows from hanging indefinitely.

• Capture and Pass resumeId – Store the ID in a database or send it to external systems for later use.

• Use Sleep for Short Intervals – For milliseconds/seconds, use the Sleep node instead.

Conclusion

The Wait & Resume Node is the modern replacement for the deprecated Delay Node. It supports all legacy time-based features while adding event-driven resumption via webhooks, making it more versatile for asynchronous workflows.

For short pauses where you simply want the workflow to sleep synchronously and then move forward (e.g., adding a lag between third-party API calls to handle rate limits), use the Sleep node.

For longer or conditional waits, where the workflow should enter an asynchronous state and resume later based on time or external events, always prefer Wait & Resume.