Loading…
Use case · Email to chat
Point the noisy sender at an address, connect Telegram, Slack, Discord or ntfy, and let rules decide what pings. The channel gets a templated one-liner; the full email stays searchable in your HideMy inbox. No Zapier in the middle, no per-email task fees.
one pipeline, start to finish
# pipeline · billing alerts → #on-call
address billing@you.hidemy.world
rule subject contains "payment failed"
channel slack · #on-call
template [billing] {{subject}}
{{from.email}} · {{fields.customer}}
# what the channel sees
[billing] Payment failed: invoice 8841
no-reply@stripe.example · acme-corp
# what it does not see
74 KB of multipart MIME, footers and HTML soup
(the full email stays in your HideMy inbox)The problem
# the usual options
# with hidemy.world
Signal only
[channels]
Telegram, Slack, Discord and ntfy as first-class delivery targets. Connect a channel once and point any pipeline at it. No middleman service to pay or babysit.
[rules]
Rules match on sender, subject or content and run before anything posts. Mail that doesn't match never reaches the channel; it just sits in the inbox.
[ai]
Write the filter as a sentence: “is this a payment failure from a real customer?”. 250 evaluations a month on Lite, 1,000 on Pro.
[template]
Compose the message from {{subject}}, {{from.email}} and extracted fields. The channel gets one line a human can read at a glance.
[fields]
A transformer pulls the invoice id, the amount or the customer name out of the body, and the template drops it straight into the message.
[inbox]
Every email stays searchable in your HideMy inbox for 7 to 365 days depending on plan. The ping is a pointer; the inbox is the copy of record.
[auth]
SPF, DKIM and DMARC are checked on receipt, and rules can require a pass. A forged “payment failed” never wakes your on-call channel.
[webhook]
Prefer your own bot? Use HMAC-signed webhook delivery with retries and replay instead, or the n8n community node, n8n-nodes-hidemy.
How it works
billing@you.hidemy.world in a couple of clicks, then point the sender at it: a Stripe notification address, a vendor, a forward from the old inbox.
Paste a Slack or Discord webhook URL, link Telegram with one tap on our bot, or enter an ntfy topic. Fire a test email and watch it post.
Decide what pings (subject contains “payment failed”) and what it looks like ([billing] {{subject}}). Everything else stays in the inbox.
No testimonials, just configs
Plans
One stream, free: Free
2 addresses, 100 emails a month, all four chat channels included. No card. Enough to put payment failures in front of on-call today.
The team tier: Lite
€9.90/mo: unlimited addresses, 1,000 emails a month and 250 AI rule evaluations, so every noisy sender gets its own address, filter and channel.
Need the REST API or 5 team members? Pro is €24.90/mo. Compare all plans
FAQ
Whatever your template says: a line built from {{subject}}, {{from.email}} and any fields a transformer extracted, like an amount or an order id. No footers, no signatures, no base64 blobs. The channel gets the summary; the full email stays searchable in your HideMy inbox.
No. Telegram, Slack, Discord and ntfy are native delivery channels: the email arrives, rules run, the message posts. There is no per-email task fee because there is no middleman. If n8n is already your glue, there is a community node (n8n-nodes-hidemy), but it's optional.
Rules run before delivery, so only matching mail ever posts. Everything else is still received, stored and searchable in HideMy, which means filtering aggressively costs you nothing. On Lite and up you can phrase the filter as a plain-English AI rule instead of matching on subject strings.
Yes. Pipelines are per-address and you can add several: payment failures to Slack with a template, everything to an HMAC-signed webhook for your own archive, a VIP match to Telegram. Each pipeline has its own rules, channel and template.
Inbound mail is checked for SPF, DKIM and DMARC on receipt, and rules can require a pass before the ping fires. A forged sender claiming to be your payment provider never reaches the channel; the mail is still kept in the inbox if you want to look at it.
Create an address, connect a channel, and put the first clean alert in front of your team in the next ten minutes. Free, no card.