> For the complete documentation index, see [llms.txt](https://docs.bluestorm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluestorm.io/administration/pipelines/notification.md).

# Notification

A notification task is used to send e-mail notifications. The following settings are available for this type of task:

* **Proceed on Failure.** If enabled, the pipeline will continue executing when this step fails.
* **Recpient(s):** Who the notification should be send to:
  * **App Owner.** Send the notification to the app owner(s).
  * **App Administrator.** Send the notification to the app administrator(s).
  * **Owner & Administrator.** Send the notification to all app owners and app administrators.
  * **Specific E-mail.** Send the notification to a specific e-mail address.
* **E-mail Address(es):** The comma separated list of e-mail addresses to send the notification too. Only visible if the Recipient type is set to 'Specific E-mail'.
* **Subject:** The subject of the notification.
* **Message:** The content of the notification. The following tokens can be used in the message and will be replaced when the notification is sent:
  * `{%ApplicationName%}` - The name of the app that is the target for this release.
  * `{%Environment%}` - The name of the target environment for this release.
  * `{%Branch%}` - The name of the branch that is the source of this release.
  * `{%Revision%}` -  The revision ID that is used for this release.
  * `{%ReleaseNotes%}` - The release notes for this release.
  * `{%ReleaseVersion%}` - The release version of this release.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bluestorm.io/administration/pipelines/notification.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.