Check live transcription sessions on a calmer cadence
A daily status check can replace repeated app-switching throughout your workday.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List live transcription jobs
Tool to list live transcription jobs. Use when you need an overview of live transcription sessions with optional filtering and pagination. Use after setting up live transcription.
Why this helps
Checking job status ad hoc interrupts focus and makes it harder to remember which sessions are complete.
- Consolidate status checking into one predictable moment.
- Reduce context switching during focused work.
- Notice sessions that may need follow-up.
Setup
Build it in a few focused steps.
- 1Connect Gladia to Notis once in the portal; connect Notion if you want to keep related workflow context there.
- 2Create an automation in the portal or ask Notis to set up a daily check.
- 3Use one instruction asking Notis to list Gladia live transcription jobs and summarize which may need attention.
- 4Choose a daily Notis schedule and select a channel for run reports.
- 5Test with a day when at least one live session exists.
Questions about this workflow
Does this require a Notion event?
No. It uses a recurring Notis schedule, as allowed for Notis-native triggers.
Does it retrieve detailed transcript results?
It lists live jobs. Detailed results for a specific job use a separate Gladia action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Gladia. A trigger fires from one place; an action lands in another.
Notion triggers
Gladia actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get live transcription result
Tool to retrieve metadata and results of a live transcription job. Use when you need detailed status or results for a specific live transcription session.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Pre-recorded Transcription Result
Tool to retrieve metadata for a pre-recorded transcription job. Use when checking the status or retrieving results of a specific job ID.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Initiate Live Transcription Session
Tool to initiate a live transcription session. Use before streaming audio to get a WebSocket URL.
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.
Initiate Pre-Recorded Transcription
Tool to initiate a pre-recorded transcription job. Use when you have an audio URL and need asynchronous transcription results.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List live transcription jobs
Tool to list live transcription jobs. Use when you need an overview of live transcription sessions with optional filtering and pagination. Use after setting up live transcription.
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.
Gladia List Pre-Recorded Transcriptions
Tool to list pre-recorded transcription jobs with optional filters. Use after submitting or querying jobs to retrieve paginated results.
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.
Upload Audio/Video File
Tool to upload an audio or video file to Gladia's servers. Use when preparing a file for transcription.
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.
Connect any two apps with Notis in the middle.
Notion and Gladia, 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 Gladia.