Auto-Create Trello Cards From a Gmail Label or Search — No Zapier, No Per-Task Fees

The goal, precisely

Not "forward emails to Trello" — that's manual, and the native route has a list of problems of its own. The goal is a standing rule: whenever an email matching X arrives, a card appears on list Y, with the attachments and the sender, while I do something else.

Gmail can't do this alone (no Trello actions), and Trello can't do it alone (no inbox access). Two kinds of middlemen can: an automation platform, or a power-up connected to the mailbox. They differ more than the listicles suggest.

Route 1: Zapier (or Make) — the DIY pipeline

The canonical zap is two steps: Gmail trigger "New Email Matching Search" → Trello action "Create Card". Setup, honestly described:

1. Connect both accounts in Zapier, create a zap, choose the Gmail trigger and enter your search (e.g. label:leads is:unread).
2. Map fields: subject → card name, body → description, pick board and list. Test with a sample email.
3. If you want attachments, add steps — and this is where it gets sticky (see below).
4. Turn it on. Zapier polls the search — every 15 minutes on the free plan — and creates cards for new matches.

It genuinely works, and if the email is one step in a chain that also posts to Slack and writes a spreadsheet row, Zapier is the right tool. But run it as your primary email→Trello pipeline and the seams show:

• Attachments arrive as URLs, not files. By default the card gets links into temporary storage; users have hit expired files and "file not found" errors trying to make real attachments land. More steps, more tasks, more fragility.
• You pay per email, forever. Free = 100 tasks/month — about three emails a day, fewer with multi-step zaps. Then ~$19.99/month (annual) and up. A busy inbox turns each incoming message into a metered event.
• Polling lag. 15-minute cycles on free tiers; "the customer emailed 12 minutes ago" is invisible until the next poll.
• One-way, one-time. The card never hears about replies, and answering still happens in Gmail. Each nicety (auto-move on reply, appending follow-ups) is another zap to build and babysit.

Make (ex-Integromat) softens the pricing — its free tier's operation count is roomier — but the architecture and its consequences are the same.

Route 2: The automation living inside Trello

The alternative skips the middleman platform: Email Inbox connects your Gmail or Google Workspace account to the board via Google's OAuth sign-in, and automations are a built-in primitive — a Gmail search plus a destination list:

1. Add Email Inbox to the board and connect the account (or several — sales@ and your own inbox can feed different lists).
2. Create an automation: type the same query you'd type into Gmail — from:invoices@supplier.com has:attachment, label:leads, to:jobs@ filename:pdf — and pick the list. Optionally preset assignees and titles with routing.
3. Done. It runs 24/7. New matching mail becomes cards with the real sender and the actual files attached — not links — and each card carries the live thread: reply from it, get badged when they answer (how that works).

Because the power-up reads the mailbox in place, there's no per-message metering — €4 per member per month flat, whether the automation catches five emails or five hundred — and no forwarding rules for corporate mail policy to veto.

Side by side

That last row is the honest decision rule: if your workflow fans out across many apps, Zapier earns its fee. If the workflow is "Gmail → Trello, properly," a metered general-purpose pipeline is the expensive way to do a specific thing.

Five automation recipes worth stealing

• Support queue: to:support@yourco.com is:unread → list New requests — the intake half of a Trello help desk.
• Invoice processing: has:attachment (subject:invoice OR filename:pdf from:billing) → To approve, with the PDFs already on the card.
• Lead capture: label:leads (let a Gmail filter apply the label from your webform) → New leads, assigned to whoever's on point.
• Recruiting: to:jobs@yourco.com has:attachment → Applicants — CVs attached, and the thread private to the hiring team.
• VIP watch: from:(bigclient.com) is:unread → Priority, so nothing from the account that pays the bills waits in a crowd.

Frequently asked questions