Skip to main content

​
Overview

After your trigger fires, action nodes execute in sequence to complete your business process. There are six categories of action nodes in Reevo.

​
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 you define.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 Find Records node.When to use: Stamp a lifecycle stage, 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 to use.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 to pass into a downstream step.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 of records

​
Logic Actions

These nodes control the flow and branching of your workflow based on conditions.
Splits your workflow into two paths — one if a condition is true, one if it is false. Only one path executes per run.When to use: Send different notifications based on deal size, skip a step if a field is already populated, or route records down separate paths based on a single condition.Key configuration:
  • Define a condition using field values or variables from earlier nodes
  • Connect action nodes to the True path and the False path independently
Branches your workflow into multiple paths based on the value of a field or 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 — when you have more than two possible outcomes.Key configuration:
  • Select the field or 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
Merges multiple branching paths back into a single flow, or fans out a single path into parallel branches. Used to manage complex workflow structures after If/Else or Switch nodes.When to use: After branching logic completes, use a Gateway to rejoin the paths so shared downstream steps don’t need to be duplicated in each branch.

​
Timing & Delay Actions

These nodes pause a workflow run for a defined period before continuing.
Pauses the workflow for a fixed number of seconds, then automatically continues to the next node.When to use: Wait a set amount of time between steps — for example, hold for 3,600 seconds (1 hour) before sending a follow-up notification.Key configuration:
  • Enter the number of seconds to delay (must be a positive integer)
  • Delays are enforced server-side — closing your browser or logging out has no effect on a running workflow
Pauses the workflow until a specific future datetime is reached, then continues automatically.When to use: Hold a workflow until a contract renewal date, a scheduled call time, or any future datetime stored in a record field.Key configuration:
  • Provide a future datetime — either a static value or a variable pulled from a record field
  • The datetime must be in the future at the time the node executes; if it is already in the past, the node will error and the run will fail
Calculates a new datetime by adding or subtracting a fixed amount of time from an existing datetime value. The result is stored as a variable for use in downstream nodes.When to use: Calculate “30 days from contract start date,” “2 hours before a scheduled meeting,” or any relative time value you want to use later in the workflow — for example, feeding into a Delay Until node.Key configuration:
  • Provide a base datetime (static or variable)
  • Specify the offset — e.g., +7 days, -2 hours
  • The computed datetime is passed to subsequent nodes as an internal variable

​
Notification Actions

These nodes send alerts and messages to your team.
Sends an internal email notification to one or more recipients. This is not a customer-facing sequence email — it is for internal team alerts.When to use: Alert a rep when a new lead is assigned to them, notify a manager when a deal reaches a key stage, or send a summary to a distribution list on a trigger event.Key configuration:
  • Set recipient email addresses (static or using variables from record data)
  • Write the subject line and body — variables from earlier nodes can be embedded to personalize the message
Sends a message to a Slack channel or user via your organization’s connected Slack integration.When to use: Notify a channel when a high-value deal is created, alert a rep in real time when their lead submits a form, or post automated pipeline updates to a dedicated Slack channel.Key configuration:
  • Select the target Slack channel or user
  • Compose the message — variables from earlier nodes can be used to include live record data
  • Requires Slack to be connected under Settings → Integrations

​
Outreach Actions

Enrolls a contact into a Reevo sequence to kick off automated multi-channel outreach.When to use: Automatically enroll inbound leads, start a nurture sequence on a lifecycle stage change, or trigger outreach when a specific event occurs.Key configuration:
  • Select the sequence to enroll into
  • Specify which contact to enroll (the trigger contact or one retrieved by a Find Records node)
  • The contact must have a valid email address and must not already be actively enrolled in another sequence — failed enrollments will appear as errors in your Runs tab

​
User Assignment Actions

Distributes records evenly across a defined list of users. Each time the node runs, it assigns the next user in the rotation and cycles back to the beginning when the list is exhausted.When to use: Evenly distribute inbound leads across your sales team, rotate account assignments across CSMs, or cycle task ownership across a group.Key configuration:
  • Define the list of users to rotate through
  • The assigned user is available as a variable in subsequent nodes — typically passed into an Update Record node to stamp an Owner field

​
Utility Actions

These nodes perform calculations and data manipulation to support downstream steps.
Generates a random integer within a range you specify. The result is stored as an internal workflow variable available in subsequent nodes.When to use: Apply probabilistic routing (e.g., send 50% of leads down one path and 50% down another when combined with an If/Else node), or generate randomized assignments when round-robin isn’t appropriate.Key configuration:
  • Set a minimum and maximum value for the range
  • The generated number is available as a variable downstream

​
External Integration Actions

Sends an HTTP request (GET, POST, PUT, PATCH, or DELETE) to any external URL. The response data — status code, body text, and parsed JSON — is available as a variable in subsequent nodes.When to use: Push data to an external system, trigger a Zapier webhook, call a custom API endpoint, or integrate with any tool that accepts HTTP requests.Key configuration:
  • Set the request method and URL
  • Add headers (e.g., Authorization, Content-Type)
  • Define the request body using static values or variables from earlier nodes
  • The response status, response text, and parsed JSON fields are all passed forward as variables
See Sending HTTP Requests from Workflows for a detailed setup walkthrough.

​
Node Deletion Rules

You can only delete a node if it is a leaf node — meaning it has no downstream nodes connected below it. To delete a node in the middle of a workflow, work from the bottom up: delete the lowest nodes first, then delete the one above, and so on until you reach the node you want to remove. Two ways to delete a leaf node:
  1. Select the node → click Delete step in the right-hand side panel
  2. Select the node → press the Delete key on your keyboard

​
Troubleshooting / FAQs

You can only delete leaf nodes — nodes with no child nodes connected below them. Delete all downstream nodes first, then come back to delete the parent.
Check the run details in the Runs tab and look at the error message for that node. Common reasons include: the contact is missing a valid email address, the contact is already enrolled in another active sequence, or the sequence itself is not in an active state.
Yes — each branch of an If/Else or Switch node can have its own chain of action nodes. Use a Gateway node to merge the branches back together if you want shared steps to run after the branching logic completes.
Yes — this is how variables work in workflows. Any node that creates or retrieves data (Create Record, Find Records, Send HTTP Request, etc.) 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.