Skip to content
Notis

Recheck transcription work when your tracking changes

A change to recording-tracker columns can be a useful cue to review the related job queue.

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

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.

Why this helps

When a tracking setup changes, it is easy to lose confidence about work already in progress.

  • Pair a structural tracker change with a quick queue review.
  • Make in-progress work visible during process updates.
  • Reduce uncertainty after reorganizing recording records.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Gladia to Notis once in the portal.
  • 2Create an automation through the portal or a plain-language request to Notis.
  • 3Ask Notis in one instruction to list Gladia pre-recorded transcription jobs when the recording data source schema changes.
  • 4Choose Data Source Schema Updated for the relevant source and select a run-report channel.
  • 5Test by making a safe schema change and reviewing the resulting job list.

Questions about this workflow

Why use a schema trigger here?

It fires for structural changes such as adding, removing, or renaming a column, which can be a good time to review the queue.

Does the list identify which Notion rows changed?

The action lists Gladia jobs; correlating them with Notion records depends on the information available in the job results.

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.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

Initiate Live Transcription Session

Tool to initiate a live transcription session. Use before streaming audio to get a WebSocket URL.

ActionInstant

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.

TriggerInstant

Initiate Pre-Recorded Transcription

Tool to initiate a pre-recorded transcription job. Use when you have an audio URL and need asynchronous transcription results.

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

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.

ActionInstant

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.

TriggerInstant

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.

ActionInstant

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.

TriggerInstant

Upload Audio/Video File

Tool to upload an audio or video file to Gladia's servers. Use when preparing a file for transcription.

ActionInstant

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.

TriggerInstant

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.