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

# Journey Steps

The Journey Builder gives you a set of step types to combine into automated subscriber flows. Each step does one thing -- send a notification, wait, branch, hold for an action, write to a profile, or hand off to another journey -- and steps connect to form a path subscribers move through one at a time.

<figure><img src="https://810756845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lry9Z27iWOZyQEGAgY7%2Fuploads%2FD7ZLseCm7a5sVCQexa0U%2FScreenshot%202026-11-10%20at%201.36.30%E2%80%AFPM.png?alt=media&amp;token=eb274841-e4af-4938-8287-d5ff0ff4c4e3" alt=""><figcaption></figcaption></figure>

### Step categories

Steps are organized into categories in the **Add Step** panel.

**Notifications**

Send a push notification to subscribers at a point in the journey.

* **Custom Notification** -- A manually composed notification with your own title, body, image, and landing URL.
* **Recommendation steps** -- Personalized notifications driven by catalog data: Abandoned Cart, Saved Item, Recently Viewed, Trending Item, and Personalized Recommendation.

**Timing**

Control when subscribers move to the next step.

* **Delay** -- Hold subscribers for a configured amount of time before continuing.
* **Wait for Event** -- Hold subscribers until they take a specific action (purchase, add to cart, notification click, or catalog item interaction), then route them to the matching path or a Timed out path.

**Logic**

Branch subscribers based on rules or random distribution.

* **Decision** -- Route subscribers into up to nine ordered paths based on rules: profile data, custom attributes, behavior counts, journey status, or cart and catalog items.
* **Split Test** -- Divide subscribers randomly into 2 to 4 named variant paths by percentage for A/B testing. See Split Testing & Promotion.

**Profile**

Write to a subscriber's profile mid-journey.

* **Update Profile** -- Set, clear, or modify a subscriber's custom attributes when they reach this step.

**Journey Management**

Control how subscribers exit or continue across journeys.

* **Move to Journey** -- End this path by sending subscribers into another journey at its Entry step.
* **Exit Journey** -- End a subscriber's journey immediately at this point.

### Copying steps

Any send step, Delay, or Update Profile step can be copied and pasted elsewhere on the canvas -- including into branches of a split test or a decision. See [Copy and Paste Steps](https://documentation.pushly.com/platform/journeys/journey-steps/copy-and-paste-steps.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://documentation.pushly.com/platform/journeys/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 `automate deployments from our CI pipeline` 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.
