> ## Documentation Index > Fetch the complete documentation index at: https://docs.os.default.com/llms.txt > Use this file to discover all available pages before exploring further. # Node reference > Find every workflow node, what it does, and when to use it. Use this reference to choose the next node in a workflow. Each row explains what the node does and when it is a good fit. Follow the link for its fields, setup, and examples. 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. **Loop** and **Deep Research** also need their workspace features enabled. ## Actions | Node | How it works | Use it when | | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | | [**Send to Webhook**](/workflows/steps-actions#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**](/workflows/steps-actions#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**](/workflows/steps-actions#date-transformer) | Moves a date forward or backward and saves the result. | A later node needs a date such as one day before a meeting. | | [**Create Variable**](/workflows/steps-actions#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](/workflows/steps-crm) shows each provider version separately. | Node | Provider | How it works | Use it when | | ------------------------------------------------------------------------------------------------- | ---------------------- | -------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- | | [**Create Record**](/workflows/steps-crm#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**](/workflows/steps-crm#match-record) | Salesforce and HubSpot | Finds one 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**](/workflows/steps-crm#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**](/workflows/steps-crm#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**](/workflows/steps-crm#create-activity-or-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**](/workflows/steps-crm#match-activity-or-engagement) | Salesforce and HubSpot | Finds one 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**](/workflows/steps-crm#update-activity-or-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**](/workflows/steps-crm#create-association) | HubSpot | Links two HubSpot records with a default or labeled relationship. | You must connect records such as a contact and company. | | [**Match Default Record**](/workflows/steps-crm#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**](/workflows/steps-sequencing#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**](/workflows/steps-sequencing#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**](/workflows/steps-sequencing#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**](/workflows/steps-sequencing#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**](/workflows/steps-sequencing#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**](/workflows/steps-sequencing#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**](/workflows/steps-sequencing#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**](/workflows/steps-notifications#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**](/workflows/steps-notifications#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**](/workflows/steps-notifications#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**](/workflows/steps-notifications#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**](/workflows/steps-enrichment#enrich-data) | Uses one 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**](/workflows/steps-ai#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**](/workflows/steps-research) | 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**](/workflows/steps-routing-scheduling#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**](/workflows/steps-routing-scheduling#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. | ## Logic and timing | Node | How it works | Use it when | | ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- | | [**Multi-Branch**](/workflows/steps-logic-timing#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**](/workflows/steps-logic-timing#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. | | [**Loop**](/workflows/steps-logic-timing#loop) | Repeats the nodes inside it until an exit condition, pass limit, or time limit stops it. | The same group of nodes must run more than once with a clear stop rule. | | [**Time Delay**](/workflows/steps-logic-timing#time-delay) | Pauses the workflow for a duration, then continues. | A later action must wait, such as a follow-up one 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**](/workflows/steps-enrichment#abstract-geolocation-legacy) | 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. |