Orient new databases with existing maps
When a new database container appears, Notis can show the maps already available before the workflow takes shape.
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 Maps
Tool to list all maps accessible to the user. use after authentication to retrieve maps with pagination and optional filtering.
Why this helps
A newly created database can quickly become a process without a clear view of existing location resources.
- Bring existing map resources into early workflow planning.
- Reduce extra exploration during database setup.
- Use a clear event as a setup reminder.
Setup
Build it in a few focused steps.
- 1Connect Notion and Mapulus to Notis once.
- 2Create an automation in the portal or ask Notis to create it in plain language.
- 3Ask Notis in one instruction to list Mapulus maps when a new Notion database is created.
- 4Choose Database Created, set a channel for reports, and test with a real new database event.
Questions about this workflow
Is this for a new data source inside an existing database?
No. Database Created fires for a database container. A newly created data source has its own event.
Does it create maps for the database?
No. The Mapulus action only lists maps.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Mapulus. A trigger fires from one place; an action lands in another.
Notion triggers
Mapulus actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Find Location by External ID
Tool to retrieve locations by external id. use after obtaining an external identifier to find the matching location(s).
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Map Details
Tool to retrieve detailed information about a map. use when you have a map id and need full map metadata.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Locations
Tool to list all locations. use after authentication to retrieve a paginated list of locations.
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.
List Maps
Tool to list all maps accessible to the user. use after authentication to retrieve maps with pagination and optional filtering.
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 Mapulus, 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 Mapulus.