Give new landing pages a clean cache start
When a new landing page record is created, let Notis clear its BunnyCDN URL so early visitors get the intended content.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Purge URL
Tool to purge a specific url from the bunnycdn cache. use when you need to invalidate a resource immediately after updating it.
Why this helps
New campaign pages may be served from cache before the latest final version is visible.
- Adds a cache-refresh step to page creation.
- Reduces launch-day follow-up tasks.
- Targets the specific landing page URL.
Setup
Build it in a few focused steps.
- 1Connect Notion and BunnyCDN in Notis once.
- 2Create the automation conversationally or in the portal.
- 3Give Notis one instruction to purge a new landing page's BunnyCDN URL once its published URL is available.
- 4Select Notion Page Created and choose where run reports should appear.
- 5Test with one newly created page that has a live URL.
Questions about this workflow
Will it purge a URL before a page is live?
The instruction should tell Notis to purge only when the corresponding published URL is known.
Can it cover campaign pages in one database?
Yes. Select the relevant Notion data source trigger scope if available and describe campaign pages in the prompt.
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.