Know Your Video Production Status at a Glance
Create a video view in Notion. Instantly see every video in production in Adrapid. Stop hunting through two platforms to understand pipeline status.
Trigger
View Created
Triggers when a new Notion view is created. Fires workspace-wide. The payload includes `data.view_type` (`table`, `board`, `gallery`, `calendar`, `list`, `timeline`, `gantt`) and `data.parent` pointing at the view's tree parent (typically the teamspace), so customers can filter downstream.
Action
List Banners
Tool to list all banners and their statuses. use when you need to retrieve banners after creation or to audit existing banners. ensure you apply filters to narrow down results (e.g., status='ready').
Why this helps
Video projects exist in both Notion and Adrapid but you never have a clear picture of what is in progress, stuck, or ready to ship.
- See your entire video production pipeline in one place
- Spot bottlenecks and prioritize urgent work immediately
- Prevent videos from getting lost in the production queue
Setup
Build it in a few focused steps.
- 1Connect Notion and Adrapid integrations to Notis
- 2Prompt Notis: 'When I create a view in my video database, show me all videos currently in Adrapid production'
- 3Select 'View Created' as the trigger type
- 4Choose your team's production channel for the status update
- 5Create a new view in your Notion video database and confirm the Adrapid video list appears
Questions about this workflow
Can I filter the video list by status or priority?
Yes - ask Notis to 'show only videos in progress' or 'show videos from Q4' and it will refine the list to what matters right now.
How often does the list update?
It's pulled live each time so you always see the current production status without manual checking.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Adrapid. A trigger fires from one place; an action lands in another.
Notion triggers
Adrapid actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get API info
Tool to retrieve api root information. use when you need to discover the api's description and version details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get user and API info
Tool to get user account and api information. use when you need to retrieve authenticated user details and api versions.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Banners
Tool to list all banners and their statuses. use when you need to retrieve banners after creation or to audit existing banners. ensure you apply filters to narrow down results (e.g., status='ready').
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 Adrapid, 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 Adrapid.