> 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-notify-stakeholder.md).

# Notify stakeholder

Journey step that sends a notification email with your own message to one or more email addresses.

The Notify stakeholder step sends an email with your own message to one or more email addresses. Use it to alert a colleague, for example when a contact submits a form.

<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-92daa1290311cb80b66951918181117b8edd79a2%2Fjourney-step-notify-stakeholder-dialog.png?alt=media" alt="Notify dialog with recipient email addresses, a subject line and a notification message that uses contact fields"></div>

## Settings

* **Recipient email address** — the address to send the notification to. Separate several addresses with commas.
* **Subject line** — the subject of the notification email.
* **Notification message** — the text of the email.

## Use contact fields

Type `@` in any of the three fields to insert a contact field, such as the contact's name, company or email address. The field is filled in with the details of the contact who reaches the step.

Because this also works in **Recipient email address**, the notification can go to someone stored on the contact. For example, if the contact card holds the email address of the contact's key account manager, insert that field to send the notification to the right person for each contact.

To notify someone by email or SMS straight from a campaign, without a Journey, use the [Send notification automation](https://support.emarketeer.com/guides/guides/campaigns/campaign-automations/campaign-automation-send-notification.md).

Click **Apply** to save the step.

This step is not the same as the notifications eMarketeer sends you about your account and your tasks. For those, see [Notification system](https://support.emarketeer.com/references/references/notification-system.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/journey-step-notify-stakeholder.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.
