Trigger
In NocoDB workflows, a Trigger node sets when a workflow starts. Every workflow must start with exactly one trigger. The trigger is the entry point of the automation.
A trigger node listens for a specific event, for example a data change, a form submission, or a scheduled time. When the event occurs, the trigger starts the workflow. Select the right trigger, so that the workflow runs automatically and only when the relevant conditions are met.
Copy a prompt, paste it into NocoAI in any base, and replace the words in [brackets] with your own.
- Build a workflow that starts when [a record is added to Leads]
- Build a workflow that starts every [Monday at 9am]
- Build a workflow that starts when [Status] changes to [Approved]
How trigger nodes work
- A trigger continuously monitors for its configured event.
- When the event occurs, the workflow starts.
- Each time the trigger fires, NocoDB counts one workflow run. For conditional triggers, NocoDB counts a run only when the conditions are met and the run starts.
The trigger gives context and input data to the action, flow, and integration nodes that come after it.
Types of trigger nodes
NocoDB has these types of Trigger Nodes:
| Trigger | The workflow starts |
|---|---|
| Manual trigger | Only when a user starts it manually. Use it for testing or on-demand runs. |
| Button clicked | When a user clicks a Run automation button on an interface record. The workflow gets the clicked record. |
| Scheduled time | At a set date, time, or recurring interval. |
| Record created | When a new record is added to a specified table. |
| Record updated | When an existing record in a table changes. |
| Record deleted | When a record is removed from a table. |
| Form submitted | When a user submits a specific form of a table. |
| Record enters a view | When a record shows in a view for the first time. |
| Record matches conditions | When the set field conditions are met. |
| When comment changes | When a comment on a record is added, edited, deleted, resolved, or reopened. |
| When webhook received | When an HTTP request arrives at the webhook URL of the workflow. |
With these trigger nodes, workflows run automatically when events, schedules, or data changes occur in your base. Some trigger nodes are available only on some plans. For details, refer to the page of each trigger.
Availability
- Availability of certain trigger nodes depends on your plan. Refer to the individual trigger documentation for plan-specific details.
Last updated on