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. This page lists released action nodes plus custom object nodes. It does not include unreleased nodes.

​
Account Actions

Use account nodes when the workflow should create, find, update, or move account records.
Creates a new account or updates an existing account when a matching record already exists.When to use: Create an account from an inbound lead, webhook payload, import, or another workflow step.Key configuration:
  • Map account fields using static values or variables
  • Use trigger data or previous node outputs to populate fields
  • Optionally add relationships, such as linking contacts to the account.
  • The created or updated account becomes available as a variable in later nodes
Updates fields on an existing account.When to use: Assign an owner, stamp lifecycle data, clear a field, or update account information when a condition is met.Key configuration:
  • Identify the account to update
  • Choose the fields to update
  • Optionally add or remove relationships, such as linking or unlinking contacts.
  • Enter static values or variables for each field
Updates multiple accounts with the same field values.When to use: Apply the same owner, status, or field value to a list of accounts returned by a search step.
Searches for account records matching filter conditions.When to use: Find an account by domain, look up a related account before updating it, or retrieve a list of accounts for a bulk action.Key configuration:
  • Use Search Account when later steps need one matching account
  • Use Search Many Accounts when later steps need a collection
  • Define filter conditions using static values or variables
Moves one account or many accounts to a target account stage.When to use: Move an account to “Customer” when an opportunity closes, or move a set of accounts into a lifecycle stage.Key configuration:
  • Provide the account ID or account IDs
  • Select the target stage
  • Use Ignore Stage Criteria when the move should proceed even if configured criteria would otherwise block it

​
Contact Actions

Use contact nodes when the workflow should create, find, update, or move contact records.
Creates a new contact or updates an existing contact when a matching record already exists.When to use: Create contacts from webhook payloads, imports, or account activity.Key configuration:
  • Map contact fields using static values or variables
  • Use trigger data or previous node outputs to populate fields
  • Optionally add relationships, such as linking the contact to an account or opportunity.
  • The created or updated contact becomes available as a variable in later nodes
Updates fields on an existing contact.When to use: Assign an owner, update a lifecycle field, stamp source data, or change a contact field after a condition is met.Key configuration:
  • Identify the contact to update.
  • Choose the fields to update.
  • Optionally add or remove relationships, such as linking or unlinking accounts or opportunities.
Updates multiple contacts with the same field values.When to use: Apply the same value to contacts returned by a Search Many Contacts node.
Searches for contact records matching filter conditions.When to use: Look up a contact by email, find contacts associated with an account, or retrieve a collection of contacts for bulk updates or stage moves.Key configuration:
  • Use Search Contact when later steps need one matching contact
  • Use Search Many Contacts when later steps need a collection
  • Define filter conditions using static values or variables
Moves one contact or many contacts to a target contact stage.When to use: Move contacts to “Selling” after an opportunity is created, or cascade an account stage change to related contacts.Key configuration:
  • Provide the contact ID or contact IDs
  • Select the target stage
  • Use Ignore Stage Criteria when the move should bypass configured stage criteria

​
Opportunity Actions

Use opportunity nodes when the workflow should create, find, update, or move opportunities.
Creates a new opportunity or updates an existing one when a matching record already exists.When to use: Generate an opportunity when a qualifying event occurs or when inbound data indicates a new deal should be tracked.Key configuration:
  • Map opportunity fields using static values or variables.
  • Use trigger data or previous node outputs to populate fields.
  • Optionally add relationships, such as linking contacts to the opportunity.
Updates fields on an existing opportunity.When to use: Stamp deal metadata, update owner or amount fields, or keep opportunity information in sync with other workflow steps.Key configuration:
  • Identify the opportunity to update.
  • Choose the fields to update.
  • Optionally add or remove relationships, such as linking or unlinking contacts.
Updates multiple opportunities with the same field values.When to use: Apply a shared update to opportunities returned by a search step.
Searches for opportunities matching filter conditions.When to use: Find the opportunity related to a contact or account, or retrieve multiple opportunities for a bulk update.
Moves an opportunity forward, backward, or to a specific stage.When to use: Automate stage transitions based on deal outcomes or other workflow events.Key configuration:
  • Provide the opportunity ID
  • Choose whether to move to a specific stage, forward, or backward
  • Select closed reason fields when moving to a terminal Closed Won or Closed Lost stage
  • Use Ignore Stage Criteria to bypass configured stage exit criteria when needed

​
Custom Object Actions

Custom object nodes are available when custom object workflows are enabled for your workspace.
Creates a record for a selected custom object.When to use: Store structured data that does not fit account, contact, or opportunity records.Key configuration:
  • Select the custom object type.
  • Map custom object fields using static values or variables.
  • Optionally add custom relationships to other records.
Updates an existing custom object record.When to use: Keep custom CRM data current when related activity happens elsewhere in Reevo.Key configuration:
  • Identify the custom object record to update.
  • Choose the fields to update.
  • Optionally add or remove custom relationships to other records.
Searches custom object records matching filter conditions.When to use: Find custom data before updating it, creating relationships, or using it as context in later nodes.

​
Adding Relationships from Create and Update Nodes

Create and update nodes can manage relationships at the same time they create or update a record. Use this when the relationship is part of the record operation, such as creating a contact and linking it to the account from the trigger. Create nodes can add relationships. Update nodes can add or remove relationships, and can be used even when the only change is the relationship. For contact-account and contact-opportunity relationships, you can set relationship details such as primary account, title, department, primary contact, or contact role when those options are available. Custom relationships are plain links and do not have those built-in details.
Some relationship rules are enforced automatically. For example, a contact must be linked to an opportunity’s account before the contact can be added to that opportunity.

​
Sequence Actions

Use sequence nodes to coordinate outreach.
Enrolls a contact into a sequence.When to use: Start automated outreach when a contact reaches a certain stage or meets qualification criteria.
Removes a contact from a sequence.When to use: Stop outreach when a contact replies, books a meeting, or no longer qualifies.

​
Communication Actions

Use communication nodes to send Slack messages.
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 team when a webhook receives a new lead, or post automated pipeline updates.Key configuration:
  • Select the target Slack channel
  • Compose the message using static text, variables, and @mentions for Slack users
  • Requires Slack to be connected under Settings → Integrations
Sends a direct message to a Slack user.When to use: Notify a specific rep or manager without posting to a shared channel.

​
Logic and Flow Control Actions

These nodes control how a workflow branches, waits, and computes values.
Branches your workflow into multiple paths based on conditions.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:
  • Define one or more cases
  • Configure conditions for each case
  • Optionally configure a default path for records that do not match other cases
Computes formulas so later nodes can use calculated values.When to use: Calculate dates, compare values, apply conditional labels, or transform values for later steps.Key configuration:
  • Write a formula
  • Select variables from the trigger or previous nodes
  • Use the computed output in downstream nodes
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
Selects a user from a list, rotating assignment across the available users.When to use: Pair with an Update Account, Update Contact, or Update Opportunity node to distribute records across reps.

​
Integration Actions

These nodes connect workflows to external systems.
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

Node availability can depend on enabled product areas, integrations, and workflow scope. This page lists released nodes and custom object nodes; unreleased nodes are intentionally excluded.
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 Stage node when changing a contact, account, or opportunity stage. Update nodes are for field updates; stage move nodes handle the stage transition logic, criteria evaluation, and change tracking.
Check the run details in the Runs tab. Common reasons include missing required data, an invalid value, an integration issue, or a record that does not meet configured criteria.
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, retrieves, computes, or receives data can make data available to downstream nodes. 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.