---
title: "New Relic connector: setup and compatibility | Stacksync"
description: "New Relic integration guide: plan Custom Events, record identity, setup, and compatibility."
canonical: https://www.stacksync.com/connectors/newrelic
last_modified: 2026-09-15
---

Developer tools · Two-way sync platform

# New Relic integration.

> For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md

Connect your New Relic workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Custom Events.

Set this up from Claude or ChatGPT

- Review your systems with an integration engineer
- Get a scoped implementation and validation plan

Technical workflow review

## Bring one workflow. Leave with a technical plan.

An engineer will assess the required records, access method, and read/write operations before recommending an implementation.

- **Dashboards**
- **Alert Policies & Conditions**
- **NRQL Query Results**

**What to bring** Bring a sample record, the other system, and the change your team needs to automate.

[Talk through your workflow](https://www.stacksync.com/book-a-demo?connector=newrelic)

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

- Gladia Case study
- IDEXX
- MedPro Migrated from MuleSoft
- Eko Case study
- Ubicloud
- Vimeo
- Codility Migrated from Celigo
- ACERTUS Migrated from Heroku Connect
- Syringa Migrated from Matillion
- Truora
- Streaam Case study
- SEAL SQ
- Rinsed Migrated from Fivetran
- IA Capital Group Case study
- Meter
- Golden Pear Funding Migrated from Celigo

Record types

## New Relic records to discuss.

These New Relic record examples help scope a technical review. They are not a list of verified Stacksync operations.

Dashboards

Identify this record type and the operation you need to review with Stacksync.

Alert Policies & Conditions

Identify this record type and the operation you need to review with Stacksync.

NRQL Query Results

Identify this record type and the operation you need to review with Stacksync.

### See 3 more record examples

Entities

Identify this record type and the operation you need to review with Stacksync.

Workloads

Identify this record type and the operation you need to review with Stacksync.

Synthetics Monitors

Identify this record type and the operation you need to review with Stacksync.

Connection setup

## New Relic connection requirements.

Review New Relic access and the operations your workflow needs with Stacksync. The vendor API reference below can help your administrator prepare for that discussion.

### Prepare access and scope for the engineering review

- Identify the New Relic account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for New Relic, including read/write support, authentication, and initial-load limits.

Integration design

## Match records and fields for your New Relic integration.

Define repository/project context, issue or change identity, and relationships to operational records. Moving metadata does not authorize a code change, build, or deployment.

Use these design questions to prepare a representative record and the business rules your integration must preserve.

### Explore record matching and field-mapping checks

New Relic **Source record ID** Keep the account and record type

Record matching **Source ID ↔ destination ID** Link the same record across systems

Selected destination **Destination record ID** Preserve its local key and rules

*Conceptual identity model. Keep source and destination IDs linked so an update reaches the right record. Confirm the supported sync direction separately.*

Match the same record in both systems

Keep the source event ID, source system, occurrence time, and ingestion time. Use an explicit duplicate-detection key.

Load related records in the right order

Resolve the related customer, user, or transaction identity without assuming the event ID is the entity ID.

### Mapping checks by record type

#### Custom Events

Confirm object support with Stacksync

Identity

Keep the source event ID, source system, occurrence time, and ingestion time. Use an explicit duplicate-detection key.

Fields to consider

Source event ID · Event type · Occurred-at time · Related record ID · Payload version

Related records to resolve first

Resolve the related customer, user, or transaction identity without assuming the event ID is the entity ID.

Test before going live

Deliver the same event twice, then an older event after a newer one; verify duplicate and ordering behavior.

[Download the field-mapping workbook (CSV)](https://www.stacksync.com/downloads/sync-planning/field-mapping-workbook.csv) to capture the actual API fields, matching keys, owners, and test results. Use it as you build with your team or a Stacksync engineer.

Setup and validation

## Validate the New Relic integration in four steps.

A record update reaches the intended repository or project, and repeated event delivery does not create duplicate work or execute a second action.

### View the four setup tests and expected results

1. ### Verify New Relic credentials and resource scope

   After confirming an implementation path, validate the selected access method with the intended account, region or workspace, and resource scope. Record the credential owner and renewal procedure, then demonstrate access to one selected object.

   **Expected result:** The selected resource is accessible through the approved credential, with the renewal and revocation procedure assigned to an owner.
2. ### Test record matching for Custom Events

   Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Deliver the same event twice, then an older event after a newer one; verify duplicate and ordering behavior.

   **Expected result:** A record update reaches the intended repository or project, and repeated event delivery does not create duplicate work or execute a second action.
3. ### Test the operation your workflow needs

   Review one New Relic record with a Stacksync engineer. Confirm how it should reach the other system, how often it must update, and whether your workflow needs reads, creates, or updates. Test those operations before expanding the integration.

   **Expected result:** The selected operation is confirmed, addresses the intended record, and exposes rejected values for repair.
4. ### Test recovery and name the support owner

   For the confirmed implementation, interrupt a non-production transfer and restore access. Establish whether recovery uses the current source state or a stored historical event, and verify that repeated delivery preserves record identity.

   **Expected result:** The records have the expected current values, repeated delivery creates no duplicate business record, and your team knows who handles unresolved errors.

[Use the production-readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) to record test results, assign support owners, and agree on when to go live.

Troubleshooting

## Troubleshoot your New Relic integration.

### Diagnose record matching, delayed changes, and rejected operations

A New Relic record appears under the wrong destination record

Keep the source event ID, source system, occurrence time, and ingestion time. Use an explicit duplicate-detection key. Resolve the related customer, user, or transaction identity without assuming the event ID is the entity ID. Repair the ID relationship before repeating the operation.

The first load looks correct but later results differ

Confirm the selected New Relic implementation’s change-detection method for Custom Events. Compare later changes with the original source rather than using a successful initial copy as evidence of ongoing capture.

One operation succeeds while another is rejected

Check the specific New Relic object, field permissions, required references, and allowed operation. A successful read does not establish that a create, update, deletion, or business action is available.

[Review retry, replay, and recovery behavior](https://www.stacksync.com/blog/two-way-sync-error-handling-retries-replay) before repeating an operation that may already have succeeded.

[Review your New Relic workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=newrelic)

## New Relic integration guides

- [checklist Two-Way Sync Production-Readiness Checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist)
- [guide How Digital Innovation Is Reshaping Modern Business Operations](https://www.stacksync.com/blog/how-digital-innovation-is-reshaping-modern-business-operations)

FAQ

## New Relic connector FAQ

### How should I plan an integration with New Relic?

Define repository/project context, issue or change identity, and relationships to operational records. Moving metadata does not authorize a code change, build, or deployment. Confirm the connection and read/write operations with Stacksync. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding.

### Can the New Relic connector write changes back?

Write-back support is not established for this connection. Review the New Relic records and fields you need with a Stacksync engineer, then test the required operation with a representative record.

### Which identifiers should I preserve for New Relic data?

Keep the source event ID, source system, occurrence time, and ingestion time. Use an explicit duplicate-detection key.

### Which related records should I load first for New Relic?

Resolve the related customer, user, or transaction identity without assuming the event ID is the entity ID.

### How do I validate New Relic changes after the initial load?

Deliver the same event twice, then an older event after a newer one; verify duplicate and ordering behavior. A record update reaches the intended repository or project, and repeated event delivery does not create duplicate work or execute a second action.

### What will we cover in a New Relic integration demo?

Start with one workflow and a sample record from Custom Events. We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document.

AI assistant

## Set up New Relic from Claude or ChatGPT

Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste.

### 1. Add the Stacksync MCP server

Server URL

`https://mcp.stacksync.com/mcp`

#### In Claude

1. Open Customize → Connectors, select + Add, then Add custom connector.
2. Name it Stacksync and enter https://mcp.stacksync.com/mcp.
3. Select Connect, sign in to Stacksync and choose your workspace.

#### In ChatGPT

1. Open Settings → Apps → Advanced settings and turn on Developer mode.
2. Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth.
3. Sign in to Stacksync, then enable Stacksync from the tools menu in a chat.

##### Set up Codex or Claude Code

#### Codex

```
codex mcp add stacksync --url https://mcp.stacksync.com/mcp
codex mcp login stacksync
```

Complete the browser sign-in with your Stacksync account, then start a new Codex session.

#### Claude Code

```
claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp
```

Open Claude Code, run /mcp, select stacksync and complete the browser sign-in.

Then ask: “List my Stacksync workspaces.” Sign-in connects your assistant; it does not create a sync yet.

Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and other assistants: [setup steps in the docs](https://docs.stacksync.com/mcp).

### 2. Ask your assistant

> Create a sync between my New Relic and another app or database.

#### Also from the same chat

You can also ask for workflows and AI agents (Genies) that use New Relic. The assistant checks what each app supports, for example:

- “Build a workflow that messages our team in Slack when a New Relic record changes.”
- “Create a Genie that answers questions about our New Relic data in Slack.”

#### What happens next

- Signs you in with your Stacksync login (OAuth). No API key is pasted into the chat.
- Gives you a secure sign-in link for each app it connects; you open it and sign in to that app.
- Builds the sync with your permissions in Stacksync, nothing more. Turn on Ask before every change in the MCP settings to approve each change first.

New to Stacksync? [Create an account](https://app.stacksync.com/signup) first, then sign in from your assistant.

## Explore New Relic connections

Choose the other system in your workflow. Each guide explains the connection options, available operations, field mapping, and setup checks for that pair.

### Start with these integration guides

- [New Relic and Slack](https://www.stacksync.com/integrations/newrelic-and-slack)
- [New Relic and Rockset](https://www.stacksync.com/integrations/newrelic-and-rockset)
- [New Relic and Oracle DB](https://www.stacksync.com/integrations/newrelic-and-oracle-db)
- [BigQuery and New Relic](https://www.stacksync.com/integrations/bigquery-and-newrelic)
- [Atlassian and New Relic](https://www.stacksync.com/integrations/atlassian-and-newrelic)
- [New Relic and Pendo](https://www.stacksync.com/integrations/newrelic-and-pendo)
- [New Relic and Splunk](https://www.stacksync.com/integrations/newrelic-and-splunk)
- [New Relic and SQL Server](https://www.stacksync.com/integrations/newrelic-and-sql-server)

### Database · 50

- [New Relic and Airtable](https://www.stacksync.com/integrations/airtable-and-newrelic)
- [New Relic and Amazon Aurora](https://www.stacksync.com/integrations/amazon-aurora-and-newrelic)
- [New Relic and Amazon DynamoDB](https://www.stacksync.com/integrations/dynamo-db-and-newrelic)
- [New Relic and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-newrelic)
- [New Relic and Amazon Lightsail](https://www.stacksync.com/integrations/amazon-lightsail-and-newrelic)
- [New Relic and Amazon RDS](https://www.stacksync.com/integrations/amazon-rds-and-newrelic)
- [New Relic and Apache Cassandra](https://www.stacksync.com/integrations/apache-cassandra-and-newrelic)
- [New Relic and AWS Aurora MySQL](https://www.stacksync.com/integrations/aws-aurora-mysql-and-newrelic)
- [New Relic and AWS Aurora PostgreSQL](https://www.stacksync.com/integrations/aws-aurora-postgresql-and-newrelic)
- [New Relic and Azure Cosmos DB](https://www.stacksync.com/integrations/azure-cosmos-db-and-newrelic)
- [New Relic and Azure SQL Database](https://www.stacksync.com/integrations/azure-sql-database-and-newrelic)
- [New Relic and Citus](https://www.stacksync.com/integrations/citus-and-newrelic)
- [New Relic and CockroachDB](https://www.stacksync.com/integrations/cockroachdb-and-newrelic)
- [New Relic and Couchbase](https://www.stacksync.com/integrations/couchbase-and-newrelic)
- [New Relic and DuckDB](https://www.stacksync.com/integrations/duckdb-and-newrelic)
- [New Relic and Elasticsearch](https://www.stacksync.com/integrations/elasticsearch-and-newrelic)
- [New Relic and Firebase](https://www.stacksync.com/integrations/firebase-and-newrelic)
- [New Relic and Google AlloyDB](https://www.stacksync.com/integrations/google-alloydb-and-newrelic)
- [New Relic and Google Cloud Spanner](https://www.stacksync.com/integrations/google-cloud-spanner-and-newrelic)
- [New Relic and Google Cloud SQL](https://www.stacksync.com/integrations/google-cloud-sql-and-newrelic)
- [New Relic and IBM AS/400](https://www.stacksync.com/integrations/ibm-as400-and-newrelic)
- [New Relic and IBM Db2](https://www.stacksync.com/integrations/ibm-db2-and-newrelic)
- [New Relic and IBM Informix](https://www.stacksync.com/integrations/ibm-informix-and-newrelic)
- [New Relic and InfluxDB](https://www.stacksync.com/integrations/influxdb-and-newrelic)
- [New Relic and InterSystems IRIS](https://www.stacksync.com/integrations/intersystems-iris-and-newrelic)
- [New Relic and JDBC](https://www.stacksync.com/integrations/jdbc-and-newrelic)
- [New Relic and MariaDB](https://www.stacksync.com/integrations/mariadb-and-newrelic)
- [New Relic and MarkLogic](https://www.stacksync.com/integrations/marklogic-and-newrelic)
- [New Relic and MongoDB](https://www.stacksync.com/integrations/mongodb-and-newrelic)
- [New Relic and MySQL](https://www.stacksync.com/integrations/mysql-and-newrelic)
- [New Relic and Neo4j](https://www.stacksync.com/integrations/neo4j-and-newrelic)
- [New Relic and OCI Database (Oracle Cloud)](https://www.stacksync.com/integrations/newrelic-and-oci-database)
- [New Relic and OpenSearch](https://www.stacksync.com/integrations/newrelic-and-opensearch)
- [New Relic and Oracle DB](https://www.stacksync.com/integrations/newrelic-and-oracle-db)
- [New Relic and Postgres Heroku](https://www.stacksync.com/integrations/newrelic-and-postgres-heroku)
- [New Relic and PostgreSQL](https://www.stacksync.com/integrations/newrelic-and-postgresql)
- [New Relic and RavenDB](https://www.stacksync.com/integrations/newrelic-and-ravendb)
- [New Relic and Redis Enterprise](https://www.stacksync.com/integrations/newrelic-and-redis-enterprise)
- [New Relic and Reltio](https://www.stacksync.com/integrations/newrelic-and-reltio)
- [New Relic and Render Postgres](https://www.stacksync.com/integrations/newrelic-and-render-postgres)
- [New Relic and SAP ASE (Sybase)](https://www.stacksync.com/integrations/newrelic-and-sap-ase-sybase)
- [New Relic and SAP HANA](https://www.stacksync.com/integrations/newrelic-and-sap-hana)
- [New Relic and Scaleway Postgres](https://www.stacksync.com/integrations/newrelic-and-scaleway-postgres)
- [New Relic and SingleStore](https://www.stacksync.com/integrations/newrelic-and-singlestore)
- [New Relic and SQL Server](https://www.stacksync.com/integrations/newrelic-and-sql-server)
- [New Relic and Supabase](https://www.stacksync.com/integrations/newrelic-and-supabase)
- [New Relic and TiDB](https://www.stacksync.com/integrations/newrelic-and-tidb)
- [New Relic and TimescaleDB](https://www.stacksync.com/integrations/newrelic-and-timescaledb)
- [New Relic and VoltDB](https://www.stacksync.com/integrations/newrelic-and-voltdb)
- [New Relic and YugabyteDB](https://www.stacksync.com/integrations/newrelic-and-yugabytedb)

### Data warehouse · 28

- [New Relic and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-newrelic)
- [New Relic and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-newrelic)
- [New Relic and Apache Doris](https://www.stacksync.com/integrations/apache-doris-and-newrelic)
- [New Relic and Apache Druid](https://www.stacksync.com/integrations/apache-druid-and-newrelic)
- [New Relic and Apache Hive](https://www.stacksync.com/integrations/apache-hive-and-newrelic)
- [New Relic and Apache Impala](https://www.stacksync.com/integrations/apache-impala-and-newrelic)
- [New Relic and Apache Pinot](https://www.stacksync.com/integrations/apache-pinot-and-newrelic)
- [New Relic and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-newrelic)
- [New Relic and BigQuery](https://www.stacksync.com/integrations/bigquery-and-newrelic)
- [New Relic and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-newrelic)
- [New Relic and Cloudera Data Platform](https://www.stacksync.com/integrations/cloudera-data-platform-and-newrelic)
- [New Relic and Databricks](https://www.stacksync.com/integrations/databricks-and-newrelic)
- [New Relic and Dremio](https://www.stacksync.com/integrations/dremio-and-newrelic)
- [New Relic and Exasol](https://www.stacksync.com/integrations/exasol-and-newrelic)
- [New Relic and Firebolt](https://www.stacksync.com/integrations/firebolt-and-newrelic)
- [New Relic and Google Cloud Platform](https://www.stacksync.com/integrations/google-cloud-platform-and-newrelic)
- [New Relic and Greenplum](https://www.stacksync.com/integrations/greenplum-and-newrelic)
- [New Relic and IBM Netezza](https://www.stacksync.com/integrations/ibm-netezza-and-newrelic)
- [New Relic and Materialize](https://www.stacksync.com/integrations/materialize-and-newrelic)
- [New Relic and MotherDuck](https://www.stacksync.com/integrations/motherduck-and-newrelic)
- [New Relic and Rockset](https://www.stacksync.com/integrations/newrelic-and-rockset)
- [New Relic and Snowflake](https://www.stacksync.com/integrations/newrelic-and-snowflake)
- [New Relic and Starburst Enterprise](https://www.stacksync.com/integrations/newrelic-and-starburst-enterprise)
- [New Relic and StarRocks](https://www.stacksync.com/integrations/newrelic-and-starrocks)
- [New Relic and Teradata Vantage](https://www.stacksync.com/integrations/newrelic-and-teradata-vantage)
- [New Relic and Tinybird](https://www.stacksync.com/integrations/newrelic-and-tinybird)
- [New Relic and Vertica](https://www.stacksync.com/integrations/newrelic-and-vertica)
- [New Relic and Yellowbrick](https://www.stacksync.com/integrations/newrelic-and-yellowbrick)

### Business productivity · 37

- [New Relic and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-newrelic)
- [New Relic and Agiloft](https://www.stacksync.com/integrations/agiloft-and-newrelic)
- [New Relic and Asana](https://www.stacksync.com/integrations/asana-and-newrelic)
- [New Relic and Atlassian](https://www.stacksync.com/integrations/atlassian-and-newrelic)
- [New Relic and Braze](https://www.stacksync.com/integrations/braze-and-newrelic)
- [New Relic and Campfire](https://www.stacksync.com/integrations/campfire-and-newrelic)
- [New Relic and ConnectWise](https://www.stacksync.com/integrations/connectwise-and-newrelic)
- [New Relic and Customer.io](https://www.stacksync.com/integrations/customer-io-and-newrelic)
- [New Relic and Docusign](https://www.stacksync.com/integrations/docusign-and-newrelic)
- [New Relic and eClinicalWorks](https://www.stacksync.com/integrations/eclinicalworks-and-newrelic)
- [New Relic and Front](https://www.stacksync.com/integrations/front-and-newrelic)
- [New Relic and FullEnrich](https://www.stacksync.com/integrations/full-enrich-and-newrelic)
- [New Relic and Gainsight](https://www.stacksync.com/integrations/gainsight-and-newrelic)
- [New Relic and Gatekeeper](https://www.stacksync.com/integrations/gatekeeper-and-newrelic)
- [New Relic and GitHub](https://www.stacksync.com/integrations/github-and-newrelic)
- [New Relic and Google Sheets](https://www.stacksync.com/integrations/google-sheets-and-newrelic)
- [New Relic and Ironclad](https://www.stacksync.com/integrations/ironclad-and-newrelic)
- [New Relic and Klaviyo](https://www.stacksync.com/integrations/klaviyo-and-newrelic)
- [New Relic and Lemlist](https://www.stacksync.com/integrations/lemlist-and-newrelic)
- [New Relic and Microsoft 365](https://www.stacksync.com/integrations/microsoft-365-and-newrelic)
- [New Relic and Microsoft Dynamics 365](https://www.stacksync.com/integrations/microsoft-dynamics-365-and-newrelic)
- [New Relic and Microsoft Teams](https://www.stacksync.com/integrations/microsoft-teams-and-newrelic)
- [New Relic and Monday](https://www.stacksync.com/integrations/monday-and-newrelic)
- [New Relic and NextGen Healthcare](https://www.stacksync.com/integrations/newrelic-and-nextgen-healthcare)
- [New Relic and Notion](https://www.stacksync.com/integrations/newrelic-and-notion)
- [New Relic and Orderful](https://www.stacksync.com/integrations/newrelic-and-orderful)
- [New Relic and Quip](https://www.stacksync.com/integrations/newrelic-and-quip)
- [New Relic and Resend](https://www.stacksync.com/integrations/newrelic-and-resend)
- [New Relic and SendGrid](https://www.stacksync.com/integrations/newrelic-and-sendgrid)
- [New Relic and ServiceMax](https://www.stacksync.com/integrations/newrelic-and-servicemax)
- [New Relic and ServiceNow](https://www.stacksync.com/integrations/newrelic-and-servicenow)
- [New Relic and Slack](https://www.stacksync.com/integrations/newrelic-and-slack)
- [New Relic and Smartsheet](https://www.stacksync.com/integrations/newrelic-and-smartsheet)
- [New Relic and SysAid](https://www.stacksync.com/integrations/newrelic-and-sysaid)
- [New Relic and Twilio](https://www.stacksync.com/integrations/newrelic-and-twilio)
- [New Relic and Wrike](https://www.stacksync.com/integrations/newrelic-and-wrike)
- [New Relic and Zendesk](https://www.stacksync.com/integrations/newrelic-and-zendesk)

### Analytics · 3

- [New Relic and Pendo](https://www.stacksync.com/integrations/newrelic-and-pendo)
- [New Relic and Splunk](https://www.stacksync.com/integrations/newrelic-and-splunk)
- [New Relic and Treasure Data](https://www.stacksync.com/integrations/newrelic-and-treasuredata)

### Communications · 5

- [New Relic and Aircall](https://www.stacksync.com/integrations/aircall-and-newrelic)
- [New Relic and Amazon SES](https://www.stacksync.com/integrations/amazon-ses-and-newrelic)
- [New Relic and Infobip](https://www.stacksync.com/integrations/infobip-and-newrelic)
- [New Relic and RingCentral](https://www.stacksync.com/integrations/newrelic-and-ringcentral)
- [New Relic and Zoom](https://www.stacksync.com/integrations/newrelic-and-zoom)

### Security and identity · 6

- [New Relic and Active Directory](https://www.stacksync.com/integrations/active-directory-and-newrelic)
- [New Relic and Auth0](https://www.stacksync.com/integrations/auth0-and-newrelic)
- [New Relic and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-newrelic)
- [New Relic and JumpCloud](https://www.stacksync.com/integrations/jumpcloud-and-newrelic)
- [New Relic and Okta](https://www.stacksync.com/integrations/newrelic-and-okta)
- [New Relic and OneLogin](https://www.stacksync.com/integrations/newrelic-and-onelogin)

### Storage · 4

- [New Relic and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-newrelic)
- [New Relic and Box](https://www.stacksync.com/integrations/box-and-newrelic)
- [New Relic and Egnyte](https://www.stacksync.com/integrations/egnyte-and-newrelic)
- [New Relic and SharePoint](https://www.stacksync.com/integrations/newrelic-and-sharepoint)

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.

[Learn more about security](https://www.stacksync.com/security)

|  |  |
| --- | --- |
|  | 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:

[OAuth 2](https://www.stacksync.com/security) [SSH Tunnelling](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ssh-tunneling) [SSL certificates](https://docs.stacksync.com/two-way-sync/connectors/postgres/authorize-postgres/amazon-rds/ensuring-secure-rds-connections-with-ssl-certificate) [IP Whitelisting](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ip-whitelisting) [VPN gateway](https://docs.stacksync.com/two-way-sync/legal/service-consumption-tables#:~:text=%E2%9C%93-,VPN%20gateway,-%2D) [VPC peering](https://www.stacksync.com/security) and more

## Connect the systems your business runs on. Build your next workflow with Stacksync.

[Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)
