Start a project database with a subgraph inventory
A new project database can trigger a subgraph lookup, helping the team start with a view of the published components.
Trigger
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.
Action
List Grafbase Subgraphs
Tool to list published subgraphs in a branch. Use when you need to retrieve endpoints of all subgraphs for a given branch.
Why this helps
New project setup can leave people hunting for existing architecture context across tools.
- Make an architecture lookup part of the project setup moment.
- Reduce the chance that existing subgraphs are overlooked.
- Give the project owner a concrete reference for early planning.
Setup
Build it in a few focused steps.
- 1Connect Notion and Grafbase to Notis once in the portal.
- 2Create an automation that asks Notis to list Grafbase subgraphs when a new project database is created.
- 3Select Database Created as the trigger and describe the project databases this applies to in the prompt.
- 4Choose a channel for run reports and test with one real database creation.
Questions about this workflow
Does this create a subgraph?
No. It lists published subgraphs in a branch.
Is a database container different from a data source?
Yes. This trigger is for database container creation; adding a data source to an existing database is a separate event.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Grafbase. A trigger fires from one place; an action lands in another.
Notion triggers
Grafbase actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Grafbase API Key
Tool to delete an existing API key. Use after confirming the key ID to revoke access.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Grafbase Audit Log
Tool to delete a specific Grafbase audit log entry. Note: As of current Grafbase public documentation, there is no documented API to delete audit logs programmatically. This action will attempt a best-effort REST DELETE to `/audit-logs/{id}` and, if unsupported or not found, it will gracefully fall back to validating connectivity with the GraphQL Management API and return a structured response instead of failing.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Extension
Tool to delete an extension configuration. Use after confirming the extension_id to remove the extension.
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 MCP Server
Tool to delete a Grafbase MCP server configuration by its unique ID. Use after confirming the server ID to remove an existing MCP server.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Grafbase Schema
Tool to delete a Grafbase schema. Use when you need to remove a specific schema from the registry after confirming its 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 Schema Check
Tool to delete a Grafbase schema check. Use when you need to remove a specific schema check by its ID after reviewing the registry.
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.
Disable MCP server
Tool to disable the Model Context Protocol server. Use when you need to turn off MCP via API after it has been enabled.
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.
Enable Grafbase MCP Server
Tool to enable the Model Context Protocol (MCP) server for a Grafbase project. Use when you need to activate MCP support; if the API endpoint is not supported, this returns guidance for enabling via configuration.
Connect any two apps with Notis in the middle.
Notion and Grafbase, 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 Grafbase.