Give incident comments useful monitoring context
A short comment can start an important incident thread. Bring in the relevant alert conditions so the next step is easier to decide.
Trigger
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.
Action
Get Alert Conditions
Tool to retrieve alert conditions for a specified policy. use after you have the policy id.
Why this helps
Incident discussion can stall while someone searches separately for the alert conditions tied to the affected policy.
- Surface alert condition details during a Notion discussion.
- Reduce context switching between incident notes and monitoring tools.
- Help the team move from comment to informed follow-up.
Setup
Build it in a few focused steps.
- 1Connect Notion and New Relic to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to retrieve the relevant New Relic alert conditions when an incident comment arrives.
- 3Choose the Notion Comment Created trigger and specify the incident context in the instruction.
- 4Choose a channel for run reports and test with a real comment on an incident page.
Questions about this workflow
Does this read every comment?
The Comment Created trigger can fire workspace-wide or be scoped to a page with its optional page_id filter.
Does this resolve incidents?
No. It retrieves alert conditions for a policy to support discussion and follow-up.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to New relic. A trigger fires from one place; an action lands in another.
Notion triggers
New relic actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Alert Notification Channel
Tool to create an alert notification channel. use when you need to register a new endpoint (email, webhook, etc.) for alert notifications.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Alert Policy
Tool to create an alert policy. use when you need to programmatically set up a new alert policy in new relic.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete alert policy
Tool to delete an existing alert policy via rest api. use when you have the policy id and want to remove it via new relic's rest api. use after confirming the policy id exists.
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 Alert Channels
Tool to retrieve a list of alert notification channels. use when you need to list all configured channels after verifying your api key.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Alert Conditions
Tool to retrieve alert conditions for a specified policy. use after you have the policy 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.
Get Alert Policies
Tool to retrieve a list of alert policies. use when you need to list existing alert policies with optional filtering and pagination.
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 Applications
Tool to retrieve a list of new relic applications. use when you need to list all applications or filter by name, host, or ids after authenticating your api key.
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 Browser Applications
Tool to list new relic browser applications. use when you need to retrieve all browser applications or filter by name after authenticating your api key.
Connect any two apps with Notis in the middle.
Notion and New relic, 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 New relic.