Look up transcripts after marking a meeting complete
Mark the meeting complete in Notion and retrieve the related Fireflies transcript for your follow-up routine.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Get Transcripts
The gettranscripts action is designed to fetch a list of transcripts against input arguments.
Why this helps
After a call ends, remembering to search for its transcript adds another task to an already busy transition.
- Creates a clear cue for transcript retrieval.
- Reduces manual searching after a call.
- Supports a repeatable meeting wrap-up habit.
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 ask Notis conversationally.
- 3Give Notis one instruction to find the matching Fireflies transcript when a Notion meeting record is marked complete.
- 4Choose Page Properties Updated as the trigger and a reporting channel.
- 5Test by changing one meeting record to its completed status.
Questions about this workflow
What should the meeting record contain?
Include enough meeting context, such as its title or date, for Notis to identify a likely matching Fireflies transcript.
Does this create meeting notes in Notion?
This workflow retrieves transcripts from Fireflies. Any further handling should be stated in the automation instruction and supported by the connected tools.
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.