> For the complete documentation index, see [llms.txt](https://documentation.pushly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.pushly.com/platform/journeys/journey-builder.md).
# Journey Builder
## Journey Builder
The Journey Builder is a visual canvas where you design the flow of steps subscribers will move through after enrollment. The builder uses an automatic layout engine that positions nodes and routes connections cleanly, keeping flows readable even with complex branching paths.
**Canvas Overview**
Every journey starts with an **Entry** node (representing the trigger or schedule configuration) and ends with an **Exit** node. Steps are added between these nodes to define the subscriber's path.
**Placeholder Steps**
New journeys start with a visible **placeholder step** between the entry trigger and exit node. The placeholder makes it immediately clear where to add your first step.
Click the placeholder or use the **+** button on adjacent edges to replace it with a real step. Once replaced, the placeholder is removed from the flow automatically.
**Adding Steps**
To add a step to the journey, click the **+** button on any edge between nodes, or click a placeholder step. The **Add Step Panel** appears as a floating panel with step descriptions organized by category.
**A/B/n Split Testing**
Journeys support **variant split steps** for A/B and multivariate testing directly within the flow. Add a **Split Test** step from the **+** button on any edge to divide subscribers into 2–4 named variant paths — each allocated a configurable percentage of traffic (totaling 100%) — that automatically converge at a downstream join point, so the journey continues as a unified flow after the test.
For the full split-test workflow — configuring variants, reading variant performance, promoting a winner, and viewing revision history — see [Split Testing & Promotion](/platform/journeys/split-testing-and-promotion.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://documentation.pushly.com/platform/journeys/journey-builder.md?ask=&goal=
```
`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.
