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

# Workflows in Default

> How workflows in Default automate what happens to inbound leads: triggers, nodes, testing, publishing, version history, and run logs.

A workflow in Default is an automation that starts from a **trigger** and then runs a series of
**nodes**.

Default has 8 triggers, including a form submission, an incoming webhook, a meeting status change,
and a new or updated CRM record. Nodes route the lead, enrich it, update your CRM, send a
notification, book a meeting, or call an outside system.

> [!NOTE]
>
> In the sidebar, under **Automation**, select **Workflows** to see every workflow in your
> workspace. Select one to open it in the builder, or create a new one.

## Triggers and nodes

Every workflow has 2 kinds of building block:

* A **trigger** starts the workflow. Each workflow needs at least 1 trigger and can have more
  than 1. See [Triggers](https://docs.os.default.com/workflows/triggers.md) for the full list.
* **Nodes** are the actions that run after the trigger fires, laid out on a canvas. A node
  can route a lead, write to your CRM, or add someone to a sequence. It can also send a
  Slack message, show a scheduler, branch on a condition, and more.

## The workflows list

Opening **Workflows** shows the workflows you have access to. At the top right, **Create new**
makes a **New workflow** or a **New folder**; if you can create only one of them, that button
shows instead. The row above the list has these controls:

* **Folders**: **All workflows**, then 1 pill per folder. Folders that don't fit go under
  **More**. Select a pill to show only that folder. If you can manage folders, right-click a
  folder to **Rename** it in place (or double-click it) or **Delete** it, drag a folder pill
  sideways to reorder it (or focus it and press Alt+Left or Alt+Right), and select the folder
  button after the pills to create one. Folders under **More** are reordered from
  **Reorder folders** at the bottom of that menu.
* **Search**: select the search icon to find workflows by name.
* **View options**: select the sliders icon to open one panel for how the list looks. A dot on
  the icon means filters are on.
  * **Table** or **Cards** switches the view.
  * **Ordering** sorts by **Recently edited**, **Name**, or **Date created**. The icon beside it
    shows the direction and reverses it when selected: newest or oldest first for the dates, A to Z
    or Z to A for names. A new sort starts newest first, or A to Z for names.
  * **Status** (**Active**, **Paused**, **Draft**) and **Trigger type** each take 1 or more
    values. A workflow has to match both.
  * **Reset filters** clears Status and Trigger type and keeps your view, order, search, and
    folder.

The table view shows each workflow's **Last run**, **Status**, **Last edited**,
**Last edited by**, **Created**, and **Created by**.

Each workflow shows a status badge:

* **Draft**: never published.
* **Paused**: published, but turned off.
* **Active**: published and turned on.

## Create a workflow

**1. Open Workflows**

In the sidebar, under **Automation**, select **Workflows**.

**2. Create a new workflow**

Select **Create new**, then **New workflow**. Under **Name your workflow**, enter a name, for
example `Inbound demo requests`, and select **Create workflow** to open it in the builder.

**3. Choose a trigger**

Add a trigger to define what starts the workflow. Then add the nodes that follow.

## Add a node

Nodes sit on the builder canvas as connected nodes. Drag from one node to another to connect
them, or branch a node into more than 1 path.

Select **Add Node** to open the node picker. Choose a node to add it to the canvas.

The picker groups nodes into sections: **Logic**, **Actions**, **AI**, **Records**,
**Notifications & Reminders**, **Enrichment**, and **Sequencing**. Nodes that create, match,
or update CRM records are in the **Records** section.

A section appears only when it holds nodes your workspace can use. Each node you add starts
unconfigured, so open it to set it up.

To leave a comment for your teammates, select **Add Note** in the canvas toolbar. A note never
runs. See [Notes on the canvas](https://docs.os.default.com/workflows/node-reference.md#notes-on-the-canvas).

## Insert data from earlier in the workflow

Most fields accept values pulled from the trigger or from an earlier node. This lets a CRM
field, a Slack message, or a webhook body carry the lead's real data.

Type `{{` in a field to open the data picker. You can also select the **{ }** button in the
field's toolbar.

The picker groups values under **CRM**, **Enrichment**, **AI**, **Slack**,
**Default Objects**, and **Workflow**. Default Objects holds the person and company details
every trigger provides.

Workflow holds scheduling and meeting details, the trigger data, and any values earlier nodes
produced.

In a Slack message field, type `@` instead, or select the **@** toolbar button. This opens a
separate picker for mentioning people.

The mention picker offers mapped Slack recipients, user groups, and upstream references, such
as an account owner. An upstream reference resolves to a real Slack user when the message
sends.

Outside Slack message fields, `@` has no special meaning. Use `{{` there.

## The deployment switch

Each published workflow has a deployment switch next to its status in the builder's top Context Bar.
The status reads **Live** while the published version runs for live traffic, and **Paused** while it
does not. The switch appears after you publish the workflow for the first time.

A new workflow goes live the first time you publish it. Turn the switch off to pause the workflow
without deleting anything, and turn it on again to resume. Publishing new changes keeps the current
state, so a paused workflow stays paused. A duplicated or migrated workflow starts paused, so turn
the switch on after you publish it.

## Test a workflow

**1. Open the test panel**

Select **Test** to open the **Test Workflow** panel.

**2. Choose the trigger**

Choose the trigger to fire.

**3. Edit the payload**

Edit the trigger's sample payload.

**4. Run the test**

Select **Run Test**. The workflow runs with your sample data.

For a workflow that starts from a CRM record trigger, the payload opens as a record. It
already lists the record's identifying field, for example email or domain, and any fields
your trigger's condition checks.

Every listed field starts blank. Fill in real values before you run the test.

Testing is not available yet for workflows that start from a **Meeting Status** or an
**Extension** trigger.

> [!WARNING]
>
> A test performs real actions: it can create or update CRM records, and it sends any
> configured messages or webhooks for real. Use test data you are comfortable sending through.

## Publish a workflow

Your edits save to a **draft** automatically. The draft does not run for live traffic until
you publish it.

* Select **Publish** to make the current draft live. The button reads **Publish** whenever
  you have unpublished edits.
* When the live version matches your draft, a status label replaces the button. It reads
  **Published** plus the live version number, for example **Published v3**.
* Each publish creates a new version, so you can see what was live and when.

Each workflow has 1 draft, shared by everyone in your workspace. Publishing takes the whole
draft live, including any unpublished changes your teammates made.

The version control in the top Context Bar shows whether you are editing the draft or viewing a
published version, including a count of unpublished changes.

### If more than one person is editing

Everyone works on the same draft, so there is no separate copy per person and nothing to merge.

* Publishing publishes everything in the draft, yours and your teammates'. If someone is still
  part-way through a change, publishing takes that unfinished change live too.
* Agree on who publishes. Publish once you are both finished.
* Editing different nodes is safe: both sets of changes land.
* If you both edit the **same** node, the last save replaces the earlier one. Each save writes
  that node's whole configuration.
* Split the work by node to avoid this.
* The builder does not show who else is in the workflow with you, and it does not update live as
  they work. Reload the page to pick up their latest changes before you publish.
* The workflow's details panel shows **Modified**: who changed the workflow last, and when.

### Version history

Select the version control in the top Context Bar. The list shows every published version,
newest first, with who published it and when.

**Current Version** at the top is the draft you are editing.

* Select a version to view it on the canvas. Past versions are read-only; select **Draft** in the
  same control to return to editing.
* Select **Restore to draft** to bring a version back for editing. Use this to undo an unwanted
  publish, or to recover a change captured in an earlier published version.
* Version history holds published versions only. If a draft edit was overwritten before anyone
  published, no version captured it and you cannot restore it.
* Restoring replaces the whole draft with that version, and discards any unpublished changes in
  the draft, including your teammates'. Check with them first.
* Restoring does not publish anything and does not change the **Enabled** switch. Review the
  restored draft before you publish it.

## Review past runs

Select **Runs** in the top Context Bar to see every past run: the version that ran, the record it
processed, the trigger, and whether it succeeded. See [Run logs](https://docs.os.default.com/workflows/run-logs.md) for a
full walkthrough. Select **Canvas** in the same bar to return to the workflow graph.

## Node references

See the [Node reference](https://docs.os.default.com/workflows/node-reference.md) for every node, how it works, when to use
it, and which CRM provider versions it supports.

* [Actions](https://docs.os.default.com/workflows/steps-actions.md): Send to Webhook, Redirect, Date Transformer, Create
  Variable
* [CRM](https://docs.os.default.com/workflows/steps-crm.md): create, match, and update records and activities, create
  associations, and convert a Salesforce lead
* [Sequencing](https://docs.os.default.com/workflows/steps-sequencing.md): add people to Apollo, Outreach, Salesloft,
  Amplemarket, Smartlead, HubSpot, and Gong Engage
* [Notifications](https://docs.os.default.com/workflows/steps-notifications.md): Slack messages and channels, internal email
* [Enrichment](https://docs.os.default.com/workflows/steps-enrichment.md): enrich people and companies, geolocation
* [Deep Research](https://docs.os.default.com/workflows/steps-research.md) (Beta): research the live web and return typed
  fields
* [Routing and scheduling](https://docs.os.default.com/workflows/steps-routing-scheduling.md): Round-Robin, Rules of
  Engagement, show a scheduler, and cancel a meeting
* [Logic and timing](https://docs.os.default.com/workflows/steps-logic-timing.md): branch on conditions, split traffic for
  an experiment, and add a delay
* [AI](https://docs.os.default.com/workflows/steps-ai.md): prompt a model and use its response in later nodes

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.