Trello Card from Microsoft Form

Overview

This flow turns each Microsoft Forms submission into a Trello card on a configured board and list, maps the submission type to a Trello label, sets a due date, and emails the submitter a confirmation containing a direct link to the new card. It is a clean, portable intake form to Trello pipeline.

Why it matters: structured intake beats free-text email. Every request, idea, or bug lands directly on the board ready to triage, and the submitter gets an immediate acknowledgement with a link they can follow.

Ships Off (Stopped) - turn it on by authorizing the three connections and setting the env var values.

Use Case

A team collects requests / ideas / bugs through a Microsoft Form and wants each submission to become a Trello card pre-filled from the answers, carry a label derived from the submission type and a due date, and trigger a confirmation email back to the submitter with the card link.

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.

Bind the real questions

After import, open Get Form Response Details and rebind the r1-r4 placeholders to your actual questions (summary -> title, details -> description, type -> label, date -> due). Only the four Initialize Variable expressions need editing.

Routing

Point different request types at different lists or boards by branching on the type answer and switching the list/board before Create Trello Card.

Labels

Fill flowlibs_TrelloLabelMap with your real label ids, or add a label-lookup step to resolve ids at runtime.

Attachments

Extend with Trello AddAttachmentToCard (or a file-source op) to push uploaded form files onto the card.

Priority / members

Set newCard/idMembersArray to auto-assign, or derive a priority label from the answers.

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.

triggerOutputs()?['body/resourceData/responseId']

coalesce(outputs('Get_Form_Response_Details')?['body/r1'], 'New Intake Request')

coalesce(json(variables('varLabelMap'))?[string(outputs('Get_Form_Response_Details')?['body/r3'])], '')

coalesce(outputs('Get_Form_Response_Details')?['body/r4'], addDays(utcNow(), 7))

if(empty(variables('varSelectedLabelId')), json('[]'), json(concat('["', variables('varSelectedLabelId'), '"]')))