Novu webhook connectors

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.

How to add a connector endpoint

1. Go to the Webhooks page in the Novu dashboard.
2. Select the Endpoints tab.
3. Click Add Endpoint.
4. Search for or select the connector you want to use from the integrations list.
5. Enter a Description to identify this endpoint.
6. Configure the connector-specific connection settings described in the sections below.
7. 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. 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 the event types you want this endpoint to subscribe to.
10. Click Create.
11. 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:

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:

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.

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.

Recommended setup flow

1. Create the destination table in your warehouse with columns for the fields you want to store (for example, event_type, message_id, subscriber_id, payload, created_at).
2. Grant insert permissions to the user or role Novu connects with.
3. Add the connector endpoint in Novu and fill in connection settings (URL, credentials, database, table name, and so on).
4. Define the table schema in the connector configuration so it matches your destination table.
5. Write the transformation to map Novu payloads into that schema. Start from the dashboard template and adjust field names and types for your table.
6. Subscribe to the event types you want to store.
7. 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

Setup

1. Create a ClickHouse table to receive webhook events.
2. Ensure the configured user has permission to insert rows into the target table.
3. In the Novu dashboard, select ClickHouse when adding a webhook endpoint.
4. Fill in connection settings, table schema, and transformation.
5. 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

Setup

1. Create a Snowflake table to receive webhook events.
2. Configure a Snowflake user with key-pair authentication and insert permissions on the target table.
3. In the Novu dashboard, select Snowflake when adding a webhook endpoint.
4. Fill in connection settings, table schema, and transformation.
5. 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

Setup

1. Create a Redshift table to receive webhook events.
2. Create an IAM user with the permissions required to write data to Redshift.
3. In the Novu dashboard, select Redshift when adding a webhook endpoint.
4. Fill in connection settings, table schema, and transformation.
5. 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

Setup

1. Create an SQS queue in your AWS account.
2. Create an IAM user with sqs:SendMessage permission on the target queue.
3. In the Novu dashboard, select SQS when adding a webhook endpoint.
4. Fill in connection settings and review the transformation.
5. 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

Setup

1. Create an SNS topic in your AWS account.
2. Create an IAM user with sns:Publish permission on the target topic.
3. In the Novu dashboard, select SNS when adding a webhook endpoint.
4. Fill in connection settings and review the transformation.
5. 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:

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.