Skip to main content
In addition to standard HTTP webhook endpoints, Novu supports webhook connectors that deliver events directly to third-party services. Use them to route Novu events to data warehouses, analytics databases, and AWS messaging services without building a custom receiver. Novu webhook delivery is powered by Svix. Connector endpoints use Svix transformations to shape each event before it is written to your destination.
Outbound webhooks feature is only available in the Team and Enterprise plans.

​
How to add a connector endpoint

1

Open Webhooks in the dashboard

Go to the Webhooks page in the Novu dashboard.
2

Select the Endpoints tab

In the Novu dashboard, open Settings > Webhooks, then select Endpoints.
3

Add an endpoint

On the Webhooks page, click Add Endpoint.
4

Select a connector

Search for or select the connector you want to use from the integrations list.Webhook integrations list
5

Enter a description

Add a label that helps you identify this connector later.
6

Configure connection settings

Configure the connector-specific connection settings described in the sections below.
7

Define table schema and transformation (data warehouses)

For data warehouse connectors (ClickHouse, Snowflake, Redshift): define the table schema and write a transformation that maps Novu webhook payloads to rows matching that schema. See Data warehouse connectors.
8

Customize transformation (message connectors)

For message connectors (Amazon SQS, Amazon SNS): review and customize the transformation that shapes the message body sent to the queue or topic. See Message connectors.
9

Select event types

Select the event types you want this endpoint to subscribe to.
10

Create the endpoint

Review the configuration, then click Create.
11

Test delivery

Open the endpoint, go to the Testing tab, and Send Example for each subscribed event type. Confirm delivery succeeds in Logs, then verify the row or message appears in your destination.
After the endpoint is created, Novu delivers matching events to your configured destination. You can monitor delivery attempts, retry failed messages, and test the endpoint from the dashboard.

​
Available connectors

Novu supports the following webhook connectors:
ConnectorTypeDescription
ClickHouseData warehouseStore events in a ClickHouse table.
SnowflakeData warehouseStore events in a Snowflake table.
Amazon RedshiftData warehouseStore events in an Amazon Redshift table.
Amazon SQSMessageSend events to an Amazon SQS queue.
Amazon SNSMessageSend events to an Amazon SNS topic.
Additional warehouse connectors (such as BigQuery) may appear in the dashboard. They follow the same table schema + transformation pattern described below.

​
Transformations

Every connector endpoint runs a JavaScript transformation before delivery. The transformation converts the raw Novu webhook into the format your destination expects. In the Novu dashboard, configure the transformation when creating or editing a connector endpoint. Each connector type ships with a default template—use it as your starting point.

​
How to write a transformation

Svix expects a function named handler. For connector endpoints, the handler receives a webhook object with:
PropertyDescription
webhook.eventTypeThe Novu event type (for example, message.sent).
webhook.payloadThe webhook JSON body. Shape depends on the event type—see event types.
webhook.methodHTTP method. Usually "POST".
webhook.urlDestination URL. Generally leave unchanged for connectors.
webhook.cancelSet to true to skip delivery for a given event. Defaults to false.
The handler must return the webhook object after modifying webhook.payload (and optionally other allowed properties). Test your code in the dashboard against a sample payload before going live.
Handle every event type your endpoint subscribes to. Use switch (webhook.eventType) or equivalent logic so each event maps to a valid destination record.

​
Data warehouse connectors

Data warehouse connectors (ClickHouse, Snowflake, Redshift, and similar) insert one row per delivered webhook. Credentials and table location alone are not enough—you must also configure:
  1. Table schema — Column names and types that match your destination table.
  2. Transformation — JavaScript that maps each webhook eventType and payload into a row compatible with that schema.
1

Create the destination table

Create a table with columns for the webhook fields you want to store.
2

Grant insert permissions

Ensure the database user Novu connects with can insert rows into the destination table.
3

Add the connector endpoint

In Novu, add the connector endpoint and fill in connection settings (URL, credentials, database, and table).
4

Define the table schema

Map Novu payload fields to your destination table columns.
5

Write the transformation

Map Novu payloads into your table schema. Start from the dashboard template and adjust as needed.
6

Subscribe to event types

Subscribe to the event types you want to store.
7

Test and verify

Test with Send Example, confirm success in Logs, then query the table to verify rows were inserted.

​
Example transformation

This example maps a message.sent event into a flat row. Adjust field names to match your table schema and add cases for every event type you subscribe to. 
function handler(webhook) {
  switch (webhook.eventType) {
    case "message.sent":
      webhook.payload = {
        event_type: webhook.eventType,
        message_id: webhook.payload.id,
        subscriber_id: webhook.payload.subscriberId,
        channel: webhook.payload.channel,
        created_at: webhook.payload.createdAt,
        raw_payload: JSON.stringify(webhook.payload),
      };
      break;
    // Add a case for each subscribed event type
  }
  return webhook;
}
If deliveries succeed in Novu but no rows appear in your warehouse, the transformation output likely does not match your table schema. Compare the transformed payload in the Logs tab with your table definition.

​
Message connectors

Message connectors (Amazon SQS and Amazon SNS) publish each webhook as a queue message or topic notification. Use the transformation to shape the JSON body your consumers receive. The default template typically forwards the webhook payload. Customize it if downstream workers expect a specific structure (for example, flattening nested fields or adding metadata). 
function handler(webhook) {
  webhook.payload = {
    eventType: webhook.eventType,
    data: webhook.payload,
    receivedAt: new Date().toISOString(),
  };
  return webhook;
}
After creating the endpoint, send a test event and confirm the message appears in your SQS queue or SNS topic subscription.

​
ClickHouse

The ClickHouse connector stores Novu webhook events directly in a ClickHouse table. Use it when you want to analyze notification events in ClickHouse without building a custom ingestion pipeline.

​
Configuration

FieldRequiredDescription
URLYesThe ClickHouse server URL (for example, https://clickhouse.example.com:8443).
UsernameYesThe username used to authenticate with ClickHouse.
PasswordYesThe password for the ClickHouse user.
Table nameYesThe name of the table where events are stored.
DatabaseNoThe ClickHouse database name. If omitted, the default database is used.
Table schemaYesColumn definitions that match your ClickHouse table.
TransformationYesJavaScript that maps webhook payloads to rows matching the table schema.

​
Setup

1

Create a ClickHouse table

Define columns for the webhook event fields you want to store.
2

Grant insert permissions

Ensure the configured user has permission to insert rows into the target table.
3

Select ClickHouse in Novu

In the Novu dashboard, select ClickHouse when adding a webhook endpoint.
4

Fill in connection settings

Enter credentials, define the table schema, and review the transformation.
5

Verify with Send Example

Select event types, create the endpoint, and verify rows with Send Example.

​
Snowflake

The Snowflake connector stores Novu webhook events directly in a Snowflake table. Use it when you want notification data available in your Snowflake data warehouse for reporting, analytics, or downstream pipelines.

​
Configuration

FieldRequiredDescription
Account identifierYesYour Snowflake account identifier.
User IDYesThe Snowflake user used to authenticate.
Private keyYesThe private key for key-pair authentication.
Database nameNoThe Snowflake database where events are stored.
Schema nameNoThe schema containing the target table.
Table nameNoThe table where events are stored.
Table schemaYesColumn definitions that match your Snowflake table.
TransformationYesJavaScript that maps webhook payloads to rows matching the table schema.

​
Setup

1

Create a Snowflake table

Define columns for the webhook event fields you want to store.
2

Configure key-pair authentication

Configure a Snowflake user with key-pair authentication and insert permissions on the target table.
3

Select Snowflake in Novu

In the Novu dashboard, select Snowflake when adding a webhook endpoint.
4

Fill in connection settings

Enter credentials, define the table schema, and review the transformation.
5

Verify with Send Example

Select event types, create the endpoint, and verify rows with Send Example.

​
Amazon Redshift

The Amazon Redshift connector stores Novu webhook events directly in a Redshift table. Use it when you want notification events available in your Redshift data warehouse for analytics and reporting.

​
Configuration

FieldRequiredDescription
RegionYesThe AWS region where your Redshift cluster or workgroup is located.
Access key IDYesThe AWS access key ID with permission to write to Redshift.
Secret access keyYesThe AWS secret access key for the IAM user.
Cluster identifierNoThe Redshift cluster identifier. Required for provisioned clusters.
Workgroup nameNoThe Redshift Serverless workgroup name. Required for serverless deployments.
Database userNoThe database user for provisioned clusters.
Database nameNoThe Redshift database where events are stored.
Schema nameNoThe schema containing the target table.
Table nameNoThe table where events are stored.
Table schemaYesColumn definitions that match your Redshift table.
TransformationYesJavaScript that maps webhook payloads to rows matching the table schema.
For provisioned Redshift clusters, set Cluster identifier and Database user. For Redshift Serverless, set Workgroup name instead.

​
Setup

1

Create a Redshift table

Define columns for the webhook event fields you want to store.
2

Create an IAM user

Grant only the permissions this connector needs.
3

Select Redshift in Novu

In the Novu dashboard, select Redshift when adding a webhook endpoint.
4

Fill in connection settings

Enter credentials, define the table schema, and review the transformation.
5

Verify with Send Example

Select event types, create the endpoint, and verify rows with Send Example.

​
Amazon SQS

The Amazon SQS connector sends Novu webhook events to an Amazon SQS queue. Use it when you want to process notification events asynchronously through your existing AWS messaging infrastructure.

​
Configuration

FieldRequiredDescription
Queue URLYesThe URL of the target SQS queue.
RegionYesThe AWS region where the queue is located.
Access key IDYesThe AWS access key ID with permission to send messages to the queue.
Secret access keyYesThe AWS secret access key for the IAM user.
Endpoint URLNoA custom endpoint URL. Use this when connecting to LocalStack or other SQS-compatible services.
TransformationYesJavaScript that shapes the message body sent to the queue.

​
Setup

1

Create an SQS queue

Use this queue as the destination for Novu webhook events.
2

Create an IAM user

Grant only the permissions this connector needs.
3

Select SQS in Novu

In the Novu dashboard, select SQS when adding a webhook endpoint.
4

Fill in connection settings

Enter your connection credentials and review the transformation before saving.
5

Verify with Send Example

Select event types, create the endpoint, and verify messages with Send Example.

​
Amazon SNS

The Amazon SNS connector publishes Novu webhook events to an Amazon SNS topic. Use it when you want to fan out notification events to multiple subscribers through SNS.

​
Configuration

FieldRequiredDescription
Topic ARNYesThe ARN of the target SNS topic.
RegionYesThe AWS region where the topic is located.
Access key IDYesThe AWS access key ID with permission to publish to the topic.
Secret access keyYesThe AWS secret access key for the IAM user.
Endpoint URLNoA custom endpoint URL. Use this when connecting to LocalStack or other SNS-compatible services.
TransformationYesJavaScript that shapes the notification body published to the topic.

​
Setup

1

Create an SNS topic

Use this topic as the destination for Novu webhook events.
2

Create an IAM user

Grant only the permissions this connector needs.
3

Select SNS in Novu

In the Novu dashboard, select SNS when adding a webhook endpoint.
4

Fill in connection settings

Enter your connection credentials and review the transformation before saving.
5

Verify with Send Example

Select event types, create the endpoint, and verify messages with Send Example.

​
Monitoring and troubleshooting

Connector endpoints support the same delivery monitoring, retry, and recovery features as standard webhook endpoints. From the endpoint details page in the Novu dashboard, you can:
  • View delivery attempts and failure reasons in the Logs tab.
  • Inspect the transformed payload sent to your destination.
  • Resend individual failed events.
  • Recover or replay failed messages from a selected time window.
If deliveries fail consistently, check the following:
SymptomWhat to check
Authentication errorsConnector credentials, IAM permissions, or database user grants.
Schema or type errorsTable schema matches your destination table; transformation output uses the correct column names and types.
Missing rows or messagesDelivery shows success in Logs but destination is empty—transformation may not match the expected insert or message format.
Unhandled event typesTransformation includes a branch for every subscribed event type.
If the destination service is unreachable from Novu’s webhook infrastructure, deliveries will continue to retry according to the retry schedule before the endpoint is disabled.