Notion (via Zapier)

When TeamsMaestro finishes summarizing a meeting, the Zap creates a new item in the Notion data source you pick. You decide which properties get the title, date, attendees, summary, and action items.

It works well as a running log. One database for client calls, filtered by customer, or one for your weekly team syncs that anyone can search without opening TeamsMaestro.

Pick which meetings run it. The trigger has optional filters for the meeting title (contains, starts with, or matches exactly) and for the host or participants. You can combine conditions and run the Zap when any of them is met.

1. Open the template and sign in to Zapier. Connect your TeamsMaestro account, which shows up in Zapier as AI TeamsMaestro.
2. Keep Meeting Summarized as the trigger, and add filters if you only want some meetings.
3. Test the trigger. Zapier loads a recent meeting from your account so you can see the fields: title, platform, start and end times, organizer, attendees, summary, and action items.
4. Connect Notion and choose the data source (database) the items should go into.
5. Map the TeamsMaestro fields to your properties. The meeting title is usually the item name, and the summary and action items go in the page content.
6. Run a test, check the new item in Notion, and publish the Zap.

New to Zapier and TeamsMaestro? The Zapier setup guide walks through a full example, and the Zapier integration page lists everything else you can connect.