Cloud FlowCloud FlowsBeginner

SharePoint Item Assigned to Outlook Task

When a SharePoint list item is assigned to a user, create a corresponding Outlook Task with the due date and item link.

SharePointOffice 365 Outlook

Unique name

flowLibsSPItemToOutlookTaskDemo

Publisher

FlowLibs (flowlibs)

Version

1.0.0.1

Components

3 env vars + 1 cloud flow

Request access

Provided as-is, without warranty of any kind. Review and test each pattern in a non-production environment before deploying it to live automations. See our Terms.

What it does

Overview

This flow bridges SharePoint list assignments with personal task management in Outlook. When a list item in a tracked SharePoint list is assigned to a person (either at creation or via an update to the assignee column), the flow automatically creates an Outlook Task in that person's tasks folder. The task carries over the SharePoint item's title, due date, and a deep link back to the originating item so the assignee can jump straight to the source record from their task list.

The pattern is intentionally simple — one trigger, one create-task action, and a small amount of field mapping — so it serves both as a useful productivity utility and as a learning template for connecting SharePoint events to Outlook 365 actions.

Why you'd use it

Use Case

Teams that track work in SharePoint lists (project tasks, requests, change items, action logs) frequently want assignees to see those items show up in their personal task list without having to remember to add them manually. This flow closes that gap: the moment an item is assigned, it appears as an Outlook Task on the assignee's to-do list, complete with the due date and a one-click link back to the SharePoint record.

It is especially well suited for project managers and team leads who assign work in SharePoint but whose team members live day-to-day in Outlook.

The flow is ideal for teams that:

Project managers who assign tasks in SharePoint but want the work to surface in each assignee's Outlook task list
Teams that track action items, change requests, or follow-ups in SharePoint lists
Business users who prefer Outlook Tasks/To Do as their personal task surface
Organizations standardizing on Microsoft 365 task management without a dedicated PM tool

Step-by-step

Flow Architecture

When an item is created or modified

SharePoint - When an item is created or modified

Fires whenever a list item in the configured SharePoint list is added or updated. The flow uses the item payload to read the title, assignee, due date, and item link.

Create Outlook task for assignee

Office 365 Outlook - Create a task (V3)

Creates an Outlook Task in the assignee's tasks folder. The subject is taken from the SharePoint item title, the due date is mapped from the item's due-date column, and the task body includes a hyperlink back to the SharePoint item for one-click navigation.

Solution config

Environment Variables

Schema name	Type	Default	Description
flowlibs_SharePointSiteUrl	String	<configure>	Full URL of the SharePoint site that hosts the assignment list (e.g. https://your-tenant.sharepoint.com/sites/Projects).
flowlibs_SharePointListName	String	<configure>	Display name of the SharePoint list whose items should generate Outlook tasks when assigned.
flowlibs_TaskSubjectPrefix	String	[SharePoint]	Optional prefix prepended to every Outlook Task subject so assignees can spot SharePoint-sourced tasks at a glance. Set to an empty string to disable.

Auth dependencies

Connectors & Connections

Connector	API name	Actions used
SharePoint	shared_sharepointonline	OnUpdatedItems (trigger - when an item is created or modified)
Office 365 Outlook	shared_office365	CreateTaskV3

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Tweaks & variations

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Point at your own SharePoint list: Update the trigger's Site Address and List Name (or set the flowlibs_SharePointSiteUrl and flowlibs_SharePointListName environment variables) so the flow watches the list your team actually uses.
Map your assignee and due-date columns: If your SharePoint list uses column names other than the defaults (e.g. 'Owner' instead of 'AssignedTo', 'TargetDate' instead of 'DueDate'), update the dynamic content references inside the Create task action to point at your column internal names.
Only fire on assignee change: By default the trigger fires on any create or modify event. To avoid creating duplicate tasks on every edit, insert a Condition that compares the new assignee against the previous value (using the SharePoint trigger's previous-value outputs) and only continue when they differ.
Add a subject prefix or project code: Customize the task subject template to include a project code, ticket number, or status emoji so SharePoint-sourced tasks stand out in the assignee's Outlook task list.