How to Get Emails Into Trello Automatically: 4 Methods Compared

If your work arrives by email but lives in Trello, you've probably done the ritual: open the email, copy the subject, switch tabs, create a card, paste, go back for the attachment, download it, upload it, and repeat after lunch. It works — until the day you forget one, and a client asks why their request vanished.

There are four realistic ways to make emails become Trello cards on their own. They are not interchangeable. The right one depends on whether you need attachments, whether the original sender matters, whether the conversation continues after the card is created, and who controls your mail server.

The short version: all 4 methods compared

Now the detail — including the parts the marketing pages skip.

Method 1: Trello's built-in email-to-board address

Every Trello board gives each member a unique, board-specific email address. Anything sent or forwarded to that address becomes a card: the subject line turns into the card title, the body into the description, and attachments come along within Trello's limits (10 MB per attachment on free accounts, 250 MB on paid plans). You'll find the address in your board's menu under email-to-board settings, and Atlassian documents the basics in Creating cards by email.

Where it works

Occasional, one-off capture. If a client sends a brief and you want it on the board before you forget, forwarding it to the board address is genuinely fast, free, and needs no setup beyond saving the address as a contact.

Where it breaks

• Nothing is automatic. The board only reacts to mail that reaches its address — so either you forward each email by hand, or you set up an auto-forwarding rule in your mail account. That's where most teams hit a wall: company mail servers commonly block external auto-forwarding, failing with errors like "550 5.7.520 Access denied, your organization does not allow external forwarding." We wrote up why that happens and what actually fixes it.
• The card is created as you, not the sender. The original sender's identity gets buried in the pasted body text — awkward the moment two people email you about different things.
• It's a one-way snapshot. When the customer replies to the original thread, the card doesn't know. Replies only reach the card in narrow cases, and Trello users have been reporting replies not showing up for years.

There's a longer list — the address can't be customized, delivery can lag by several minutes, oversized attachments fail quietly. We catalogued all of them in Trello email-to-board: the limitations you'll hit.

Method 2: The official Trello for Gmail add-on

Trello's add-on from the Google Workspace Marketplace adds a Trello panel inside Gmail. Open an email, click the Trello icon, pick a board and list, and it creates a card with the subject as the title and the message text in the description.

Where it works

Manual triage on the go — especially in the Gmail mobile app, where forwarding to a board address is fiddly. Zero cost, official, two-minute setup.

Where it breaks

• It's manual, every single time. There is no rule or filter support — you are the automation.
• It creates a text snapshot. No attachments, no link back to the live thread, no updates when replies arrive, and no way to add an email to an existing card.
• Community verdict. When a user asked whether the add-on could do more, the Atlassian Community's answer was blunt — the integration is "incredibly minimal": it adds a card with a deadline, and that's about it. We took it apart wall by wall in our add-on review.

Method 3: Zapier, Make, and friends

Automation platforms poll your Gmail account and run a workflow when a matching email arrives — typically the Gmail trigger "New email matching search" feeding the Trello action "Create card." This is the first method on the list that's genuinely automatic.

Where it works

When email→card is one step inside a bigger cross-app workflow (say, also posting to Slack and adding a row to a spreadsheet). If you already pay for Zapier and live in its editor, it's a capable glue layer.

Where it breaks

• Attachments arrive as links, not files. By default Zapier passes Gmail attachments to Trello as URLs; getting real files onto the card needs extra steps, and users have reported temporary-file expiry and "file not found" errors along the way.
• Polling delay and task math. Free plans poll every 15 minutes, and every email consumes tasks from your monthly quota. A busy support inbox burns through a paid tier surprisingly fast — you're paying per email, forever.
• Still one-way. The card doesn't follow the thread, and there's no replying from Trello. Each extra nicety is another zap to build and maintain. (Full walkthrough and cost math: cards from a Gmail search, with and without Zapier.)

Method 4: A power-up that connects to Gmail itself

The three methods above share one design: they push a copy of an email toward Trello and hope for the best. The fourth flips it — the power-up connects to your Gmail account through Google's official OAuth sign-in and works with the mailbox directly, from inside Trello. That's the approach we took with Email Inbox for Trello.

Because the integration sees the real mailbox rather than a forwarded copy, the annoying parts of the other methods stop being problems:

• Automation without forwarding rules. You pick any Gmail search — from:support@ is:unread, label:invoices has:attachment, anything Gmail understands — and a destination list. New matching mail becomes cards on its own, 24/7. Nothing to configure on the mail server, nothing for IT to block.
• The whole email travels. Sender, thread, and attachments land on the card as real files — no copy-paste, no link rot.
• The card stays live. It's two-way: read the full thread on the card, reply from it (with proper Gmail threading, from your real address), and get a "new email" badge the moment an answer arrives — here's how replying from a card works.
• Private by default. An email attached to a card is visible only to you until you explicitly share it — the rest of the board can't read it, or even tell it's there. On shared boards this matters more than people expect; it's the difference between a shared inbox and a shared overexposure.
• Inbox triage from the board. Archive, mark spam, and bulk-clear without switching tabs — Trello becomes a place you can actually process email, not just collect it.

Where it breaks

Honesty cuts both ways: Email Inbox is Gmail and Google Workspace only. If your team runs on Outlook or a generic IMAP mailbox, a forwarding-address power-up such as SendBoard or Hipporello is the better fit — we compare them in our rundown of email power-ups for Trello. And if you need email to fan out into five different apps at once, an automation platform still earns its keep.

How to choose (by scenario)

• You capture an email once a week → the native board address is plenty. Save it as a contact and move on.
• You triage on your phone → the Gmail add-on covers manual capture, as long as snapshots are enough.
• Email is one step in a multi-app pipeline → Zapier or Make, budgeted per task.
• Email is where your Trello work actually starts — support requests, invoices, leads, client threads — and replies matter → connect the inbox itself with a Gmail power-up and let the board run the mail.

Frequently asked questions