# Create your first Journey

This guide walks through a simple first Journey that is easy to validate and safe to launch.

<figure><img src="/files/ElOtvdPiptjcW8dAdAdk" alt="New empty Journey draft with a single Start node and a plus button to add the next step"><figcaption><p>A new Journey starts with a single Start node. Click the <strong>+</strong> button to add steps.</p></figcaption></figure>

## Goal

Build a basic lifecycle flow with:

* one Start step
* one Wait step
* one Activate step
* one Stop step
* optional exit rules

This is the recommended starting shape for most teams. Once this simple version behaves correctly, you can expand to Segment or Pause Until.

## Before you begin

Make sure you already have:

* access to a Customer Hub
* at least one audience or entry condition you can use
* at least one destination available for Activate
* permission to publish, or a reviewer who can approve the launch

## Step 1: Create the Journey draft

1. Open **Journeys** in DinMo.
2. Create a new Journey.
3. Give it a clear, business-focused name that describes the lifecycle goal (for example, `Welcome series – new signups` or `Re-engagement – 30-day inactive`).

{% hint style="info" %}
A descriptive name makes run history easier to read when multiple Journeys are live at the same time.
{% endhint %}

## Step 2: Configure the Start step

<figure><img src="/files/BYuy3hVHSJDpXqUx4Sqy" alt="Start step panel showing no entry rules defined and an Add entry rule button"><figcaption><p>The Start step panel — click <strong>+ Add entry rule</strong> to define who enters the Journey.</p></figcaption></figure>

Click the **Start** step and add your entry rules.

For a first Journey, keep this simple:

* start from one clear audience or one qualifying rule
* avoid combining too many entry conditions at the beginning

If you enable **Allow Journey Repeat**, make sure re-entry is intentional. If the first activation happens immediately after re-entry, you may create repeated activations faster than expected.

{% hint style="warning" %}
Entry rules are locked once the Journey is published and Active. If you need to adjust who enters, you will need to pause the Journey first.
{% endhint %}

## Step 3: Add a Wait step

Add a **Wait** step after Start.

Why start with a Wait:

* it gives contacts a buffer before activation
* it reduces the risk of activating contacts the moment they enter
* it makes it easier to reason about expected entry and activation timing

For a first Journey, a Wait of 1–2 days is a reasonable default. You can adjust this once you understand how contacts flow through.

## Step 4: Add an Activate step

Add an **Activate** step after the Wait.

Select the destination or destinations that should receive contacts at this point in the flow.

{% hint style="warning" %}
Placing Activate directly after Start with no Wait means contacts will be activated the moment they enter the Journey. This is sometimes intentional, but the publish checklist will flag it as a warning so you can confirm it was deliberate.
{% endhint %}

## Step 5: Add a Stop step

Add a **Stop** step after Activate so the end of the Journey is explicit.

Stop is a terminal node with no outgoing edges. It makes the intended ending visible in the canvas and easier to review.

## Step 6: Add exit rules if needed

Open **Exit rules** if there is a condition that should immediately remove a contact from the Journey, regardless of where they are in the flow.

Good first examples:

* exit once a contact converts (for example, `status = converted`)
* exit once a cancellation event occurs

Exit rules apply across the entire Journey, not to a single branch.

## Step 7: Review the publish checklist

Before publishing, review the validation and warnings shown in the publish checklist.

Pay close attention to:

* **Blocking errors** — these must be resolved before you can publish
  * missing entry rules
  * missing destinations on Activate
* **Warnings** — these do not block publishing but flag risk
  * immediate activation after Start
  * repeated entry without an early delay

{% hint style="danger" %}
Do not dismiss warnings without understanding them. A warning about immediate activation after Start means real contacts will be activated as soon as they enter. If that is not intentional, add a Wait step before Activate.
{% endhint %}

## Step 8: Publish the Journey

Publish only when:

* the entry logic is clear and intentional
* the activation path is understood
* the stopping point is obvious
* any warnings have been reviewed and accepted

Publishing freezes the current configuration as the live version. Entry rules and exit rules are locked until you pause the Journey.

## Step 9: Run and monitor

After publishing, use the available controls to validate the Journey operationally.

Check:

* whether the run started successfully
* whether the run completed successfully
* whether contacts entered when expected
* whether the destination activation count matches your expectation

{% hint style="info" %}
Check run history immediately after the first run. If the Journey is healthy and behaving as expected, you can expand to more complex shapes with confidence.
{% endhint %}

## Recommended first pattern

<figure><img src="/files/YaYOlindE2gt8XGFbP6C" alt="Journey builder showing a complete multi-step flow with Start, Wait, Segment, Activate and Stop nodes"><figcaption><p>A Journey with multiple steps — start simple and expand once the basic flow works correctly.</p></figcaption></figure>

For most teams, this is the safest first shape:

```
Start → Wait → Activate → Stop
```

Then expand to Segment or Pause Until only after the simple version behaves correctly.

## Related pages

* [Publish, Pause, and Resume a Journey](/journey/getting-started/publish-pause-and-resume-a-journey.md)
* [Entry rules](/journey/concepts/entry-rules.md)
* [Wait](/journey/concepts/wait.md)
* [Activate](/journey/concepts/activate.md)
* [Common validation issues](/journey/monitoring-and-troubleshooting/common-validation-issues.md)


---

# 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://docs.dinmo.io/journey/getting-started/create-your-first-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.