> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/workflows.md).

# Workflows

Connect triggers, routing, scheduling, and follow-up actions.

A workflow starts from a trigger and follows connected steps. Use it to capture a lead, qualify it, choose an owner, open a scheduler, update your CRM, and notify the team.

**Open Workflows.** Admins create and publish flows; access to individual workflows can also be shared.

## Explore workflows

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><strong>Create a workflow</strong></td><td>Add steps and connect the outcomes of a lead journey.</td><td><a href="/workflows/create-a-workflow.md">Create a workflow</a></td><td><a href="https://1584026818-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV2wz5iuVqF38uyorXQp5%2Fuploads%2F7kcPURcldgL3DldTwRGY%2Fdistro3-workflow.webp?alt=media">distro3-workflow.webp</a></td></tr><tr><td><strong>Triggers</strong></td><td>Choose what starts a run and which data it supplies.</td><td><a href="/workflows/triggers.md">Workflow triggers</a></td><td><a href="https://1584026818-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV2wz5iuVqF38uyorXQp5%2Fuploads%2FovULWBSMT4XqN11NpLk5%2Fdistro3-routing.webp?alt=media">distro3-routing.webp</a></td></tr><tr><td><strong>Show Scheduler</strong></td><td>Offer meeting times after qualification and routing.</td><td><a href="/workflows/show-scheduler.md">Show Scheduler</a></td><td><a href="https://1584026818-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV2wz5iuVqF38uyorXQp5%2Fuploads%2FEXoO5bJigqAN1OiIcMR7%2Fdistro3-calendar.webp?alt=media">distro3-calendar.webp</a></td></tr><tr><td><strong>Logs and troubleshooting</strong></td><td>Follow a run and find the step that needs attention.</td><td><a href="/workflows/logs.md">Logs and troubleshooting</a></td><td><a href="https://1584026818-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FV2wz5iuVqF38uyorXQp5%2Fuploads%2Fv5FdtB08qK1iaTZrvLwd%2Fdistro3-logs.webp?alt=media">distro3-logs.webp</a></td></tr></tbody></table>

## Build your first flow

Start with [Create a workflow](/workflows/create-a-workflow.md), then choose the [trigger](/workflows/triggers.md) that fits the journey.

A simple demo flow looks like this:

```
New form submission
  → Show Scheduler
      Booked → Notify in Slack
      Not booked → Notify by Email
```

Add CRM matching, a rulebook, or enrichment when you need more specific routing.

## Choose a guide

| I need to…                                   | Guide                                                         |
| -------------------------------------------- | ------------------------------------------------------------- |
| Add and connect steps                        | [Create a workflow](/workflows/create-a-workflow.md)          |
| Start from a form, CRM, extension, or API    | [Triggers](/workflows/triggers.md)                            |
| Use an earlier step's output                 | [Use data in steps](/workflows/use-data.md)                   |
| Choose an owner or queue                     | [Routing steps](/workflows/routing-steps.md)                  |
| Offer meeting times                          | [Show Scheduler](/workflows/show-scheduler.md)                |
| Find or update CRM records                   | [CRM steps](/workflows/crm-steps.md)                          |
| Send messages or enroll a lead in a sequence | [Notifications and follow-up](/workflows/notifications.md)    |
| Branch, wait, or request approval            | [Logic and human steps](/workflows/logic.md)                  |
| Make changes live                            | [Test, publish, and versions](/workflows/test-and-publish.md) |
| Explain a run or investigate a failure       | [Logs and troubleshooting](/workflows/logs.md)                |
| Start from the seller's browser              | [Browser extension](/workflows/extension.md)                  |
| Start from your own system                   | [API and webhooks](/workflows/api-and-webhooks.md)            |
| See the available building blocks            | [Step reference](/workflows/step-reference.md)                |

Workflows replace the old router configuration model. See [Move from the old routers](/migrate.md) for complete examples.

## More guides

* [Handle sequence enrollment outcomes](/workflows/sequence-outcomes.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.distro.so/workflows.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.