How to Reply to Emails Directly From a Trello Card (Gmail)

First, the blunt answer: Trello can't send email

There is no native compose button anywhere in Trello. People keep asking — "How to send an email from the Trello?" is a perennial community thread — and the answer is always the same: not without a power-up. Email-to-board is strictly an inbound chute (with its own list of catches).

That leaves three things people try. Two of them are half-solutions worth understanding, because knowing why they fall short explains what to look for in the real one.

Half-solution 1: The card email address (it's not what you think)

Every card has a secret email address (visible in the card's share menu). Sending mail to it adds a comment on the card. Useful for pushing information in — but it's a one-way mailbox, not an outbox. Emailing the card address does not send anything to your customer, and the customer never sees it. It also comes with quirks: the address is hard to retrieve programmatically, and users report it's not exposed on mobile or via the API.

Half-solution 2: Butler's "send email" action

Trello's built-in automation (Butler) does have an email action: when a trigger fires — card moved to Done, due date approaching — it can send a templated message to an address you specify. Genuinely handy for notifications ("your request is resolved"). But it's not replying:

• It starts a new email — the message doesn't thread into the conversation the customer already has open, so their mail client shows a disconnected one-off.
• It doesn't come from your mailbox — no copy in your Gmail Sent folder, no thread history, and the From line isn't your normal address.
• It's fire-and-forget — Butler can't read the answer, so the conversation immediately falls back off the board.

Butler is a notifier, not a correspondent. For real back-and-forth with a human on the other end, you need the third option.

The real solution: a card linked to the live Gmail thread

For a reply to behave like a reply — threaded under the original message, sent from your address, visible in your Sent folder — it has to be sent by your mailbox. That's exactly what Email Inbox does: it connects your Gmail or Google Workspace account via Google's OAuth sign-in and links cards to actual threads, two-way.

What replying from a card looks like

1. Attach the thread to a card. Turn an email into a card in one click, or let an automation create cards from a Gmail search. Either way, the card carries the live conversation — not a pasted copy.
2. Open the card, read everything. The full thread is on the card back: every message, attachments, the works. No tab switch to check "what did they say again?"
3. Write the reply right there. Hit reply on the card, type, send. Gmail sends it — proper In-Reply-To threading, your real From address, a copy in your Sent folder. To the recipient it's indistinguishable from a reply written in Gmail, because technically it is one.
4. Let the card flag the answer. When the other side responds, the card shows a "new email" badge and updates itself. Move the card across lists while the conversation lives inside it.

The teamwork part: who else can reply?

By default, nobody — an email attached to a card is visible only to you, and other board members can't even tell it's there. When you want a teammate to take over, grant them access on that card: read to follow along, or read + write to reply themselves. That per-card handover is how a shared inbox on a board works without exposing every conversation to everyone.

The three approaches, side by side

One honest note for non-Gmail teams: if your mailbox is Outlook or another provider, the OAuth-Gmail approach won't apply — a forwarding-based tool like SendBoard covers sending from cards there, with the trade-offs we covered in the power-up comparison.

Frequently asked questions