Regulatory Incident Webhook Workflow: Email + PDF Reports

Automate Regulatory Notification Webhooks with Email + Branded PDF Delivery Reports

Streamline regulatory incident handling in n8n: this workflow receives notification requests via a webhook, validates your CSV/XLSX recipient list, sends personalized email notifications in throttled batches, then generates and emails a branded PDF delivery report.

What this workflow does

• Receives a POST webhook containing notification details, a recipients CSV/XLSX file, and a shared secret.
• Enforces security by verifying the secret and returning 401 Unauthorized immediately when the request is not authorized.
• Normalizes and validates inputs, decodes the uploaded file, and extracts recipient rows from either CSV or Excel.
• Validates email addresses, removes duplicates, and supports optional recipient limiting in test mode.
• Responds to the webhook with an “accepted” summary after validation.
• Sends personalized emails to each recipient, using the selected notification type or custom templates, and processes recipients in configurable batches with a wait-based throttle while recording sent and failed outcomes.
• Generates a compliance report: aggregates send metrics, builds branded HTML, converts it to a PDF via Gotenberg (HTTP request), and emails the PDF report to the configured recipient.

Use cases

• Regulatory incident teams can trigger notifications from internal systems with a single webhook call.
• SaaS operators can maintain a validated recipient list (CSV/XLSX) for consistent, deduplicated outreach.
• Compliance workflows can produce an auditable PDF delivery report after email dispatch.

Technical details

• n8n nodes/workflow steps include: Webhook, If, Set, Code, Wait, and Email Send.
• PDF generation is done through Gotenberg using an HTTP request.
• Includes batching/throttling controls (batch size and wait) for reliable email sending.

Set your webhook URL, shared secret (header x-notification-secret or body webhook_secret), and report recipient in the workflow configuration to get started.