Nected Docs
Try Nected For Free
  • 5 min QuickStart Guide
  • Getting Started
    • Introduction
    • Core Concepts
    • Use Cases
    • Tech Architecture
    • FAQs
  • INTEGRATIONS
    • Overview
    • Integrations Libraries
      • PostGres
      • MySQL
      • Oracle
      • MS SQL Server
      • Snowflake
      • MongoDB
      • RedShift
      • REST API
      • Google Sheets
      • Slack
    • Managing Integrations
  • DATASETS
    • Overview
    • Managing Dataset
  • Rules
    • Overview
    • Rule Types
      • SimpleRule
      • DecisionTable
      • Ruleset
      • Rule Chain
    • Rule Conditions
    • Rule Actions
    • Concepts
      • Rule Result
      • Test & Publish Rules
    • Add Input Attributes
      • JSON Input Attributes
      • List Input Attributes
  • Triggers
    • Trigger Rule via API
    • Trigger Rule via WebHook
    • Trigger Workflow via API
    • Trigger Workflow via WebHook
    • Scheduler
    • Rule Response Format
  • Workflow
    • Overview
    • Managing Workflow
    • Add Node
      • Action Nodes
        • Rule Node
        • Workflow Node
        • Custom Code Node
        • Database Node
        • REST API Node
      • Control Nodes
        • Loop Node
        • Delay Node
        • Response Node
        • Set Variables Node
        • Switch Block
    • Test & Publish Workflows
  • CODE AND DATABASE QUERIES
    • JavaScript Editor
    • Formula Editor
    • JSON Editor
    • List Editor
    • Excel-like Function
  • Embedded System
    • White-Labelling
    • Embeddable View
  • Self Hosting
    • Overview
    • Infrastructure Sizing
    • New Installation
      • Docker
      • Kubernetes
        • Set Up Kubernetes Cluster on AWS EKS
    • Additional Configuration
      • High Availability
      • Email Setup Guide
    • Upgrade Nected Version
  • Security
    • API Authentication
      • OAuth as part of Authentication under REST API
    • Role Based Access Control (RBAC)
    • SOC 2 Type 2, GDPR, ISO Compliance
  • Audit
    • Audit Trail
    • Approval Flow
    • Version Control & Rollback
    • Import/Export
  • Management API
    • Audit Log API
    • Global Variable API
  • References
    • Attribute Library
    • Global Variables
    • Pre-Configured Tokens
    • Pre-Configured Operators
    • NULL Value Handling/Behavior
    • Troubleshooting Errors
      • Multiple Tabs/Users Edits
      • Limits in Nected
    • Allowed Status Combinations
    • Environments
    • Usage Widget
    • Gen AI
  • ACCOUNT SETTINGS
    • Workspace Setting
      • Date Format and Timezone Settings
Powered by GitBook
On this page
  • Functionality
  • Integration of Delay Node in Workflows
  • Conclusion
  1. Workflow
  2. Add Node
  3. Control Nodes

Delay Node

PreviousLoop NodeNextResponse Node

Last updated 1 year ago

The Delay node is a crucial tool in workflow design, allowing for the introduction of pauses for specified durations. This feature is particularly valuable for timing-based operations and rate-limiting API calls.

Functionality

  • Pausing Workflows: The primary function of the Delay node is to pause the execution of the workflow for a specified duration.

  • Timing-Based Operations: It enables workflows to wait for a specific period before proceeding, which is useful for tasks that require timing precision.

  • Rate-Limiting API Calls: Delay nodes can be employed to control the rate at which API calls are made, preventing excessive requests within a short timeframe.

Integration of Delay Node in Workflows

  1. Click on + icon and add the delay node from the list of available nodes.

  2. Configure the Delay node by selecting available options from the Action menu.

The list of three options are:

  1. Immediately: it delays for milliseconds.

  2. After Time Interval: it gives us the delay interval of minutes, hours, days, and weeks.

  3. At Specific Time: it provides the Date and Time option for how long the delay should last.

Incorporating Delay nodes into workflows involves placing them strategically where pauses are required, ensuring smooth and controlled execution.

Note: A delay node is automatically added in case of a response node, and there is no option to test the delay node, only the save option is available.

Conclusion

The Delay node provides a simple yet powerful mechanism for introducing pauses in workflows, enabling precise timing control and effective rate-limiting of API calls. By leveraging Delay nodes effectively, users can enhance the efficiency and reliability of their workflows.