> 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.md).

# Journey Steps

**Steps** are the ordered pages a customer moves through in a journey. Each step is bound to a [page](/product/journeys-and-pages/pages.md), reads and writes the journey's shared data (input/output context), can run [commerce actions](/product/journeys-and-pages/journey-steps/commerce-actions.md) (create order, change plan, cancel, …), and can carry a [role](/product/journeys-and-pages/journey-steps/journey-step-types.md) that mandates the internal writes a step must perform. You manage them in the journey builder (**Content → Journeys → Edit → Steps**).

This section covers:

* [Journey Steps Overview](/product/journeys-and-pages/journey-steps/journey-steps-overview.md) — the step model end to end.
* [Managing Journey Steps](/product/journeys-and-pages/journey-steps/managing-journey-steps.md) — add, reorder, branch, and map data.
* [Commerce Actions](/product/journeys-and-pages/journey-steps/commerce-actions.md) — the operations a step performs.
* [Step Roles](/product/journeys-and-pages/journey-steps/journey-step-types.md) — what a role does and the required actions it brings.
* [Confirmation and Thank-You Steps](/product/journeys-and-pages/journey-steps/step-confirmation-page-step.md) · [Collect Payment as a Separate Step](/product/journeys-and-pages/journey-steps/step-payment-information-as-a-separate-step.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.peakcommerce.com/product/journeys-and-pages/journey-steps.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.