> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/guides/journeys/journey-steps.md).

# Journey Steps

The basic steps you can add to a Journey, grouped as in the Add Journey step panel, with a link to each step's settings.

Journey steps are the actions a Journey runs for each contact who enters it. This page lists the basic steps and links to how each one is set up.

Journey steps are not the same as [campaign automations](https://support.emarketeer.com/guides/guides/campaigns/campaign-automations.md), which run a single action when a contact interacts with a component in one campaign.

To add a step, click a dot on the line between two steps in the Journey builder. The **Add Journey step** panel opens, with the steps grouped as below. For a walkthrough of building a Journey, see [Creating your first Journey](https://support.emarketeer.com/guides/journeys/creating-your-first-journey.md).

## Campaign Component

* [**Send Email**](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-send-email.md) — send an email to the contact.
* [**Send SMS / Text message**](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-send-sms.md) — send a text message to the contact.
* [**Notify stakeholder**](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-notify-stakeholder.md) — alert a team member about the contact.

## Logic

* [**Wait for trigger**](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-wait-for-trigger.md) — pause until the contact meets a set of conditions.
* [**Wait**](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-wait.md) — pause for a set amount of time.
* [**If / Else**](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-if-else.md) — branch the Journey on a condition.
* [**Start New Journey**](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-start-new-journey.md) — add the contact to another Journey.

## Lead

* [**Create Lead (MQL)**](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-create-lead.md) — create a marketing-qualified lead.
* [**Change Lead Stage**](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-change-lead-stage.md) — move the lead to another stage.
* [**Delete Lead**](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-delete-lead.md) — remove the lead from all Lead Streams.

## Contact

* [**Legal Basis**](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-legal-basis.md) — set the legal basis for the contact.
* [**Update Subscription**](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-update-subscription.md) — subscribe or unsubscribe the contact.
* [**Contact Category**](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-contact-category.md) — change the contact category.
* [**Update Contact Card**](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-update-contact-card.md) — update a field on the contact card.
* [**Contact List**](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-contact-list.md) — add the contact to, or remove them from, a contact list.
* [**Add / Remove tags**](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-add-remove-tags.md) — tag or untag the contact.

## CRM Journey steps

The **CRM** group holds steps that create records and update data in your connected CRM. They are described with each integration:

* [SuperOffice Journey Steps](https://support.emarketeer.com/integrations/superoffice/superoffice-journey-steps.md)
* [Dynamics - Journey Steps](https://support.emarketeer.com/integrations/dynamics/dynamics-journey-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://support.emarketeer.com/guides/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.
