webhook-processing

Verify and process email delivery event webhooks from major providers.

2|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/chunkydotdev/email-skills --skill webhook-processing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webhook-processing
Source: https://github.com/chunkydotdev/email-skills/tree/main/skills/operations/webhook-processing
Command: npx skills add https://github.com/chunkydotdev/email-skills --skill webhook-processing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the critical challenge of reliably receiving, verifying, and processing email delivery event webhooks from major email service providers, eliminating risks of missed events, duplicate processing, unverified malicious requests, and incorrect delivery status tracking.

Core Features & Use Cases

  • Multi-provider signature verification: Secure webhook validation for SendGrid, Postmark, AWS SES, Resend, and Mailgun with provider-specific implementation guidance.
  • Idempotent event processing: Deduplication logic to prevent double-counting bounces, duplicate suppression entries, and corrupted delivery metrics.
  • Cross-provider event normalization: Adapter pattern to convert provider-specific webhook payloads into a consistent internal format for agnostic business logic.
  • Use Case: If you run a SaaS platform that sends 10,000+ transactional emails monthly, use this skill to build a webhook endpoint that automatically suppresses hard bounces and spam complaints to protect your sender reputation and reduce wasted send volume.

Quick Start

Use the webhook-processing skill to build a secure Resend webhook endpoint that automatically adds hard bounce recipients to your tenant-scoped suppression list.

Frequently Asked Questions about webhook-processing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify SendGrid and AWS SES webhook signatures securely?

Webhook signature verification validates incoming requests using provider-specific cryptographic signatures for SendGrid, AWS SES, Postmark, Resend, and Mailgun. This ensures your endpoint only processes authenticated email delivery events and rejects unverified malicious requests.

How do I prevent duplicate processing when receiving email delivery webhooks?

Idempotent event processing uses deduplication logic to prevent double-counting bounces, duplicate suppression entries, and corrupted delivery metrics. This ensures reliable webhook handling even when providers retry delivery or send duplicate event payloads.

What's the best way to normalize email bounce events across multiple providers?

Cross-provider event normalization uses an adapter pattern to convert provider-specific webhook payloads from SendGrid, Mailgun, and AWS SES into a consistent internal format. This allows agnostic business logic to process delivery statuses uniformly across all services.

How do I handle email bounces and spam complaints to protect sender reputation?

Bounce and complaint handling processes delivery event webhooks to automatically suppress hard bounces and spam complaints. This protects your sender reputation and reduces wasted send volume by preventing future emails to invalid or hostile recipients.

Do I need asynchronous processing for high volume transactional email webhooks?

Asynchronous processing architecture is required for reliable webhook handling at high volume. This design supports secure processing of sensitive email metadata and ensures your endpoint responds quickly while managing tenant-scoped suppression lists in the background.