> 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/use-data.md).

# Use data in steps

Use trigger fields and earlier outputs so each action carries the right prospect, owner, and meeting details.

## Insert a value

Open a step's settings and use its data picker. In fields that support it, type `{{` or use the variable control to choose an available value.

Choose the field from the picker instead of typing an output path from memory. The available values depend on the trigger, preceding steps, and the outcome path.

For example:

| Destination                    | Select a value such as…                              |
| ------------------------------ | ---------------------------------------------------- |
| CRM contact email              | The form trigger's email answer.                     |
| Rulebook owner input           | The owner from a matched CRM record.                 |
| Scheduler **Earlier assignee** | The member from Assign from Queue or Apply Rulebook. |
| Scheduler **Booking details**  | The prospect's name, email, and notes.               |
| Slack booking message          | The meeting host, guest, and start time from Booked. |

## Respect the path

An output is only available where the step produced it. A matched record can be used on **Match**; it does not exist on **No match**.

Meeting details from Show Scheduler are available on **Booked**. Use prospect details for a Not booked follow-up instead.

If a value is missing from the picker, check the canvas connections and run **Validate**.

## Match the expected type

Some fields need text; others need a number, record, owner, or configured resource. A CRM owner ID is not interchangeable with a Distro member.

Select a workspace resource, such as a CRM connection or event type, in its resource picker. Use a runtime reference only when the field explicitly supports it.

## Handle missing values

A field can be absent even when the step succeeded. Add a Branch condition such as **has a value**, or use a supported fallback where appropriate.

Do not pass an optional CRM owner straight into a required host without deciding what should happen when it is missing.

## Save reusable values

Use **Set Variables** when a later step needs a derived or named value. Use **Shift Date** for supported date changes, then select its output in the next step.

Use the [Field catalog](/data-and-integrations/field-catalog.md) for reusable person and company fields across your workspace.

After changing form questions or CRM properties, refresh the relevant configuration and validate the workflow again.


---

# 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/use-data.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.