Outlook Calendar to Notion, meeting tracker stays current
Your meeting tracker starts out clean. Then the reschedules happen. Someone changes the Teams link, a client moves the time, and suddenly your Notion database is lying to you.
Ops leads feel it when leadership asks for “a quick view” of what’s coming up. Account managers feel it when they’re prepping for back-to-backs. And if you run a small team, the Outlook Notion sync problem becomes a weekly ritual of copy-paste and second-guessing.
This automation keeps Outlook Calendar events synced into Notion so your meeting tracker stays current. You’ll see what it does, what you need, and how to avoid the usual setup headaches.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Outlook Calendar to Notion, meeting tracker stays current
flowchart LR
subgraph sg0["On schedule Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "On schedule", pos: "b", h: 48 }
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/notion.dark.svg' width='40' height='40' /></div><br/>Try get database page"]
n2["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/merge.svg' width='40' height='40' /></div><br/>Merge"]
n3@{ icon: "mdi:swap-horizontal", form: "rounded", label: "If database page not found", pos: "b", h: 48 }
n4["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/notion.dark.svg' width='40' height='40' /></div><br/>Create database page"]
n5["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/notion.dark.svg' width='40' height='40' /></div><br/>Update database page"]
n6@{ icon: "mdi:cog", form: "rounded", label: "X days into the future", pos: "b", h: 48 }
n7["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/itemLists.svg' width='40' height='40' /></div><br/>Split out items"]
n8["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Get Outlook Calendar events"]
n2 --> n3
n0 --> n6
n7 --> n2
n7 --> n1
n1 --> n2
n6 --> n8
n3 --> n4
n3 --> n5
n8 --> n7
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0 trigger
class n3 decision
class n1,n4,n5 database
class n8 api
classDef customIcon fill:none,stroke:none
class n1,n2,n4,n5,n7,n8 customIcon
The Problem: Your Notion Meeting Tracker Drifts Out of Sync
Keeping a Notion “Meetings” database accurate sounds simple until you actually do it for a month. Outlook changes constantly: times shift, invites get updated, and meeting links get replaced. If you’re manually copying subjects, dates, IDs, and URLs into Notion, you’ll miss updates. Or you’ll “fix it later,” which turns into a messy tracker full of duplicates, wrong dates, and broken links right when you need it most. The worst part is the mental load. You can’t trust your own system, so you check Outlook anyway.
It adds up fast. Here’s where the friction usually shows up.
- Copying every event into Notion takes about 5 minutes per meeting, and it’s never just one meeting.
- Reschedules create duplicates because nobody wants to hunt down the “old” Notion page.
- Links get outdated, which means you’re scrambling in the last minute before a call.
- Your tracker becomes personal instead of team-ready, because only the person maintaining it knows what’s accurate.
The Solution: Automatically Sync Outlook Calendar Events to Notion
This workflow runs on a schedule and pulls Outlook Calendar events inside a defined time window (by default, the next year). Each event gets expanded into individual items, then checked against your Notion database using a unique identifier (the Outlook Event ID). If Notion doesn’t have that event yet, the workflow creates a new database page using the event subject as the title, adds the date, stores the Event ID, and saves the meeting link as a URL property. If the event already exists, it updates the Notion page so the tracker stays accurate when meeting details change. You’re not rebuilding your system. You’re making it reliable.
The workflow starts with a scheduled trigger, calculates the date range, then retrieves Outlook events through an HTTP request. From there, it compares each event to Notion and either creates or updates the matching page. The end result is a Notion meeting tracker you can actually trust day to day.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you have 12 meetings a week that you want logged in Notion. Manually, even a “fast” routine is about 5 minutes per meeting to copy the subject, date, link, and paste it into the right database, which is roughly an hour a week. Add reschedules and link updates and it becomes more like 90 minutes because you’re cleaning up duplicates. With this workflow, you spend maybe 10 minutes once setting up the Notion fields, then it runs on schedule and stays current in the background.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Microsoft Outlook / Microsoft account to read calendar events.
- Notion to store your meeting tracker pages.
- Notion database properties (Title, Date, Event ID, Link) set up in advance.
Skill level: Intermediate. You’ll connect Microsoft and Notion credentials and map a few database fields carefully.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A scheduled run kicks things off. n8n starts the workflow on the interval you choose (daily is common), so your Notion tracker refreshes without anyone remembering to do it.
A date window keeps it focused. The workflow calculates a time frame (default is within the next year), then uses an HTTP request to pull only the Outlook events that fit.
Each event is checked against Notion. Events are expanded into items, then the workflow looks up your Notion database to find a matching page based on the Outlook Event ID. That ID is the key that prevents duplicates.
Notion pages are created or updated. Missing events become new pages, while existing ones get updated so changes to the title, date, or link actually show up in your tracker.
You can easily modify the time window (next 90 days, next 30 days) to match how far ahead your team plans. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Scheduled Trigger
Set the schedule that starts the calendar sync workflow.
- Add the Scheduled Automation Trigger node as the workflow trigger.
- Set the Rule interval to run every minute (as configured in the node).
Step 2: Connect Outlook and Fetch Events
Build the date window and retrieve calendar events from Microsoft Graph.
- Connect Scheduled Automation Trigger to Advance Date Window.
- In Advance Date Window, set Operation to
addToDate, Duration to365, Magnitude to{{ $json.timestamp }}, and Output Field Name toFuture date. - Connect Advance Date Window to Retrieve Outlook Events.
- In Retrieve Outlook Events, set URL to
https://graph.microsoft.com/v1.0/me/calendarviewand enable Send Query. - Set query parameters: startdatetime to
{{ new Date($('Scheduled Automation Trigger').item.json.timestamp).toISOString() }}and enddatetime to{{ new Date($json['Future date']).toISOString() }}. - Credential Required: Connect your oAuth2Api credentials in Retrieve Outlook Events.
Step 3: Expand Events and Match with Notion
Split the Outlook response into individual events and check for existing Notion entries.
- Connect Retrieve Outlook Events to Expand Event Items.
- In Expand Event Items, set Field to Split Out to
value. - Expand Event Items outputs to both Combine Records and Lookup Notion Entry in parallel.
- In Lookup Notion Entry, set the filter to Event ID|rich_text equals
{{ $json.id }}with Return All set totrue. - Set the Database ID to your Notion database and keep Resource as
databasePageand Operation asgetAll. - Credential Required: Connect your notionApi credentials in Lookup Notion Entry.
- Connect Lookup Notion Entry to Combine Records (Input 2).
- In Combine Records, set Mode to
combine, Join Mode toenrichInput1, and merge by id ↔ property_event_id.
[YOUR_ID] in Lookup Notion Entry with your actual Notion database ID or select it from the list picker.Step 4: Create or Update Notion Pages
Route each event based on whether a matching Notion page exists, then create or update records.
- Connect Combine Records to Branch If Missing.
- In Branch If Missing, set the condition to check if
{{ $json.property_event_id }}isEmpty. - Connect the true output of Branch If Missing to Generate Notion Page to create new entries.
- In Generate Notion Page, set Title to
{{ $json.subject }}and map properties: Date|date with{{ $json.start.dateTime }}and{{ $json.end.dateTime }}, Event ID|rich_text to{{ $json.id }}, and Link|url to{{ $json.webLink }}. - Credential Required: Connect your notionApi credentials in Generate Notion Page.
- Connect the false output of Branch If Missing to Modify Notion Page to update existing entries.
- In Modify Notion Page, set Page ID to
{{ $json.id }}and update properties with{{ $json.start.dateTime }},{{ $json.end.dateTime }},{{ $json.webLink }}, and{{ $json.subject }}. - Credential Required: Connect your notionApi credentials in Modify Notion Page.
Date, Event ID, Link, and Name with matching types, or the page creation/update will fail.Step 5: Test and Activate Your Workflow
Validate that events are correctly created or updated in Notion and then enable the schedule.
- Click Execute Workflow to run a manual test.
- Confirm Retrieve Outlook Events returns items and Expand Event Items splits them into individual events.
- Verify that new events go through Generate Notion Page and existing events go through Modify Notion Page.
- Open Notion and confirm pages are created/updated with the mapped date range, event ID, and link.
- Turn the workflow Active to enable scheduled syncing.
Common Gotchas
- Microsoft credentials can expire or need specific permissions. If things break, check your Microsoft connector/auth status in n8n’s Credentials first.
- If you’re using scheduled runs and pulling a lot of events, processing times vary. Bump up time windows carefully and watch for empty responses that make downstream Notion steps look “broken.”
- Notion database fields must match what the workflow expects. If “Event ID” is the wrong property type (it should be text), the lookup fails and you’ll create duplicates all day.
Frequently Asked Questions
About 30–45 minutes if your Notion database is ready.
No. You will connect accounts and map a few Notion properties to Outlook fields.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Notion and Microsoft account access (usually already covered for most teams).
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and it’s a smart tweak if you have a busy calendar. Change the date window logic in the “Advance Date Window” part of the workflow, then the “Retrieve Outlook Events” request will only pull what falls inside that range. Common customizations include syncing only specific calendars, filtering out internal meetings by keyword, and mapping extra Notion properties like “Client” or “Owner.”
Usually it’s expired Microsoft authorization or missing permissions for the calendar scope you’re trying to read. Reconnect the Microsoft credential in n8n and confirm the calendar being queried is accessible to that account. Also check the HTTP request configuration (tenant/org settings can matter) and watch for rate limits if you’re pulling a large time window with lots of events.
A few hundred events per run is normal for most small teams, and self-hosting can scale further if your server is sized appropriately.
It depends on how strict you are about data quality. Zapier and Make can absolutely move calendar events into Notion, but this workflow’s “check first, then create or update” pattern is where n8n tends to shine, especially when you want to avoid duplicates using an Event ID as a key. n8n also gives you more control over date windows and merging data without paying extra for every branch. If you’re syncing a lot of events, self-hosting is frankly a big deal because you’re not watching task counts. Zapier or Make may still be easier for a quick two-step setup, so if you’re unsure, Talk to an automation expert.
Once this is running, your Notion meeting tracker stops being a side project. It stays current, and you get that time (and attention) back every week.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
