Make new Notion meeting recordings readable
Meeting pages can capture the recording and the next step in the same place. Transcription helps you find the moment that matters.
Trigger
New Page
Triggers when a new page is added to a Notion database.
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
Finding a decision or follow-up in a long meeting recording takes focus and time.
- Scan meeting audio for key moments more quickly.
- Make recordings easier to revisit during follow-up.
- Keep transcript output associated with meeting work.
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 ask Notis to make one conversationally.
- 3Give a single instruction to transcribe accessible recordings on new meeting pages and return the result.
- 4Choose the Notion New Page trigger, select a run-report channel, and test with one real meeting page.
Questions about this workflow
Does this create meeting action items?
No. It transcribes audio so you can review it; it does not assign tasks by itself.
Can the trigger be limited to meeting pages?
The New Page trigger supports a data_source_id scope, so it can watch the meeting data source.
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.