Supabind

Utilities

Control flow, timing, and data inside a workflow-branch on a condition, call an external API, wait before continuing, notify someone, edit fields on the fly, or respond to a webhook caller directly.

Quick Navigation

• Delay• If/Else• HTTP Request• Send Notification• Set Variable / Edit Fields• Respond to Webhook

Overview

Utilities nodes don't move files in or out of the workflow-they shape how the workflow behaves. Use them to pause execution, branch logic, reach out to other systems over HTTP, alert a person, adjust the JSON output as it passes between nodes, or send a custom response back to whoever triggered a webhook.

Delay

Pause the workflow for a set amount of time before the next node runs.

Delay

Wait before continuing

Steps

  1. Add the Delay node between two steps that need a gap-for example, after an export and before a notification.
  2. Set the wait duration in seconds, minutes, or hours.
  3. Save the workflow-every run will pause for that duration at this point.

A Delay node counts against the workflow's total run time-long delays can make a run look "stuck" in Execution History until it completes.

If/Else

Branch the workflow down one of two paths based on a condition you define.

Steps

  1. Add the If/Else node after the point in the workflow where you need to branch.
  2. Set the condition-for example, checking a variable set earlier by Set Variable / Edit Fields.
  3. Connect the If output to one chain of nodes and the Else output to another.

Only one branch runs per execution-use this to skip a sync step entirely when a file doesn't meet your condition, instead of syncing empty or invalid data.

HTTP Request

Call an external API from inside the workflow and use its response in later steps.

Steps

  1. Add the HTTP Request node where the API call should happen.
  2. Set the method, URL, headers, and body-use {{ variables.name }} to insert values from earlier nodes.
  3. Feed the response into a Set Variable / Edit Fields node or an If/Else condition downstream.

Send Notification

Send an email notification at any point in the workflow-often used to confirm a run finished or flag that something needs attention.

Steps

  1. Add the Send Notification node, typically as the last step in a chain or branch.
  2. Enter the recipient, subject, and message body-workflow variables can be included in the message.
  3. Use Run Now to confirm the notification arrives as expected.

Pair this with an If/Else node to only notify someone when a condition is met-for example, when a sync step reports failures.

Set Variable / Edit Fields

Set fields on the JSON output as it passes through the workflow, and optionally store values as workflow variables for later nodes to reference.

Steps

  1. Add the Set Variable / Edit Fields node wherever the output needs adjusting.
  2. Add or edit fields directly on the JSON output, and check store as variable for any value you want to reuse later.
  3. Reference stored variables downstream using {{ variables.name }}, including in an HTTP Request body or an If/Else condition.

Respond to Webhook

Return a custom HTTP response to whatever called the workflow's webhook trigger-only relevant for workflows that start with a Webhook trigger node.

Steps

  1. Add the Respond to Webhook node at the point where the calling system should get a response.
  2. Set the status code and response body-use workflow variables to echo back data from earlier steps.
  3. Place it after the steps that must finish before responding, since anything after it still runs, but the caller won't wait for it.

If a workflow triggered by webhook never reaches this node, the caller will receive a default response once the run finishes or times out.

Was this article helpful?

Need More Help?

If a branch isn't taking the path you expect, an HTTP call is failing, or a webhook response isn't coming back correctly, our support team is here to help.

Contact Support