Check API version during transcription process updates
When you update the transcription process page, let Notis retrieve the current API version information as part of the review.
Trigger
Page Updated
Triggers when any block within a specified Notion page is updated.
Action
Get API Version
Tool to retrieve current API version and check for updates. If Happy Scribe does not expose a dedicated /version endpoint, this tool attempts to infer the version from HTTP response headers or from the base_url path (e.g., /api/v1).
Why this helps
Integration notes can become stale, leaving founders unsure whether current setup guidance still fits.
- Adds a current version lookup to process maintenance.
- Helps keep integration documentation grounded in live information.
- Reduces uncertainty when revisiting a workflow.
Setup
Build it in a few focused steps.
- 1Connect Notion and Happy Scribe to Notis once through the portal.
- 2Create an automation with a plain-language instruction to retrieve Happy Scribe API version information when the process page is updated.
- 3Choose the Notion Page Updated trigger for the specified process page.
- 4Select a channel for run reports and test with a real page update.
Questions about this workflow
Will this update my process document automatically?
The action retrieves version information. The workflow prompt can ask Notis to report the result in your selected channel.
Can the trigger watch a single page?
Yes. Choose the Page Updated trigger scoped to the process page you maintain.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Happy scribe. A trigger fires from one place; an action lands in another.
Notion triggers
Happy scribe actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Subtitle
Tool to generate subtitles for a video file by creating a transcription with the is_subtitle flag. Use after confirming the media URL is publicly accessible and valid.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Transcription
Tool to initiate a new transcription job using a publicly accessible or signed URL. Use when you have uploaded a media file and want to start transcription immediately.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Translation Task
Tool to create a translation task for a transcription (deprecated). Use after transcription is complete to request translation.
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.
Delete Transcription
Tool to delete a transcription job. Use when you have a transcription ID and want to remove it, optionally permanently. Use after confirming the transcription ID.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Webhook
Tool to delete a specific webhook. Use when you need to remove a webhook after confirming its identifier.
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.
Export Subtitle
Tool to export subtitle in the requested format. Use after transcription is completed.
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 Account Details
Tool to retrieve details about your account, including subscription status and usage statistics. Use after authenticating your API key to monitor plan and usage.
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 Supported Languages
Tool to retrieve supported language codes and names. Use when you need the list of valid languages for transcription or subtitle services.
Connect any two apps with Notis in the middle.
Notion and Happy scribe, 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 Happy scribe.