FEATURE ยท EMAIL TRIGGER

The world's most universal API is email

Half your stack can't do webhooks. All of it can send email. Relaye gives every flow an inbox and turns those messages into clean, templated alerts on every channel.

Available from the Pro plan up ยท Custom domain from Business up
Mission controlemail trigger ยท 4 flowslive
๐Ÿ“ง Email triggernotify+7fK3โ€ฆ@notify.relaye.io
๐Ÿ’ฌ Slack#ops-alerts
โœˆ๏ธ TelegramOps group
๐ŸŽฎ Discord#monitoring
๐Ÿช Webhookapi.acme.io/ingest
Slack #ops-alerts200 ยท 10:42:07
Telegram Ops group200 ยท 10:42:07
Discord #monitoring200 ยท 10:42:08
Webhook api.acme.io/ingest200 ยท 10:42:08
ANY SENDER ๐Ÿ“Ÿ legacy monitor ๐Ÿ“จ contact form ๐Ÿงพ invoicing tool โ†’ ๐Ÿ“ง your relaye address โ†’ ๐Ÿ’ฌ โœˆ๏ธ ๐ŸŽฎ every channel
Why it works

Email in, everything else out

๐Ÿ“ฌ

One address, zero setup

No SMTP servers, no MIME parsing, no polling an inbox. The address works the moment you create the trigger.

๐ŸŒŠ

Fan-out included

The same email becomes a Slack ping, a Telegram push and a webhook POST, each formatted for where it lands.

๐Ÿ–ผ

Attachments understood

Screenshots post as images in chat, CSVs ride along as files. Relaye splits them by type so you never write a parser.

Use cases

Built for the tools that never got webhooks

๐Ÿ“Ÿ

Legacy monitors

The old watchdog that only knows SMTP now pages your on-call in Slack, with the subject as the headline.

๐Ÿ“จ

Contact forms

Every site submission reaches the whole team at once, sender and message templated per channel.

๐Ÿงพ

Invoices and digests

Route receipts and weekly reports to a webhook or the relay queue, where your systems can consume them.

๐Ÿ‘ต

That one vendor

Every stack has the tool that can only email. Now it participates in your incident flow like everything else.

The trigger

A unique inbox for every flow

Create an email trigger and Relaye mints an address just for it. Anything that can send email can now start a flow: legacy monitors, contact forms, invoicing tools, CI jobs.

Your trigger address
notify+7fK3mQ9tZ2@notify.relaye.io
โœ“ unique per trigger โœ“ no SMTP setup โœ“ any sender works
Your own domain ยท Business
alerts@status.acme.ioBUSINESS
โœ“ claim a domain once โœ“ every trigger can live under it
Templates

One email, a different message per channel

Each flow carries its own template. The same alert email becomes a loud Slack ping, a compact Telegram push and a structured webhook POST.

๐ŸŽ›Flow templateSlack ยท #ops-alerts
template.erb LIQUID
# subject becomes the headline
๐Ÿšจ {{ email_body.subject }}
from {{ addresses.from.address }}

{{ email_body.body.text }}

{% if email_body.attachments != empty %}๐Ÿ“Ž {{ email_body.attachments.size }} attachment(s){% endif %}
โœ“Conditionalsper destination
โœ“Live previewbefore you save
Available from the Pro plan up
Every email counts as one event toward your plan's monthly quota.
Hobby โœ• Pro โœ“ Business โœ“ + your domain Platform โœ“

Your stack can already send email

Put it to work. Start free, add the email trigger on Pro.

Start on Pro    See pricing โ†’
Pro from $29 / mo ยท 25,000 events included