Export captions after approval in Notion
Keep approval and caption delivery connected: update the Notion page, then let Notis request the finished subtitle export.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Export Subtitle
Tool to export subtitle in the requested format. Use after transcription is completed.
Why this helps
Approval can be the last visible milestone, leaving the actual caption export unclaimed.
- Connects approval context to subtitle delivery.
- Helps teams finish the publishing handoff after review.
- Reduces the chance of approved captions being forgotten.
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 export subtitles for the completed job when the page content indicates approval.
- 3Choose the Notion Page Content Updated trigger for the relevant approval page.
- 4Pick a channel for run reports and test with one approved subtitle job.
Questions about this workflow
What if the approval text changes but the job is incomplete?
The prompt should specify that the export is for a completed subtitle job. The action is meant to follow completion.
Can the page be the approval record?
Yes. Scope the page content trigger to that approval page and ensure it references the correct Happy Scribe job.
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.