Skip to content
Developer tools ⇄ Business productivity

Newrelic to Notion integration — real-time, two-way sync

Keep Newrelic and Notion in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Newrelic and Notion

Connect the tickets, records, and events in Notion to the systems engineering runs in Newrelic, kept current in real time and in both directions.

Notion is where customer-facing and operational work happens: the tickets, conversations, contacts, and records a team touches every day. Newrelic is where engineering runs the systems behind that work — the issue trackers, message brokers, directories, and monitors that keep services moving. The same items, people, and events matter to both, and when the only link between them is a manual hand-off or an overnight export, each side acts on a stale copy of what the other already knows.

Stacksync syncs Properties, Blocks, Formula and Rollup properties, Users in Notion with Workloads, Synthetics Monitors, Custom Events, Change Tracking (Deployments) in Newrelic field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync maps the overlap, resolves conflicts by rules you set, and keeps every copy current, with no middleware to build and no API limits to babysit.

Common use cases

  • 01 Push rows from a warehouse or another database into a Notion data source as Pages so ops and leadership read live metrics in a familiar Notion view.
  • 02 Sync a Notion content-calendar database with Jira or Linear by mapping status and date properties both directions.
  • 03 Provision and update Dashboards and Alert Policies from a config repository or database through NerdGraph so definitions stay versioned and consistent across accounts and environments.
  • 04 Push custom business or pipeline Events and Metrics into New Relic through the Event and Metric APIs so they appear alongside APM data in dashboards and NRQL.

Common sync patterns

Where Newrelic tracks engineering work: requests become issues

A ticket or request raised in Notion opens or updates a matching issue in Newrelic, and status, comments, and resolution flow back, so support and engineering work the same item instead of retyping it.

Where Newrelic moves messages between services: activity lands on the stream

Records created or changed in Notion publish to the queue or topic in Newrelic as they happen, so downstream services react to real events rather than polling for them.

Where Newrelic is the directory or identity source: one set of users

People and accounts in Notion stay matched to the users in Newrelic, so access, provisioning, and org changes propagate instead of being keyed in twice.

What you can sync between Newrelic and Notion

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Newrelic objects Notion objects How this pairing syncs
Synthetics Monitors Synthetic uptime and scripted browser checks managed through NerdGraph synthetics mutations (create, update, delete); monitor results are read via NRQL for availability and latency reporting. Properties Typed columns on a page — title, rich_text, number, select, multi_select, date, people, relation, status, checkbox, URL. Read and written both ways. Synthetics Monitors is specific to Newrelic and Properties to Notion — each maps to any object or custom field on the other side.
Custom Events Custom events posted write-only to the Event API on insights-collector with a License/Ingest key; business or pipeline events pushed into New Relic to enrich dashboards, then queried back out with NRQL. Blocks The page body — paragraphs, headings, to-dos, tables — nested as children and fetched recursively, separate from a page's properties. Custom Events is specific to Newrelic and Blocks to Notion — each maps to any object or custom field on the other side.
Change Tracking (Deployments) Deployment and change markers recorded through NerdGraph changeTrackingCreateDeployment; written from CI/CD to annotate charts, and read back via NRQL on the Deployment event for release correlation. Formula and Rollup properties Values computed by Notion from other fields; read-only, so they are pulled out for reporting but never written back. Change Tracking (Deployments) is specific to Newrelic and Formula and Rollup properties to Notion — each maps to any object or custom field on the other side.
Dashboards Dashboard definitions and widgets via NerdGraph dashboardCreate/dashboardUpdate/dashboardDelete mutations and entity queries, with full CRUD; exported for backup and audit or provisioned and updated programmatically from a source of truth. Users Workspace members and bots referenced by people properties; read-only — users cannot be created or invited through the API. Dashboards is specific to Newrelic and Users to Notion — each maps to any object or custom field on the other side.
Alert Policies & Conditions Alert policies and NRQL alert conditions managed through NerdGraph alertsPolicy and alertsNrqlCondition mutations with full create, update, and delete; read out for audit or provisioned from a config source so alerting stays consistent across accounts. Comments Page and inline discussion threads; can be read and created, useful for surfacing Notion activity in another system. Alert Policies & Conditions is specific to Newrelic and Comments to Notion — each maps to any object or custom field on the other side.
NRQL Query Results Telemetry events, metrics, logs, and spans queried through NerdGraph's nrql field (or the legacy Insights query API) over time windows; read-only and bounded by data retention, commonly streamed into a warehouse for long-term analysis. Files and attachments File-property and file-block values. Notion-hosted URLs are temporary and expire, so files are re-fetched or copied at sync time. NRQL Query Results is specific to Newrelic and Files and attachments to Notion — each maps to any object or custom field on the other side.

How changes propagate between Newrelic and Notion

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Newrelic Notion Sub-second propagation

DetectionNewrelic notifies Stacksync of record changes through webhook events. NRQL polling over timestamp windows for telemetry (events, metrics, logs, spans).

DeliveryEach detected change is written to Notion through its API, with automatic retries and rate-limit backoff.

Notion Newrelic Sub-second propagation

DetectionNotion notifies Stacksync of record changes through webhook events. Workspace webhooks (page.created, page.content_updated, data_source.schema_updated, comment.created.

DeliveryEach detected change is written to Newrelic through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Newrelic: NerdGraph allows 25 concurrent requests per user and returns HTTP 429 when exceeded; NRQL run via APIs is capped at 3,000 queries per account per minute with a 5-second default timeout and about 5,000 data points per response. The Event API accepts 1MB per POST and 100,000 POSTs per minute per account.
  • Notion: Average of ~3 requests/second per integration with some bursts; 429 with a Retry-After header when exceeded. Payloads capped at 500 KB and 1000 block elements.
What ships with Newrelic ⇄ Notion

Connect Newrelic and Notion for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Newrelic–Notion connection.

Real-time

Two-way sync

Changes in Newrelic or Notion instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Newrelic or Notion data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Newrelic or Notion record.

Observability

Monitoring

Track your Newrelic ⇄ Notion sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Newrelic and Notion.

How the Newrelic and Notion connectors work

Newrelic

Integration surface
NerdGraph (GraphQL) plus REST data-ingest APIs (Event, Metric, Log, Trace) and the legacy REST API v2
Authentication
User API key (prefixed NRAK-) sent in the API-Key header for NerdGraph queries and mutations; the data-ingest APIs (Event, Metric, Log) use a License/Ingest key in the Api-Key header. Keys, endpoints, and data are region-scoped (US, EU, JP).
Change detection
NRQL polling over timestamp windows for telemetry (events, metrics, logs, spans); config objects such as dashboards, alert policies, and workloads carry no modified-date and are diffed on each run. Alert workflows can push outbound webhook notifications for near-real-time alerting. No CDC feed.
Capabilities
read · write · webhooks
Rate limits
NerdGraph allows 25 concurrent requests per user and returns HTTP 429 when exceeded; NRQL run via APIs is capped at 3,000 queries per account per minute with a 5-second default timeout and about 5,000 data points per response. The Event API accepts 1MB per POST and 100,000 POSTs per minute per account.

Notion

Integration surface
REST API (api.notion.com/v1)
Authentication
OAuth 2.0 for public integrations, or an internal integration secret (bearer token); every request must send a Notion-Version header
Change detection
Workspace webhooks (page.created, page.content_updated, data_source.schema_updated, comment.created; HMAC-SHA256 signed) plus polling on each page's last_edited_time
Capabilities
read · write · webhooks
Rate limits
Average of ~3 requests/second per integration with some bursts; 429 with a Retry-After header when exceeded. Payloads capped at 500 KB and 1000 block elements.
How it works

How to connect Newrelic to Notion — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Newrelic and Notion with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Newrelic connected
    Notion connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Newrelic and Notion objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Newrelic ⇄ Notion
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Newrelic Notion
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Newrelic and Notion integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 390 integrations available for Newrelic and Notion.

Popular · 7 of 390
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.