Use a recurring check to catch meeting record gaps
A scheduled review can surface calls that need a meeting page, follow-up, or a clearer next step in Notion.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List Conference Records
Tool to list conference records. use when you need to retrieve a list of past conferences, optionally filtering them by criteria like meeting code, space name, or time range.
Why this helps
When attention moves quickly between calls, it is easy to miss a record that needs preparation or follow-up.
- Surface recent conferences that may not have a corresponding Notion record.
- Make follow-up review a predictable routine.
- Spend less effort reconstructing missed meeting admin from memory.
Setup
Build it in a few focused steps.
- 1Connect Notion and Google Meet to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally to review meeting records on a recurring basis.
- 3Write one instruction asking Notis to list recent Google Meet conference records, compare them with relevant Notion meeting pages, and report likely gaps.
- 4Choose a recurring schedule and report channel, then test against a recent set of meetings.
Questions about this workflow
Can this check a period such as the previous week?
Describe the desired review period in the instruction and select a matching schedule.
Does it retrieve transcripts?
No. This workflow uses the conference record listing action and a Notion comparison instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Google Meet. A trigger fires from one place; an action lands in another.
Notion triggers
Google Meet actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create a Meet
Creates a new google meet space, optionally configuring its access type and entry point access controls.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get conference record
Get conference record
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Meet details
Retrieve details of a google meet space using its unique identifier.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
Get Participant Session
Tool to get a specific participant session from a conference record. use when you need to retrieve details about a particular participant in a past meeting.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get recordings by conference record ID
Retrieves recordings from google meet for a given conference record id.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Get transcripts by conference record ID
Retrieves all transcripts for a specific google meet conference using its conferencerecord id.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
List Conference Records
Tool to list conference records. use when you need to retrieve a list of past conferences, optionally filtering them by criteria like meeting code, space name, or time range.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
List Participant Sessions
Tool to list all participant sessions for a specific conference record in google meet. use this when you need to retrieve a list of participants who joined a particular meeting.
Connect any two apps with Notis in the middle.
Notion and Google Meet, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Google Meet.