Workflow Triggers

A Trigger is the start condition for a workflow — the thing that decides when a deployed Workflow Definition actually runs. Every deployed workflow has exactly one trigger, set as a node on its canvas.

Trigger kinds

Kind	Fires when…
Manual	You click Run on the workflow. No configuration needed.
Schedule	A recurring time you set — every interval (e.g. every 15 minutes), or daily, weekly, or monthly at a specific time, in a timezone you choose.
Webhook	An external system calls a GreenVee URL.
Data change	A record in a table you choose is created, updated, and/or deleted. You pick which of those operations count.

Conditions

Every trigger kind (except Manual) can carry an optional condition — a rule that further narrows down when it actually fires, based on the data of the event itself. For example, a data-change trigger can be limited to only fire when a specific field changes to a particular value, instead of on every change to that table.

The Triggers page

The Triggers page lists every trigger across every deployed workflow in one place, so you don’t have to open each workflow individually to see what’s wired up. For each trigger you can see:

• Which workflow it belongs to
• Its kind (with a short summary of its configuration — e.g. the table and operations for a data-change trigger, or the cadence and timezone for a schedule)
• Which deployed version it’s attached to
• Whether it’s active or disabled, with a toggle to switch it

Reliability

Trigger events are deduplicated — if the same underlying event is delivered more than once (for example, after a retry), GreenVee only starts one run for it, never a duplicate.

Related pages

• AI Glossary — plain-English definition of Workflow Trigger
• Workflow Definitions — building and deploying the workflow a trigger belongs to
• Workflow Executions — the runs a trigger starts
• How Automation Runs — where triggers fit in the bigger picture