Connect Salesforce and New Relic

Connecting Salesforce and New Relic for a company that uses both could enable the transfer of relevant customer or incident data between the systems. This could support improved visibility into application performance issues in relation to customer records or support cases, allowing teams to coordinate responses based on more complete and timely information from both platforms.

You can build this integration on the System2System platform. We design the connection between Salesforce and New Relic around the way you work — not as an off-the-shelf connector, but to fit your systems.

Contact us

Why connect Salesforce and New Relic?

A company that runs both Salesforce and New Relic could benefit from connecting these systems to enable more efficient data exchange. Without a connection between the two, teams might have to duplicate data entry, which increases the risk of errors and wastes time. Information about customers, incidents, or performance issues could become inconsistent between systems, leading to situations where decisions are made based on outdated or incomplete data. This can affect customer service, reporting accuracy, and the ability to respond quickly to operational issues. If a connection were established, it could allow for the exchange of data such as customer records, incident or case updates, and performance metrics. For example, alerts or incidents tracked in New Relic could be made available in Salesforce to provide customer-facing teams with up-to-date technical information. Conversely, customer or account details from Salesforce could be shared with New Relic to help technical teams prioritize issues based on business impact. The specific types of data exchanged would depend on the business needs and the capabilities of both systems. Ultimately, what can actually be exchanged depends on what each system exposes through its API, and is determined per situation.

How System2System builds an integration

Connectors

We connect to each system through the interface it offers — an API, a database, a file exchange or a webhook — and handle authentication, rate limits and retries.

Mapping

Fields rarely line up one to one. We map and transform the data so both systems receive it in the shape they expect.

Workflow

We define what triggers an exchange, in which direction data flows and which system takes precedence when the two disagree.

Monitoring

Every exchange is logged. Failures are flagged and can be replayed, so nothing disappears without anyone noticing.

What can actually be exchanged?

That depends on what Salesforce and New Relic make available through their APIs, on the licences and modules in use, and on the version each system runs. Which records are synchronised, in which direction and how often, is something we determine together before any work starts.

We are happy to look at your specific situation and tell you what is feasible — including when the answer is that it is not.