> 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.md).
# Journeys
A journey is a sequential list of actions (steps) that runs on every contact who matches the criteria set as its starting point.
Journeys are the automation engine in eMarketeer. They let you nurture contacts, update your CRM, and drive other processes without manual work.
## Introduction to journeys
When a new contact matches the criteria (filter) for a journey, the contact enters the journey and moves through the steps in order.
## Key benefits
Journeys can be used to:
* Nurture leads from your website
* Automate tasks in eMarketeer
* Create and update tasks in your CRM
* Automate your lead board
And more. Using the filter as a starting point, combined with the logic and steps available, gives you a powerful tool for automating any process.
## System requirements
You can use journeys even without purchasing the add-on. In trial mode you can create as many journeys as you like, but only one journey can be active at a time.
## What to do next
[Learn how to create your first journey.](/guides/journeys/creating-your-first-journey.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.md?ask=&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.
