Overview
Every workflow begins with a trigger - the event that kicks off your automation. Without one, your workflow will never run. When creating a new workflow from a template, the trigger type is pre-selected, but you can change it while the workflow is in Draft status. This page lists released triggers plus custom object triggers. It does not include unreleased triggers.Trigger Types at a Glance
Trigger Details
Account, Contact, and Opportunity Created
Account, Contact, and Opportunity Created
- Assign an owner to a new account
- Enroll a new contact in an onboarding sequence
- Send a Slack alert when a new opportunity is created
- Choose the object-specific trigger that matches the record type you want to watch
- Add optional filter conditions to only trigger for records matching your criteria
- For contacts and accounts, filter on Timezone to only trigger for records in specific timezones, for example Timezone equals America/New_York, or is any of a list of timezones
- Use trigger variables in downstream nodes to reference the record that started the workflow
Account, Contact, and Opportunity Updated
Account, Contact, and Opportunity Updated
- Notify a Slack channel when an opportunity stage changes to “Closed Won”
- Add a contact to a sequence when their lifecycle stage updates
- Update related records when an account field changes
- Add filter conditions that define the update you care about
- Use AND/OR logic to combine multiple conditions
- For contacts and accounts, filter on Timezone, for example Timezone changed to a timezone in a region you route to a specific owner. A contact’s timezone comes from their address or is set manually; see Contact Timezone
- For stage changes, use the appropriate stage fields and then use a Move Stage action node if the workflow needs to change another record’s stage
Relationship Created and Relationship Updated
Relationship Created and Relationship Updated
- Contact linked to account.
- Contact linked to opportunity.
- Custom object relationships configured in your workspace.
- Notify a team when a contact is added to a strategic account.
- Create a task when a decision maker is linked to an opportunity.
- Update a related record when a custom object record is linked.
- Choose the relationship type the workflow should watch.
- Add optional filters for either side of the relationship, such as only contacts with a certain title or accounts in a certain segment.
- For contact-account and contact-opportunity relationships, you can also filter on relationship details such as primary account or primary contact.
- Use relationship variables in downstream nodes to reference both linked records.
Meeting Triggers
Meeting Triggers
- Send a prep reminder before a customer meeting starts
- Create a task 30 minutes before an upcoming sales meeting
- Send a follow-up Slack reminder after a meeting ends
- Alert a manager when an important customer meeting starts
- Use Time Before Meeting Start for pre-call workflows that should run before the scheduled start time
- Use Meeting Ended for post-call workflows
- Add filters when the workflow should only apply to certain meeting types, owners, or related records
Time Before Meeting Start
Time Before Meeting Start
- Notify a rep before a high-priority meeting starts
- Create a final prep task before a customer call
- Send meeting context to Slack before a sales meeting
- Set the duration amount and time unit, such as 30 minutes, 1 hour, or 1 day before the meeting starts
- The minimum allowed duration is 10 minutes before the meeting starts
- Add optional filters when the workflow should only apply to certain meetings, such as sales meetings, meetings with a specific account, or meetings owned by a specific organizer
- Use meeting trigger variables in downstream nodes to reference the meeting and its related records
Recurring Schedule
Recurring Schedule
- Send a recurring Slack reminder to review pipeline hygiene.
- Create a periodic task for reps or managers.
- Run a workflow once at a future date and time.
- Trigger maintenance or follow-up automation on a recurring cadence.
- Choose the frequency type: Once, Daily, Weekly, Monthly, or Custom (Cron).
- Pick the timezone for the schedule. Reevo uses IANA timezone names such as America/Los_Angeles, America/New_York, or UTC.
- For Once, choose a future date and time.
- For Daily, choose the time of day. Daily schedules can also run every N days.
- For Weekly, choose one or more days of the week and the time of day.
- For Monthly, choose the day of the month and the time of day.
- For Custom (Cron), enter a 5-field cron expression in the format
minute hour day-of-month month day-of-week.
Email Received
Email Received
- Reply in the email’s thread with a Send Email node that has Reply In Thread selected. Reply In Thread requires this trigger.
- Alert an account owner in Slack when a contact at a key account emails in.
- Create a follow-up task when an email with a specific subject arrives.
- Add at least one filter condition. A workflow with no condition can’t be launched, because it would run for every email delivered to every connected mailbox in your organization.
- Filter on Latest received email sender address, Latest received email sender domain, Latest received email subject, To recipients of latest received email, or CC recipients of latest received email, or on the opportunity, account, contacts, or users associated with the email thread.
- A contact condition matches any contact on the thread, not only the sender.
- Trigger variables include From Email Address, To Email Addresses, CC Email Addresses, Subject, Sender Domain, Received At, Thread ID, and Message ID.
- Each incoming email starts the workflow once, even when several mailboxes in your organization received it.
- The email thread must include at least one contact in Reevo.
- Emails sent by Reevo workflows, sequences, and other Reevo automations don’t start it, so a workflow can’t re-trigger itself with its own emails. A contact’s reply to a sequence email is an ordinary incoming email and does start it.
- Emails sent from one of your organization’s mailboxes start it only when another mailbox in your organization is on the To line.
- Emails filed as spam or trash, drafts, and emails that reach your organization’s mailboxes only as a CC don’t start it.
- Older emails that sync in later, for example during a mailbox’s first sync or an import, don’t start it.
- The workflow starts after the email syncs into Reevo, so it may not start the moment the email arrives.
SMS Received
SMS Received
- Reply automatically with a Send SMS node set to Number that received the text, which keeps the reply on the same thread. That option requires this trigger.
- Alert the contact owner in Slack when a contact texts in.
- Create a follow-up task when a text contains a specific word.
- Optionally add conditions on Body, Word Count, From Number, To Number, or Received At. For example, use Word Count to ignore one-word replies.
- Optionally filter on the contact who texted, or their account or opportunity.
- Only incoming texts. Texts your organization sends, including texts sent by workflows, don’t start it.
- The sender’s number must match a contact in Reevo. Texts from unknown numbers don’t start it.
Webhook Received
Webhook Received
- 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
- Reevo generates a unique webhook URL for your workflow
- The external system must send a POST request with a JSON body
- You can define the expected payload structure so payload fields are easy to use as variables
- API key authentication is available when the sender should be required to authenticate
Sequence Engagement
Sequence Engagement
- Create a follow-up task when a contact replies to a sequence email.
- Notify an owner in Slack when an Outreach sequence email bounces.
- Move a contact to a new stage when their enrollment status changes.
- Source: choose Reevo for Reevo sequences, or a connected app. The trigger only fires for engagement from the source you pick.
- Event: choose one or more events. With none selected, the workflow never fires.
- Sequences: optionally limit the trigger to specific sequences. Leave it empty to fire for any sequence from the source.
- Filter: optionally filter on the engagement, its contact, account, opportunity, or enrollment.
Sequence Enrollment Updated
Sequence Enrollment Updated
- Move a contact to a new stage when they reply with interest.
- Notify an owner in Slack when an enrollment exits because the email bounced.
- Create a follow-up task when a contact finishes a sequence.
- Filter on Status to target a specific enrollment state. The available states are Enrolled, Paused, Completed, Removed, Failed, Failed Risky Email, Exited, and Converted. Active and queued enrollments both show as Enrolled.
- Filter on the exit reason to separate a reply from a bounce, an unsubscribe, a missing email, or a booked meeting.
- Filter on Sequence when the workflow should only apply to one sequence.
- Filter on engagement counts such as replies or clicks.
- Use enrollment variables in downstream nodes to reference the contact, the account, the opportunity, and the sequence.
Public Form Submitted
Public Form Submitted
- Create or update an account and contact from an inbound lead.
- Route a qualified submission to an owner and enroll them in a sequence.
- Show a booking calendar to qualified submitters and a thank-you page to everyone else.
- Build this workflow from the form’s Workflow tab, not from the workflow list. The trigger is owned by the form, so it is locked to that form and cannot be changed from inside the builder.
- Add optional conditions on form details such as form name, form type, or submission time, and on UTM parameters such as
utm_source,utm_medium, andutm_campaign. - Use the submitted contact and account fields, the unmapped answers, and the UTM values as variables in downstream nodes.
- Pair the trigger with the form action nodes: Create Account from Form, Create Contact from Form, and Show Scheduler.
Custom Object Triggers
Custom Object Triggers
- Custom Object Created
- Custom Object Updated
- Update a standard record when a related custom object changes
- Notify a team when a new custom object record is created
- Keep custom CRM data synchronized with standard records
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 the previous trigger may break and will need to be updated.Troubleshooting / FAQs
Why do I see different triggers than another workspace?
Why do I see different triggers than another workspace?
What's the difference between Schedule and Delay?
What's the difference between Schedule and Delay?
My updated-record workflow is firing too often - how do I control it?
My updated-record workflow is firing too often - how do I control it?
Can I have multiple triggers in one workflow?
Can I have multiple triggers in one workflow?
My created-record trigger didn't fire for a record I just added - why?
My created-record trigger didn't fire for a record I just added - why?
Still have questions? Sign in and use Ask Reevo for instant answers or to raise a support ticket.