cancel
Showing results for 
Search instead for 
Did you mean: 

Flow: Create Plan in Planner

It would be great to have a "Create Plan" Action for Planner in Flow. At the moment it is only possible to create buckets or tasks.

Status: New
Comments
Anonymous
Not applicable

I strongly support the creation of a Flow Action that creates a Planner plan. The end game here is to create a standard project in Teams and Planner from a calendar event entry. Here's the beauty of this tactic. Today I can create a calendar in SharePoint and upon the addition of an event I have the ability to create a Channel in Teams. Ideally, I'd use that exact same calendar event creation to trigger the creation of a Plan with a set of standard buckets and task assignments. The only remaining step would be to add the Plan to the Tab in the right Teams Channel. This would be a tremendously useful automation.

Anonymous
Not applicable

I can't understand why is this not implemented yet! 

Regular Visitor

I agree there is every single connecter for planer, but most imporant one is missing, to create plan! I am attempting to do this writing my own HTTP Requests but I am having a lot of issues, either share your connector info and let me make it or make it yourself 🙂 

Regular Visitor

@Anonymous @Anonymous @thomas_d I have created connector myself if anyone is interested in. I cannot attach file here so below are steps how to import, keep in mind you have to have Flow Plan 1 or Flow Plan 2 to import connector:

 

1. Open your favorite texteditor

2. Copy everything from code snippet below

3. Save file with .json extension, example "Create-Plan-in-Planner.swagger.json" (this is the file name microsoft creates for me when downloading file, you can use that too)

4. Go to flow.microsoft.com, once logged in click "Gear Icon" and go to Custom Connectors"

5. Import custom connectior using that json file.

6. Upon Flow import feel free to change name, description, upload photo, etc.

{
  "swagger": "2.0",
  "info": {
    "title": "Create Plan in Planner",
    "description": "Create Plan in Planner",
    "version": "1.0"
  },
  "host": "graph.microsoft.com",
  "basePath": "/",
  "schemes": [
    "https"
  ],
  "consumes": [],
  "produces": [],
  "paths": {
    "/v1.0/planner/plans": {
      "post": {
        "responses": {
          "default": {
            "description": "default",
            "schema": {
              "type": "object",
              "properties": {
                "createdBy": {
                  "type": "object",
                  "properties": {
                    "application": {
                      "type": "object",
                      "properties": {
                        "id": {
                          "type": "string",
                          "description": "ID of application that created plan",
                          "title": "Application ID",
                          "x-ms-visibility": null
                        }
                      },
                      "description": "application"
                    },
                    "user": {
                      "type": "object",
                      "properties": {
                        "id": {
                          "type": "string",
                          "description": "ID of a user that created plan",
                          "title": "User ID",
                          "x-ms-visibility": null
                        }
                      },
                      "description": "user"
                    }
                  },
                  "description": "createdBy"
                },
                "createdDateTime": {
                  "type": "string",
                  "description": "Date and time plan was created",
                  "title": "Created Date and Time",
                  "x-ms-visibility": null
                },
                "owner": {
                  "type": "string",
                  "description": "Office 365 group that this plan is part of",
                  "title": "Plan Owner",
                  "x-ms-visibility": null
                },
                "title": {
                  "type": "string",
                  "description": "Title of a plan",
                  "title": "Plan Title",
                  "x-ms-visibility": null
                },
                "id": {
                  "type": "string",
                  "description": "ID of a plan",
                  "title": "Plan ID",
                  "x-ms-visibility": null
                }
              }
            },
            "headers": {
              "HTTP/1.1": {
                "description": "HTTP/1.1",
                "type": "string"
              },
              "Content-type:": {
                "description": "Content-type",
                "type": "string"
              },
              "Content-length:": {
                "description": "Content-length",
                "type": "integer"
              }
            }
          }
        },
        "operationId": "createmuprojectplan",
        "summary": "Create Plan",
        "description": "Create plan",
        "parameters": [
          {
            "name": "Content-type",
            "in": "header",
            "required": true,
            "type": "string",
            "default": "application/json",
            "x-ms-visibility": "internal"
          },
          {
            "name": "body",
            "in": "body",
            "required": true,
            "schema": {
              "type": "object",
              "properties": {
                "owner": {
                  "type": "string",
                  "description": "Group ID (GUID) that will be used for project owner",
                  "title": "Project owner (Group ID)",
                  "x-ms-visibility": null
                },
                "title": {
                  "type": "string",
                  "description": "Plan name that will be displayed",
                  "title": "Plan name",
                  "x-ms-visibility": null
                }
              },
              "required": [
                "owner",
                "title"
              ]
            }
          }
        ]
      }
    }
  },
  "definitions": {},
  "parameters": {},
  "responses": {},
  "securityDefinitions": {
    "oauth2_auth": {
      "type": "oauth2",
      "flow": "accessCode",
      "authorizationUrl": "https://login.windows.net/common/oauth2/authorize",
      "tokenUrl": "https://login.windows.net/common/oauth2/authorize",
      "scopes": {
        "Group.ReadWrite.All": "Group.ReadWrite.All"
      }
    }
  },
  "security": [
    {
      "oauth2_auth": [
        "Group.ReadWrite.All"
      ]
    }
  ],
  "tags": []
}   

 

Dual Super User III

It is tough to wait for a specific new feature to be implemented in Microsoft Flow, specially in this case, since current Planner REST API supports creating Plans in Planner via Create PlannerPlan method.

There are several other other ideas marked as NEW (i.e. not evaluated yet by Microsoft) asking for other features present in Planner REST API, so I was thinking on an overall solution that would let us enjoy all Planner features currently available via Planner REST API and are not available in Microsoft Flow Planner connector yet.

 

Can we have more chances to catch the attention of Flow Product Managers by concentrating votes from all these ideas into an overall solution? If you think it is worth a try, you can vote this overall idea here

New Member

Hi all,

 

I completely agree with @ipalikuca it's so bloody ridicolous that a "create plan" doesn't exists on the planner connector (same situation for many other connectors, e.g. Teams) ... @efialttes Regarding exploting the graph API to create a plan, rubbish as well, at least in this case... Since the http connector is premium (rubbish) I'm using the "send an http request to sharepoint" (a bit of a trick here for not using the Http connector,) which works for all other missing default actions in connectors (api calls to graph v1. 0 or beta, doesn't matter) but in this case it fails miserably .. And the HTTP connector is way to complicated to explote the graph API (authenticating is a nightmare!) 

 

At the end, frustrated power users everywhere... Looks like to me that Microsoft is into the business of offering to their partners the task that the user should be able to achieve using Flow...