Pair a new tracking view with a live-session check
Creating a clearer view of your work can be a cue to see which live transcription sessions are active.
Trigger
View Created
Triggers when a new Notion view is created. Fires workspace-wide. The payload includes `data.view_type` (`table`, `board`, `gallery`, `calendar`, `list`, `timeline`, `gantt`) and `data.parent` pointing at the view's tree parent (typically the teamspace), so customers can filter downstream.
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
A new organization system is less useful when ongoing work remains hidden in another service.
- Connect a tracking change with a timely job overview.
- See live transcription activity while organizing your workflow.
- Reduce the need to search across tools for current sessions.
Setup
Build it in a few focused steps.
- 1Connect Notion and Gladia to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to describe the outcome.
- 3Use one instruction asking Notis to list Gladia live transcription jobs when a relevant Notion view is created.
- 4Choose View Created and a channel for run reports.
- 5Test by creating a view in the session-tracking area.
Questions about this workflow
Will every new view run the workflow?
View Created is workspace-wide, so describe the relevant session-tracking context in your instruction.
Does it show transcript content?
The list action provides a job overview; use Get live transcription result for a specific session's details.
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.