Skip to main content

​
Overview

Every workflow begins with a trigger. Without one, your workflow will never run. Reevo supports seven 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

TriggerWhat Starts ItBest For
Record CreatedA new record is saved in ReevoOnboarding new contacts, auto-assigning owners
Record UpdatedA field on an existing record changesReacting to stage changes, status updates, data stamps
Form SubmissionA Reevo form is submittedRouting inbound leads, creating contacts from web forms
Cron ScheduleRuns on a repeating scheduleDaily digests, weekly cleanups, recurring syncs
One-Time ScheduleRuns once at a specific date and timeScheduled bulk updates, one-off campaign launches
Manual RunA user triggers it on demandTesting a workflow, ad-hoc operations
Webhook ReceivedAn external system sends a payloadIntegrating with third-party tools like Clay or Zapier

​
Trigger Details

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 that match certain criteria (e.g., only contacts where Lead Source = “Web Form”)
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 — without one, the workflow fires on every field change across every record of that type.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 is updated
  • 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
  • If your workflow fires unexpectedly, review your filter conditions — they may be too broad
You must configure at least one filter condition on a Record Updated trigger. Without it, the workflow will fire on every update to every record of that type, which can cause unexpected behavior and excessive executions.
Fires when a Reevo form is submitted. All form field values (name, email, company, phone, etc.) are passed into the workflow and available as variables in downstream action nodes.Common use cases:
  • Create a new Contact record from an inbound form submission
  • Enrich the contact and add them to a sales sequence
  • Route the lead to the right owner based on form answers
Configuration tips:
  • Select which form to watch
  • All standard form fields are available as variables in subsequent nodes
Runs your workflow automatically on a repeating schedule defined using a cron expression — for example, every day at 9am, or every Monday at 8am.Common use cases:
  • Send a daily pipeline summary to your team
  • Run a weekly data cleanup or field update across records
  • Trigger a recurring sync or export on a fixed cadence
Configuration tips:
  • Enter a valid cron expression to define the schedule
  • The workflow runs server-side at each scheduled interval — no manual action needed
Runs a workflow exactly once at a specific date and time you define. After it executes, it will not run again unless re-triggered manually.Common use cases:
  • Schedule a one-time bulk record update for a future date
  • Send a notification at a specific planned moment
  • Trigger a campaign launch at a set time
Configuration tips:
  • Select a future date and time (timezone-aware)
  • After execution, the workflow status will show the run in your Runs tab
Allows you or your team to trigger the workflow on demand from the workflow builder. Useful for testing or for workflows that should only run when explicitly initiated by a user.Common use cases:
  • Test a workflow end-to-end before going live
  • Run a one-off bulk operation when needed
  • Ad-hoc automations that don’t need a scheduled or event-based trigger
See the Testing Workflows with Manual Run article for full details.
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 your own product
  • 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 — share this with the external system
  • The external system must send a POST request with a JSON body
  • All fields in the JSON payload become available as variables in your workflow
See the Using Webhooks to Trigger Workflows article 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.

​
Troubleshooting / FAQs

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.
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.
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 — workflows in Draft status never execute.
Not directly. However, workflows can chain together naturally — 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.