Form Submission to Assigned Outlook Task

Overview

FlowLibs - Form Submission to Outlook Task turns every Microsoft Forms response into a tracked task. When a form is submitted, the flow pulls the response details, builds a task title and notes block from the submission, creates a Microsoft To-Do task on the connection owner's account, then emails the assignee an HTML notification summarizing the new work item.

This is a Beginner-level demo that ships in the Off state. Turning it on requires only authorizing three connections and updating five environment variables — the architecture is fully wired with real connector actions (no inline fixtures).

Use Case

Many small teams collect intake — change requests, IT tickets, training nominations, content reviews — through Microsoft Forms because it's already in their tenant and friction-free for submitters. The downside is responses just sit in a spreadsheet. This flow closes the loop: every submission becomes a real task in someone's Microsoft To-Do list and the assignee gets an email confirming it. No spreadsheet refresh, no manual triage, no missed requests.

The flow is ideal for teams that:

• Operations intake form to task in the ops queue with a 7-day SLA
• Training request form to task assigned to the L&D lead
• IT support form to task in the helpdesk owner's list with the request details inline
• Content review form to task to the editor with the submitter and submission timestamp captured

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.

Create the Microsoft Form and set the form ID

Build a Form in Microsoft Forms with the questions you want to capture (e.g. Title, Description, Assigned To, Due Date). Copy the form ID from the URL (forms.office.com/Pages/...?formid={ID}) and paste it into the flowlibs_FormID env var.

Set the To-Do list ID

Open Microsoft To-Do and confirm the target list exists. The first time the connection is authorized in Power Automate, the picker will surface list IDs — paste the desired one into flowlibs_ToDoListId.

Set the default assignee UPN

Update flowlibs_DefaultAssigneeUpn with the UPN you want tasks routed to when the form does not specify an assignee.

Wire form fields into the variables (recommended for production)

Open Init varAssigneeUpn and replace the value with the form's 'Assigned To' field token (e.g. outputs('Get_Response_Details')?['body/{question-id}']). Repeat for varTaskTitle (Title field), varTaskNotes (description/justification fields), and varDueDate (form-supplied due date, falling back to addDays(utcNow(), 7) via coalesce()).

Switch to Planner for true assignment

Microsoft To-Do tasks are personal — CreateToDoV3 writes to the connection owner's account. To assign tasks to other users, swap the Create To Do Task action for Planner 'Create a task (V3)' and pass groupId, planId, and assignedUserIds. The notification email step already handles assignee awareness in the meantime.

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']

@{parameters('flowlibs_TaskTitlePrefix')} Task from form submission

Submitted by: @{outputs('Get_Response_Details')?['body/responder']}. Submission time: @{outputs('Get_Response_Details')?['body/submitDate']}. Response ID: @{outputs('Get_Response_Details')?['body/responseId']}.

@{addDays(utcNow(), 7)}

@{concat(parameters('flowlibs_TaskTitlePrefix'), ' New task assigned to you')}