Nodes

In NocoDB workflows, nodes are the core building blocks used to design and run automation. Each node performs a well-defined function—starting a workflow, executing an operation, applying execution logic, or interacting with external services.

By connecting nodes, you define when a workflow runs, what it does, and how it progresses. Nodes exchange data with one another, enabling workflows to react dynamically using conditions, loops, delays, and integrations. This modular structure keeps workflows readable, maintainable, and easy to extend as requirements evolve.

Types of nodes

NocoDB workflows are composed of the following node types, each serving a specific role:

• Trigger Nodes Start the workflow in response to an event or condition, such as a record change, form submission, scheduled time, or manual execution.

• Action Nodes Perform operations within the workflow, including creating, updating, deleting, or retrieving records, and sending notifications.

• Flow Nodes Control execution logic by enabling conditional branching, iteration, and time-based pauses.

• Integration Nodes Connect workflows to external services, APIs, or AI capabilities, allowing data exchange beyond NocoDB.

Node inputs and outputs

Nodes can accept inputs and produce outputs, allowing data to flow between steps in a workflow. Outputs from one node can be used as inputs for subsequent nodes, enabling context-aware automation and decision-making.

For example, a trigger may output the details of a newly created record, which an action node can then use to update related records or send notifications.

Configuring inputs

Node inputs can be configured in two ways:

• Static values Fixed values defined at design time. These follow the same interaction patterns as grid cells—select fields use dropdowns, date and datetime fields use pickers, and boolean fields use toggles.

• Dynamic values Values derived from the outputs of previous nodes. These allow workflows to adapt to runtime data and execution context.

To configure a dynamic value, click the + icon next to an input field and select from the available outputs of earlier nodes in the workflow.

Execution data and logs

Each node’s execution output is recorded as part of the workflow run and is available in the execution logs. These logs help track execution flow, inspect data, and troubleshoot failures at a node level.

During workflow testing, nodes display sample data based on their current configuration. This allows you to validate logic and data mapping before enabling the workflow.

On error behavior

By default, if a node encounters an error during execution, workflow run stops immediately, and the error is logged. Error details are available in the execution logs for troubleshooting. Learn more.

NocoDB doesn't support custom error handling or retry mechanisms at the node level yet. Future updates may introduce advanced error handling features.