Webhook Ingester

A self-hosted solution to store all your Resend webhook events in your own database.

The Resend Webhook Ingester is an open-source Next.js application that receives, verifies, and stores all your webhook events in your own database. Deploy it to your infrastructure and gain full control over your email event data.

While you can build your own webhook handler, the Webhook Ingester provides a production-ready solution with:

• Signature verification using Svix to ensure webhook authenticity
• Idempotent storage that safely handles duplicate webhook deliveries
• Multiple database support including PostgreSQL, MySQL, MongoDB, and data warehouses
• One-click deployment to Vercel, Railway, or Render

Get started in minutes with one-click deployment:

Or use Docker:

docker pull ghcr.io/resend/resend-webhooks-ingester

The ingester creates three tables to store webhook events:

Each table includes:

• svix_id - Unique webhook event ID for idempotency
• event_type - The type of event (e.g., email.delivered)
• event_created_at - When the event occurred
• webhook_received_at - When the webhook was received
• Event-specific fields (e.g., email details, bounce info, click data)

The ingester handles duplicate webhooks automatically. Each webhook includes a unique svix-id header, and the ingester uses this to ensure events are stored only once.

If Resend retries a webhook delivery (due to a temporary failure), the duplicate will be safely ignored without creating duplicate records in your database.

SUPABASE_URL=https://your-project.supabase.co
SUPABASE_SERVICE_ROLE_KEY=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...

NEON_DATABASE_URL=postgresql://user:password@ep-xyz.us-east-1.aws.neon.tech/database?sslmode=require

POSTGRESQL_URL=postgresql://user:password@host:5432/database

MYSQL_URL=mysql://user:password@host:3306/database

PLANETSCALE_URL=mysql://username:password@host/database?ssl={"rejectUnauthorized":true}

MONGODB_URI=mongodb+srv://username:password@cluster.mongodb.net/
MONGODB_DATABASE=resend_webhooks

SNOWFLAKE_ACCOUNT=your-account-identifier
SNOWFLAKE_USERNAME=your-username
SNOWFLAKE_PASSWORD=your-password
SNOWFLAKE_DATABASE=your-database
SNOWFLAKE_SCHEMA=your-schema
SNOWFLAKE_WAREHOUSE=your-warehouse

BIGQUERY_PROJECT_ID=your-project-id
BIGQUERY_DATASET_ID=your-dataset-id
BIGQUERY_CREDENTIALS={"type":"service_account","project_id":"..."}

CLICKHOUSE_URL=https://your-instance.clickhouse.cloud:8443
CLICKHOUSE_USERNAME=default
CLICKHOUSE_PASSWORD=your-password
CLICKHOUSE_DATABASE=default

Once your data is stored, you can run analytics queries. Here's an example to get email status counts by day:

SELECT
  DATE(event_created_at) AS day,
  event_type,
  COUNT(*) AS count
FROM resend_wh_emails
GROUP BY DATE(event_created_at), event_type
ORDER BY day DESC, event_type;

db.resend_wh_emails.aggregate([
  {
    $group: {
      _id: {
        day: {
          $dateToString: { format: '%Y-%m-%d', date: '$event_created_at' },
        },
        event_type: '$event_type',
      },
      count: { $sum: 1 },
    },
  },
  { $sort: { '_id.day': -1 } },
]);

SELECT
  toDate(event_created_at) AS day,
  event_type,
  count() AS count
FROM resend_wh_emails
FINAL
GROUP BY day, event_type
ORDER BY day DESC, event_type;

By default, webhook events are stored indefinitely. To implement data retention policies, you can set up scheduled jobs to delete old events.

Example for PostgreSQL (delete events older than 90 days):

DELETE FROM resend_wh_emails
WHERE event_created_at < NOW() - INTERVAL '90 days';