> 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/journey-step-wait-for-trigger.md).

# Wait for trigger

Journey step that holds the contact until they meet a set of conditions, with an optional time limit.

The Wait for trigger step holds the contact at this step until they meet a set of conditions. The contact then moves on to the next step.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-3000a550565c195f7c6160ff30f1fe496c796e79%2Fjourney-step-wait-for-trigger-settings.png?alt=media" alt="Wait for trigger dialog with a form submission condition and a time limit of 3 days"></div>

## Settings

* **Conditions** — click **Set conditions** to choose what the contact must do or match, for example submit a form. The conditions you set are shown in the step. Click **Edit** to change them.
* **Set a time limit** — optional. If the contact doesn't meet the conditions within the time limit, they move to the next step anyway. Enter a number and choose a unit, such as hours or days.

Click **Apply** to save the step.

{% hint style="warning" %}
If you don't set a time limit, the contact does not move on in the Journey until they meet the conditions. A contact who never meets them stays in this step for good. Set a time limit if the Journey should continue for these contacts too.
{% endhint %}


---

# 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/journey-step-wait-for-trigger.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.
