> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cognigy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Email Notification

<a href="/release-notes/2026.1"><Badge className="version-badge" color="blue">Updated in 2026.1</Badge></a>

<Frame>
  <img class="image-center" src="https://mintcdn.com/cognigy-15abf2ba/OU10XTKbB-9IwiZJ/_assets/ai/develop/node-reference/email-notification.png?fit=max&auto=format&n=OU10XTKbB-9IwiZJ&q=85&s=b223e0f8e4a3304964178cc3d5651963" alt="Email Notification Node configuration panel" style={{ width: 'auto' }} width="464" height="124" data-path="_assets/ai/develop/node-reference/email-notification.png" />
</Frame>

## Description

The Email Notification Node allows you to send quick and easy emails during sessions or for in-house communications without requiring any provider settings to be set up in the UI. Instead, you can configure the necessary provider settings in the environment variables and secrets. Only one provider can be set up at a time.

## Restrictions

* Your SMTP Server settings need to be adjusted to use the internal Cognigy Email notification.
* Email attachments are restricted (for example, files, images). If required, use [Send SMTP Email Node](/ai/agents/develop/node-reference/data/send-smtp-email).

## Authentication

This Node supports both Basic Auth and OAuth2 authentication methods.

If you have an on-premises installation, you need to add the following parameters to the `values.yaml` file:

<Tabs>
  <Tab title="OAuth2 (recommended)">
    object:

    ```yaml theme={null}
    smtpEmailNotificationCredentials:
     authType: "oauth2"
     oauth2:
       user: "<smtp-server>@domain.com"
       clientId: "your client id"
       clientSecret: "your client secret"
       refreshToken: "your refresh token"
       accessToken: "your access token"
    ```

    variables:

    ```yaml theme={null}
    EMAIL_NOTIFICATION_SMTP_FROM: "<smtp-server>@domain.com"
    EMAIL_NOTIFICATION_SMTP_AUTH_TYPE: "oauth2"
    EMAIL_NOTIFICATION_SMTP_EMAIL_SERVICE_TYPE: "<email service, for example, Outlook365>"
    EMAIL_NOTIFICATION_SMTP_OAUTH2_TOKEN_ACCESS_URL: "<provider token access url, for example, for Microsoft https://login.microsoftonline.com/common/oauth2/v2.0/token, for Google https://accounts.google.com/o/oauth2/token>"
    EMAIL_NOTIFICATION_SMTP_OAUTH2_EXPIRY_DATE_UNIX_TIMESTAMP: "<unix timestamp for the current accessToken, for example, 1681382246000>"
    EMAIL_NOTIFICATION_SMTP_TLS_REQUIRED: "<tls method, for example, 'tls' for default TLS on port 443, 'starttls' to upgrade an insecure connection on the same port, or 'none' to connect without TLS>"
    ```

    Cognigy.AI caches connections by default, and for OAuth2 connections, Cognigy.AI also caches the refresh and access tokens. To update the refresh token or access token, create a [Snapshot](/ai/agents/deploy/snapshots).
  </Tab>

  <Tab title="Basic Auth">
    object:

    ```yaml theme={null}
    smtpEmailNotificationCredentials:
      authType: "basic"
      basic:
        username: "<your email client's username>"
        password: "<your email clientl's password>"
    ```

    variables:

    ```yaml theme={null}
    EMAIL_NOTIFICATION_SMTP_AUTH_TYPE: "basic"
    EMAIL_NOTIFICATION_SMTP_HOST: "<SMTP_HOST>"
    EMAIL_NOTIFICATION_SMTP_PORT: "<SMTP_PORT>"
    EMAIL_NOTIFICATION_SMTP_FROM: "<smtp-server>@domain.com"
    EMAIL_NOTIFICATION_SMTP_TLS_REQUIRED: "<tls method, for example, 'tls' for default TLS on port 443, 'starttls' to upgrade an insecure connection on the same port, or 'none' to connect without TLS>"
    ```
  </Tab>
</Tabs>

## Parameters

| Parameter         | Description                                                           |
| ----------------- | --------------------------------------------------------------------- |
| Email Sender Name | The name displayed as the sender of the email.                        |
| Recipient         | Comma-separated list of email addresses to send the email to.         |
| Subject           | The subject of the email.                                             |
| Content           | The content of the email. The field supports basic rich text editing. |

<Accordion title="Store location of SMTP Request result">
  | Option             | Description                                                                                |
  | ------------------ | ------------------------------------------------------------------------------------------ |
  | Don't store result | Default option. The result isn't stored.                                                   |
  | Input              | The result is stored at a specified location in the **Input Key to store Result** field.   |
  | Context            | The result is stored at a specified location in the **Context Key to store Result** field. |
</Accordion>

#### Stop on Error

If switched on, the Flow execution will halt in case the mail-sending fails.

<Accordion title="Advanced">
  | Parameter                    | Description                                                                                                                                                          |
  | ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
  | CC Email Addresses           | The CC recipients of your email.                                                                                                                                     |
  | BCC Email Addresses          | The BCC recipients of your email.                                                                                                                                    |
  | Email Priority               | The priority of the email.                                                                                                                                           |
  | Execute Request asynchronous | If switched on, the Flow execution continues directly after the Send Email Node has been triggered. If turned-off, the Flow execution waits until the email is sent. |
</Accordion>