Schema Evolution Design Prep
Schema changes. Templates refresh. Designs ready.
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
Get Designs
Tool to retrieve all designs with optional filtering by category or type. use after authenticating to list available templates.
Why this helps
Database schema updates happen without triggering design prep, so designers start templates before understanding the new content structure.
- Design templates are ready before content gets added to new fields
- Templates match the evolved content structure automatically
- Reduces design rework caused by late template changes
- Keeps designs and content structure aligned from the start
Setup
Build it in a few focused steps.
- 1Connect Notion and Abyssale to Notis.
- 2Create an automation: 'When a Notion data source schema changes, fetch templates from Abyssale that match the updated structure.'
- 3Specify your content database or leave workspace-wide.
- 4Set notifications and create the automation.
- 5Add a new field to a database schema and verify templates are fetched for the new field type.
Questions about this workflow
How does Notis know which templates match the new schema?
In your prompt, define the relationship between field types and templates (e.g., 'If a video field is added, fetch video templates').
Does this trigger for any schema change (rename, delete, add)?
Yes, this automation fires for any schema update. You can add filters to only trigger for specific types of changes (e.g., only new fields).
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Abyssale. A trigger fires from one place; an action lands in another.
Notion triggers
Abyssale actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Test Abyssale Authentication
Tool to test api authentication via the /ready endpoint. use after configuring your api key to ensure credentials are valid before other requests.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Abyssale Project
Tool to create a new project to organize designs and images. use after deciding on a project name to group your templates and assets.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Designs
Tool to retrieve all designs with optional filtering by category or type. use after authenticating to list available templates.
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.
Get Fonts
Tool to list all available fonts, including custom and google fonts. use when you need to fetch font options before generating or editing designs.
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 Abyssale, 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 Abyssale.