Review meeting transcripts after changing your Notion schema
When you revise meeting data columns, sample relevant Fireflies transcripts to check that the workflow still supports your review habits.
Trigger
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.
Action
Get Transcripts
The gettranscripts action is designed to fetch a list of transcripts against input arguments.
Why this helps
Structural changes to a meeting database can quietly interrupt a reliable routine for reviewing calls.
- Adds a practical review cue after structural edits.
- Helps check whether meeting capture still supports the process.
- Reduces the chance of unnoticed workflow gaps.
Setup
Build it in a few focused steps.
- 1Connect Notion and Fireflies to Notis once through the portal.
- 2Create the automation in the portal or request it from Notis in plain language.
- 3In one instruction, ask Notis to search representative Fireflies transcripts when the meeting data source schema changes.
- 4Choose Data Source Schema Updated as the trigger and a report channel.
- 5Test after a planned schema edit using a meeting data source.
Questions about this workflow
Does this trigger on ordinary page edits?
No, this trigger is for data source schema changes such as adding, removing, or renaming columns.
What should the transcript search review?
State the meeting context and the aspects of the workflow you want to recheck in the plain-language instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Fireflies. A trigger fires from one place; an action lands in another.
Notion triggers
Fireflies actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add to Live Meeting
The addtolive action allows you to add the fireflies.ai bot to an ongoing meeting. note: this action requires a paid fireflies plan to add bots to meetings.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Transcript by ID
The deletetranscriptbyid action is designed to delete a specific transcript by its id.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Fetch AI App Outputs
Fetch outputs for a specific ai app or meeting/transcript.
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 Bite by ID
The getbite action is designed to fetch details associated with a specific bite id.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Transcripts
The getbites action is designed to fetch a list of bites against input arguments.
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 Transcript by ID
The gettranscriptbyid action is designed to fetch details associated with a specific transcript id. note: this action requires a paid fireflies plan to access transcript details.
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.
Get Transcripts
The gettranscripts action is designed to fetch a list of transcripts against input arguments.
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.
Get User by ID
The getuser action is designed to fetch details associated with a specific user id.
Connect any two apps with Notis in the middle.
Notion and Fireflies, 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 Fireflies.