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
  • Purpose of Action Nodes
  • Configuration of Action Nodes
  1. Workflow
  2. Add Node

Action Nodes

PreviousAdd NodeNextRule Node

Last updated 1 year ago

Action Nodes are the workhorses of the Nected workflow editor. They perform the primary operations and tasks within a workflow, executing specific functions that drive processes forward. Here’s a closer look at the role of Action Nodes:

Purpose of Action Nodes

Action Nodes are designed to carry out a wide array of tasks ranging from data manipulation to communication with external services. Each Action Node type corresponds to a particular action such as retrieving data, sending notifications, processing information, or integrating with other software systems.

Types of Action Nodes

  1. Rule Node: introduce decision-making capabilities into the workflow. They evaluate conditions based on the data and direct the workflow path accordingly, triggering different actions based on the results of the evaluation.

  2. Workflow Node: allow the inclusion of sub-workflows within a primary workflow. This helps in modularizing complex processes and reusing existing workflows, thereby creating an organized, maintainable structure.

  3. Database Nodes: include a variety of nodes that allow you to interact with different types of databases like MySQL, PostgreSQL, MS SQL Server, MongoDB, and Redshift. Operations can range from querying data to performing insertions, updates, and deletions.

  4. API Nodes: are used to connect with external APIs, enabling the workflow to send requests and receive responses from other services over the web. REST API nodes, for example, can trigger actions on web services or retrieve data from them.

  5. Code Execution Nodes: offer a flexible environment within the workflow for writing and executing custom scripts. This allows for custom logic that can’t be captured with pre-configured nodes.

Configuration of Action Nodes

Configuring an Action Node is pretty straightforward, which is discussed in the Overview Page under th e section "".

In summary, Action Nodes in Nected's workflow editor provide the functionality necessary to execute the steps of a workflow. Properly configured, these nodes can automate complex sequences of tasks, integrate with databases and external APIs, and perform custom processing, thus enabling a high degree of automation and efficiency in various business processes.

Rule nodes
Workflow nodes
Database nodes
API nodes
Code nodes
Add Node