# Create a Planner task automatically from a Forms response

> For the full documentation index, see https://250highstreet.com/llms.txt

> Turn each Microsoft Forms response into a Planner task in the right bucket with Power Automate: field mapping, a one-response test, limits and what to avoid.

Short answer: a Power Automate flow can turn every Microsoft Forms response into a Planner task. The trigger is "When a new response is submitted". The first action is "Get response details". The second action is the Planner action "Create a task", where you set the plan, the bucket, the title, a due date and who it is assigned to. Then you test with one response.

## Why requests need a task and an owner

A request is only useful when someone owns it. A team may collect requests with a form, then read the results page and copy the answers into a task by hand. That copy step is where requests wait, get skipped or get lost.

A flow removes the copy step. Each response becomes one task. The task sits in a bucket, has a due date and has a person on it. Your team works from Planner, where tasks move across buckets as work moves forward.

If your requests keep getting lost, see "[Requests lost in a shared inbox: add an owner and a status](/guides/requests-lost-in-shared-inbox/)". This guide covers one fix: a form that creates a Planner task.

## What you are building

- One Microsoft Form with a few questions.
- One Planner plan with a bucket for each stage, such as New, In progress and Done.
- One Power Automate flow with three parts: a trigger, "Get response details" and "Create a task".

One limit to know first. Microsoft's page for the Planner connector says the connector supports basic plans only. Premium plans are not covered.

## Before you start

You need a Microsoft 365 work or school account, a Planner plan you can add tasks to, and access to Power Automate. Microsoft's page for the Forms connector says the connector only works with organizational accounts. Which license you need depends on your plan, so check with your admin.

Write the questions first. One way to start is four to six questions:

1.  What do you need? (short text, becomes the task title)
2.  More detail (long text)
3.  Who is asking? (email address, see the note on owners below)
4.  When do you need it? (date)
5.  Type of request (choice)

## Step 1. Build the plan and buckets

Create the plan in Planner and add one bucket for each stage. Give the buckets short names that are easy to pick in the flow, such as "1 New", "2 In progress" and "3 Done".

New tasks from the flow all go to one bucket. One way to start is to send every new task to "1 New". People move the task across buckets as the work moves.

## Step 2. Build the form

Open Microsoft Forms, select a new form and add one question for each item in your list. Keep the wording short. The flow will show your question text as labels later, so "What do you need?" is easier to find than a long sentence.

Settle the questions before you share the form. Changing questions later can break the flow's field mapping.

## Step 3. Add the trigger and response details

Create an automated cloud flow and name it something you will recognize, such as "Request form to Planner". Add the Forms trigger "When a new response is submitted" and then the "Get response details" action, both set to your form. The trigger and action settings, including group forms and the Response Id, are covered step by step in "[Save Microsoft Forms answers to a SharePoint list](/guides/microsoft-forms-to-sharepoint-list/)". Come back here when your questions show up as dynamic content.

## Step 4. Add the Planner "Create a task" action

1.  Add a step after "Get response details". Search for "Create a task" under Planner.
2.  Pick the Group Id and then the Plan Id from the drop-down lists.
3.  Fill in the fields in the table below. Exact names may differ on your screen.

Microsoft's connector page also lists "Create a task (Preview)" beside "Create a task". The Preview version adds a Priority field, a number from 0 to 10, where 0 is the highest priority. This guide uses "Create a task". Microsoft's connector page adds a note about Group Id. It is used to fill in the Plan Id drop-down list. Once the list is filled, any value can sit in the Group Id field and the action still works, even if the connector shows a warning.

## Field mapping table

This table follows the "Create a task" fields on Microsoft's Planner connector page.

Field \| What goes in it \| Notes

Plan Id \| Your plan, picked from the list \| Required

Title \| The answer to "What do you need?" \| Required. Maximum 255 characters

Bucket Id \| The bucket, such as "1 New", picked from the list \| Optional. Set it so every task lands in the bucket you want

Start Date Time \| Leave empty, or the date the work can start \| Optional

Due Date Time \| The answer to "When do you need it?" \| Optional. The connector page shows the format '2018-04-13T00:42:19.284Z'

Assigned User Ids \| The email address of the owner \| Optional. Separate several people with semi-colons

Two details matter.

Due date. The connector expects a date and time in the format shown above. A Forms date answer is not always in that format. Test it, and if the task has no due date or the step fails, convert the date in the flow before the Planner step.

Assigned User Ids. The field takes user ids or email addresses. A plain name will not work. Collect an email address in the form and map it here. If you want a fixed owner, type that person's email address into the field instead. If you want different owners for different request types, one way to start is to add a Condition on the "Type of request" answer and give each branch its own "Create a task" action with its own bucket and owner.

The description is not part of "Create a task". Microsoft lists a separate action, "Update task details", which has a Description field and takes the Task Id from the first action. Use it to carry the "More detail" answer into the task.

## Checklist items and links

"Create a task" has no checklist or attachment fields. Microsoft's "Update task details" action does. It takes a Task Id, a Description, a Resource link with an Alias and a Type of the reference, and checklist items with an Id, a Title and an Is Checked value. The Resource link must be "A valid URL based on the HTTP/HTTPS protocols." So add "Update task details" after "Create a task", map the Task Id from the first action, and fill in the checklist or link fields. A file uploaded to a Forms question is a different matter: the connector page does not describe attaching a file itself, only a link to it.

## Assign the person named in the form

Collect an email address in the form and map that answer to Assigned User Ids. Microsoft's Forms connector page says the outputs of "Get response details" are dynamic, so the fields you see depend on your form. Use the answer to your email question, not a name.

## Step 5. Test it with one response

1.  Save the flow.
2.  Open your form and submit one real-looking answer. Use your own email address in the owner question.
3.  Open Planner and check the bucket. The new task should show the title, the due date and the person.
4.  If it is not there, go to Power Automate, open your flow and look at the run history. Select the run to see the inputs and outputs of each step.

Check two things first: a due date in the wrong format, or an owner that is not an email address. Fix the step, save and submit another test. Each test adds a task, so delete the test tasks from the plan when you are done.

## Limits to know

Microsoft's Planner limits page gives these numbers:

- Maximum active tasks in a plan: 3,000.
- Maximum tasks in a plan: 9,000.
- Maximum buckets in a plan: 200.
- Maximum assignees in a task: 20.
- Maximum checklist items in a task: 20.
- Maximum references on a task: 15.
- Maximum tasks assigned to a user: 9,000.

Microsoft says these limits can be raised or lowered from time to time without notice. A small team will not come close, but a busy form that runs for years can. Close finished tasks and keep an eye on the number.

Microsoft's connector pages also list throttling limits: 300 calls per connection every 60 seconds for Forms and 100 calls per connection every 60 seconds for Planner. A form that gets hundreds of answers in a minute could hit them.

## What to avoid

- Do not build on a premium plan. The connector page says basic plans only.
- Do not map a person's name to Assigned User Ids. Use an email address.
- Do not map a free-text date into Due Date Time without a test. A wrong format breaks the step.
- Do not leave the flow owned by one person only. Each step runs under the connection of the person who added it. See "[The person who built your flows left: what happens and what to do](/guides/power-automate-flow-owner-left-company/)".
- Do not delete form questions after go-live. The flow labels and response data depend on them.
- Do not send private answers to a plan that a wide group can read. Task titles show to everyone with access. Ask your admin about rules for sensitive data.

## When a SharePoint list is steadier

A Planner task is good for one person doing one piece of work. It is less good when you need to sort, filter and report on a large number of requests. A SharePoint list holds every request as a row, with columns for status, owner and dates, and views to filter them. If your team needs a log of all requests and a count by type, a list is steadier.

See "[Save Microsoft Forms answers to a SharePoint list](/guides/microsoft-forms-to-sharepoint-list/)". For the full comparison, see "[Microsoft Planner vs SharePoint list for tracking team work](/guides/planner-vs-sharepoint-list/)".

## When to get help

You can build all of this yourself in Microsoft 365. If you would rather have it built and tested for your team, I do that. A tracker like this is a fixed price: \$5,000 for one, built in 2 weeks. See "[What a SharePoint tracker costs to build](/guides/what-a-sharepoint-tracker-costs/)". Bring one example of the problem to a free call.

I am Al Davies. I run 250 High Street LLC and build SharePoint trackers and Power Automate flows for operations teams. I work remotely. The first call is free, and I will not try to sell you anything.

See trackers I built: [Tools I built](/portfolio/)

## FAQ

### Which Power Automate action creates a Planner task from a form?

"Create a task". Use the trigger "When a new response is submitted", then "Get response details", then "Create a task" with a plan, title and optional bucket, dates and assignees.

### Can a flow add a checklist to a new Planner task?

Not in "Create a task". Microsoft's "Update task details" action takes checklist items with an Id, a Title and an Is Checked value, and a task can hold 20 checklist items.

### Why is the task not assigned to anyone?

The Assigned User Ids field takes semi-colon separated ids or email addresses. A plain name does not match, so collect an email address in the form.

### Does the Planner connector work with premium plans?

No. Microsoft's Planner connector page says the connector supports basic plans only.

### Why does the Forms trigger give only a Response Id?

The trigger tells the flow that a response arrived. Add "Get response details" to fetch the answers, as Microsoft's Forms connector page describes.

### Which license do I need?

Check with your admin. Microsoft's connector pages list Planner and Forms as Standard connectors in Power Automate, but what your account includes depends on your plan.

## Sources

- [Microsoft Learn, Planner connector reference ("Create a task", known issues, throttling)](https://learn.microsoft.com/en-us/connectors/planner/)
- [Microsoft Learn, Microsoft Forms connector reference (trigger, "Get response details", known limits)](https://learn.microsoft.com/en-us/connectors/microsoftforms/)
- [Microsoft Learn, Microsoft Planner limits](https://learn.microsoft.com/en-us/planner/planner-limits)

## Related guides

- [Save Microsoft Forms answers to a SharePoint list](/guides/microsoft-forms-to-sharepoint-list/)
- [Move a Planner task to another plan](/guides/planner-move-task-to-another-plan/)
- [Planner does not email me when a task is assigned](/guides/planner-notifications-not-working/)
- [Planner checklist limit and workarounds](/guides/planner-checklist-limit/)
- [Fix "The response is not in a JSON format" in Power Automate](/guides/power-automate-response-is-not-in-json-format/)

Source: https://250highstreet.com/guides/power-automate-create-planner-task-from-form/