Get alerts when new Notion databases are created
A teammate creates a new database in Notion to track something new. Notis adds a sticky to your Mural board instantly. No one misses new tracking initiatives.
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
Create sticky note
Tool to create one or more sticky note widgets on a mural. use when you need to add notes to a mural layout.
Why this helps
Databases get created but not everyone hears about them, leading to duplicate databases and wasted effort setting up tracking twice.
- Team discovers new databases immediately
- Prevent duplicate database creation
- Improve visibility of tracking efforts
- Reduce wasted effort from not knowing
Setup
Build it in a few focused steps.
- 1Ensure Notion and Mural are integrated with Notis.
- 2Create an automation named 'New database alerts'.
- 3Set the prompt: 'When a new database container is created in my Notion workspace, create a sticky note on my Mural board announcing it with the database name and creator.'
- 4Choose 'Database Created' from Notion triggers.
- 5Select your notification channel.
- 6Test by creating a new Notion database.
Questions about this workflow
Will this catch databases created via templates?
Yes, this catches database containers created any way, including templates.
Can I see what the database is being used for?
Your prompt can ask Notis to include the database description or title if available.
Should we require approval before creating databases?
This automation just alerts the team, but you could establish a process where the team reviews new databases before they're used.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Mural. A trigger fires from one place; an action lands in another.
Notion triggers
Mural actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create sticky note
Tool to create one or more sticky note widgets on a mural. use when you need to add notes to a mural layout.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get current user
Tool to retrieve information about the currently authenticated user. use when you need current user details after authentication.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get files for a mural
Tool to retrieve a list of file widgets in a mural. use after confirming the mural id when listing file attachments.
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 Mural Widgets
Tool to retrieve all widgets within a specified mural. use after confirming the mural id is correct.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
MURAL Authorization Request
Tool to initiate the oauth 2.0 authorization process. use when you need to redirect a user to mural to obtain an authorization code.
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 Mural, 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 Mural.