> For the complete documentation index, see [llms.txt](https://docs.brigge.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brigge.ai/documentation/brigge-for-transformers/pipelines/pipeline-nodes/notification-node.md). # Notification node ## Overview The *Notification* node sends an alert at a defined point in a pipeline run. Use it to notify a person or system when something happens - for example, when certain records are found, a check fails, or a run completes. {% hint style="info" %} One notification is triggered for every payload that the `notification` node receives. {% endhint %} ## Notification types You can choose how notifications are delivered from the following notification types:

Notification type	Summary
Email	Sends the notification to the members of the selected notification group. Notification groups are defined in Brigge settings. Notification group members will only receive these messages if they have opted in to Brigge notifications.
Webhook	Posts the notification to an external endpoint.

## Notification content You can provide notification content (for email and webhook notifications) in two ways:

Content type	Summary
Notification template	A predefined template. Notification templates are defined in Brigge settings.
Content	Write the subject and body directly in notification settings.

## Configuring notifications

Configuration options for the `notification` node are summarised below: {% stepper %} {% step %} **Notification type** Select the required notification type (`email` or `webhook`). {% hint style="info" %} If necessary, you can define both notification types. {% endhint %} {% endstep %} {% step %} **Content type** Choose how you want to provide content for these notifications. If you have an existing template for these notifications, select [notification template](#notification-template). Otherwise, select the [content](#content) option to add the required content directly. {% endstep %} {% step %} **Content** Options for providing content vary, depending on the content type selected in step 2.

Notification template

After selecting `notification template`, you are prompted to select an existing template. For example:

Choose the required template and continue with the node configuration.

Content

Click the `open full-screen editor` button to access a [Markdown](https://en.wikipedia.org/wiki/Markdown#Examples) editor:

{% hint style="info" %} This editor is used for both `email` and `webhook` notification types. For emails, this content is added to the email body. Additionally, you'll see a `subject` field, so you can provide a subject for the email message. For webhooks, this content is added to the webhook body. {% endhint %} Provide required Markdown in the `content` tab. You can use the `preview` tab to see how this will be rendered:

{% hint style="info" %} Some useful Markdown conventions are listed below: ``` # Heading 1 ## Heading 2 ### Heading 3 Paragraphs are separated by a blank line. This is _italic text_ This is **bold text** * This is bullet item 1 * This is bullet item 2 1. This is numbered item 1 2. This is numbered item 2 ``` {% endhint %}

{% endstep %} {% step %} **Finish configuration** Final configuration options vary, depending on the notification type selected in step 1.

**Payload attachments** It's often useful to attach incoming payloads to notification messages. To do this, toggle on the `use the passed payload as a file attachment` setting. Optionally, you can set your preferred filename for payload attachments. For example:

**Notification recipients** Click the `+` symbol in the `notification groups` section:

Then select a `notification group` from the dropdown list. Optionally, you can choose to only notify this group when the pipeline runs in a specific [environment](/documentation/brigge-for-transformers/environments.md) (the default setting is to trigger notifications when the pipeline runs in all environments).

{% hint style="warning" %} One notification email is triggered for every payload that the `notification` node receives. For example, if 10 payloads hit the `notification` node, then each recipient receives 10 emails. {% endhint %} {% hint style="info" %} Notification groups and associated recipients are defined in [Brigge settings](/documentation/brigge-settings.md). You can add as many notification groups as needed. {% endhint %}

Webhook

Click the `+` symbol in the `webhooks` section:

Then update the `webhook URL` field with your required URL. Optionally, you can choose to only fire this webhook when the pipeline runs in a specific [environment](/documentation/brigge-for-transformers/environments.md) (the default setting is to fire when the pipeline runs in all environments).

{% hint style="info" %} You can add as many webhooks as needed. {% endhint %} {% hint style="warning" %} For each defined webhook, one notification is triggered for every payload that the `notification` node receives. For example, if 10 payloads hit the `notification` node then each webhook is fired 10 times. {% endhint %}

{% endstep %} {% endstepper %}