Two-way sync
Changes in Asana or Newrelic instantly reflect in both systems. No stale data, no manual imports.
Keep Asana and Newrelic in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Asana 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 Tasks, Projects, Sections, Custom fields in Asana with Alert Policies & Conditions, NRQL Query Results, Entities, Workloads 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.
Records created or changed in Asana publish to the queue or topic in Newrelic as they happen, so downstream services react to real events rather than polling for them.
People and accounts in Asana stay matched to the users in Newrelic, so access, provisioning, and org changes propagate instead of being keyed in twice.
Open items, throughput, and error counts from Asana replicate into Newrelic, so the operational view reflects what is actually happening in the business.
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.
| Asana objects | Newrelic objects | How this pairing syncs | |
|---|---|---|---|
| Portfolios Collections of Projects for program-level rollup; read for cross-project status and progress reporting (Business and Enterprise). | 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. | Portfolios is specific to Asana and NRQL Query Results to Newrelic — each maps to any object or custom field on the other side. | |
| Tags Labels applied across Tasks; synced as a many-to-many attribute for filtering and categorization. | 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. | Tags is specific to Asana and Entities to Newrelic — each maps to any object or custom field on the other side. | |
| Teams / Workspaces Organizational containers that hold projects and members; used to scope which projects a given sync covers. | 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. | Teams / Workspaces is specific to Asana and Workloads to Newrelic — each maps to any object or custom field on the other side. | |
| Tasks The primary unit of work and main record; created, updated, completed, and deleted via REST and synced two-way. Subtasks are Tasks with a parent reference. | 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. | Tasks is specific to Asana and Synthetics Monitors to Newrelic — each maps to any object or custom field on the other side. | |
| Projects Collections of Tasks with a layout (list, board, timeline, calendar); each project maps to a synced table scope and its custom fields define the mapping. | 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. | Projects is specific to Asana and Custom Events to Newrelic — each maps to any object or custom field on the other side. | |
| Sections Ordered groupings of Tasks within a project; synced as a grouping attribute or category field on the row. | 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. | Sections is specific to Asana and Change Tracking (Deployments) to Newrelic — each maps to any object or custom field on the other side. |
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.
DetectionAsana notifies Stacksync of record changes through webhook events. Resource-scoped webhooks (established with an X-Hook-Secret handshake) POST events on create, change, and delete.
DeliveryEach detected change is written to Newrelic through its API, with automatic retries and rate-limit backoff.
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 Asana through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Asana–Newrelic connection.
Changes in Asana or Newrelic instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Asana or Newrelic data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Asana or Newrelic record.
Track your Asana ⇄ Newrelic sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Asana and Newrelic.
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.
Authenticate Asana and Newrelic with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Asana and Newrelic 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Asana and Newrelic: authenticate both systems, choose the objects to sync (such as Asana's Portfolios and Tags), map fields visually, and changes propagate both ways in milliseconds — no code required.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Asana and Newrelic records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Asana and Newrelic connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Asana–Newrelic integration in-house.
Yes — Stacksync ships production-grade connectors for both Asana and Newrelic. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Asana: Resource-scoped webhooks (established with an X-Hook-Secret handshake) POST events on create, change, and delete; the sync-token Events API returns incremental changes on a task or project when webhooks are not used. On Newrelic: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Asana side: Tasks, Projects, Sections, Custom fields, plus custom fields where Asana exposes them. On the Newrelic side: Alert Policies & Conditions, NRQL Query Results, Entities, Workloads. Stacksync auto-detects both schemas and converts types between the two systems.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 390 integrations available for Asana and Newrelic.