Create and assign Outlook tasks to someone else

[Trumpetritz]

It would be great to have an Outlook connector that enables me to create a task an assign to someone else. E.g. if a list item within a sharepoint list has been changed, assign todo to my colleague.

[AlanPilz]

Perhaps to take this one step further, I would also think it useful that when the assigned task is completed it could be used to update a ShareList item to reflect the fact that the task has been completed.

[GlennMurphy]

Flow to define a task is not very useful if tasks cannot be assigned to the appropriate individual.  I'm trying to automate tracking of onboarding actions - the new hire, security, payroll, IT, benefits, etc.  Different people have responsiblity for performing actions. I can manage the onboarding task list in powerapp, but I need flow to create the tasks.

[Dominik87]

The same. I tried to create a flow for onboarding of new customers and employees in the company. To create it, it would be great to have possibility to assign task to a person using MS FLOW.

[woolee]

---

@AlanPilz  wrote:

Perhaps to take this one step further, I would also think it useful that when the assigned task is completed it could be used to update a ShareList item to reflect the fact that the task has been completed.

---

I totally agree with you, good idea!

[KWalent]

SInce you can create a task in Outlook for yourself when a new item is added in a SharePoint list, you would think you can create Outlook tasks for someone else. It's just a different email to send it to. Has anything changed regarding this issue yet?

[aterrito]

@KWalent I did manage to create a Flow that will add items to my Microsoft To Do list (which is replacing Outlook tasks) when someone fills out a Form. I haven't tried to get it to upload to multiple individual's To Do lists, but at the very least, if you had someone create a Form that you could populate, and then create their own Flow to take the responses of that form and add them to their own To Do list, that should work for being able to populate their To Do list.

[DustinDortch1]

Yeah, this has been problematic.  A custom graph connector could probably do the trick, though.  https://graph.microsoft.com/beta/{$UserPrincipalName}/outlook/tasks

It just needs to have a principal created that has Delegated permissions to Tasks.ReadWrite for all required users.

I had to make a custom connector for Teams Provisioning and it is easy enough to do.

https://docs.microsoft.com/en-us/graph/api/outlookuser-post-tasks?view=graph-rest-beta&tabs=csharp

JSON definition of the connector (just created and tested):

{
"swagger": "2.0",
"info": {
"title": "Outlook Tasks for all users",
"description": "Create Outlook Tasks for all users",
"version": "1.0"
},
"host": "graph.microsoft.com",
"basePath": "/",
"schemes": [
"https"
],
"consumes": [],
"produces": [],
"paths": {
"/beta/{UserPrincipalName}/outlook/tasks": {},
"/beta/users/{UserPrincipalName}/outlook/tasks": {
"post": {
"responses": {
"default": {
"description": "default",
"schema": {}
}
},
"summary": "Create Task",
"operationId": "CreateTask",
"parameters": [
{
"name": "UserPrincipalName",
"in": "path",
"required": true,
"type": "string"
},
{
"name": "Content-type",
"in": "header",
"required": true,
"type": "string",
"default": "application/json"
},
{
"name": "body",
"in": "body",
"required": false,
"schema": {
"type": "object",
"properties": {
"@odata.context": {
"type": "string",
"description": "@odata.context"
},
"@odata.etag": {
"type": "string",
"description": "@odata.etag"
},
"id": {
"type": "string",
"description": "id"
},
"createdDateTime": {
"type": "string",
"description": "createdDateTime"
},
"lastModifiedDateTime": {
"type": "string",
"description": "lastModifiedDateTime"
},
"changeKey": {
"type": "string",
"description": "changeKey"
},
"categories": {
"type": "array",
"items": {},
"description": "categories"
},
"assignedTo": {
"type": "string",
"description": "assignedTo"
},
"hasAttachments": {
"type": "boolean",
"description": "hasAttachments"
},
"importance": {
"type": "string",
"description": "importance"
},
"isReminderOn": {
"type": "boolean",
"description": "isReminderOn"
},
"owner": {
"type": "string",
"description": "owner"
},
"parentFolderId": {
"type": "string",
"description": "parentFolderId"
},
"sensitivity": {
"type": "string",
"description": "sensitivity"
},
"status": {
"type": "string",
"description": "status"
},
"subject": {
"type": "string",
"description": "subject"
},
"completedDateTime": {
"type": "string",
"description": "completedDateTime"
},
"recurrence": {
"type": "string",
"description": "recurrence"
},
"reminderDateTime": {
"type": "string",
"description": "reminderDateTime"
},
"body": {
"type": "object",
"properties": {
"contentType": {
"type": "string",
"description": "contentType"
},
"content": {
"type": "string",
"description": "content"
}
},
"description": "body"
},
"dueDateTime": {
"type": "object",
"properties": {
"dateTime": {
"type": "string",
"description": "dateTime"
},
"timeZone": {
"type": "string",
"description": "timeZone"
}
},
"description": "dueDateTime"
},
"startDateTime": {
"type": "object",
"properties": {
"dateTime": {
"type": "string",
"description": "dateTime"
},
"timeZone": {
"type": "string",
"description": "timeZone"
}
},
"description": "startDateTime"
}
}
}
}
]
}
}
},
"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": {
"Tasks.ReadWrite": "Tasks.ReadWrite"
}
}
},
"security": [
{
"oauth2_auth": [
"Tasks.ReadWrite"
]
}
],
"tags": []
}

[PHemingway610]

If Nintex has been able to do this with Flexi tasks for a long time, then why doesn't it exist for Flow/Power Automate already?  What is the use case for someone creating a flow which is only capable of putting a task in their own My Tasks folder?  I have never had to build anything like that but I get requirements for workflows to assign tasks to other people... all the time.  It boggles my mind that Microsoft hasn't built this.