Trello Card from Email Intake

Overview

This flow turns a shared email intake mailbox into a structured Trello queue. Each new email becomes a Trello card on a configured list - the subject becomes the card title, the sender and body preview become the description, and any attachments are archived to a SharePoint document library and linked back on the card via a comment.

Why it matters: requests that arrive by email to a shared inbox are easy to lose. This captures every one as a trackable, assignable Trello card, with supporting files preserved in a governed SharePoint location rather than buried in the mailbox.

Ships Off (demo).

Use Case

A team that runs its work on a Trello board but receives requests by email at a shared address wants each request captured automatically as a board card, with attachments retained in SharePoint. Typical adopters: operations queues, facilities/helpdesk intake, vendor onboarding, creative/work request boards.

Flow Architecture

Environment Variables

Connectors & Connections

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Sender as a label

Add a flowlibs_TrelloIntakeLabelId env var and pass it through idLabelsArray on CreateCard_V2, or build a sender-domain to label-id map.

Routing by sender/subject

Branch before Create Trello Card on the from address or subject keywords to choose a different list per request type.

Due dates

Parse a due date from the subject/body and set the card's due via a follow-up UpdateCard_V2.

Dedup / threading

Look up an existing card by a subject reference (e.g. [REQ-123]) and comment onto it instead of creating a duplicate.

Auto-assign

Add a member with AddMemberToCard based on the intake type.

Attachment filtering

Skip inline signature images by filtering the loop on IsInline = false or by content type/size.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

if(empty(triggerOutputs()?['body/subject']),'(No subject)',triggerOutputs()?['body/subject'])

concat('From: ', coalesce(triggerOutputs()?['body/from'],'unknown'), ' | Received: ', triggerOutputs()?['body/receivedDateTime'], ' | ', triggerOutputs()?['body/bodyPreview'])

coalesce(triggerOutputs()?['body/Attachments'],json('[]'))

base64ToBinary(items('For_Each_Attachment')?['ContentBytes'])

concat(variables('varSiteUrl'), outputs('Save_Attachment_To_SharePoint')?['body/Path'])