Trigger

In NocoDB workflows, a Trigger node defines when a workflow starts. Every workflow must begin with exactly one trigger, making it the entry point for all automation.

Trigger nodes listen for specific events—such as data changes, form submissions, or scheduled times—and initiate the workflow when those events occur. By choosing the right trigger, you ensure workflows run automatically and only when relevant conditions are met.

How trigger nodes work

• A trigger continuously monitors for its configured event
• When the event occurs, the workflow starts
• A workflow run is counted each time the trigger fires. For conditional triggers, a run is counted only when conditions are satisfied and execution begins

Triggers provide the context and input data that subsequent action, flow, and integration nodes can consume during execution.

Types of trigger nodes

NocoDB offers multiple types of Trigger Nodes that define how a workflow is initiated:

• Manual trigger: Starts the workflow only when manually triggered by a user. Commonly used for testing or on-demand execution.
• Scheduled time: Starts the workflow at a defined date, time, or recurring interval.
• Record created: Starts the workflow when a new record is added to a specified table.
• Record updated: Starts the workflow when an existing record in a table is modified.
• Record deleted: Starts the workflow when a record is removed from a table.
• Form submitted: Starts the workflow when a specific form associated with a table is submitted.
• Record enters a view: Starts the workflow when a record appears in a view for the first time.
• Record matches conditions: Starts the workflow when defined field conditions are met.

These trigger nodes ensure workflows run automatically in response to events, schedules, or data changes within your base. Availability of specific trigger nodes may vary by plan. Refer to individual trigger documentation for details.