Secure Webhook-to-Email

Turn a JSON request into an HTML email that can only ever reach you.

Send reports, summaries, and alerts from your scripts and scheduled jobs without giving each of them mail credentials. They post JSON to one webhook. The workflow checks it and sends you an HTML email.

• Header token. Requests without the right token are refused before the workflow runs.
• Validation and size limits. A one-line subject and an HTML body under a size cap. Anything else gets a clear error back.
• Fixed recipient. The address lives in your config, never in the request. A leaked token can only send email to you.
• JSON responses. Callers get a plain success or a list of what was wrong.
• No stored content. Execution data isn't saved, so report contents don't pile up in n8n's database.

What's included

• 1 workflow JSON file
• README with setup, configuration, and example requests
• Docker self-hosting guide
• License for one business

Requirements

• Self-hosted n8n 2.x (tested on 2.42.6)
• An SMTP mail account

License

One license covers one business, for unlimited use in its own operations. Setting it up for a client? You can, as long as that client's business has its own license. No reselling or redistributing the files. Free updates for 12 months from purchase. Full terms are in the license in the download.

FAQ

What if my token leaks?

Whoever has it can only email the one address in your config, though they could still flood it. Rotate the token in n8n to shut them out.

Can callers choose the recipient?

No. Extra fields like to are ignored.

What can I send with it?

Anything your scripts can turn into HTML: nightly reports, backup summaries, form digests, alerts.

What if the HTML comes from someone I don't trust?

Switch the body mode to text and the content is escaped and shown as plain text.

What does a caller get back?

A JSON response: success, a list of validation errors, or a notice that the mail server refused the message.