Skip to main content
You’ll learn how to automatically trigger notification workflows when Stripe events occur, such as payments, subscriptions, or customer changes.

Overview

When specific events happen in Stripe (for example, payment, subscription, or customer events), this integration will:
  1. Receive the webhook event from Stripe.
  2. Verify the webhook signature.
  3. Process the event data.
  4. Trigger the corresponding Novu notification workflow.
You can also clone this repository: https://github.com/novuhq/stripe-to-novu-webhooks

Prerequisites

Before proceeding, ensure you have:
1

Install Dependencies

Run the following command to install the required packages:
2

Configure Environment Variables

Add the following variables to your .env.local file:
3

Expose Your Local Server

To test webhooks locally, you need to expose your local server to the internet.There are two common options:
localtunnel is a simple and free way to expose your local server without requiring an account.
  1. Start a localtunnel listener
  2. Copy and save the generated public URL (for example, https://your-localtunnel-url.loca.lt).
Learn more about localtunnel here.
localtunnel links may expire quickly and sometimes face reliability issues.
4

Set Up Stripe Webhook Endpoint

Stripe supports two endpoint types: Account and Connect. Create an endpoint for Account unless you’ve created a Connect application. You can register up to 16 webhook endpoints on each Stripe account.
When you create an endpoint in the Dashboard, you can choose between your Account’s API version or the latest API version. You can test other API versions in Workbench using stripe webhook_endpoints create, but you must create a webhook endpoint using the API to use other API versions in production.
Use the following steps to register a webhook endpoint in the Developers Dashboard.
  1. Navigate to the Webhooks page.
  2. Click Add Endpoint.
  3. Add your webhook endpoint’s HTTPS URL in Endpoint URL.
  4. If you have a Stripe Connect account, enter a description, then click Listen to events on Connected accounts.
  5. Select the event types you’re currently receiving in your local webhook endpoint in Select events.
  6. Click Add endpoint.
5

Add Signing Secret to Environment Variables

  1. Copy the Signing Secret from Stripe’s Webhook Endpoint Settings.
  2. Add it to your .env.local file:
6

Keep the webhook route public

Stripe signs webhook requests itself. Do not put /api/webhooks/stripe behind session authentication.If your app uses Clerk middleware and you protect routes by default, exclude the webhook path:
If you are not using Clerk, skip this step and make sure your framework is not requiring a logged-in session for the webhook route.
7

Create the Stripe webhook endpoint in Next.js

Create app/api/webhooks/stripe/route.ts:
app
The following snippet is the complete webhook route for Stripe in Next.js:
8

Add Novu Workflow Notification Trigger Function

Create app/utils/novu.ts :
app
This helper is for the Next.js route above. For other languages, see the server SDKs.
9

Add or create Novu workflows in your Novu dashboard

In Novu, a Stripe webhook event can trigger one or more workflows, depending on how you want to handle those events.A workflow defines a sequence of actions (for example, sending email or in-app notifications) that run when triggered.The Novu dashboard lets you create a custom workflow from scratch or start from a template.Follow these steps to set up your workflow(s) in the Novu dashboard:

Identify the Triggering Event(s)

Determine which Stripe webhook events will activate your workflow (for example, customer.subscription.created).Your route maps each Stripe event type to a Novu workflow identifier by replacing dots with dashes, so customer.subscription.created becomes customer-subscription-created. Create matching workflow IDs in Novu.
To find a list of all the events Stripe supports and learn more about them, visit the Stripe documentation.
Stripe wraps each event as { id, type, data: { object } }. Your route uses event.data.object as the Novu payload and loads the customer from event.data.object.customer.See the full shape in the Stripe event types docs. A shortened customer.subscription.created object looks like:

Choose Your Starting Point

Browse the workflow template store in the Novu dashboard. If a template matches your use case (for example, a billing or subscription notice), select it and customize it.Create a Novu workflow from a template

Configure the Workflow

  • For a template, tweak the existing steps to align with your requirements.
  • For a blank workflow, add actions like sending emails, sending in-app notifications, Push notifications, or other actions.
  • For a code-first workflow, you can use the Novu Framework to build your workflow right within your code base.

Set Trigger Conditions

  • Link the workflow to the correct webhook event(s).
  • Ensure the Novu workflow identifier matches the mapped Stripe event type (for example, customer-subscription-created).
  • Start Simple: Use templates for common tasks and switch to blank workflows for unique needs.
  • Test Thoroughly: Simulate webhook events to ensure your workflows behave as expected.
  • Plan for Growth: Organize workflows logically (separate or combined) to make future updates easier.
10

Disable Email Delivery by Stripe

By default, Stripe sends email notifications whenever necessary, such as subscription created, updated, and more.To prevent users from receiving duplicate emails, we need to disable email delivery by Stripe for the notifications handled by Novu.
  1. In your Stripe Dashboard, navigate to the Settings.
  2. Under the Product Settings section, navigate to the Billing tab.
  3. Toggle off delivery of the events you want to handle with Novu.
This keeps Stripe from sending the same email that Novu already handles.
11

Test the Webhook

Stripe CLI

Learn how you can test the webhook events using the Stripe CLI.