ServiceNow
Salesforce integration.
How Salesforce and MuleSoft document connecting ServiceNow incidents to Service Cloud cases, and which option fits which team.
Request an integration map →Download the spec sheet →A ServiceNow Salesforce integration links ServiceNow, where IT logs incidents, with Salesforce Service Cloud, where support works cases. Salesforce's Trailhead shows a MuleSoft Composer flow that creates or updates a case from each new or updated incident and writes the case ID back. MuleSoft also publishes a ServiceNow Connector for larger builds.
[ How it works ]
Why connect ServiceNow and Salesforce?
Trailhead's example describes IT logging incidents in ServiceNow and emailing support, who then create cases by hand and send the case ID back. It calls that manual sync time-consuming and highly error-prone, and replaces it with a near real-time flow.
[ The connector ]
ServiceNow for IT. Salesforce for customers.
Techila Global Services is a Salesforce Summit partner. We design how incidents and cases relate, choose between MuleSoft Composer and a full MuleSoft build, and set up the fields, matching and error handling on both sides.
After launch we test the flows with realistic volumes and support them.
What moves between ServiceNow and Salesforce?
Trailhead's MuleSoft Composer module walks through one documented pattern. It aims for near real-time integration across ServiceNow, Salesforce and Slack.
- The flow finds any new or updated incident in ServiceNow.
- It checks Salesforce for a matching case. If there is none, it creates one with the incident details; if there is one, it updates it.
- For new cases, it writes the Salesforce case ID back to the ServiceNow incident.
- It posts the new or updated case to a Slack channel.
What moves between ServiceNow and Salesforce?
- Incidents to new or updated cases (from ServiceNow to Salesforce)
- Salesforce case ID to the incident (from Salesforce to ServiceNow)
Each side needs a custom field for the other's ID: Trailhead adds a Salesforce Case ID text field to the ServiceNow Incidents form and a ServiceNow incident ID field to the Salesforce Case object.
Which ServiceNow Salesforce integration option should you use?
| Option | What it covers | Limits |
|---|---|---|
| MuleSoft Composer flow | Incidents to cases and case IDs back, plus a Slack notice, as in Trailhead's example | Needs MuleSoft Composer and the MuleSoft Composer User permission set; not available in a Trailhead Playground |
| MuleSoft ServiceNow Connector | Connects Mule apps to ServiceNow, including custom tables and installed plugins | A MuleSoft build; Basic or OAuth 2.0 Authorization Code authentication |
| MuleSoft Accelerator for Salesforce Clouds | Prebuilt integration assets for bringing order, ServiceNow and Jira data into Service Cloud | Downloaded from Anypoint Exchange; still needs set-up for your data |
| Custom API work | Any objects or rules the options above do not cover | More code to build, test and maintain |
MuleSoft's documentation lists the ServiceNow Connector at version 7.0. Our MuleSoft services and Salesforce integration services cover each route; to choose one, book a discovery call. Working with Jira too? See Jira and Salesforce.
[ Architecture ]
How does a ServiceNow incident become a Salesforce case?
How data moves between the two systems.
ServiceNow
MuleSoft
Salesforce
[ What's included ]
What does Techila set up for ServiceNow and Salesforce?
What the integration work covers.
[ FAQ ]
Frequently asked questions.
What architects ask before commissioning a Techila integration.
Yes. Salesforce's Trailhead shows a MuleSoft Composer flow that turns ServiceNow incidents into Service Cloud cases, and MuleSoft publishes a ServiceNow Connector for Mule apps.
In Trailhead's example, incidents flow from ServiceNow to Salesforce cases, and the new case ID is written back to the incident. Anything more needs extra design.
A running ServiceNow instance with its URL and credentials, Salesforce sandbox and production credentials, a Slack workspace if you post notices, and the MuleSoft Composer User permission set.
MuleSoft's documentation lists Basic and OAuth 2.0 Authorization Code authentication. It notes that metadata does not work with OAuth 2.0 Authorization Code.
Yes. Trailhead recommends designing and testing flows with test systems and data before running them against production.
Sources
Last reviewed:
- Salesforce Trailhead, Service case management with MuleSoft Composer: examine an integration use case (read 10 November 2026)
- MuleSoft Documentation, ServiceNow Connector 7.0 (read 10 November 2026)
- MuleSoft, MuleSoft Accelerator for Salesforce Clouds (read 10 November 2026)
Let's now look at how to build
the next 10 years of
your customer platform.