Skip to main content

​
Overview

Templates are pre-built workflow structures designed for the most common automation use cases. Each template includes a pre-configured trigger, the right action nodes in the right order, and a Deploy Checklist that guides you through what to fill in before going live. You can always customize a template after selecting it — add nodes, change the trigger conditions, or adjust any field mappings to match your exact process.

​
Template Categories

When you click New Workflow, templates are organized into the following categories:
Templates that fire when something happens to a Contact record — a new contact is created, a field is updated, a form is submitted, etc.Best for: Lead routing, contact lifecycle automation, and reacting to contact data changes.Example use cases:
  • Assign a newly created contact to the right owner based on territories
  • Update contact Stage from “Untouched” to “Lead” when a first activity is logged
  • Send an alert when a Contact’s Last Activity Date is >X days ago
Templates that fire based on changes or events on Account records.Best for: Account-level automation, territory assignments, updating related contacts when an account changes.Example use cases:
  • Update all contact Stages on an account when the account’s Stage changes (e.g. when an Account becomes a Customer, update all related Contacts to Stage = Customer)
  • Create a follow-up task when a new account is added
  • Send an internal notification when an Account changes owners
Templates that fire when Opportunity records are created or updated — stage changes, close date shifts, owner reassignments, etc.Best for: Pipeline automation, deal-stage notifications, and revenue operations workflows.Example use cases:
  • Send a Slack message to a channel when a deal reaches “Closed Won”
  • Create a task for the account manager when an opportunity moves to “Negotiation”
  • Update the associated contact’s lifecycle stage when a deal closes
  • Stamp a re-engagement date when an Opportunity goes to Closed Lost
Templates specifically designed to assign and distribute incoming leads across your team. These typically combine a trigger with location-based territory or If/Else logic to route the right lead to the right person.Best for: Sales teams that need structured, automated lead distribution.Example use cases:
  • Route leads to different reps based on company size or geography
  • Assign leads from specific sources to a dedicated team
Templates that automate transitions through your defined contact or account lifecycle stages — moving records forward, triggering actions at each stage, and keeping your pipeline clean.Best for: RevOps and marketing teams managing lead lifecycle and handoff between stages.Example use cases:
  • Automatically progress a contact’s stage when they book a meeting
  • Automatically update Account and Contact stages to Customer when a deal is closed won
  • Move an Account to Nurture when an opportunity is closed lost
Templates that send notifications to your team when important events occur — Slack messages, email notifications, or task creation based on trigger conditions.Best for: Teams that want real-time visibility into key CRM events without manually monitoring records.Example use cases:
  • Alert a rep via Slack when a contact they own books a meeting
  • Notify a manager when a deal stalls for more than 14 days
  • Share recaps of sales calls with the team
Templates that automatically create new CRM records based on events or incoming data — such as creating a contact from a form submission or generating an account from a webhook payload.Best for: Inbound lead capture, form-to-CRM flows, and any process where new data needs to result in new records.Example use cases:
  • Create a Contact and Account from an inbound web form
  • Generate a new Opportunity when a contact reaches a specific lifecycle stage
  • Create a task record automatically when a webhook is received
Templates built around the Webhook Received trigger — designed for workflows that are initiated by external systems rather than in-Reevo events.Best for: Technical integrations with tools like Clay, Zapier, Make, or custom applications.Example use cases:
  • Accept inbound data from a form builder to create contacts when they fill out a demo request form
  • Trigger a workflow from a Zapier automation
  • React to events in your own product by sending a webhook to Reevo

​
Starting from Scratch

If none of the templates fit your use case, click Create from scratch. You’ll manually select your trigger type and add action nodes one by one for full control.

​
Customizing a Template After Selecting It

Templates are a starting point — not a constraint. After selecting one:
  • Add nodes by clicking + in the builder at any point in the flow
  • Remove nodes by selecting a leaf node and clicking Delete step (or pressing Delete)
  • Change the trigger by clicking the trigger node and updating its settings (only available in Draft status)
  • Rename the workflow at any time from the Edit button in the workflow list

​
Troubleshooting / FAQs

Yes — every template is fully customizable. You can add, remove, or reconfigure any node after selecting it. Think of templates as a head start, not a fixed structure.
Start with the template category that most closely matches your trigger event (e.g., Contact-Based Triggers if your workflow starts when a contact is updated). Then customize the action nodes to match your specific process. Alternatively, start from scratch with a blank workflow for full control.
Custom template saving is not currently available. You can clone an existing workflow (Clone button in the workflow list) to reuse a configuration you’ve built, or reach out to your Reevo representative for guidance on team-level workflow sharing.
Still have questions? Sign in and use Ask Reevo for instant answers or to raise a support ticket.