Connect Notion to New relic
When something happens in Notion, Notis takes the next step in New relic. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Notion to New relic
Review alert conditions after a Notion schema change
When a Notion data source schema changes, retrieve its New Relic alert conditions so the owner can review whether monitoring still matches the work.
Inventory New Relic policies for each new project record
When a new Notion database page is created, retrieve New Relic alert policies to help the team check whether the project has monitoring coverage.
Surface New Relic applications when a service page is created
When a Notion page is created, retrieve New Relic applications to support a service ownership or onboarding check.
Bring alert condition context into incident discussion
When someone comments in Notion, retrieve New Relic alert conditions for the relevant policy to support a more informed incident discussion.
Surface policy context when a Notion record changes
When a Notion page's properties change, retrieve New Relic alert policies to support ownership or status follow-up on operational records.
Check browser applications after runbook edits
When a Notion page's body content changes, retrieve New Relic browser applications to help validate that a runbook still reflects the monitored front end.
Check policies when an operational subpage is added
When a subpage is added beneath a Notion operations hub, retrieve New Relic alert policies to support its setup and monitoring review.
Check alert notification channels when a monitoring view is created
When a Notion view is created for operational tracking, retrieve New Relic alert notification channels to make channel availability visible for review.
Create a New Relic policy for a new operational database
When a new Notion database is created for operational tracking, create a New Relic alert policy as a starting point for monitoring setup.
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.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Notion and New relic
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.