Trello Email-to-Board: 8 Limitations You'll Hit (and How to Fix Each)

A 30-second primer on email-to-board

Every Trello board gives each member a unique, secret email address (find yours in the board menu's email-to-board settings). Send or forward a message to it and Trello creates a card: subject becomes the title, body becomes the description, attachments come along, and you can even set a list, labels and members with special syntax in the subject line. Atlassian's reference is Creating cards by email.

For "get this one email onto the board before I forget," it's great. The trouble starts when you try to run a real workflow — support requests, invoices, client threads — through it. Then the design decisions underneath start to show.

1. You can't customize the address

The board address looks like a long random string at boards.trello.com. You can regenerate it, but you can't choose it — no help@yourcompany.com, ever. Customers won't email a robot address, so in practice you end up forwarding from a real mailbox anyway, which is where limitation #4 is waiting. Users have asked Atlassian for personalized board addresses; the answer remains no.

Fix: keep your real address (help@, sales@, you@) as the public face and connect that mailbox to Trello — either with a forwarding rule (see #4) or with a power-up that reads the mailbox directly.

2. Cards are created as you — the real sender vanishes

Because the address is tied to your membership, every card created through it is attributed to you. The customer who actually wrote the email becomes plain text buried in a forwarded body — no avatar, no reply-to, nothing structured. One long-running community thread asks exactly this: how do I get the originating email address? You don't.

Fix: if sender identity matters (support, sales, recruiting — i.e. always), use an integration that preserves the real sender on the card instead of stamping your own name on every request.

3. Replies thread onto the card for only ~7 days — then they fork

This is the one that surprises everyone. Replies to a card-creating email are appended to the card as comments — but only for a limited window (about seven days). After that, further replies on the same thread create brand-new cards, quietly splitting one conversation across several places. And even inside the window, people report replies never arriving as comments at all.

Fix: for any conversation that lives longer than a week (so: every real client thread), the card needs to be linked to the thread, not seeded by a copy of it. That's an architectural difference — see the last section.

4. Corporate mail servers block the forwarding you depend on

To automate email-to-board you need an auto-forwarding rule from your real mailbox to the board address. On Microsoft 365 and many Google Workspace setups, external auto-forwarding is disabled by default as an anti-exfiltration measure. The result is a bounce like:

550 5.7.520 Access denied, Your organization does not allow external forwarding.

That's not a Trello bug — it's your IT policy working as intended, and admins rarely make exceptions. There's a whole community thread of people hitting it, and we wrote a dedicated guide to this error — including the integration model that sidesteps forwarding entirely.

5. Attachment limits, enforced silently

Attachments obey Trello's plan limits — 10 MB per file on free accounts, 250 MB on paid plans. Emails that exceed them tend to fail without a helpful error: the card appears without its files, or nothing appears at all. If your workflow is invoices, CVs, or design files, you'll meet this one early.

Fix: know the caps, and for attachment-heavy workflows prefer an integration that pulls files through an API rather than squeezing them through email relay.

6. It's slow — minutes, not moments

Email-to-board delivery routinely takes several minutes. For weekly planning that's irrelevant; for a support queue where someone is waiting on "did you get my email?", it's an awkward gap — especially combined with #3's uncertainty about whether a reply became a comment, a new card, or nothing.

7. It's strictly one-way — you can never answer from Trello

Email-to-board is an inbound chute. There is no reading a thread inside Trello, no replying from the card, no sending at all — people asking how to send an email from Trello are pointed to power-ups. So the "workflow" becomes: see card in Trello → switch to Gmail → find the thread → reply → switch back. The tab-switching you were trying to eliminate is still your job; here's what replying from the card actually takes, and the full comparison of all four email→Trello methods.

8. Everything it touches is visible to the whole board

A card created by email shows its content — the email body — to everyone on the board, like any other card. There's no concept of a private email on a card. For a personal board that's fine; on a shared board with clients, contractors, or a wider team, forwarding real correspondence in means everyone reads everything. (This is also true of most email power-ups, by the way — here's how we think privacy on a shared board should work instead.)

When email-to-board is genuinely enough

Fairness matters: if you forward an email into Trello once or twice a week, none of the above will hurt you. Solo board, occasional capture, no replies expected, no attachments over 10 MB — use the built-in feature and spend your money elsewhere. The limitations bite when email is a channel, not an exception.

The structural fix: connect the mailbox, not a forwarding pipe

Every limitation above traces back to one design choice: email-to-board receives copies of messages relayed to a synthetic address. The alternative is to connect the mailbox itself — which is exactly what Email Inbox for Trello does. It signs into your Gmail or Google Workspace account with Google's official OAuth and works with the real inbox from inside Trello:

• Your address stays the address — customers email you@ or help@, nothing is forwarded anywhere (#1, #4 solved).
• The real sender rides along onto the card, with attachments as actual files (#2, #5).
• Cards link to the live thread — replies update the card indefinitely with a "new email" badge, and you answer right from the card with proper Gmail threading (#3, #6, #7).
• Private by default — an email attached to a card is visible only to you until you grant specific people read or read+write access (#8).
• Automation included — any Gmail search (from:billing@ has:attachment) auto-creates cards on the list you choose, 24/7.

Frequently asked questions