Send ready podcast episodes to Cincopa
Mark an episode ready in Notion and have Notis start its upload, so the release handoff does not live in your head.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are 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 property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Upload Asset From URL
Tool to upload a new asset directly from a provided external url and receive a status id for tracking. use when you need to import media from a remote source and optionally specify a gallery or existing asset.
Why this helps
A finished episode can stall between its production status and the hosting step.
- Use the ready status as the clear upload cue.
- Reduce extra checks during episode release.
- Keep the publishing plan and media handoff connected.
Setup
Build it in a few focused steps.
- 1Connect Notion and Cincopa to Notis once in the portal.
- 2Create an automation instructing Notis to upload an episode URL only after its Notion record is marked ready.
- 3Select Page Properties Updated for the episodes data source and choose a channel for run reports.
- 4Test by marking a sample episode ready.
Questions about this workflow
Can it avoid uploading on other property edits?
Tell Notis to proceed only when the episode's status changes to ready.
What should I store on the episode record?
Include the remote media URL that Cincopa can access.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Cincopa. A trigger fires from one place; an action lands in another.
Notion triggers
Cincopa actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Upload Asset From URL
Tool to upload a new asset directly from a provided external url and receive a status id for tracking. use when you need to import media from a remote source and optionally specify a gallery or existing asset.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Abort Asset Upload From URL
Tool to abort an ongoing asset upload-in-progress by providing its status id. use when an upload is no longer needed, was initiated by mistake, or is taking too long.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Asset Upload From URL Status
Tool to check the status of an asset upload initiated via url by its status id. use after calling 'upload asset from url' to poll for completion.
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.
Validate API Connection
Tool to validate api connection. use after obtaining a valid api token to confirm connectivity.
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 Cincopa, 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 Cincopa.