Triggering workflows in Vetta
Start your automations at the right moment with record and pipeline triggers, manual launches, schedules, webhooks, sequence steps and enrichment.
Updated October 25, 2026 · 8 min read
A workflow trigger is the event that starts a workflow in Vetta: a record being created or changed, a pipeline record moving stage, a schedule, a call from another app, a sequence step, a finished enrichment, or you launching it by hand. Every workflow has exactly one trigger, and it is always the first node on the canvas.
Whatever the trigger produces (the record that changed, the webhook payload, the enriched field) is available to every later step as variables.
Adding the trigger
- Open the workflow and click Add Trigger on the empty canvas.
- Browse the groups. Hover any trigger to read what it does.
- Pick one, for example Record is created.
- Fill in its settings, such as Record Type set to People, and save.
With Record is created on People, every new contact starts the workflow once it is active.
Choosing what starts a workflow. Click Add Trigger to see every kind, and hover to read each one. Record is created, updated or deleted, with the same set for Pipelines, and under Others: Launch manually from selected records in a table, On a schedule, Webhook, Sequence (as a step in outreach) and Enrichment. The example sets Record is created with Record Type People and saves, so every new contact starts the workflow. Use it when you are unsure which trigger fits.
Transcript
Every workflow starts with a trigger, the moment it springs into action. Click Add Trigger to see every kind, and hover one to read what it does. The first group fires when a record is created, updated or deleted. Pipelines has the same set, for records in your pipelines. Under Others, Launch manually lets you start it yourself, from the records you select in a table. On a schedule runs it on a timer you set. A webhook lets another app start it. Sequence runs it as a step in your outreach, and Enrichment fires when a record is enriched. Here it's Record is created. Set the Record Type to People and save, so every new contact starts this workflow.
Record triggers
Record triggers fire when CRM records change on the entity you choose: People, Companies, Opportunities, Tasks, Notes or any custom entity. Four event types are available:
- Record is created: runs when a new record is created
- Record is updated: runs whenever a record is updated
- Record is deleted: runs when a record is deleted
- Record created or updated: runs on either event
Workflows · TriggerFor an update trigger you can Select specific fields to listen to, so the workflow only runs when, for example, the Stage or Owner field changes rather than on every edit. Common uses include routing new contacts, data hygiene and score-based follow-ups.
A Record is updated workflow that writes to the same record it was triggered by can set itself off again, and loop. To avoid that, listen only to specific fields the workflow doesn't write, or add a Continue only if check that stops the run once the record already has the value.
Pipeline triggers
Pipeline triggers respond to changes in pipeline records, with the same four event types:
- Pipeline record is created: a record is added to a pipeline
- Pipeline record is updated: a pipeline record changes, such as when its stage changes
- Pipeline record is deleted: a record is removed from a pipeline
- Pipeline record is created or updated
Use them for follow-ups and deal management as records move through stages. See Working with pipelines.
Launch manually
A manual workflow starts when you decide, rather than on an automatic event. It suits operational jobs you want to run deliberately, such as enriching a hand-picked list. Under Availability you choose how it is launched:
- Global: no record is needed, so you can launch it from anywhere
- Single: the selected record is passed to the workflow
- Bulk: the selected records are passed to the workflow
For Single and Bulk you also pick the Object it works on. To run it, select the records in that object's table and click Trigger Workflow in the bar that appears at the bottom, then choose the workflow. With Single, selecting several records starts one run per record.
Set Navbar to Pinned to display a button in the top navbar that triggers the workflow, and choose its Command Icon.
On a schedule
Scheduled workflows run on a timer. Under Trigger interval choose:
- Days: every so many days, at an hour and minute you set
- Hours: every so many hours
- Minutes: every so many minutes
- Cron (Custom): a cron expression for advanced schedules, in the format minute, hour, day of month, month, day of week
Schedules run in the UTC timezone, so convert your local time when you set the hour. Use them for periodic jobs like data clean-ups and recurring checks.
Webhook triggers
Another app can start a workflow by calling its Live URL. You can configure:
- HTTP method: GET or POST
- Auth: None, or an API key the caller must supply
The body of the request becomes the trigger's variables, so later steps can use whatever the sender posts. A GET request has no body, so it brings in no variables. Check a real run to see the exact paths before you build on them. For API keys and outgoing webhooks, see API keys and webhooks.
Sequence triggers
A sequence-triggered workflow runs as a step inside an outreach sequence. Add a Trigger Workflow step to the sequence and select the workflow; when a contact reaches that step, the workflow runs with that person's record. Use it for mid-sequence CRM updates, task creation or calls to another system while a campaign runs. See Understanding multi-channel sequences.
Enrichment triggers
Enrichment-triggered workflows run when a record is enriched. Choose the object and the enrichment option to watch, then the outcomes that should start the workflow:
- Found: the option ran and returned data for the record
- Not found: the option ran but no data was available
- Already present: the option was skipped because the record already had this data and overwrite was off
- Already attempted: the option was skipped because a previous enrichment already ran it
Found is selected by default. For example: when enrichment finds an email for a person, a workflow can add them to a sequence straight away. See Data enrichment.
Choose the narrowest trigger that does the job. A Record is updated trigger that listens to one field runs far less often than one that fires on every edit, which keeps your runs list readable and makes a failed run easier to trace.
How triggers work with logic
The trigger decides when a workflow starts; filters, conditions and branching decide what happens next for each record. Together they let one workflow respond differently based on your CRM data.
Common questions
Why didn't my workflow run when I updated a record?
First check that the workflow is active, because a draft never runs. Then open the trigger: if you used Select specific fields to listen to, the workflow only runs when one of those fields changes, not on every edit. See Record triggers.
Does a Record is updated trigger fire again when the workflow itself updates the same record, and how do I avoid a loop?
Yes, a workflow that writes to the record it listens to can retrigger itself. Listen only to specific fields the workflow doesn't write, or add a Continue only if check. See Record triggers.
Why does the workflow fire for some teammates' changes but not others?
Workspace access under the workflow name lists the teammates whose actions can set it off. Anyone removed from that list can change records without triggering it. See Step 3: Choose your approach.
Can a workflow have more than one trigger?
No. Every workflow has exactly one trigger, and it's always the first node on the canvas. Record created or updated and Pipeline record is created or updated cover both events when you need them in one workflow. See Record triggers.
How do I run a workflow on records I pick myself?
Use the Launch manually trigger with Availability set to Single or Bulk and the Object it works on. Then select the records in that object's table, click Trigger Workflow in the bar at the bottom and choose the workflow. See Launch manually.
Why did my scheduled workflow run at the wrong time?
Schedules run in the UTC timezone, so the hour you set is a UTC hour. Convert your local time before you set it. See On a schedule.
Why does my webhook trigger bring in no data?
A GET request has no body, so it brings in no variables. Send a POST with a body: the body becomes the trigger's variables, and a real run shows the exact paths to use in later steps. See Webhook triggers.
Can I start a workflow from inside a sequence?
Yes. Add a Trigger Workflow step to the sequence and select the workflow; when a contact reaches that step, the workflow runs with that person's record. See Sequence triggers.
Can a workflow run when enrichment finds nothing?
Yes. The enrichment trigger lets you choose which outcomes start it: Found, Not found, Already present or Already attempted. Only Found is selected by default, so tick Not found as well. See Enrichment triggers.
Key outcome
You can now pick the right starting point for any automation: a change in your CRM, a pipeline move, a schedule, another app, a sequence step, an enrichment result, or a deliberate manual launch on the records you choose.
Still stuck?
We reply the same business day, 9:00 to 17:00 CET, Monday to Friday.