Workflows
Learn how automation workflows in NocoDB help streamline processes and reduce manual effort.
Workflows in NocoDB let you automate tasks by responding to events or conditions in your base. A workflow starts with a trigger and runs a sequence of actions, optionally guided by flow logic such as conditions or iteration.
Workflow runs are limited based on your plan. See Pricing for details.
A workflow run is counted each time a workflow is triggered, regardless of the number of actions it executes. For conditional triggers, a run is counted only when the conditions are met and the workflow executes.
Availability of certain nodes depends on your plan. Refer to the individual node documentation for plan-specific details.
Workflow structure
A Workflow is composed of the following building blocks:
| Component | Purpose |
|---|---|
| Trigger node | Defines when the workflow starts |
| Action nodes | Defines what the workflow does |
| Flow nodes | Defines how actions are executed (logic, iteration or delays) |
| Integration nodes | Action nodes. Connects to external services or AI capabilities |
Trigger nodes
A Trigger defines the event that starts a workflow. Each workflow must have exactly one trigger.
| Trigger | Description |
|---|---|
| Manual trigger | Runs only when started by a user |
| Scheduled time | Runs on a defined schedule |
| Record created | Runs when a new record is added |
| Record updated | Runs when an existing record changes |
| Record deleted | Runs when a record is removed |
| Form submitted | Runs when a specific form is submitted |
| Record enters a view | Runs when a record appears in a view for the first time |
| Record matches conditions | Runs when defined field conditions are met |
Action nodes
Action nodes define the operations executed after the trigger fires. Actions run sequentially in the order they are connected.
| Action | Description |
|---|---|
| List records | Retrieves multiple records based on filters |
| Create record | Creates a new record in a table |
| Update record | Updates fields in an existing record |
| Delete record | Removes a record from a table |
| Find record | Retrieves a single matching record |
| Send email | Sends an email using configured email settings |
Flow nodes
Flow nodes control execution logic within a workflow. They do not perform actions themselves, but manage how actions run.
| Flow node | Description |
|---|---|
| If / else | Executes different paths based on a condition |
| Iterate | Repeats actions for each item in a list |
| Delay | Pauses execution for a specified time |
| Wait until | Pauses until a condition is met |
Flow nodes can consume data from previous actions to drive branching, iteration, or delays.
Execution order
Workflow execution follows a predictable sequence:
- Trigger fires
- Actions execute in top-to-bottom order
- Flow nodes apply branching or iteration
- All execution paths complete
- Execution logs are recorded for auditing and debugging
FAQ(s)
How can I monitor workflow runs?
Workflow runs can be monitored through execution logs. Each workflow includes a run history that displays execution status, duration, and any errors encountered. Execution logs are retained according to your plan limits.
Can I edit a workflow after it is created?
Yes, workflows can be edited at any time. Changes apply only to future runs. Any executions already in progress continue using the workflow version that was active when they started. For workflows that are paused (for example, due to Delay or Wait Until nodes), you are prompted to either continue with the existing workflow definition or update to the latest version.
Are there limits on the number of workflows I can create?
There is no limit on the number of workflows you can create. However, workflow runs, log retention, and availability of certain node types may be restricted based on your subscription plan. Refer to the Pricing page for details.
Can workflows interact with external services?
Yes, workflows can interact with external services using Integration nodes. These nodes enable workflows to send data to or receive data from third-party APIs. Additional integration nodes will be introduced in future releases.
How are workflow runs counted?
A workflow run is counted each time a workflow is triggered, regardless of how many actions it executes. For conditional triggers, a run is counted only when the defined conditions are met and the workflow proceeds to execution.