Make escalation setup part of service onboarding
As each service enters your Notion database, ask Notis to create a Better Stack escalation policy for review.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Create Escalation Policy
Tool to create a new escalation policy. use when defining how incidents should escalate across team members.
Why this helps
Service onboarding involves many steps, and incident escalation can be overlooked until the first urgent issue.
- Bring response planning into the service onboarding path.
- Reduce dependence on remembering an extra setup step.
- Create a policy for a responsible person to review.
Setup
Build it in a few focused steps.
- 1Connect Notion and Better Stack to Notis once in the portal.
- 2Create an automation in Automations or ask Notis to create one.
- 3Use a single prompt to request a Better Stack escalation policy when a service entry is added in Notion.
- 4Select the Notion New Page trigger for the service data source and choose a report channel.
- 5Add a test service and review the policy created in Better Stack.
Questions about this workflow
Will the policy contact the right people automatically?
The action creates a policy. Verify the responders and escalation sequence in Better Stack.
Can it be restricted to the services database?
Yes. Scope the New Page trigger to that Notion data source.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Better stack. A trigger fires from one place; an action lands in another.
Notion triggers
Better stack actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Escalation Policy
Tool to create a new escalation policy. use when defining how incidents should escalate across team members.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Heartbeat Group
Tool to create a new heartbeat group. use when you need to organize related heartbeat checks under a single, logical group. example prompt: "create a new heartbeat group named 'backend services'."
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Outgoing Webhook Integration
Tool to create a new outgoing webhook integration. use when you need to register an endpoint to receive event notifications from better stack.
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.
Create Source Group
Tool to create a new source group. use when you have finalized the group name (and optional sort index) and need to organize related log sources under that group.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Escalation Policy
Tool to delete an escalation policy by id. use when you need to permanently remove an existing escalation policy 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 Source Group
Tool to delete a source group by id. use when you need to permanently remove an existing source group after confirming it is no longer needed.
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.
Get Heartbeat
Tool to get a single heartbeat by id. use when you need to fetch details of a specific heartbeat.
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.
Get Heartbeat Availability
Tool to retrieve availability summary for a specific heartbeat. use when you need availability metrics for a heartbeat within an optional date range.
Connect any two apps with Notis in the middle.
Notion and Better stack, 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 Better stack.