Send email to a Slack channel

Why not a shared mailbox

The default answer to "we need an address the whole team can see" is a shared mailbox, and it is a bad one. Somebody has to own the password, a seat gets billed, and nobody actually checks it — mail sits unread in a place that is nobody's first tab.

Slack's own email-to-channel feature solves the visibility problem, but it sits behind a paid plan and it gives you an address on Slack's domain rather than your own. Handing customers acme-support-aaa1bb@slack-mail.example is not the look you want on an invoice.

MXcatch gives you support@your-domain.com, posts everything it receives into the channel, and does not care which Slack plan you are on.

Setting it up

1. Create an incoming webhook in Slack. In your workspace's app settings, add an Incoming Webhook and pick the destination channel. Slack gives you a URL — that URL is bound to that one channel.
2. Add your domain to MXcatch and point its MX records at us. Per-provider instructions.
3. Create the alias — support, alerts, whatever you want before the @.
4. Add a Slack action to that alias and paste the webhook URL.

Send a test message. It shows up in the channel with the sender, the recipient address, the subject, and a preview of the body.

Useful arrangements

One address per channel

Because each incoming webhook URL is bound to a single channel, routing by address is just a matter of which alias holds which action. billing@ to #finance, support@ to #support, security@ to #security-alerts.

Slack plus your inbox

Actions are independent. Add a forward action next to the Slack one and the message goes to the channel and to a real mailbox, so there is a searchable copy and a repliable thread.

Vendor alerts you cannot configure

Plenty of services only notify by email. Give each one its own address on a catch-all domain — vendor-uptime@, vendor-billing@ — and route each to the channel that should see it. As a bonus, you learn immediately which vendor leaked your address when spam starts arriving at one of them.

Filtering the noise

Posting every message to a channel is how channels get muted. Use routing rules to match only what matters — subject contains failed, sender ends with your monitoring vendor's domain — and let the rest go quietly to the inbox.

When you need more than a post

The Slack action formats a message for humans. If you want the mail as structured data — to open a ticket, extract a PDF, or feed a pipeline — use a webhook action instead, or alongside it. Same message, one goes to the channel and one to your code.