node-red-contrib-webhookrelay-email 1.0.0
Receive email in Node-RED without SMTP servers or a public IP — unique inbound mailboxes, delivered to your flow over an outbound WebSocket
node-red-contrib-webhookrelay-email
Receive email in Node-RED without SMTP servers or a public IP. Deploying the node mints a unique inbound mailbox on Webhook Relay; mail sent to it is parsed and delivered straight into your flow over an outbound WebSocket — Node-RED is never exposed to the internet.
Typical use: turn alert, report or device emails into flows on a Node-RED running on a laptop, Raspberry Pi or private network.
Quick start
- Install the node (palette manager, or
npm install node-red-contrib-webhookrelay-email) - Get an API key from my.webhookrelay.com/tokens (free tier available)
- Drag the webhook relay email node into a flow, paste the API key (
sk-…) into the secret field (a classic token pair fills both fields), wire it to a debug node and Deploy
The node creates the bucket and its inbound email address for you and logs it:
bucket "node-red-email": send email to <generated>@<inbound-domain>
Nothing is ever deleted and the address stays stable across redeploys; it is also shown on the buckets page. Optionally restrict who can trigger the flow with the Senders allow-list.
Output message
msg.topic is the bucket name, msg.payload the parsed email,
msg.meta the Webhook Relay metadata:
{
"from": "[email protected]",
"to": ["<generated>@<inbound-domain>"],
"subject": "Disk space warning",
"text": "Volume /data is 92% full",
"html": "<p>Volume /data is 92% full</p>",
"attachments": []
}
Receiving webhooks too?
Use the companion node-red-contrib-webhookrelay node — same idea, but for HTTP webhooks.
Development
Local Docker-based Node-RED setup, tests and release process: see AGENTS.md.
