Example workflow automations

These example workflow automations are recipes you can build in your Vetta workspace as they are, or use as starting points. Each one lists the trigger, any condition, and the actions in order, using the names you'll see in the editor. The full catalogs are in Triggering workflows and Setting workflow actions.

Lead assignment

Trigger: Record is created (People) Actions: Update Record (assign an owner) → Create/Update Pipeline Record

Every new contact gets an owner and lands in the right sales pipeline the moment it is created.

Inbound lead enrollment

Trigger: Record is created (People) Condition: lead source is website Action: Add to Sequence Campaign

Website sign-ups enter your follow-up sequence without anyone adding them by hand. If the sequence isn't active yet, they wait in it until you activate it, and nobody is added twice.

Enrichment follow-up

Trigger: Enrichment (outcome: Found) Action: Add to Sequence Campaign

The moment enrichment finds an email address for a contact, they enter your outreach sequence, with no list-building step in between.

Enrich people from any data provider

Vetta has its own data enrichment. If you also pay for another data provider that offers an API, a workflow can bring that provider's data into your People records. There is no native connector to set up: an HTTP Request step calls the provider, and an Update Record step writes the answer into the person.

Trigger: Launch manually (People, one record at a time) Actions: HTTP Request (the provider's API) → Update Record (People)

1. Create a workflow from scratch and add the Launch manually trigger. Set Availability to Single and the Object to People, so the person you select is passed to the workflow.
2. Add an HTTP Request step. Enter the provider's API URL and the HTTP Method its documentation asks for. Put the person's email or LinkedIn URL where the provider expects it, in the URL or in a Raw JSON body, by dragging the field in from the Input panel.
3. Under Headers Input, add the header the provider uses for your API key, exactly as its documentation shows (often Authorization or an API key header).
4. Paste an example response from the provider's documentation into Expected Response Body, so the next step can pick its fields.
5. Open the Test tab, type a real email or LinkedIn URL as the test value and click Send Request to check the call works and see what comes back.
6. Expand Continue only if on the HTTP Request step and add a rule that the field you need is not empty, so nothing is written when the provider finds nothing.
7. Add an Update Record step: object People, record set to the person from the trigger, and each field you want to fill (job title, phone, company size) mapped to the matching field from the HTTP Request output.
8. Activate the workflow. In the People table, select the people to enrich, click Trigger Workflow in the bar at the bottom and choose the workflow. It runs once for each selected person.

Pipeline stage progression

Trigger: Pipeline record is updated (listening to the Stage field) Condition: Stage equals Qualified Actions: Create Task (book a discovery call) → Update Pipeline Record (set the next step field)

When a deal reaches Qualified, the owner gets a task and the record shows what happens next, so qualified deals never sit untouched.

Route by company size

Trigger: Record is created (People) Logic: If / Else on the company's Employees, greater than or equal to 50 Actions: True → Add to Sequence Campaign (enterprise sequence); False → Add to Sequence Campaign (sequence for smaller teams)

One workflow sends each new contact into the journey that fits their company. For more than two groups, for example one sequence per language, use Switch with a case per value and Otherwise for everyone else. See Leveraging workflow logic.

High-scoring lead sequences

Trigger: Record is updated (People, listening to your score field) Condition: score is 80 or more Action: Add to Sequence Campaign

Top prospects get outreach the moment their score crosses your threshold.

AI intent scoring

Trigger: Record is created (People) Action: AI CRM Agent on the person: "Score this person's buying intent from 1 to 5, using their role, their company and their notes", reading the person, their company and their notes, writing to an Intent score field

Every new person is scored the same way, and later steps (or a view filtered on the field) can act on the score. See AI agents in workflows.

Sequence exit on deal creation

Trigger: Pipeline record is created Action: Exit from Sequence Campaign

Contacts leave cold outreach once they enter an active opportunity, so nobody gets a prospecting message in the middle of a live deal. A reply already stops a person's sequence on its own; this covers deals that start from a call or a meeting instead.

Thank-you tasks on a won deal

Trigger: Pipeline record is updated (Opportunity), Stage equals Closed Won Actions: Search Records (the people at the deal's company, with the Limit raised) → Iterator → Create Task for each person

Everyone at the new customer gets a personal thank-you from their owner, not just the main contact.

Customer onboarding

Trigger: Pipeline record is updated (Opportunity) Condition: Stage equals Closed Won Actions: Add to Sequence Campaign (onboarding) → Create Task (for the account manager)

New customers start an onboarding journey right after the deal closes, with a task so a person owns the handoff.

Common questions

Key outcome

You now have a set of proven automations to start from: routing and enrolling new contacts, enriching them from any provider with an API, moving deals forward, scoring intent with AI and handing customers to onboarding. Build one, check its first runs, and add the next once it holds up.