# Build Journey

In the Build step of the Journey is the fourth step and several components are designed to facilitate the creation and management of user engagement journeys. Here’s a breakdown of the key components:

{% @arcade/embed flowId="Mp7sH69w6m5Lp54qg6k3" url="<https://app.arcade.software/share/Mp7sH69w6m5Lp54qg6k3>" %}

### Journey Flow

Journey Flow area in the Build screen is a visual workspace where users can see the layout and sequence of steps within a user engagement journey. It shows how each step connects to the next, providing a clear depiction of the campaign flow from start to finish.

### Add Step Button

Add Step button is located at the bottom of the Journey Flow area. This button enables you to add new steps to their journey. Each step represents a specific event or action that contributes to the overall engagement process. By clicking this button, you can expand your journey by incorporating additional interactions or triggers.

<figure><img src="/files/wY6kGwKl21Zl5qHLFTTm" alt="" width="414"><figcaption></figcaption></figure>

### Step Container

Each step within the journey is contained within a Step Container. This container includes several elements. You can click on these containers to edit the configurations and rules for each step. This typically involves setting the criteria for the step, such as the trigger event or the audience segment it targets. The container visually represents the step in the context of the entire journey, making it easy to see where it fits within the flow.

<figure><img src="/files/KJlmyTg2SOUiDa6AWivB" alt="" width="377"><figcaption></figcaption></figure>

### Journey Name and Status

At the top of the screen, the Status area displays the current status of your journey (e.g., Draft, Stopped or Active) and the last saved time. This serves as a quick reference for you to understand which journey you are working on and its progression state.

<figure><img src="/files/px3NNpyegfqVV5eRYm11" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://user.netmera.com/netmera-user-guide/omnichannel-engagement/journey-orchestration/build-journey.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.