Skip to content
Developer tools ⇄ Data warehouse

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

Keep Newrelic and Tinybird 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 Tinybird

Close the gap between analytics and operations: Tinybird holds the record while Newrelic runs the day-to-day work, and Stacksync keeps the two in step in real time, in both directions.

Tinybird is the central store where teams keep Data Sources, Pipes, API Endpoints, Materialized Views for reporting and analysis; Newrelic runs the operational side of engineering work — tracking issues, moving messages and events, watching systems, and managing users and access. The two overlap wherever the same operational data matters to both: the NRQL Query Results, Entities, Workloads, Synthetics Monitors produced in Newrelic are exactly what analysts want to measure in Tinybird, and the curated rows in Tinybird are what should drive the next action in Newrelic. When that overlap is bridged by nightly ETL or hand-written scripts, dashboards lag a day behind reality and the tools that should react to warehouse signals never see them.

Stacksync syncs Data Sources, Pipes, API Endpoints, Materialized Views in Tinybird with NRQL Query Results, Entities, Workloads, Synthetics Monitors in Newrelic field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync matches records on a stable external key, keeps every copy consistent, and resolves conflicts by rules you set — so analytics and operations work from the same current data instead of two drifting copies.

Common use cases

  • 01 Stream CRM activity such as deals and tickets into Tinybird Data Sources to power customer-facing dashboards.
  • 02 Sync order events from an ERP into Tinybird to serve low-latency operational analytics endpoints.
  • 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

No batch jobs to babysit

New and changed records move field by field the moment they change, replacing scheduled ETL and one-off scripts that fail quietly and leave stale rows behind.

One shared record, kept consistent

Where both systems track the same entity, a change on either side propagates to the other, ending the manual reconciliation between the operational copy and the warehouse copy.

Keep user and access records aligned

Where Newrelic manages users, directory, or access data, those records stay current in Tinybird — and can be provisioned back from it — so ownership and permissions match across both.

What you can sync between Newrelic and Tinybird

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 Tinybird objects How this pairing syncs
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. API Endpoints Published Pipe outputs exposed as parameterized HTTP queries; the main read surface. Dashboards is specific to Newrelic and API Endpoints to Tinybird — 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. Materialized Views Pipes materialized into new Data Sources for pre-aggregation at ingest time. Alert Policies & Conditions is specific to Newrelic and Materialized Views to Tinybird — 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. Workspaces Project boundary that scopes Data Sources, Pipes, and tokens for a sync. NRQL Query Results is specific to Newrelic and Workspaces to Tinybird — each maps to any object or custom field on the other side.
Entities The entity catalog of APM applications, hosts, services, and monitors searched via NerdGraph entitySearch; read for inventory, with tags added or replaced through taggingAddTagsToEntity so ownership and environment metadata stay in sync. Tokens Scoped credentials that control read and append rights per resource. Entities is specific to Newrelic and Tokens to Tinybird — each maps to any object or custom field on the other side.
Workloads Workload groupings of related entities via NerdGraph workloadCreate/workloadUpdate/workloadDelete with full CRUD; read for status rollups or provisioned from a service catalog to keep team-level views current. Data Sources ClickHouse-backed tables that receive ingested rows; the write target for syncs into Tinybird. Workloads is specific to Newrelic and Data Sources to Tinybird — each maps to any object or custom field on the other side.
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. Pipes Chained SQL nodes that transform Data Sources into query-ready results. Synthetics Monitors is specific to Newrelic and Pipes to Tinybird — each maps to any object or custom field on the other side.

How changes propagate between Newrelic and Tinybird

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 Tinybird 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 applied to Tinybird as a row-level write, with types converted between the two schemas.

Tinybird Newrelic Interval-based propagation

DetectionStacksync polls Tinybird for changes on an incremental schedule, reading only records changed since the previous pass. Append-oriented ingestion.

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.
  • Tinybird: Subject to the platform's ingestion and query rate limits; batch appends where possible.
What ships with Newrelic ⇄ Tinybird

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Newrelic or Tinybird 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 Tinybird record.

Observability

Monitoring

Track your Newrelic ⇄ Tinybird 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 Tinybird.

How the Newrelic and Tinybird 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.

Tinybird

Integration surface
REST API (Events API for ingestion, published query endpoints) with a ClickHouse SQL dialect
Authentication
Scoped auth tokens
Change detection
Append-oriented ingestion; reads are pulled by querying published endpoints, no outbound CDC
Capabilities
read · write
Rate limits
Subject to the platform's ingestion and query rate limits; batch appends where possible.
How it works

How to connect Newrelic to Tinybird — 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 Tinybird 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
    Tinybird connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Newrelic and Tinybird 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 ⇄ Tinybird
    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 Tinybird
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Newrelic and Tinybird 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 310 integrations available for Newrelic and Tinybird.

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

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