Understanding Workflow Triggers

Triggers are the starting point of every workflow - they define what event causes your automation to run. Choosing the right trigger is the most important decision when building a workflow.

Overview

Every workflow begins with a trigger - the event that kicks off your automation. Without one, your workflow will never run. Reevo supports three trigger types, each designed for a different scenario. When creating a new workflow from a template, the trigger type is pre-selected - but you can always change it while the workflow is in Draft status.

---

Trigger Types at a Glance

Trigger	What Starts It	Best For
Record Created	A new record is saved in Reevo	Onboarding new contacts, auto-assigning owners
Record Updated	A field on an existing record changes	Reacting to stage changes, status updates, data stamps
Webhook Received	An external system sends a payload	Integrating with third-party tools like Clay or Zapier

---

Trigger Details

Record Created

Fires whenever a new record of a specified object type (Contact, Account, Opportunity, etc.) is created in Reevo - whether created manually, via import, or by another workflow.

Common use cases:

• Enroll a new contact into an onboarding sequence
• Assign an owner to a new account via round-robin
• Send an internal Slack notification when a new opportunity is created

Configuration tips:

• Select the object type to watch (e.g., Contact, Account)
• Add optional filter conditions to only trigger for records matching certain criteria (e.g., Account City equals San Francisco)

Record Updated

Fires when a field on an existing record is changed in Reevo. You must specify at least one filter condition defining which type of update should trigger the workflow.

Common use cases:

• Notify a Slack channel when an opportunity stage changes to “Closed Won”
• Add a contact to a sequence when their lifecycle stage updates
• Update a related record when a field is stamped on the parent

Configuration tips:

• Always set at least one filter condition (e.g., “Stage changed to Closed Won”)
• Use AND/OR logic to combine multiple conditions for precision

You must configure at least one filter condition on a Record Updated trigger. Without it, the workflow fires on every update to every record of that type, which can cause unexpected behavior and excessive executions.

Webhook Received

Fires when an external system sends an HTTP POST request to your workflow’s unique webhook URL. The incoming payload data is available as variables in downstream nodes.

Common use cases:

• Trigger a workflow from a third-party tool like Clay, Zapier, or Make
• Create or update Reevo records from data sent by an external system
• React to events happening outside Reevo in real time

Configuration tips:

• Reevo generates a unique webhook URL for your workflow
• The external system must send a POST request with a JSON body
• All fields in the JSON payload become available as variables

See Using Webhooks to Trigger Workflows for setup instructions.

---

Changing a Trigger

You can change a workflow’s trigger type while it is in Draft status. If your workflow is currently Active, deactivate it first, update the trigger, then re-deploy and reactivate. Note that when changing triggers, any variables pointing to that trigger may break and will need to be updated.

---

Troubleshooting / FAQs

My Record Updated workflow is firing too often - how do I control it?

Add more specific filter conditions to your trigger. For example, instead of watching all updates to Contact records, set the condition to “Stage changed to Qualified” so it only fires on that specific transition. You can layer multiple conditions using AND/OR logic to get precise control over what activates your workflow.

Can I have multiple triggers in one workflow?

No - each workflow has exactly one trigger. If you need the same actions to fire from different events, create separate workflows (one per trigger) that share the same downstream action structure.

My Record Created trigger didn't fire for a record I just added - why?

Check two things: (1) verify the record type matches what you configured, and (2) confirm any filter conditions on the trigger are satisfied by the new record. Also make sure the workflow is set to Active - Draft workflows never execute.

Can one workflow trigger another workflow?

Not directly. However, workflows can chain together - for example, one workflow stamps a field on a record, and a second workflow fires when that field is updated (using a Record Updated trigger).

Still have questions? Sign in and use Ask Reevo for instant answers or to raise a support ticket.