Select Add Node in the workflow builder to see the nodes available to your workspace.
A node that needs an integration appears only when that integration is connected.
Deep Research is in beta and also needs its workspace feature turned on.
Actions
| Node | How it works | Use it when |
|---|---|---|
| Send to Webhook | Sends an HTTP request to a public endpoint and makes the response available to later nodes. | You need to send data to a system that has no native Default integration. |
| Redirect | Sends a visitor’s browser to a URL, with optional URL parameters. | A form-driven workflow must send the visitor to a thank-you page or another destination. |
| Date Transformer | Moves a date forward or backward and saves the result. | A later node needs a date such as 1 day before a meeting. |
| Create Variable | Saves fixed values or data from earlier nodes under names you choose. | Several later nodes must reuse the same value. |
CRM and Default records
The shared CRM nodes support Salesforce and HubSpot. Their fields and behavior can differ by provider. The CRM node guide shows each provider version separately.| Node | Provider | How it works | Use it when |
|---|---|---|---|
| Create Record | Salesforce and HubSpot | Creates a CRM record from mapped workflow data. Salesforce can update a matching record instead. | The workflow must add a new lead, contact, account, company, deal, or another supported object. |
| Match Record | Salesforce and HubSpot | Finds 1 record, then follows Match or No Match. HubSpot can also match through an association. | You must find an existing record before you decide whether to update or create it. |
| Update Record | Salesforce and HubSpot | Changes mapped fields on a record selected from an earlier node. | The workflow already has the record ID and must change its fields or owner. |
| Convert Lead | Salesforce | Converts a lead into an account and contact, with an optional new opportunity. | A qualified Salesforce lead must enter your account and opportunity process. |
| Create Activity / Create Engagement | Salesforce and HubSpot | Creates a Salesforce activity or HubSpot engagement and can connect it to a record. | The CRM must record a call, email, meeting, note, task, or other activity. |
| Match Activity / Match Engagement | Salesforce and HubSpot | Finds 1 activity or engagement, then follows Match or No Match. | You must prevent duplicates or find an item before you update it. |
| Update Activity / Update Engagement | Salesforce and HubSpot | Changes fields on an activity or engagement selected from an earlier node. | The workflow must change the status, owner, date, or another field on an existing item. |
| Create Association | HubSpot | Links 2 HubSpot records with a default or labeled relationship. | You must connect records such as a contact and company. |
| Match Default Record | Default | Finds a Default record and follows Match or No Match. | You must find a queue before another routing node uses it. |
Sequencing
| Node | How it works | Use it when |
|---|---|---|
| Add to Apollo Sequence | Finds or creates an Apollo contact, then adds it to a sequence from a selected mailbox. | Apollo should start outreach for the lead. |
| Add to Outreach Sequence | Finds or creates an Outreach prospect, then adds it to a sequence from a selected mailbox. | Outreach should start outreach for the lead. |
| Add to Salesloft Cadence | Finds or creates a Salesloft person, then adds them to a cadence. | Salesloft should start a cadence, with an optional sending user and start step. |
| Add to Amplemarket Sequence | Identifies a lead by email or LinkedIn URL and adds them to a sequence. | Amplemarket should start outreach for the lead. |
| Add to Smartlead Campaign | Adds an email address to a Smartlead campaign. The campaign chooses the sender. | Smartlead should start outreach and manage sender rotation. |
| Enroll in HubSpot Sequence | Enrolls a HubSpot contact under a selected HubSpot user. | A mapped HubSpot user should send a shared HubSpot sequence. |
| Add to Gong Engage Flow | Adds a Salesforce or HubSpot record to a Gong Engage flow under a selected user. | Gong Engage should start outreach for a CRM record. |
Notifications and Slack
| Node | How it works | Use it when |
|---|---|---|
| Send Slack Message | Posts to Slack channels, sends direct messages, or does both. | A team or assigned person needs a real-time alert. |
| Send Internal Email | Emails Default workspace members. It does not email external leads. | An internal user needs an email notification or action link. |
| Create Slack Channel | Creates a public or private Slack channel and can post its first message. | A new account, deal, or project needs its own channel. |
| Add Member to Slack Channel | Adds internal users, Slack apps, or external guests to a channel. | A workflow created or selected a channel and must add the right participants. |
Enrichment and AI
| Node | How it works | Use it when |
|---|---|---|
| Enrich Data | Uses 1 provider or a waterfall to add person, company, or validation data. | Routing, CRM updates, or messages need data that the trigger did not provide. |
| AI Prompt | Sends workflow data and instructions to a language model, then returns text. | You need to summarize, classify, or transform data already in the workflow. |
| Deep Research (Beta) | Searches the live web through Parallel and returns the output fields you define. | You need current research that enrichment providers or existing workflow data cannot answer. |
Routing and scheduling
| Node | How it works | Use it when |
|---|---|---|
| Round-Robin | Uses a queue and its policy to select an assigned user. | A lead must go to an available sales or success team member. |
| Display Scheduler | Shows a booking page, waits for the visitor, then follows Booked or Not booked. | A qualified visitor should book time during the workflow. |
| Rules of Engagement | Runs a published ruleset to choose an owner or queue, then follows Resolved or Else. | Lead details such as region or company size should decide the owner or queue. See Rules of Engagement. |
| Cancel meeting | Cancels a booked Default meeting by its ID, with an optional stored reason. Can skip the cancellation messages. | A later check disqualifies the lead, or a CRM update closes the deal, after a meeting was booked. |
Logic and timing
| Node | How it works | Use it when |
|---|---|---|
| Multi-Branch | Checks branches in order and follows the first matching branch. Else catches everything else. | Different records need different actions based on their data. |
| Run Experiment | Assigns runs across weighted branches and can keep the same lead in the same branch. | You need an A/B test, a sample, or a gradual rollout. |
| Time Delay | Pauses the workflow for a duration, then continues. | A later action must wait, such as a follow-up 1 day after a meeting. |
Legacy nodes
These nodes stay registered so old workflows can load. You cannot add them to a new workflow.| Node | Current behavior | What to use now |
|---|---|---|
| Add Tag | The node is hidden and performs no action. Remove it from old workflows. | Use Create Variable for reusable workflow data. Use Update Record to write a value to your CRM. |
| Abstract Geolocation | Existing workflows still look up a visitor’s location from the trigger’s IP address. | Use Enrich Data with a provider or waterfall that returns location data. |