Design Brief Template Matcher
Write a brief. Templates appear. No platform switching.
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
Get Designs
Tool to retrieve all designs with optional filtering by category or type. use after authenticating to list available templates.
Why this helps
Designers waste time remembering what templates exist and manually switching between Notion and Abyssale to hunt for options.
- Templates surface instantly without platform switching
- Designers see what's available before starting work
- Reduces decision paralysis by centralizing options
- Keeps briefs and templates in a single view for clarity
Setup
Build it in a few focused steps.
- 1Ensure Notion and Abyssale are connected to Notis (one-time setup in portal).
- 2Tell Notis 'When I create a new design brief page in Notion, fetch all available templates from Abyssale and embed them in the page.'
- 3Select 'Page Created' as the trigger and define which database holds design briefs (optional scope).
- 4Choose your Notis notification channel and create the automation.
- 5Create a new design brief page and verify templates populate automatically.
Questions about this workflow
Will this only work for a specific database or all new pages?
You can scope it to a specific 'Design Briefs' database, or leave it open to fire for any new page. Scoping keeps noise down and focuses on relevant pages.
What happens if no templates exist in Abyssale yet?
Notis will note that and embed a message saying templates can be created in Abyssale. Once you add templates, future briefs will show them.
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.