Email to Channel

Give any service your channel's email address and its messages land in the channel — attachments intact, read by each member in their own language.

Email to Channel

Every channel can have its own email address, and so can your personal Inbox. Anything that sends email — monitoring alerts, ticketing systems, CRMs, billing, CI pipelines, newsletters, a colleague forwarding a thread — lands there as a regular message: the sender named, attachments kept, signatures and quoted reply tails stripped. Members see it live on web and desktop, get a push on mobile, and read it in their own language. The Email to Channel feature page shows this in action.

Message flow is one-way: email → InterMIND. Replying inside the channel does not send email back.

Creating a channel address

Only the channel host can create, see, or remove the address:

  1. Open the channel and click the display-settings gear icon in the chat header
  2. Choose Email to channel
  3. Click Create address — you get a private address of the form <token>@in.intermind.com
  4. Copy it and paste it wherever a tool asks for a notification email

The same dialog offers New address (rotate) and Remove address. Rotating or removing takes effect immediately — the old address stops working.

Your Inbox address

Your personal Inbox has an address too: open the Inbox chat, gear icon → Email to Inbox. Emails sent there are visible to you alone. Use it for things only you should see; use a channel address for things the team should see.

Keep the address private

The address is a capability: anyone who has it can post into the channel, so treat it like a password. If it leaks, issue a new one. Mail to an address that does not exist is dropped silently — no bounce, no reply — so a guessed address gives an attacker nothing to go on.

What arrives, and how

  • Text — the plain-text part is used; an HTML-only email is converted to text. Bodies are capped at 100,000 characters
  • Sender — the message is attributed to the sender's name and address, not to the channel host, and translated for each reader like any external message
  • Subject — kept as the first line of the message
  • Signatures and quoted tails — stripped, so a forwarded thread shows the new content rather than the whole history
  • Attachments — kept as file messages, each up to 25 MB

Limits

  • Attachments count toward your team's storage pool. When storage is full the text still arrives and the attachment is skipped, with a note in the message saying so
  • Up to 30 emails per hour per address; anything beyond that in the same hour is dropped
  • Email to channel is available on every plan