Turn Trello Into a Shared Inbox for Gmail — Without Exposing Everyone's Email

First, a naming collision: "Trello Inbox" is not a shared inbox

Trello now ships a feature literally called Inbox — a personal capture space next to your boards where your own quick notes and to-dos land before you sort them. Useful, but personal by definition: nobody else sees it.

A shared inbox is a different animal: one team address — support@, hello@, sales@ — whose conversations the whole team can see, claim, and answer, so nothing falls between two people who each assumed the other replied. That's the thing this guide builds, on a normal Trello board.

Why a Trello board makes a good shared inbox (for the right team)

• The workflow is already there. Lists are states (New → In progress → Waiting → Done), members are assignment, comments are internal discussion, due dates are follow-ups. A helpdesk reinvents all of this; your team already knows it.
• Email becomes work, visibly. An email on a board can't hide in someone's personal inbox. The column tells everyone its status without a single "did you see my email?" in Slack.
• It's one less tool. Small teams drowning in 20–60 conversations a day rarely need Zendesk — they need the mail where the work is. (Teams needing SLAs, CSAT and agent analytics: you've outgrown this pattern; use a real helpdesk.)

People have been asking whether Trello can do this for years — the Atlassian Community threads on using Trello as a support desk keep getting new replies. The answer has always been "yes, with an email power-up" — the real question is which architecture.

The classic setup — and its two structural problems

The traditional recipe forwards the shared mailbox to the board: either to Trello's native email-to-board address or to a power-up's intake address. It works, but it inherits two problems:

Problem 1: The forwarding itself

Auto-forwarding corporate mail to an external address is precisely what mail-security policy blocks — the infamous "550 5.7.520 your organization does not allow external forwarding" bounce. If your mailbox is governed (Microsoft 365, managed Workspace), the pipeline may be dead on arrival; here's the full breakdown. Add the native route's quirks — stripped senders, a 7-day reply window, silent attachment failures (catalogued here) — and "just forward it" stops sounding simple.

Problem 2: Everyone reads everything

Forwarded email lands in the card as content — readable by every board member, by design. For a tight support pod, fine. But real boards are rarely tight: there's the contractor helping this sprint, the client watching progress, the new hire, the other department. A shared inbox shouldn't mean shared correspondence — payment disputes, HR-adjacent complaints, and unhappy-customer threads don't belong in front of everyone with board access. Almost nobody talks about this trade-off; it's the main reason we built the privacy model below.

The build: a shared inbox with per-person privacy

Here's the setup we recommend with Email Inbox — no forwarding rules, no intake addresses, the shared Gmail connected directly:

1. Prepare the board. Lists: New requests → In progress → Waiting on customer → Done. Add your team as members.
2. Connect the shared mailbox. Add Email Inbox to the board and sign into the team account (support@yourco.com on Google Workspace, or any Gmail). OAuth consent, two minutes, nothing configured on the mail server. Multiple accounts? Connect them all — sales@ and support@ can feed the same board.
3. Automate intake. Create an automation from a Gmail search — in:inbox is:unread for everything, or narrower like to:support@yourco.com -label:newsletter — targeting New requests. From now on, every matching email becomes a card with sender, subject and attachments intact, 24/7.
4. Claim and route. Whoever takes a card assigns themselves (or you assign at triage). The thread is on the card: full history, files, and a "new email" badge the moment the customer writes back.
5. Reply from the card. Answers go out through Gmail itself — proper threading, the team address in the From line — without anyone opening a mail tab. Move the card to Waiting on customer; the badge will tell you when it's your turn again.
6. Share deliberately, not by default. Here's the inversion: each attached email is visible only to the person who owns it until they grant teammates read or read+write access per card. The client watching the board sees a card titled "Refund request #1042 — in progress"; the correspondence behind it stays private. The card never even reveals an email is attached.
7. Keep the mailbox clean from the board. Archive handled threads, flag spam, bulk-clear the noise — triage actions run against the real inbox, so Gmail stays as tidy as the board.

When a different tool fits better

Honest routing, because one size doesn't fit all:

• You need web forms, a request portal, or a knowledge base → Hipporello's service desk is built exactly for structured intake.
• Your mailbox is Outlook/Microsoft 365 → OAuth Gmail tools can't help; look at forwarding-based options (SendBoard, Hipporello) and clear the forwarding policy first. Our power-up comparison maps this space.
• High volume, SLAs, reporting → a dedicated helpdesk (Zendesk, Freshdesk) earns its cost past roughly a hundred conversations a day.

Frequently asked questions