Bootstrap New Databases With Best Practices Instantly
Create a new Notion view and get example layouts, field structures, and sample data pulled from template galleries automatically. No manual setup needed.
Trigger
View Created
Triggers when a new Notion view is created. Fires workspace-wide. The payload includes `data.view_type` (`table`, `board`, `gallery`, `calendar`, `list`, `timeline`, `gantt`) and `data.parent` pointing at the view's tree parent (typically the teamspace), so customers can filter downstream.
Action
Query Data
Tool to query structured data as json from a web page using an agentql query or natural language prompt. use after defining your query or prompt and a url or html.
Why this helps
Setting up new databases involves tedious manual config. Founders recreate the wheel instead of using existing patterns.
- Kickstarts new databases with proven patterns
- Reduces setup time from hours to minutes
- Ensures consistency across team workflows
Setup
Build it in a few focused steps.
- 1Connect Notion and Agentql to Notis.
- 2Create this automation: 'When I create a new view in any database, scrape Notion template galleries for similar database structures. Pull field names, view types, and filters that match this database type. Suggest them in Notion.'
- 3Set trigger to 'View Created' workspace-wide and choose your channel.
- 4Test by creating one new view and see suggested templates appear.
- 5Refine to focus on specific database types (e.g., 'when CRM views are created, pull CRM templates').
Questions about this workflow
Does it copy template data into my database?
No, it shows you the template structure and best practices. You copy what you want. This keeps your data clean and intentional.
Can it suggest views based on the field types I already have?
Yes - update the instruction to say 'suggest views that would work well with my current fields.'
Does this only work for new views or existing ones too?
Currently for new views. For existing databases, run it manually by asking Notis to suggest templates.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Agentql. A trigger fires from one place; an action lands in another.
Notion triggers
Agentql actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Usage Details
Tool to retrieve subscription usage details for the current api key, including usage limits and billing period. use after confirming api connection is valid.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Query Data
Tool to query structured data as json from a web page using an agentql query or natural language prompt. use after defining your query or prompt and a url or html.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Remote Browser Session
Tool to create a remote browser session. use when you need to run browser automation on remote infrastructure.
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.
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 Agentql, 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 Agentql.