Transcribe recordings shared in Notion comments
A comment that shares a recording can be the cue to make it readable. Astica ai transcribes the audio so the next step is easier to spot.
Trigger
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.
Action
Analyze Audio
Tool to analyze audio input for transcription. use when you need to convert an audio url or base64 string to text.
Why this helps
A recording shared in a discussion can get overlooked when everyone has to listen through it first.
- Make shared recordings quicker to review.
- Reduce repeat listening to locate a key point.
- Keep discussion context connected to a transcript.
Setup
Build it in a few focused steps.
- 1Connect Notion and Astica ai to Notis once in the portal.
- 2Create an automation in the portal or tell Notis what outcome you want conversationally.
- 3Give one plain-language instruction to transcribe accessible audio referenced by new Notion comments.
- 4Select the Notion Comment Created trigger, choose a reporting channel, and test with one real comment and recording.
Questions about this workflow
Does every comment contain audio?
No. The instruction should ask Notis to proceed when the comment provides an accessible audio source.
Can I limit comments to a page?
The Comment Created trigger supports an optional page filter when setting up the trigger.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Astica ai. A trigger fires from one place; an action lands in another.
Notion triggers
Astica ai actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Analyze Audio
Tool to analyze audio input for transcription. use when you need to convert an audio url or base64 string to text.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
ASTICA_READ_TEXT
Tool to perform ocr on an image to extract text. use when you need to read raw text from images after confirming the image source.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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 Astica ai, 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 Astica ai.