Connect process changes with pull zone settings
Keep an operational change from getting lost by asking Notis to review the pull zone and handle an explicitly defined update.
Trigger
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.
Action
Update Pull Zone
Tool to update settings for a specific pull zone. use when you need to modify existing pull zone settings after reviewing current configuration.
Why this helps
A new process field may affect how a team manages delivery, but the related infrastructure follow-up can be forgotten.
- Creates a cue to review related delivery settings.
- Checks the current pull zone context before changes.
- Keeps the next step connected to the process update.
Setup
Build it in a few focused steps.
- 1Connect Notion and BunnyCDN to Notis once.
- 2Create an automation in the portal or ask Notis in plain language.
- 3In one instruction, identify the relevant schema change, review the named pull zone, and apply only the explicitly requested settings update.
- 4Choose Data Source Schema Updated and a channel for run reports.
- 5Test with a safe schema update and a specific, reversible configuration request.
Questions about this workflow
Will any schema edit change a pull zone?
The instruction should restrict changes to a relevant schema update and a clearly stated requested setting.
Does Notis check current settings first?
The instruction should ask it to review the named pull zone before applying the request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Bunnycdn. A trigger fires from one place; an action lands in another.
Notion triggers
Bunnycdn actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Storage Zone
Tool to add a new storage zone. use when you need dedicated file storage in a specific region.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create DNS Record
Tool to create a new dns record in a specific dns zone. use after confirming the dns zone id is active.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Pull Zone
Tool to create a new pull zone. use after gathering origin details.
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.
Delete DNS Record
Tool to delete a specific dns record by its id. use after confirming the dns zone id and record id.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete DNS Zone
Tool to delete a specific dns zone by its id. use when you need to permanently remove an existing dns zone after verifying the zone id.
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.
Delete Pull Zone
Tool to delete a specific pull zone by its id. use when you need to remove a pull zone after confirming its 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.
Delete Storage Zone
Tool to delete a storage zone. use when you need to remove a storage zone after confirming its id.
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.
Get DNS Zone Details
Tool to retrieve details of a specific dns zone by its id. use when you need to verify dns zone configuration after creation or update.
Connect any two apps with Notis in the middle.
Notion and Bunnycdn, 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 Bunnycdn.