workflows

Turn Emails into Trello Cards: A Complete Workflow Guide

Leandro Zubrezki··7 min read
Turn Emails into Trello Cards: A Complete Workflow Guide

Emails often contain work that needs tracking. Client requests, bug reports, content pitches, task assignments -- they all arrive as emails but need to become actionable cards on your Trello board. By saving them to Trello, you give every item a place in your workflow where your team can see it, prioritize it, and move it through to completion.

Why Trello for Email-Based Work?

  • Visual workflow -- Drag cards between lists like Inbox, In Progress, and Done. See the state of every item at a glance.
  • Labels for categorization -- Color-code cards by type (Bug, Feature Request, Client), priority (Urgent, Normal, Low), or source (Email, Slack, Meeting).
  • Member assignment -- Assign team members to cards so everyone knows who's responsible.
  • Checklists -- Break complex requests into subtasks right on the card.
  • Due dates -- Set deadlines and see them on the calendar view.
  • Attachments -- Email attachments land directly on the card -- screenshots, PDFs, documents are all accessible without leaving Trello.
  • Butler automation -- Trello's built-in automation can trigger actions when new cards appear, like adding due dates, moving cards to specific lists, or sending notifications.

Save emails in seconds

Forward any email to your Quicktion address and it lands in Notion or Google Sheets automatically.

Setting Up Your Board

Create a Trello board for your email workflow. A simple starting structure:

ListPurpose
InboxWhere new email-based cards land
TriageCards being reviewed and prioritized
In ProgressActive work
WaitingBlocked or waiting on external input
DoneCompleted items

Add labels that match your workflow:

  • Red: Urgent
  • Orange: Bug
  • Yellow: Feature Request
  • Green: Client
  • Blue: Internal
  • Purple: Content

Connecting Your Email (via Quicktion)

Method 1: Email Forwarding

Best for emails that should always become cards. Set up a Gmail filter to auto-forward them to your Quicktion address. Learn how to set up forwarding to Trello.

Example: all emails from your support tool should become cards.

  1. Create a Gmail filter: from:notifications@helpdesk.com
  2. Forward to your Quicktion destination address
  3. Every matching email automatically appears as a card in your Inbox list

You can also combine multiple senders in one filter:

from:(support@client-a.com OR support@client-b.com OR bugs@internal.com)

Method 2: Gmail Add-on

Best for selectively choosing which emails become cards. Open an email in Gmail, click the Quicktion add-on, and save it to your Trello board. This gives you control over what gets saved -- not every email is worth a card. See our Gmail-to-Trello integration guide for setup details.

Workflow Examples

Bug Report Pipeline

Setup:

  • Board: "Bug Tracking"
  • Lists: Reported > Confirmed > In Progress > Fixed > Closed
  • Default label: "Bug" (orange)
  • Default member: QA lead

Flow:

  1. Customer support receives a bug report email
  2. Auto-forwarding sends it to the Quicktion address for the Bugs board
  3. A card appears in the "Reported" list with the bug description, screenshots attached, and the "Bug" label applied
  4. QA lead sees the new card and drags it to "Confirmed" after verifying
  5. Developer picks it up and moves to "In Progress"
  6. After the fix ships, it moves to "Fixed" and eventually "Closed"

The email body preserves all the details -- steps to reproduce, error messages, screenshots. No information is lost in the transition from email to card.

Client Request Tracking

Setup:

  • Board: "Client Work"
  • Lists: Inbox > Accepted > In Progress > Review > Delivered
  • Separate destinations per major client (different labels per destination)
  • Default member: Account manager

Flow:

  1. Client sends an email requesting a change or new deliverable
  2. Email is forwarded to the appropriate Quicktion address (either manually or via auto-forwarding)
  3. A card appears with the client's label and the account manager assigned
  4. Account manager reviews the request, adds a due date and checklist
  5. Card moves through the workflow as work progresses

Content Pipeline

Setup:

  • Board: "Content Calendar"
  • Lists: Pitched > Writing > Editing > Published
  • Default label: "Content" (purple)
  • Card position: Top of list (newest ideas first)

Flow:

  1. Editor receives a pitch via email -- from a writer, a PR agency, or an internal team member
  2. Email is forwarded to the content board's Quicktion address
  3. A card appears in "Pitched" with the full pitch in the description and any reference materials attached
  4. Editor reviews and moves approved pitches to "Writing"
  5. Cards progress through "Editing" and "Published" as work completes

Team Task Management

Setup:

  • Board: "Team Tasks"
  • Lists: To Do > Doing > Done
  • Multiple destinations for different task sources (each with a different label)
  • Members assigned based on source

Flow:

  1. Manager sends a task assignment email to the team
  2. Auto-forwarding catches it and creates a card in the "To Do" list
  3. Team member sees the card, reads the full email body in the description, and starts work
  4. Card moves to "Doing" and eventually "Done"

Configuring Your Destinations

Labels

Pre-assign labels to categorize cards by source. If you have a destination for client emails, set the "Client" label. If you have one for bugs, set the "Bug" label. This saves manual tagging and makes your board filterable from day one.

Members

Pre-assign members so the right person sees new cards immediately. For a support destination, assign the support lead. For a client destination, assign the account manager. Team members can reassign later if needed.

Card Position

Choose whether new cards appear at the top or bottom of the list:

  • Top -- newest cards are most visible, good for urgent workflows
  • Bottom -- preserves chronological order, good for queues

Enable the metadata footer to include sender name, email address, date, and a link to the original email below the card description. This is useful when you need to reply to the original sender or reference the email thread.

Tips

  1. Keep the card name clear. Email subjects are often vague. If you use the Gmail add-on, you can edit the subject before saving. For auto-forwarded emails, you can rename the card in Trello afterward.
  2. Use Butler for automation. Set up Trello Butler rules to automatically add due dates when cards enter "In Progress," move overdue cards to the top of the list, or notify team members when new cards appear.
  3. Don't auto-forward everything. Be selective with your forwarding rules. Start narrow -- one sender, one subject pattern -- and expand as you learn which emails are worth tracking.
  4. Create views with filters. Use Trello's filter feature to show only cards with a specific label, assigned to a specific member, or due within a certain date range.
  5. Archive done cards. Don't leave completed cards on your board forever. Archive them to keep the board clean. Archived cards are searchable if you need to reference them later.
  6. Combine with forwarding. Use auto-forwarding for predictable email types and the Gmail add-on for one-off saves. The same destinations work with both methods.

Getting Started

Sign up for Quicktion and create a destination linked to your Trello board. Use the Gmail add-on for selective card creation or forwarding for automatic capture.

Already using Notion, Airtable, or Linear? See how this workflow compares: Notion tasks | Airtable tasks | Linear issues.

Ready to put your emails where they belong?

Quicktion lets you forward emails or use the Gmail add-on to save messages to Notion or Google Sheets. No code required.

LZ

Leandro Zubrezki

Founder of Quicktion

Building tools to bridge the gap between email and Notion. Leandro created Quicktion to help teams save time by automating their email-to-Notion workflows.

Related Posts