> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/journeys-and-pages/journey-steps/journey-steps-overview.md).

# Journey Steps Overview

A **step** is one page in a journey's flow. Each step is bound to a page (built in [Content → Pages](/product/journeys-and-pages/pages.md)) and wired into the journey's shared data context, so information collected on one step is available to later steps.

## Where to find steps

Open **Content → Journeys**, open a journey, and go to the **Steps** tab (in the builder, via **Edit**). Steps are listed in order; the **Flow** tab shows how they connect, including branching.

## What a step carries

Expand a step, or open it with the edit pencil, to see:

* **Page** — the page that renders for this step.
* **Label** — the name shown in the journey's progress / navigation.
* **Role** — an optional behavior hint (see [Step roles](/product/journeys-and-pages/journey-steps/journey-step-types.md)).
* **Input variables** — context values the step reads (e.g. `productId`, `productName`, `productPrice`).
* **Output variables** — context values the step writes for later steps (e.g. `firstName`, `email`, `phone`).
* **Custom fields**, **Disable this step**, and **Configure branching** (advanced).

A typical e-commerce checkout runs **Signup → Billing → Confirm → Complete**, each backed by its own page.

See also: [Managing journey steps](/product/journeys-and-pages/journey-steps/managing-journey-steps.md) · [Step roles](/product/journeys-and-pages/journey-steps/journey-step-types.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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.peakcommerce.com/product/journeys-and-pages/journey-steps/journey-steps-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.