Notion Meeting Notes from Teams Meetings

Overview

This flow standardizes meeting documentation in Notion. Shortly before a scheduled Outlook/Teams meeting starts, it creates a Notion meeting-notes page pre-filled with the meeting title and date, appends a structured body template (meeting details + agenda / decisions / action-items headings), and posts the page link to a Teams channel so attendees collaborate in one place. Why it matters: Meeting notes scattered across personal docs get lost. A consistent, auto-created Notion page per meeting gives the team a single, searchable record with a ready action-items section — created without anyone setting it up by hand. Design note — trigger choice: The standard Office 365 Outlook connector has no native "meeting ended" trigger. This build uses When an upcoming event is starting soon (V3) — the closest standard trigger — so the notes page is ready by the time the meeting begins. (See Customization for a post-meeting / transcript variant.)

Use Case

A team that documents meetings in Notion wants a notes page created automatically for each meeting, using a standard template, with the link shared to attendees in Teams — instead of someone building it by hand every time.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Office 365 Outlook	shared_office365	OnUpcomingEventsV3
Notion	shared_notionip	CreateaPage Appendblockchildren
Microsoft Teams	shared_teams	PostMessageToConversation

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.

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.

Post-meeting / transcript variant

Replace the trigger with a recurring schedule + Get calendar view of events filtered to recently-ended meetings, then add the transcript link with a second Appendblockchildren once available.

Target a specific meeting chat

If you have the meeting's chat thread ID, switch the Teams location to Group chat and post there instead of a channel.

AI summary

After the meeting, summarize the transcript with Azure OpenAI and append the summary to the page.

Action extraction

Parse action items into a related Notion tasks database via a relation property.

Richer page properties

If the notes database has Date / Attendees columns, map them in Create_Notion_Notes_Page body/properties (kept to the Name title here for portability).

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

@{concat(triggerOutputs()?['body/subject'], ' — ', formatDateTime(triggerOutputs()?['body/start'],'yyyy-MM-dd'))}

@if(empty(coalesce(triggerOutputs()?['body/optionalAttendees'],'')), coalesce(triggerOutputs()?['body/requiredAttendees'],''), concat(coalesce(triggerOutputs()?['body/requiredAttendees'],''), '; ', triggerOutputs()?['body/optionalAttendees']))

@body('Create_Notion_Notes_Page')?['id']

@body('Create_Notion_Notes_Page')?['url']

Customize & download