> 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/step-reference.md).

# Workflow step reference

Use this reference to find the step that does the job you need. Exact fields and available resources depend on your connected tools.

## Routing and scheduling

| Step                  | Purpose                                                                         |
| --------------------- | ------------------------------------------------------------------------------- |
| **Assign from Queue** | Select a member through a queue's routing profile.                              |
| **Apply Rulebook**    | Apply ordered business rules to choose a person or queue and assign the member. |
| **Find Queue**        | Look up a queue by supported attributes.                                        |
| **Show Scheduler**    | Offer meeting times and continue on Booked or Not booked.                       |
| **Cancel Meeting**    | Cancel the referenced meeting through the supported meeting operation.          |

See [Routing steps](/workflows/routing-steps.md) and [Show Scheduler](/workflows/show-scheduler.md).

## Logic and human decisions

| Step                 | Purpose                                                  |
| -------------------- | -------------------------------------------------------- |
| **Branch**           | Follow the first matching condition group, or Otherwise. |
| **Split Traffic**    | Choose a weighted experiment path.                       |
| **Set Variables**    | Prepare named values for later steps.                    |
| **Shift Date**       | Transform dates for later steps.                         |
| **Wait**             | Pause until the configured time.                         |
| **Request approval** | Wait for a person's decision.                            |
| **Request input**    | Ask a person for typed information.                      |

See [Logic, timing, and human steps](/workflows/logic.md).

## Records

**HubSpot:** Match Record, Create Record, Update Record, Match Engagement, Create Engagement, Update Engagement, and Create Association.

**Salesforce:** Match Record, Create Record, Update Record, and Convert Lead. Task and Event shortcuts help configure record steps for activity logging.

**Attio:** Match Attio Record, Create Attio Record, and Update Attio Record.

**Other record actions:** Create Loops Contact and Marketo Create/Update Record.

See [CRM steps](/workflows/crm-steps.md).

## Notifications and external requests

* **Notify in Slack**, **Create Slack Channel**, and **Add Members to Slack Channel**.
* **Notify by Email**.
* **Call Webhook**, with request presets for supported services.

See [Notifications and follow-up](/workflows/notifications.md).

## Enrichment and AI

**Enrich Lead** fills person or company details through one provider or a saved enrichment chain. Supported chain providers include Clearbit, Apollo, People Data Labs, Wiza, Harmonic, and Amplemarket.

**Abstract Email Reputation**, **Check Email (Icypeas)**, and **Look up IP address** provide the corresponding checks or lookup.

**AI Prompt** sends instructions and selected inputs to the configured model connection. Choose the supported result fields when later steps need structured values.

**Web Research** uses the configured research connection to return structured findings. It can take longer than a simple lookup.

See [Enrichment](/data-and-integrations/enrichment.md) and [AI and research](/data-and-integrations/ai.md).

## Sequencing and webinar actions

* Add to Apollo Sequence.
* Add to Amplemarket Sequence.
* Add to Salesloft Cadence.
* Add to Smartlead Campaign.
* Add to Gong Engage Flow.
* Enroll in HubSpot Sequence.
* Add to Outreach Sequence.
* Register for Zoom Webinar.

These steps need provider access, permissions, and the appropriate sender or host. Check [Integration availability](/data-and-integrations/availability.md).

The public picker is the source of truth for what you can add. Internal or retired step names from older implementations are not additional customer-facing features.


---

# 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/step-reference.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.