Add Node
Last updated
Last updated
Adding nodes in the workflow editor of Nected is essential because they represent the individual tasks, decisions, or actions that comprise the overall automated process. By adding and configuring nodes, users can tailor workflows to fit their specific business processes, data handling requirements, and decision logic, ensuring that tasks are executed efficiently and consistently.
In Nected's workflow editor, there are broadly two categories of nodes available: action nodes and control nodes. Action nodes are responsible for performing operations such as executing code, interacting with databases, or calling APIs, while control nodes manage the flow of the workflow, allowing for responses to be set, delays to be introduced, and variables to be manipulated, contributing to the dynamic and conditional execution of the workflow.
To add nodes, follow the steps mentioned in the Overview Page under "Add Nodes"
Access 'Add Node': Click on the '+' button, to open the “Add node’ panel.
Select the Desired Node Type: From the 'Add Node' modal, browse through the available nodes. You'll see a variety of nodes, each represented by an icon and name, indicating its function.
Action Node: Action Nodes are the primary executors of operations and play a key role in handling data, making decisions, and executing processes.
Rule Node: Enables the implementation of business logic by defining conditions and specifying consequent actions based on whether those conditions are met.
Workflow Node: Allows you to embed a sub-workflow within the current workflow, facilitating modular design and reuse of common sequences of tasks.
Code Node: Provides a space to write and execute custom code within the workflow, often for data manipulation, calculations, or other logic that requires scripting.
MongoDB: Interfaces with MongoDB databases, allowing for actions such as querying, inserting, or updating documents in a collection.
MySQL: Connects to MySQL databases and performs SQL operations, such as running queries or updating records in the database.
PostgreSQL: Designed for PostgreSQL database operations. This node lets you interact with PostgreSQL for executing queries, updates, or other SQL statements.
REST API: Makes HTTP requests to RESTful APIs, enabling integration with various external services and data sources over the web.
Redshift: Specialized for Amazon Redshift, this node allows for database operations within Amazon's data warehousing service.
MS SQL Server: Enables connectivity and operations with Microsoft SQL Server, such as executing T-SQL queries and stored procedures.
Control Node: Control Nodes manage how and when actions occur, influencing the workflow’s logic and timing.
Delay: This node can be used to schedule the next steps or introduce a pause in the workflow for a specified duration, which can be useful for timing-based operations or rate-limiting API calls. Further, this can also be used after sending the response but performing some actions afterwards, to control the response time to API
Response: Sends responses back from the workflow, typically used in API workflows that need to return data to the caller. Response in the workflow is just the same as Results in the Rule. You can read more about Rule Results from here. Note: If a response node is being added in the middle of a flow, by default a Delay node will also be added right after the Response Node. This is happening because adding a response ends the flow above that node, so anything new that will be added after the Delay Node will run asynchronously within that workflow.
Set Variable: Sets or updates the value of a variable within the workflow, which other nodes can then use for dynamic data manipulation. In this node, you can set the following variables:
Boolean: A boolean variable holds a value of either true or false. It's commonly used to control flow with conditionals.
Numeric: Numeric variables store numerical values which can be used for calculations or quantitative conditions.
String: String variables hold text data, suitable for names, titles, or any other textual content.
Date: Date variables hold date and time information, useful for timestamps and scheduling functions.
List: A list variable stores an ordered collection of items, often of the same type, and can be iterated over or indexed.
JSON: JSON (JavaScript Object Notation) variables hold structured data, allowing for complex information to be stored as an object with key-value pairs.
Formula: A formula variable computes a value based on other variables or static values using a predefined formula.
Switch Block: Defines multiple execution paths based on specified conditions, similar to a switch-case statement. This control node allows different parts of the workflow to run simultaneously, providing flexibility and improving efficiency in workflow management.
Note: To use the output data in subsequent nodes via tokens, one must test the added node to set up sample output. More Nodes will be introduced in the future
Click on the node to configure it. Fill in the necessary parameters, test it, and set proper settings according to your requirements.
Input Params: In the Input Params section, you provide the necessary information the node needs to operate. This might include:
Test Result: Once you've entered the input parameters, you should test the node to ensure it functions as expected.
Execute a Test: Use the Test button to run the node with the input parameters you've defined. This is a safe way to ensure that your node works correctly without affecting the live data or workflow.
Review Output: After the test is completed, examine the results. This output shows what the node will produce during the actual workflow execution.
Troubleshoot Errors: If the test doesn't produce the expected results, or if errors are shown, use this information to go back and adjust the input parameters until the node operates correctly.
Settings: The Settings section allows you to define broader operational parameters and any additional options that control the node's behavior in the workflow.
Execution Options: Set options like timeout durations, concurrency limits, or retry logic for nodes that make external calls or perform resource-intensive operations.
Output Configuration: Determine how the node outputs data, which could involve specifying variable names for output values or formatting the output.
Advanced Settings: Some nodes may have advanced settings for cache control, error handling, access control, or integration-specific options, such as API keys or database credentials.
Save: After configuring the node, save your node. It's important to test the node before saving the node.
To configure each Node, go to the specific Node pages.
Based on the current configuration of the nodes, it can be in any of the following three states:
Untested:
The "Draft/Untested" status is assigned to a node when it is not tested and it will show like the above image.
During the drafting phase, you have the flexibility to make changes and adjustments to your node without affecting the environment.
Note: A node can be kept in untested status, however, the node can affect another ‘child node’ or ’post node’ to be tested. Also, as long as a node is in untested status, the workflow can’t be published.
Tested:
After you have completed the editing process or made changes to the node, you can initiate testing by clicking the "Test" button.
This action redirects you to the “Test Result” tab, where you can evaluate the node's behavior and performance in a controlled staging environment.
Error:
If your node doesn’t execute properly or gets any kind of error, the Node then looks like the above, and its status changes into ‘error’.
To fix this, you can try to run the node again by simply clicking the left ▶️ button or can click on the Node to edit the node and fix that if there’s any kind of error.
Node Limit: The maximum number of nodes within a workflow that a user can create is 50.
Once testing is completed and you exit the testing screen, the rule status transitions to "Tested."
