Make recording-page requests easy to act on
A focused comment on a recording page can be the cue for Notis to send that page's accessible recording to CastingWords.
Trigger
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Action
Order Transcript
Tool to create a new transcription order for audio/video at a url. use when you have an accessible media url and need to initiate transcription.
Why this helps
The person responsible for submitting audio may not see a request buried in a specific page's discussion.
- Scopes the cue to a dedicated recording page.
- Makes a simple comment sufficient to move the request forward.
- Reduces page-by-page checking for transcription tasks.
Setup
Build it in a few focused steps.
- 1Connect Notion and CastingWords to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to transcribe a recording when requested on its page.
- 3Describe the request and accessible recording URL requirement in one plain-language instruction.
- 4Choose New Comment and scope it to the specified recording page; select a channel for reports.
- 5Test with a real request comment on that page.
Questions about this workflow
How is this different from workspace comments?
This trigger is for a specified Notion block or page, so it can focus the workflow on one recording page.
What needs to be in place before the comment?
The page or accessible context needs to provide the recording media URL for CastingWords.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Castingwords. A trigger fires from one place; an action lands in another.
Notion triggers
Castingwords actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Cancel and Refund Audio File
Tool to cancel an ordered audio file and issue a refund if applicable. use when no transcription work has been done on the file (pre-processing, audio processing, error states).
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Prepay Balance
Tool to retrieve the current prepay balance for the account. use when you need to check available funds before placing new transcription orders.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get registered webhook URL
Tool to retrieve the currently registered webhook url for account notifications. use when you need to verify your webhook setup.
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.
Order Transcript
Tool to create a new transcription order for audio/video at a url. use when you have an accessible media url and need to initiate transcription.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Order Upgrades
Tool to order an upgrade for a specific audio file. use after transcription is complete to add items like timestamps or extra editing. example: 'order timestamps for file 12345'.
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.
Register Webhook
Tool to register a webhook url to receive transcript completion notifications. use when you want castingwords to post transcript-complete events to your service endpoint.
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.
List Available SKUs
Tool to retrieve list of available skus. use when you need to know available services and pricing before placing an order.
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.
Test Webhook Call
Tool to request a test webhook call for a specific event type. use after registering a webhook url to ensure webhook notifications are functioning properly.
Connect any two apps with Notis in the middle.
Notion and Castingwords, 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 Castingwords.