> ## 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.

# Workflow node reference for Default

> Every node you can add to a workflow in Default, grouped by job: actions, CRM records, sequencing, notifications, enrichment, AI, routing, scheduling, and logic.

This reference lists every node you can add to a workflow in Default. Each row explains what the
node does and when it is a good fit. Follow the link for its fields, setup, and examples.

> [!NOTE]
>
> 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**](https://docs.os.default.com/workflows/steps-actions.md#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**](https://docs.os.default.com/workflows/steps-actions.md#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**](https://docs.os.default.com/workflows/steps-actions.md#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**](https://docs.os.default.com/workflows/steps-actions.md#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](https://docs.os.default.com/workflows/steps-crm.md) shows each provider version separately.

| Node | Provider | How it works | Use it when |
| - | - | - | - |
| [**Create Record**](https://docs.os.default.com/workflows/steps-crm.md#create-record) | Salesforce and HubSpot | Creates a CRM record, Salesforce Task or Event, or HubSpot engagement from mapped workflow data, and can connect an activity to another record. Salesforce can update a matching record instead. | The workflow must add a new lead, contact, account, company, deal, or another supported object, or record a call, email, meeting, note, or task. |
| [**Match Record**](https://docs.os.default.com/workflows/steps-crm.md#match-record) | Salesforce, HubSpot, and Default | Finds 1 record, activity, or Default queue, 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, or find a queue before another routing node uses it. |
| [**Update Record**](https://docs.os.default.com/workflows/steps-crm.md#update-record) | Salesforce and HubSpot | Changes mapped fields on a record or activity selected from an earlier node. | The workflow already has the record ID and must change its fields, status, or owner. |
| [**Convert Lead**](https://docs.os.default.com/workflows/steps-crm.md#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 Association**](https://docs.os.default.com/workflows/steps-crm.md#create-association) | HubSpot | Links 2 HubSpot records with a default or labeled relationship. | You must connect records such as a contact and company. |

When a HubSpot engagement is selected, the canvas labels these nodes **Create Engagement**,
**Match Engagement**, and **Update Engagement**.

## Sequencing

| Node | How it works | Use it when |
| - | - | - |
| [**Add to Sequence**](https://docs.os.default.com/workflows/steps-sequencing.md) | Adds 1 person to a sequence, cadence, campaign, or flow in the tool picked in **Provider**: Outreach, Salesloft, Apollo, Amplemarket, HubSpot, Gong Engage, or Smartlead. | A sales engagement tool should start outreach for the lead. |

## Notifications and Slack

| Node | How it works | Use it when |
| - | - | - |
| [**Send Slack Message**](https://docs.os.default.com/workflows/steps-notifications.md#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**](https://docs.os.default.com/workflows/steps-notifications.md#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**](https://docs.os.default.com/workflows/steps-notifications.md#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**](https://docs.os.default.com/workflows/steps-notifications.md#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**](https://docs.os.default.com/workflows/steps-enrichment.md#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**](https://docs.os.default.com/workflows/steps-ai.md#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**](https://docs.os.default.com/workflows/steps-research.md) (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**](https://docs.os.default.com/workflows/steps-routing-scheduling.md#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**](https://docs.os.default.com/workflows/steps-routing-scheduling.md#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**](https://docs.os.default.com/workflows/steps-routing-scheduling.md#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](https://docs.os.default.com/rules-of-engagement.md). |
| [**Cancel meeting**](https://docs.os.default.com/workflows/steps-routing-scheduling.md#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**](https://docs.os.default.com/workflows/steps-logic-timing.md#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**](https://docs.os.default.com/workflows/steps-logic-timing.md#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**](https://docs.os.default.com/workflows/steps-logic-timing.md#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. |

## Notes on the canvas

A **Note** is a text card you leave on the canvas, for example to explain a branch to your
teammates. A note never runs, and nothing connects to it.

Notes are not in **Add Node**. Select **Add Note** in the canvas toolbar, or press `S`. Type in
the note and drag its edge to change its width. Open the note's menu to pick a color, **Yellow**,
**Pink**, **Blue**, or **Green**, or to select **Delete note**. Notes save to the draft and
publish with the workflow, like any other change.

## 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**](https://docs.os.default.com/workflows/steps-enrichment.md#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. |
| [**Create Activity** / **Create Engagement**](https://docs.os.default.com/workflows/steps-crm.md#workflows-built-with-the-older-steps) | Existing workflows keep running unchanged. The sidebar shows **This step is deprecated**. | Use **Create Record** with a Task, Event, or engagement as the object. |
| [**Update Activity** / **Update Engagement**](https://docs.os.default.com/workflows/steps-crm.md#workflows-built-with-the-older-steps) | Existing workflows keep running unchanged. The sidebar shows **This step is deprecated**. | Use **Update Record** with a Task, Event, or engagement as the record type. |
| [**Match Activity** / **Match Engagement**](https://docs.os.default.com/workflows/steps-crm.md#workflows-built-with-the-older-steps) | Existing workflows keep running unchanged. The sidebar shows **This step is deprecated**. | Use **Match Record** with a Task, Event, or engagement as the record. |
| [**Match Default Record**](https://docs.os.default.com/workflows/steps-crm.md#workflows-built-with-the-older-steps) | Existing workflows keep running unchanged. The sidebar shows **This step is deprecated**. | Use **Match Record** with **Source** set to **Default**. |

Related: [Sales workflow software from Default](https://www.default.com/product/sales-workflow-software)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.