Export Microsoft Planner tasks to json

The below is generated from Christine Payton’s tutorial Get Planner Task Details with Power Automate - Assignees, subtasks, buckets, dates!, except this example is implemented the Teams Workflows app rather than standalone Power Automate, and the output file is saved to a Teams channel rather than to a separate SharePoint location. 

The Teams workflow snips are intentionally summarised here to show any variances to Christine's YouTube tutorial and for reference in future posts applying this solution to Wristplanner.  However, for full details please watch the tutorial, which includes explanations on how to create each of the steps, reasons / purpose for each step, and how to configure the Run After Settings.

The test execution at the end is run on the completed tasks generated on the previous post to Automatically Load Tasks From Excel to Microsoft Planner. That article also guides in how to create the flow in Teams and general Workflow navigation and testing, so these instructions aren’t repeated here in favour of showing the action steps only.

For simplicity, configured the flow with a manual trigger only:

Next steps:

• Initialise variables (PlannerData, Assignees, and Buckets)

• Extract the list of Tasks and Buckets using the Wristplanner project (note that Microsoft has updated the icon for Planner compared to the YouTube, but otherwise the actions are the same)

• Set up an array of Bucket id and names

• Create the output array of detailed task information 

Important: Because of the either/or configuration of Run After Settings on the previous two parallel branch actions, one of the two actions will always be skipped and the other will be successful.  Therefore, the Filter array action needs to be set to run on Skip and Success for both branch actions:

• Lastly, output the completed json.

Note the use of the SharePoint connector to output to the Teams Files folder, because SharePoint is the back end of Teams:

The result of a flow execution:

And corresponding JSON:

If the above file output looks confusing, refer to Christine’s next tutorial to use this output to Report on Planner Data in Power BI.