Wicked Smart Data
LearnInsightsAboutContact
Sign InLet's Build
LearnInsightsAboutContact
Sign InLet's Build
Wicked Smart Data

Intelligence, automation, and expert execution — plus an elite library of free knowledge. We turn complexity into competitive advantage.

Start a conversation

Platform

  • Learning Paths
  • Insights
  • RSS Feed

Company

  • About
  • Contact
  • Work With Us

Legal

  • Privacy Policy
  • Terms of Service

© 2026 Wicked Smart Data. All rights reserved.

Intelligence · Automation · Advantage

All Insights
Power Automate

Automating Task Assignments in Microsoft Planner with Power Automate: Triggering from a Form Response, Creating a Task, and Notifying the Assignee in Teams

Stop manually translating form submissions into Planner tasks. This hands-on lesson walks you through building a complete Power Automate flow that triggers on a Microsoft Forms response, creates a task with the right assignee and due date, and instantly notifies that person in Teams.

🌱 Foundation17 min readNov 20, 2026Updated Nov 20, 2026
Automating Task Assignments in Microsoft Planner with Power Automate: Triggering from a Form Response, Creating a Task, and Notifying the Assignee in Teams
On this page
  • Introduction
  • Prerequisites
  • Understanding the Architecture Before You Build
  • Setting Up Your Microsoft Form
  • Building the Flow: Step by Step
  • Step 1: Create a New Automated Cloud Flow
  • Step 2: Configure the Trigger
  • Step 3: Get the Response Details
  • Step 4: Create the Planner Task
  • Step 5: Send a Teams Notification to the Assignee
  • Step 6: Save Your Flow
  • Testing the Flow End to End
  • Hands-On Exercise
  • Common Mistakes & Troubleshooting
  • Summary & Next Steps

Automating Task Assignments in Microsoft Planner with Power Automate: Triggering from a Form Response, Creating a Task, and Notifying the Assignee in Teams

Introduction

Picture this: your team runs a weekly intake process where colleagues submit project requests through a Microsoft Form. Someone fills out the form on Monday morning, and by the time the project coordinator gets around to checking their inbox, it's Wednesday. The task still hasn't been created in Planner. The right person still doesn't know they own it. And the person who submitted the request has no idea whether anyone even looked at it.

This is a genuinely common failure point in team workflows — not because people are disorganized, but because manual handoffs between tools are inherently fragile. A form submission shouldn't require a human to read it, make a decision, open Planner, create a task, and then send a Teams message. That sequence can and should happen automatically, in seconds, without anyone touching it.

By the end of this lesson, you'll have built a working Power Automate flow that listens for new Microsoft Forms responses, creates a properly configured task in Microsoft Planner, and sends a direct notification to the assignee in Microsoft Teams — all without writing a single line of code. This is one of those automations that earns its keep the first day you deploy it.

What you'll learn:

  • How to use the Microsoft Forms trigger to start a flow when a response is submitted
  • How to retrieve form response details so you can use them inside your flow
  • How to create a task in Planner with a title, due date, and assigned user
  • How to send a personalized Teams message to notify the assignee
  • How to test and troubleshoot the full end-to-end flow

Prerequisites

Before you dive in, make sure you have:

  • A Microsoft 365 account with access to Power Automate, Microsoft Forms, Planner, and Teams
  • A Microsoft Forms form already created with at least these fields: a name or title for the request, a due date, and an email or name field to identify who the work is assigned to
  • A Planner plan already set up with at least one bucket (Planner organizes tasks into buckets within plans — think of a bucket as a column on a Kanban board)
  • Basic familiarity with the Power Automate designer; if this is your first time, Getting Started with the Power Automate Interface is a good warm-up read

Understanding the Architecture Before You Build

Before clicking anything, let's map out what you're building conceptually. Your flow has three distinct stages, and understanding the relationship between them prevents a lot of confusion later.

Stage 1 — Trigger: The flow wakes up the moment someone submits a form response. This is an event-driven trigger, meaning the flow doesn't run on a schedule; it runs in reaction to something that happened. If you want to understand how triggers work more broadly, Power Automate Triggers: When to Start a Flow covers all the major types in detail.

Stage 2 — Get the response details: The trigger alone only tells you that a form was submitted — it gives you a response ID, not the actual answers. You need a separate "Get response details" action to fetch the content of those fields. This is a quirk of the Forms connector that trips up almost everyone the first time.

Stage 3 — Branch out to Planner and Teams: Once you have the response data in hand, you create the Planner task and then send the Teams notification. These two actions happen in sequence: Planner first (so you can optionally reference the task in the Teams message), then Teams.

That's it. Three stages, four actions total. Simple enough to build in one sitting, powerful enough to transform how your team handles intake.


Setting Up Your Microsoft Form

Your form is the front door to this entire automation, so the fields need to be intentional. For this lesson, we'll use a realistic scenario: a data team that accepts ad-hoc analysis requests from other departments.

Design your form with these fields:

  1. Request Title (Text, required) — a short description of the work, like "Q3 churn analysis for Sales"
  2. Assigned To (Text or Choice, required) — the email address of the person who should own this task; using email addresses makes the Planner assignment step much cleaner than display names
  3. Due Date (Date, required) — when the task needs to be completed
  4. Additional Details (Text, optional) — context, notes, links to relevant data

Tip

For the "Assigned To" field, ask submitters to enter the person's work email address (e.g., jsmith@contoso.com) rather than their display name. Email addresses map directly to user accounts in Planner and Teams, which eliminates ambiguity when multiple people share similar names.

Go to Microsoft Forms, open your form, and confirm all four fields are there before moving on. Test-submit one response with realistic data — you'll need that test data when you're configuring the flow.


Building the Flow: Step by Step

Step 1: Create a New Automated Cloud Flow

Go to Power Automate and sign in. In the left navigation panel, click My flows, then click + New flow in the top bar, and choose Automated cloud flow.

A dialog will appear asking you to name your flow and choose a trigger. Name it something descriptive like Intake Form → Planner Task + Teams Notification. In the search box under "Choose your flow's trigger," type Forms and select When a new response is submitted from the Microsoft Forms connector.

Click Create.

Note

If you're curious why we're building an automated flow rather than a scheduled or instant flow, Power Automate Flow Types Explained: Automated, Instant, and Scheduled Flows breaks down when each type is appropriate. For anything event-driven like a form submission, automated is always the right choice.

Step 2: Configure the Trigger

The designer opens with your trigger action already on the canvas. Click on the trigger card to expand it. You'll see a dropdown labeled Form Id — click it and select the name of the form you just set up. If your form doesn't appear immediately, click the refresh icon beside the dropdown.

That's genuinely all you need for the trigger. Power Automate will now watch that specific form and fire the flow every time a new response comes in.

Step 3: Get the Response Details

Click the + New step button below the trigger. Search for Microsoft Forms in the connector search box, then select the action Get response details.

This action needs two pieces of information:

  • Form Id: Select the same form you chose in the trigger.
  • Response Id: Click inside this field, and the dynamic content panel will slide open on the right. Under "When a new response is submitted," click List of response notifications Response Id. This is the unique identifier that connects the trigger's notification to the actual response content.

Warning

Do not try to skip the "Get response details" step and use dynamic content from the trigger directly. The trigger only surfaces the Response Id — it does not contain the field values from the form. Without this action, you have no access to what the person actually typed.

Step 4: Create the Planner Task

Click + New step again. Search for Planner and choose the action Create a task.

You'll see a set of fields to configure. Work through them carefully:

Group Id: This is the Microsoft 365 group associated with your Planner plan. Click the dropdown and your groups will appear. Select the group that owns the plan you're using.

Plan Id: After selecting a group, this dropdown populates with the plans inside that group. Choose your plan.

Title: Click inside this field and open the dynamic content panel. You'll see a section called "Get response details" — find and select Request Title (or whatever you named that field on your form). The task title will now be pulled directly from the form submission.

Bucket Id: Select the appropriate bucket for new intake tasks. If you have a bucket called "New Requests" or "Incoming," choose that one.

Due Date Time: Click the field and select Due Date from the "Get response details" section of the dynamic content panel.

Tip

Planner's Due Date Time field expects a date in ISO 8601 format (e.g., 2024-09-15T00:00:00Z). Microsoft Forms date fields return dates in a compatible format, so direct mapping usually works. If you run into formatting issues, use the formatDateTime() expression function. The lesson on Mastering Dynamic Expressions and the Power Automate Formula Language covers this in depth.

Assigned User Ids: This is where the magic — and the occasional confusion — lives. Click the field. You might expect to find "Assigned To" from your form in the dynamic content, and you can select it. However, Planner's API actually needs an Azure AD user object ID (a GUID like a1b2c3d4-...), not an email address.

Here's how to handle that gracefully: before this step, add a new intermediate step. Click the + between "Get response details" and "Create a task," search for Office 365 Users, and choose the action Get user profile (V2). In the User (UPN) field, select Assigned To from the dynamic content — this feeds the email address into the Office 365 Users connector, which returns the full user profile including the object ID.

Then, back in Create a task under Assigned User Ids, select Id from the "Get user profile" section of the dynamic content. This is the object ID Planner needs.

Key insight

This two-step lookup pattern — email address in, user profile out, then object ID into the downstream action — is one of the most reusable patterns in Microsoft 365 automation. You'll use it constantly when working with Planner, SharePoint permissions, and Teams. The article on chaining Microsoft 365 connectors in a single flow goes deeper on this exact pattern.

Optionally, scroll down in the "Create a task" action and expand Show advanced options. Here you can set:

  • Notes: Map the Additional Details field from your form here, so context from the submission travels into the task description.
  • Priority: Set a default priority (0 = Urgent, 1 = Important, 5 = Medium, 9 = Low) if you want newly created tasks to appear with a visual priority flag in Planner.

Step 5: Send a Teams Notification to the Assignee

Click + New step. Search for Microsoft Teams and select the action Send a message in a chat or channel. Choose Chat with Flow bot as the post type, and select User under Post in — this sends a direct message rather than posting to a channel.

Recipient: Select the Assigned To dynamic content from your form response (the email address field). Teams will resolve this to the correct user.

Message: This is where you write the notification the assignee will see. You can mix static text with dynamic content. Here's a solid template to start with:

Hi [Display Name],

You've been assigned a new task in Planner:

📋 Task: [Request Title]
📅 Due: [Due Date]

You can view your task in Planner by opening the [Your Plan Name] plan.

Additional details: [Additional Details]

Replace the bracketed placeholders with the corresponding dynamic content tokens from your flow. For Display Name, use the Display Name output from your "Get user profile" step — this gives you a proper greeting like "Hi Jordan" rather than "Hi jsmith@contoso.com".

Tip

Teams messages in Power Automate support basic HTML. You can use <b>bold text</b>, <br> for line breaks, and even bullet lists. This makes notifications much more readable than raw plain text. For a comprehensive look at what's possible with Teams automation, see Using Power Automate with Microsoft Teams: Automate Notifications, Approvals, and Channel Messages.

Step 6: Save Your Flow

Click Save in the top right corner of the designer. Power Automate will validate your flow and display any errors. If there are connection issues, you'll be prompted to sign in to the relevant connectors (Forms, Planner, Office 365 Users, Teams) using your Microsoft 365 account.


Testing the Flow End to End

A flow you haven't tested is a liability, not an asset. Here's how to run a proper test.

First, open your Microsoft Form in a separate browser tab and submit a test response. Use a real email address in the "Assigned To" field — ideally your own, so you can verify the Teams notification. Use a future date for the due date and a clear title like "TEST - Q3 Retention Analysis."

Back in Power Automate, navigate to your flow's detail page (click the flow name in My Flows). Within a minute or two, you should see a new run appear under 28 day run history. Click on that run to open the run detail view.

Each action in the flow will show a green checkmark (success) or a red X (failure). Click any action to expand it and see exactly what inputs it received and what outputs it produced. This is invaluable for debugging.

Verify three things:

  1. The "Get response details" action shows the correct field values from your test submission
  2. The "Create a task" action succeeded and shows the task ID in its outputs
  3. The "Send a message" action succeeded — then check Teams on your phone or desktop to confirm the message arrived

If the Planner task doesn't appear immediately in your Planner board, give it 30–60 seconds and refresh. Planner's display occasionally lags behind the API.

Warning

If your "Get user profile" step fails with a "Resource not found" error, the email address entered in the form doesn't match a user in your Azure AD directory. Add a brief note to your form instructing submitters to use their work email address exactly as it appears in Teams or Outlook. For more systematic debugging techniques, Using Power Automate Run History and Flow Checker to Debug and Fix Failing Flows is the definitive resource.


Hands-On Exercise

Now that you've seen the full flow, build your own version with a slight twist that reinforces the concepts.

Scenario: Your marketing team wants to automate content request intake. Someone submits a form requesting a blog post or social media asset. The flow should create a Planner task in the "Content Requests" plan, assign it to the content creator specified on the form, and notify them in Teams.

Your exercise:

  1. Create a new Microsoft Form called "Content Request Form" with these fields:

    • Content Type (Choice: Blog Post, Social Media, Email, Video)
    • Request Title (Text)
    • Assigned Creator (Text — their work email)
    • Publish By Date (Date)
    • Brief (Long text)
  2. Build the Power Automate flow following the same pattern from this lesson.

  3. Add one enhancement: use a Condition action after "Get response details" to check if the Content Type is "Video." If it is, also post a message to a Teams channel called "Video Production" to give that team a heads-up. If it isn't, skip that step and proceed normally. The article on Working with Conditions, Loops, and Variables in Power Automate will help you structure that branch correctly.

  4. Submit three test responses with different content types and verify that video requests trigger the channel post while other types do not.

This exercise reinforces the core pattern and introduces conditional branching — a combination you'll use constantly in real-world flows.


Common Mistakes & Troubleshooting

Problem: The flow runs but the task has no assignee. This almost always means the user lookup step failed silently, or the object ID didn't map correctly into the Assigned User Ids field. Open the run history, expand the "Get user profile" action, and verify it returned a valid Id. Then expand "Create a task" and check that the Assigned User Ids input shows the GUID, not the email or display name.

Problem: The due date on the Planner task is off by one day. This is a time zone issue. Power Automate stores dates in UTC, and if the form submission happens in the evening in a negative-UTC timezone, the UTC date might have rolled over to the next day. Use convertTimeZone() or formatDateTime() to normalize the date before passing it to Planner.

Problem: The Teams message is delivered but shows the raw email address instead of the person's name in the greeting. Make sure you're using the Display Name output from "Get user profile," not the Assigned To field directly from the form response. The form field contains whatever the submitter typed; the user profile output contains the canonical display name from Azure AD.

Problem: The flow fails on the trigger with "Could not retrieve values" for the Form Id. This can happen if your account's connection to Microsoft Forms was recently re-authenticated or if the form was created under a different account. Click on the trigger in the designer and re-select the form from the dropdown. If the form doesn't appear, delete and recreate the Forms connection in Power Automate's connections page.

Problem: The "Create a task" action fails with a permissions error. You need to be a member of the Microsoft 365 group that owns the Planner plan. If you built the flow under your account but the plan belongs to a group you're not a member of, the connection won't have permission to create tasks. Ask a group owner to add you, or use a service account that is a member.


Summary & Next Steps

You've built something genuinely useful: a form-to-Planner-to-Teams automation that eliminates manual handoffs in your intake process. Let's recap what you assembled:

  • A Forms trigger that fires the moment someone submits a response
  • A Get response details action to retrieve the actual field values
  • An Office 365 Users lookup to convert an email address to a user object ID
  • A Create a task action in Planner with title, due date, assignee, and notes all populated dynamically
  • A Teams direct message that greets the assignee by name and summarizes their new task

This is a complete, production-ready automation for small to medium teams. It's also a foundation you can extend significantly.

Where to go next:

  • If your intake process involves review or sign-off before the task is created, look at Building Approval Workflows with Power Automate to add an approval gate between the form submission and the Planner task creation.
  • To see how the same Planner tasks can be updated automatically as work progresses — status changes, completion, comments — explore Automating Planner Task Creation, Assignment, and Status Updates with Power Automate for the full end-to-end project workflow picture.
  • If you want to store a record of every request in SharePoint alongside the Planner task, Automating Microsoft Forms Responses: Collecting, Routing, and Storing Survey Data with Power Automate covers exactly that pattern.

The pattern you learned here — trigger, enrich, act, notify — is the backbone of dozens of real-world automation scenarios. You'll recognize it everywhere once you've built it once.

Work With Us

From insight to implementation

Reading is the start. When you're ready to build the data, automation, or AI systems behind it, our team turns strategy into shipped results.

Let's Build

Flow Automation Basics

Previous

Automating Recurring Approval Workflows with Expiry Dates in Power Automate: Triggering on SharePoint Date Columns, Notifying Owners, and Routing Renewals Through Multi-Step Sign-Off

Related Insights

Power AutomateExpert

Implementing Power Automate Premium Connector Metering and Per-Flow License Assignment at Scale: Mapping High-Volume Flows to Dedicated Capacity, Tracking API Request Consumption, and Rightsizing Entitlements Across Business Units

28 min
Power AutomateExpert

Implementing Desktop Flow Input Sanitization and Output Validation in Power Automate Desktop: Enforcing Data Type Contracts, Boundary Checks, and Structured Error Responses Across Attended and Unattended Run Modes

27 min
Power AutomateExpert

Automating Recurring Approval Workflows with Expiry Dates in Power Automate: Triggering on SharePoint Date Columns, Notifying Owners, and Routing Renewals Through Multi-Step Sign-Off

28 min

On this page

  • Introduction
  • Prerequisites
  • Understanding the Architecture Before You Build
  • Setting Up Your Microsoft Form
  • Building the Flow: Step by Step
  • Step 1: Create a New Automated Cloud Flow
  • Step 2: Configure the Trigger
  • Step 3: Get the Response Details
  • Step 4: Create the Planner Task
  • Step 5: Send a Teams Notification to the Assignee
  • Step 6: Save Your Flow
  • Testing the Flow End to End
  • Hands-On Exercise
  • Common Mistakes & Troubleshooting
  • Summary & Next Steps