Skip to main content

​
Overview

After your trigger fires, action nodes execute in sequence to complete your business process. Action nodes can update Reevo records, branch logic, wait, notify teammates, call external systems, and pass data forward to later nodes.

​
Record Actions

These nodes read, create, or update records in your Reevo CRM.
Creates a new record of a specified object type (Contact, Account, Opportunity, etc.) using data from earlier workflow steps or static values.When to use: Automatically create a Contact from a form submission, or generate an Opportunity when a qualifying event occurs.Key configuration:
  • Select the object type to create
  • Map fields using static values or variables from earlier nodes
  • The newly created record is available as a variable in all subsequent nodes
Updates one or more fields on an existing record - either the record that triggered the workflow or one retrieved by a Search Records node.When to use: Assign an owner, clear a field, or update any CRM field when a condition is met.Key configuration:
  • Select which record to update (trigger record or a found record)
  • Map the fields you want to change and the values to write (static or variable)
  • Multiple fields can be updated in a single node
Searches for existing records in Reevo that match conditions you define. Results are passed forward as variables for subsequent nodes.When to use: Look up the Account linked to a Contact before updating it, find all Contacts at a company, or retrieve a related record.Key configuration:
  • Select the object type to search
  • Define filter conditions (e.g., “Account Domain equals trigger contact’s domain”)
  • Supports returning a single record or a collection
Moves a contact, account, or opportunity to a target stage. Bulk variants are available for contacts and accounts to move multiple records in a single node.When to use: Automate stage transitions based on deal outcomes or workflow events - for example, move an account to “Customer” when a deal closes, or bulk-move all related contacts to the same stage in one step.Available nodes:
  • Move Contact Stage - moves a single contact to a target stage
  • Move Account Stage - moves a single account to a target stage
  • Move Opportunity Stage - moves an opportunity forward, backward, or to a specific stage. Supports Closed Won/Lost with optional closed reason fields. Use Ignore Stage Criteria to bypass exit criteria if needed
  • Move Many Contact Stages - bulk-moves a list of contacts to a target stage in one step
  • Move Many Account Stages - bulk-moves a list of accounts to a target stage in one step
Key configuration (contact and account nodes):
  • Record ID / Record IDs - reference the record(s) from the trigger or a previous Search Records node using {{variable}} syntax
  • Target Stage - select the stage to move the record(s) into
  • Override Criteria - when checked, the stage move proceeds even if the target stage has blocking entrance criteria configured

​
Logic Actions

These nodes control the logic and branching of your workflow.
Branches your workflow into multiple paths based on the value of a variable. Think of it as a multi-way If/Else.When to use: Route leads to different owners by territory, apply different sequences by industry, or send different notifications depending on deal stage.Key configuration:
  • Select the variable to evaluate
  • Define a downstream path for each case value
  • Optionally configure a default path for values that don’t match any defined case
Computes formulas, allowing you to configure any special calculation you need.When to use: Calculate 7 days from now, find the max of two values, apply conditional labels based on amount thresholds, or any other computation.Key configuration:
  • Write a formula and select variables
  • Add functions like MAX or TODAY as needed

​
Timing & Delay Actions

These nodes pause a workflow run for a defined period before continuing.
Pauses the workflow for a fixed amount of time, then automatically continues.When to use: Wait a set amount of time between steps - for example, hold 1 hour before sending a follow-up notification.Key configuration:
  • Enter the amount and unit of time to delay
  • Delays are enforced server-side - closing your browser or logging out has no effect on a running workflow

​
Notification Actions

These nodes send alerts and messages to your team.
Sends a message to a Slack channel via your connected Slack integration.When to use: Notify a channel when a high-value deal is created, alert a rep when their lead submits a form, or post automated pipeline updates to a dedicated Slack channel.Key configuration:
  • Select the target Slack channel
  • Compose the message - variables from earlier nodes can include live record data
  • Add formatting like **bold** for emphasis
  • Requires Slack to be connected under Settings → Integrations

​
Integration Actions

These nodes connect a workflow to systems outside Reevo.
Sends an HTTP request from your workflow to an external endpoint. This is the outbound webhook action: use it when Reevo should notify or update another system after a trigger fires.When to use: Push a qualified lead to another tool, notify an internal service when an opportunity changes, call a third-party automation endpoint, or send data from earlier workflow nodes to a custom API.Key configuration:
  • Enter the destination URL. Template variables from earlier nodes can be used in the URL
  • Choose the HTTP method: GET, POST, PUT, PATCH, or DELETE
  • Add optional request headers. Header values can use template variables
  • Add an optional JSON request body. The body must be a JSON object, and values can reference workflow variables
  • Configure timeout and redirect behavior if the endpoint needs custom handling
  • Optionally extract fields from a JSON response body using dot-notation paths so later nodes can use those response values
The Webhook action is different from the Webhook Received trigger. The trigger receives a request from an external system to start a workflow; the action sends a request from Reevo to an external system during a workflow run.

​
Troubleshooting / FAQs

Yes. Add a Webhook action node when a workflow should send data to an external endpoint. Use the Webhook Received trigger only when an external system should start the workflow by sending data into Reevo.
Always use the appropriate Move Record Stages node - not the Update Records node - when changing a contact, account, or opportunity stage. The Update Records node does not correctly process stage changes: the workflow will appear to succeed but the stage will not update on the record. Move Record Stages nodes handle the full stage transition, including criteria evaluation and change tracking.
Check the run details in the Runs tab. Common reasons include: the contact is missing a valid email address, the opportunity hasn’t met stage criteria, or an invalid value was provided.
Yes - each branch of a Condition node can have its own chain of action nodes.
Yes - this is how variables work in workflows. Any node that creates or retrieves data makes that data available as a variable. When configuring a later node, switch to variable mode in any field to see and select values from earlier steps.
Still have questions? Sign in and use Ask Reevo for instant answers or to raise a support ticket.