Revisit meeting AI output when notes change
When you update a meeting page, bring the related Fireflies output back into view for a quick consistency check.
Trigger
Page Updated
Triggers when any block within a specified Notion page is updated.
Action
Fetch AI App Outputs
Fetch outputs for a specific ai app or meeting/transcript.
Why this helps
Revising meeting notes can make it hard to remember whether an important detail came from the call or later interpretation.
- Provides a transcript-based reference during note revisions.
- Helps reduce repeated tool switching.
- Supports more confident meeting summaries.
Setup
Build it in a few focused steps.
- 1Connect Notion and Fireflies to Notis once through the portal.
- 2Create an automation in the portal or request it from Notis conversationally.
- 3Give Notis one instruction to fetch the related Fireflies AI output when meeting page content changes.
- 4Select Page Content Updated as the trigger and choose a run-report channel.
- 5Test by editing the body of a meeting page with a Fireflies record.
Questions about this workflow
Will every edit run the workflow?
Notion aggregates content edits within a short window, and the trigger can be scoped to a specific meeting page or data source.
Does fetching output update the Notion notes?
The listed Fireflies action fetches AI app output. Any write-back behavior depends on the automation's supported capabilities.
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.