How to Forward Email to Slack or Discord — Full Setup Guide

Checking your inbox every ten minutes for new customer inquiries is a productivity killer. For modern teams, the source of truth for real-time communication is usually Slack or Discord — not an email client. So why are you still context-switching to check if a lead emailed sales@yourcompany.com?

With email forwarding, you can bridge the gap: all incoming email to your custom domain addresses lands directly in the right Slack channel or Discord server — no polling, no context switching, no missed leads.

Why Route Email to Chat?

Speed is the primary reason. Research from Harvard Business Review and others consistently shows that responding to a lead within 5 minutes increases conversion rates dramatically — sometimes by 100x compared to responding after 30 minutes. Your team lives in Slack or Discord. A notification there is far more visible than a new email badge on a shared inbox nobody is actively watching.

Beyond sales, there are other great use cases for routing email to chat:

• Support aliases — Route support@yourdomain.com to a #support channel so the whole team sees incoming tickets and anyone can claim one.
• Monitoring alerts — If your application sends automated emails (server warnings, cron failures), forward them to a #alerts channel so they don't get lost.
• Partnership inquiries — Route partners@yourdomain.com to a private channel visible only to leadership.
• Contact form submissions — If your website contact form sends to hello@yourdomain.com, get those submissions in Slack without configuring a Zapier automation.

Forwarding Email to Slack — Step by Step

Slack has a built-in "Email" integration that gives every channel a unique email address. Anything sent to that address posts to the channel as a formatted message. Here's how to set it up:

1. Open Slack and go to your workspace. Navigate to the channel you want email to appear in (e.g., #incoming-leads).
2. Open channel settings. Click the channel name at the top → "Integrations" tab → "Send emails to this channel."
3. Get the Slack email address. Slack will generate a unique address like yourworkspace+channelname+token@slack.com. Copy it.
4. Create an alias in Forward. In your Forward dashboard, go to Aliases → Add Alias. Set the alias to leads@yourdomain.com (or whatever makes sense for your use case).
5. Set the destination to your Slack address. Paste the Slack-generated email address as the forwarding destination.
6. Test it. Send an email from an external account to leads@yourdomain.com. Within seconds, it should appear in your Slack channel with the subject line as the title and body as the message content.

Forwarding Email to Discord — Step by Step

Discord doesn't have a native email-to-channel feature, but it does have webhooks — and there's a clean way to build this bridge with a simple middle-layer service. Here's the recommended approach:

1. Create a Discord webhook. In your Discord server, go to Server Settings → Integrations → Webhooks → New Webhook. Choose the target channel, give it a name (e.g., "Email Alerts"), and copy the webhook URL.
2. Use a bridge service. Services like Zapier or Make (formerly Integromat) can listen for incoming email and POST to a Discord webhook. Configure a Zap: "Trigger: New email to alerts@yourdomain.com" → "Action: POST to Discord webhook."
3. Alternatively, use a self-hosted bridge. If you have a small server, you can write a tiny FastAPI or Flask app that accepts an HTTP POST (from Forward's webhook feature, if available) and relays it to Discord.
4. In Forward, create the alias. Point alerts@yourdomain.com to the Zapier/Make catch email address or configure a webhook destination if your plan supports it.
5. Test with a sample email. Send a test email to the alias and verify the Discord webhook fires correctly. Check the Discord channel for the formatted message.

Common Pitfalls and How to Avoid Them

1. Slack channel gets cluttered with automated noise

If you forward every email — including marketing newsletters and automated receipts — to a Slack channel, it quickly becomes unreadable. Solution: set up multiple aliases with different destination channels. leads@ → #sales, support@ → #support, billing@ → #billing.

2. Replies don't come from your domain

When a teammate hits "Reply" in Slack's email thread, the reply comes from Slack's servers, not from leads@yourdomain.com. For customer-facing responses, always reply from your own email client using your domain address. Slack's email integration is best for visibility, not for managing a two-way conversation.

3. Slack rate-limiting on high-volume inboxes

The Slack email integration doesn't have published rate limits, but posting hundreds of emails per hour to a single channel can trigger throttling. If you're routing a high-volume alias (like a public contact form), consider filtering or batching before forwarding.

4. Attachments may not render in Discord

When bridging email to Discord via webhook, attachment handling depends on your bridge implementation. Most webhook message formats are text-only; binary attachments need to be re-uploaded separately if you need them visible in Discord.

Real-World Example Setup

Here's how a small 5-person SaaS team might structure their email forwarding into Slack:

This setup means every important email — from a customer inquiry to a server alert — appears exactly where the right person is already looking. Nothing falls through the cracks.

Getting Started

The entire setup takes under 15 minutes. Add your domain to Forward, create your first alias, grab your Slack channel email address, and connect them. From that point on, every email to your domain alias appears in Slack automatically.