Gmail or Outlook to Slack: Send Only the Emails That Match a Sender or Subject to a Channel
Pasting the few emails that matter from Gmail into Slack by hand misses some, and forwarding the whole mailbox fills the channel with mail nobody reads. This guide is for the person who watches a shared or personal inbox at a company of 5 to 100 people and wants only the emails from certain senders, or with certain words in the subject, to appear in the right channel. It compares four ways to do that by what each needs from Slack and from your mail admin, what it posts and how much it can carry, and it shows how to test a filter before it posts anything.
The short answer
- To send a steady stream, such as every alert from one address, give the channel its own email address and forward into it with a Gmail filter or an Outlook rule. That needs a paid Slack plan and a mail system that allows forwarding to an outside address.
- To share one email now and then, use the Gmail or Outlook add-on, which works on any Slack plan. It is manual.
- To post the few emails someone must act on, in a short form, use a trigger that reads your mailbox with your own login and posts when a sender or subject matches. The Kipwise Agent does this for Gmail and Outlook, with the limits listed below.
- With any of them, test the filter against recent mail before it runs, and use a private channel for anything sensitive.
The four ways side by side
Slack's Help Center page on sending email to Slack puts the built-in options in one plan table. The last row below is a different kind of tool, one that watches the mailbox itself.
| Way | What it needs | What lands in Slack | What to watch |
|---|---|---|---|
| Channel email address plus a Gmail filter or Outlook rule | A paid Slack plan, and a mail system that allows forwarding to an outside address | The whole email, as a post every channel member can read | Anyone with the address can post to the channel. A forwarding filter affects only new mail. Outlook rules to outside addresses can be blocked by your admin |
| Slack for Gmail or Slack for Outlook add-on | Any Slack plan. The Outlook add-in works only with Office 365 and the Exchange protocol | One email you choose, sent from the open message | Manual, so it never watches a mailbox. The Gmail add-on caps an email at 1 MB of headers and body, and 30 MB with attachments |
| Slackbot forwarding address | Any Slack plan | One email at a time, in your own direct message with Slackbot, not a channel | Useful for yourself, not for a team channel |
| A trigger that reads your mailbox, such as the Kipwise Agent | Gmail or Outlook connected with your own login, and the agent in Slack | A short post of what you ask for, such as sender, subject and amount | Needs a from, to or subject filter. At most 10 emails per check and 10 runs an hour |
The plan column comes from Slack's own table: a dedicated address for a channel is on paid plans, while the email add-ons and the Slackbot forwarding address are on all plans. The Slack for Gmail listing describes the add-on as a way to share an email from an open message, and gives the size limits above.
Why a forwarding rule fails for some mailboxes
Forwarding is the route Slack's own Help Center suggests, and it has prerequisites that sit outside Slack.
On the Slack side, anyone who holds the address can post. Slack's Help Center says that once you have the email address for a conversation, anyone with it can use it to send email to Slack, and that if mail is not delivered, incoming email may have been disabled for your workspace or org.
On the Gmail side, Gmail sends a verification link to the forwarding address before it forwards anything, and to forward only matching mail you create a filter. A filter that forwards affects only new messages, and a reply is filtered only if it meets the same search criteria, so a reply with different words in the subject can slip past a rule that caught the first message. In a Google Workspace organization, an admin can allow automatic forwarding to any address, to internal addresses only, or turn it off. A Slack channel address is not internal.
On the Outlook side, Microsoft 365 lets users build Inbox rules that forward to outside recipients, but the default for automatic external forwarding changed in 2021 to off for new organizations, and a blocked forward comes back as a non-delivery report. Disabling it also disables the Inbox rules that redirect mail to outside addresses.
A 2023 Microsoft Q&A thread shows how this looks from the user's chair. Someone forwarding their inboxes to a Slack channel wrote that emails were still bouncing, and a Microsoft community moderator asked first whether automatic forwarding was enabled for the tenant, because for a business account it is off by default. That is one thread from 2023, but the mechanism matches the current Microsoft page.
Ask your mail admin whether forwarding to an outside address is allowed before you build the rule, because Microsoft 365 defaults it to off for new organizations and a Google Workspace admin can restrict it to internal addresses. If the answer is no, forwarding is closed to you, and the add-ons or a trigger that reads the mailbox with your own login are what remain.
Who reads the email once it lands
Every member of the channel reads what you post there. Slack notes that in a channel shared with another organization, any email sent to the channel is visible to all members, and that a HIPAA-compliant Enterprise organization cannot send email to Slack at all. Put finance and HR mail in a private channel, and think twice before forwarding anything whole.
A trigger lets you post less than the whole email. Each run gets the sender, the recipients, the subject, the time, the start of the text (up to 1,500 characters), the attachment names and a link, and the agent reads the whole email only when it needs to. Kipwise's own example for this trigger posts the amount from a Stripe invoice email, so a finance channel sees one line and not a full message with a signature and a legal footer.
Two checks keep a trigger from posting the wrong mail. Mail that fails the sender check and that Gmail or Outlook rejected or quarantined never posts. And the sender match is on the address, not the display name: in Kipwise's production test, an email that carried only a matching display name posted nothing.
Test the filter before it posts anything
Test the filter against recent mail before it posts anything, because a filter that is slightly too wide fills a shared channel faster than people can mute it.
In Gmail, type the search into the search box and read the results before you choose Create filter. Gmail's help page suggests exactly that: click Search to see which emails show up, then create the filter. With the Kipwise Agent the preview does it for you. Before you approve, the agent shows how many emails from the last 14 days the filter would have matched, and the newest three.
Read the count as a rate. Forty matches in 14 days is about three a day, which a channel can absorb if people act on each one. Several hundred is a stream, and a stream belongs on the forwarding route or behind a narrower filter. The filter itself needs at least one of from, to or subject, as an address or a domain. Several values in one field mean any of them, and several fields must all hold, so "from stripe.com with invoice in the subject" matches only the invoices. An optional has-attachment condition narrows it further.
Set up a matching-email trigger in Slack
- Connect your mailbox. Gmail and Outlook are separate connections, and connecting Gmail does not grant Drive or Calendar. Only you can complete the connection, and some Microsoft work or school organizations need an admin to approve the app first.
- Mention the Kipwise Agent once in the channel where the posts should land. Use a private channel for finance mail.
- Say what to match and what to post, for example: "Whenever an email from stripe.com with invoice in the subject arrives in my Gmail, post the amount here." If both mailboxes are connected and you name neither, it asks which one you mean.
- Read the preview and the approval card, then approve once. Later runs do not ask again.
- Send a test from another address or ask a colleague to. Mail you send yourself never counts.
- Later, ask the agent to list your jobs, to tell you what happened on earlier runs, including failures, or to cancel the job.
What the trigger will not do
- It will not post every email. The filter needs a from, to or subject, and "every email" is not offered. There is no label trigger either.
- It counts only mail that arrives after setup, from someone other than you. Mail you send never counts. Mail already in the inbox does not post.
- It checks about once a minute and was designed to post within two minutes. In Kipwise's own test on 25 October 2026, the trigger fired 33 seconds after a Gmail test message was sent.
- It handles at most 10 emails per check and runs at most 10 times an hour. The rest are found at the next check.
- It misses mail that a provider lists more than 10 minutes late.
- A lost connection, an admin switching off that provider's mail reading, or five failed checks stop it, and it tells its channel why.
- It counts mail in any folder or label, so a rule that files mail under another label does not stop it. It does not count Gmail chats, spam or trash, or Outlook's Drafts, Deleted Items, Junk Email, Outbox, Conversation History and Sent Items.
Use forwarding for a stream and a matching-email trigger for the few messages someone must act on, because the trigger runs at most 10 times an hour and posts only what you ask for. A supplier that sends two invoices a week suits the trigger. A monitoring address that sends forty alerts an hour does not, and a channel address with a filter fits it better.
Handle failure and edge cases
- Two routes for the same mail. If a forwarding rule and a trigger both watch the same sender, every email posts twice. Pick one route for each sender.
- Replies. A forwarding filter passes a reply only if the reply meets the same criteria, as Gmail's help page says. A trigger treats every new email that meets the filter as a match, a reply included, so choose subject words with that in mind.
- A burst above the limit. If a sender sends more than 10 matching emails in a check, the rest wait for the next check, and the last post says how many were left. If that happens often, narrow the filter or move that sender to forwarding.
- A silent stop. If the posts stop, ask the agent what happened on earlier runs. The causes it lists are a lost connection, an admin switching off mail reading and five failed checks, and the agent says so in the channel.
- A blocked forward. If a forwarding rule bounces, ask your admin about the forwarding policy before you change the rule.
- Regulated data. If your mail holds regulated data, ask whether it may leave the mailbox at all. Slack's Gmail listing notes that Slack has no business associate agreement with third-party app providers.
For replying and drafting from the same mailbox, see the guide to an AI email assistant in Slack. The cards the agent shows are covered in adding human approval to AI agent workflows in Slack.
Verify it works
Send one email that should match and one that should not, from another address. The matching one should appear within a couple of minutes and the other should not. Then watch the channel for a week and keep four counts: posts a day, emails someone found late, posts people muted or ignored, and checks that hit the 10 email limit.
If people mute the channel, the filter is too wide, so narrow it. If someone still finds an important email late, a sender or subject word is missing from the filter. If a sender regularly hits the limit, move that sender to the forwarding route.
What to do next
Today, write down the two or three senders or subject words whose emails someone currently pastes into Slack. For each, decide whether it is a stream or a few messages, and ask your mail admin whether forwarding to an outside address is allowed. For the few-message cases, mention the Kipwise Agent once in the channel, name the sender and the subject word, and read the 14-day preview before you approve. It is $10 per user per month with a 3-user minimum, and there is a free trial, so you can try one filter before you pay.
