> ## Documentation Index
> Fetch the complete documentation index at: https://novu-c5de82d9-nv-8794-quote-reply-docs.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Email Webhook Email Integration with Novu

> Connect an email webhook provider to Novu to deliver transactional emails through your own HTTP endpoint using a webhook URL and HMAC secret.

Email Webhook lets Novu hand each email payload to an HTTP endpoint you control. Instead of calling a built-in ESP SDK, Novu `POST`s the rendered message to your **Webhook URL** and signs the body with your HMAC secret.

Use this when you want Novu workflows and templates, but delivery goes through an internal service or a provider that is not listed in the Integrations Store.

## Creating an Email Webhook integration with Novu

1. Visit the [Integrations](https://dashboard.novu.co/integrations?utm_campaign=docs-email-webhook) page on Novu.
2. Click **Add a provider**.
3. Locate **Email Webhook** under the Email section and click **Connect**.
4. Enter your:
   * **Webhook URL** (HTTPS endpoint that accepts `POST` JSON)
   * **Secret Hmac Key** (used to sign each request)
   * **Secret Hmac Key Encoding** (optional) — how Novu interprets your Secret Hmac Key when signing requests. Defaults to **Text**. Choose **Base-64** or **HEX** if your verification side stores the key as binary material (for example, an AWS KMS imported key).
   * **From email address**
   * **Sender name**
5. Confirm **Active Integration** is on. New integrations start active by default.
6. Click **Create Integration**.

## Request format

For each email, Novu sends a `POST` request to your webhook URL with:

* `Content-Type: application/json`
* `X-Novu-Signature: <hmac-sha256-hex>` of the raw JSON body, using your Secret Hmac Key

Verify the signature before processing the payload. Reject requests that do not match.

The JSON body includes the rendered email fields Novu already prepared for the subscriber (to, from, subject, html/text content, and related metadata).

### Secret Hmac Key encoding

By default, Novu interprets your **Secret Hmac Key** as plain **Text** (UTF-8 bytes) when computing the HMAC. If the system that verifies the signature holds the key as binary material — for example an AWS KMS imported key — set **Secret Hmac Key Encoding** to match how the key is stored so both sides sign with the same bytes:

| Encoding         | How the key is interpreted                                                                     |
| ---------------- | ---------------------------------------------------------------------------------------------- |
| `Text` (default) | The key value is used as raw UTF-8 text. Existing integrations keep signing exactly as before. |
| `Base-64`        | The key value is Base-64 decoded to raw bytes before signing.                                  |
| `HEX`            | The key value is hexadecimal decoded to raw bytes before signing.                              |

The encoding only changes how the stored key is decoded into signing bytes; the resulting `X-Novu-Signature` is still a hex-encoded HMAC-SHA256 of the raw request body.

<Note>
  Leave this set to `Text` unless your verification side requires binary key material. Changing the encoding on an existing integration changes the signatures Novu produces.
</Note>

<Note>
  Email Webhook is marked beta in Novu. Treat it as a custom delivery bridge and monitor your endpoint health.
</Note>

## Next Steps

<Columns cols={2}>
  <Card title="Configure bcc, cc, and reply-to" href="/platform/integrations/email#sending-email-overrides">
    Learn how to configure bcc, cc, and reply-to for your email notifications using email overrides
  </Card>

  <Card title="Sending email attachments" href="/platform/integrations/email#sending-email-attachments">
    Learn how to send attachments with email notifications
  </Card>

  <Card title="Use different email integration" href="/platform/integrations/email#sending-email-overrides">
    Learn how to use different email provider integrations to be used to send emails
  </Card>
</Columns>