Logos for ServiceNow and Salesforce, representing a post about setting up a ServiceNow-Salesforce integration.
ServiceNow-Salesforce Integration: Methods, What to Sync, and How to Set It Up in 2026
Logos for ServiceNow and Salesforce, representing a post about setting up a ServiceNow-Salesforce integration.

ServiceNow-Salesforce Integration: Methods, What to Sync, and How to Set It Up in 2026

ServiceNow and Salesforce serve different functions but overlap in workflows like ITSM and support ticket escalation. In most organizations, these tools aren’t integrated, meaning someone has to manually copy and paste updates back and forth between them or teams have to communicate exclusively in other channels.

What people actually sync between ServiceNow and Salesforce

ServiceNow fieldWhat it holdsSalesforce Case equivalentSync direction
NumberThe record’s ID, generated by ServiceNowCase NumberOne-way
Short description / DescriptionThe record’s title and multi-line detailsSubject / DescriptionTwo-way
StateThe record’s status (Open, Work in Progress, Closed and so on)StatusTwo-way
Priority, Impact and UrgencyChoice fields that rank the incidentPriority or custom picklistTwo-way
Category and SubcategoryChoice fields for classifying the recordCase type and Case reasonTwo-way
Assignment GroupThe team responsible for the recordCustom picklistTwo-way
Assigned toThe user working the recordCase OwnerTwo-way
CallerThe person the incident was reported forContactTwo-way
Opened by / Resolved byWho opened and who closed the recordCreated By / Custom person fieldTwo-way
CommentsPublic comments visible to external contactsCase commentsTwo-way
Work notesInternal notes, syncable to and from comments in the other toolInternal commentsTwo-way
AttachmentsFiles attached to the recordAttachmentsTwo-way
Time workedHow long the record has been openCustom number fieldTwo-way
Created / UpdatedTimestamps for creation and the latest changeCreated date / Last modified dateOne-way
Reference fieldsValues pulled from another tableAccount, Asset, and ProductOne-way from Salesforce
Sys IDThe record’s unique system identifierCustom text fieldOne-way from ServiceNow
Link to recordA link back to the ServiceNow recordCustom URL fieldOne-way from ServiceNow

ServiceNow-Salesforce integration methods compared

ServiceNow Integration Hub (Salesforce Spoke)iPaaS (e.g., Mulesoft, Workato)Two-way sync (e.g., Unito)
Who configures itA ServiceNow admin or developer, in Flow Designer. An integration developer or specialist. Ops, IT or RevOps teams, in a no-code interface. 
DirectionMostly ServiceNow acting on Salesforce. Reacting to Salesforce changes takes extra build work. One-way or two-way. Two-way means a flow in each direction, plus logic to stop update loops. Two-way, or one-way in either direction. 
Real-time or batchEither. Record-triggered flows run in real-time; scheduled flows run in batches. Either. Event triggers run in real-time; scheduled jobs run in batches. Real-time. 
Maintenance ownerThe ServiceNow platform team. The integration team that built the flows. The team that set up the flow, with Unito maintaining the connectors. 
Pricing modelAn Integration Hub subscription on top of ServiceNow, with usage counted in transactions. An annual platform contract, usually scaled by usage. A subscription scaled by items in sync. 

The 3 most common methods for setting up a ServiceNow-Salesforce integration

ServiceNow Integration Hub

ServiceNow integration hub is an additional module for the Now Platform that comes with nearly 200 connectors out-of-the-box, called Spokes. These spokes come in two forms: pre-built through templates, and customizable versions. It’s one of the most common ways to set up a Salesforce-ServiceNow integration.

The Salesforce spoke gives ServiceNow flows ready-made actions for Salesforce accounts, contacts, cases, leads, opportunities, orders, and users, so ServiceNow can create, look up, and update those records. Reacting to changes made in Salesforce takes extra setup, such as webhook-triggered subflows.

The hub also supports the development of custom spokes for users who want to create their own integration for ServiceNow’s API (the set of rules that allows software platforms to communicate with each other). To do this requires training, scripting knowledge, or 3rd party consulting services.

Best for: ServiceNow teams that already pay for Integration Hub and want ServiceNow flows to update Salesforce records.

iPaaS (e.g., MuleSoft, Workato)

An iPaaS (integration platform as a service) is a platform for building integrations across multiple tools at once. Platforms like MuleSoft and Workato come with pre-built connectors for both ServiceNow and Salesforce, which integration teams use to build flows that move data between them. Salesforce owns MuleSoft, so it’s a common first pick for organizations that already run much of their workflows through Salesforce.

An iPaaS flow can do almost anything allowed by a tool’s API. A flow can create a ServiceNow incident whenever a Salesforce case is escalated, then pull account details into the incident and transform values along the way. These platforms can connect cloud apps, databases, and on-premise systems, which often makes them the backbone of an organization’s integration strategy rather than just a solution for a single pair.

The flexibility of iPaaS comes with increased overhead. Each flow is built manually, and a two-way integration requires building one flow per direction and logic that stops updates from looping back and forth. Most organizations need a specific developer or specialist to build and maintain these flows. Pricing is typically an annual platform contract that scales with usage.

Best for: Organizations with a dedicated integration team that need to connect ServiceNow and Salesforce to a wider stack.

Two-way sync (e.g., Unito)

A two-way (or bidirectional) sync platform like Unito creates consistent relationships between ServiceNow records and Salesforce objects, keeping everything up to date as you work. Work items are created automatically to match the ones you manually open in your tools, and fields are updated constantly as you work.

Two-way sync platforms typically offer deep integrations that cover most standard and custom fields. They usually also support attachments, comments, and more. Some even maintain hierarchies and relational fields between ServiceNow and Salesforce. These deep integrations can support simple and complex workflows, from approvals to cross-department handoffs and true cross-functional collaboration.

Best for: Support, IT, and sales teams that each stay in their own tool and need a ServiceNow-Salesforce integration that keeps records current both ways, with no extra licenses.

Why sync ServiceNow and Salesforce?

While Salesforce does have some service management features, many organizations prefer a dedicated platform like ServiceNow. An integration is incredibly valuable if critical data needs to be shared between environments, but doing so manually would be time-consuming and risk data errors from manual entry. 

For example, let’s take a company that uses Salesforce as a CRM to manage purchases, sales, and revenue generation with opportunity pipelines. Salesforce also generates a wealth of data crucial to sales predictions and forecasting. Internally they use ServiceNow for IT support and ticketing, incident management, and technical support. 

When integrated, either tool can then become a collection point for data, allowing users to perform analytics in one place without the need to manually collect data from multiple other tools or sources. You could either consolidate everything with Now Platform Reporting or build comprehensive data visualizations in Tableau through Salesforce.

Integrating these tools opens the door to a streamlined analysis process and a quicker path to action.

How much data a ServiceNow-Salesforce integration can sync

Integrations between ServiceNow and Salesforce vary across a number of factors, including integration depth, which defines how much data they can sync from each tool.

Work item previews

Some integrations create a read-only link between ServiceNow and Salesforce. A Salesforce record, for example, might turn into a panel in a ServiceNow ticket, listing a few fields like due date, assignee, and status. You can’t interact with the Salesforce record or update it by working in ServiceNow. This kind of integration is perfect for getting visibility on work happening in other tools, but doesn’t enable cross-tool work without manually moving data over.

Standard fields

ServiceNow-Salesforce integrations usually support most, if not all, standard fields. “Standard” means a field is already built into the tool, with little to no customization involved. Due dates, assignees, and descriptions are examples of standard fields.

Most standard fields can be mapped automatically, though some might require a bit of extra input. Statuses that are slightly different across tools (e.g., “To Do” and “Backlog”) might need to be mapped manually.

Custom fields

Both ServiceNow and Salesforce have an extensive list of custom fields that allow users to tailor their workspace to specific workflows. Salesforce custom fields include address, checkbox, currency, date, email, lookup relationship, and picklist. ServiceNow custom fields include choice, reference, table, and date/time fields.

Not all integrations support custom fields. When researching an integration solution for ServiceNow and Salesforce, consider whether it can handle some, most, or all of the custom fields you need.

Comments and notes

Comments and notes allow teams to communicate within their tools, without needing to use chat apps, email, or other channels. But when teams work across tools, these channels become the default. Some integrations don’t support comments and notes, which means teams have to come up with workarounds to communicate outside of ServiceNow and Salesforce.

Attachments

Attachments allow teams to share deliverables, briefs, screenshots, and more. Attachment support isn’t default with most integrations, and the way an integration solution handles attachments is almost as important as having support at all.

Unito, for example, can support attachments in three different ways, depending on the integration you’re using:

  • Linked attachments create a hyperlink in synced work items. Clicking on the link opens the original attachment in the tool it came from.
  • Copied attachments make the exact same file visible in multiple tools.
  • Streamed attachments create a unique webpage for each attachment, accessible independent of either tool.

Hierarchies

Both ServiceNow and Salesforce have hierarchies, which are relationships between levels of work items. ServiceNow, for example, can have user/manager hierarchies, nested location fields, business application to server hierarchies, and more.

Integration platforms that don’t support hierarchies treat all work items exactly the same, which makes it difficult to track workflows across tools.

How to choose a ServiceNow-Salesforce integration

Integrations for ServiceNow and Salesforce should be evaluated according to the following criteria.

One-way or two-way

One-way integrations only push data from ServiceNow to Salesforce or vice-versa, by default. Some of them can be used to move data in both directions, but that involves setting up multiple one-way flows that can lead to issues like infinite loops and sync conflicts. A true two-way sync has built-in protections to manage these problems, natively syncing data back and forth. Handoffs and other linear workflows might only need one-way integrations. More complex processes benefit from a two-way sync.

Custom field and custom object support

Both ServiceNow and Salesforce rely extensively on custom fields and objects to support complex workflows. Integration solutions that don’t support these can artificially limit your workflows. Research the number of custom fields and objects each integration option you consider can handle.

Trigger-based or near-real time updates

Trigger-based integrations only push updates when a specific event happens; other platforms continuously monitor work items for updates to ship back and forth between tools. Consider which integration logic works best for your workflows.

API limits in ServiceNow and Salesforce

APIs allow integration solutions to translate data between tools, and most of them have limits. These can be in the fields they actually expose, the actions they can allow, or even the amount of data that can be transferred. A common limitation is the number of times a tool can ping an API for updates or the volume of data that can be transferred in each ping. It’s worth researching these limits and seeing how a potential integration platform handles them.

Who can set it up

Some integration platforms need a dedicated IT team or integration specialist to set up, much like Salesforce often requires a dedicated Salesforce admin. Other integrations can be deployed by any business user, regardless of their technical knowledge. One approach isn’t always better than the other; it depends on what you need. Larger organizations might want to centralize integration deployment through IT, while smaller teams often need solutions that can be deployed by anyone on the team.

How each integration handles errors

Integrations can run into errors that prevent data from syncing entirely, create duplicates, or delete data accidentally. How much damage these errors can do depends on how a platform handles them. Some stop trying to sync entirely while others keep trying until the error resolves itself. Yet other integrations have built-in methods for avoiding many of these errors entirely.

Security and data residency

Data security is essential when integrations have access to sensitive, proprietary information. Research a platform’s security certifications and compliance record, whether it’s for generic standards like SOC 2 or specific standards, such as CCPA or HIPAA.

Data residency refers to where data is stored, and some organizations may have to meet certain data residency requirements when choosing an integration vendor.

Pricing model of each integration option

Choosing a pricing model that fits your usage can help avoid exploding costs. Some examples of pricing models common in integration platforms include:

  • Per-task, where integrations charge for every task they create or update.
  • Per-connector, where you’re charged for every integration you use.
  • Per-user, where integrations charge you based on the number of users who access the platform.
  • Per-item-in-sync, where you’re charged for every work item an integration keeps in sync.

Use cases for ServiceNow-Salesforce integration

Customer support ticket escalation

When customer support agents run into tickets they can’t handle, the tickets are escalated to a more technical team, like software developers or IT professionals. These teams typically work in different tools, meaning the initial ticket might be handled in Salesforce, while technical teams work on it in ServiceNow. The gap between these tools is where important context and follow-ups go missing. Integrating ServiceNow and Salesforce closes that gap and improves collaboration between these teams.

AI context for Salesforce agents

Salesforce has built-in AI agents that can assist human users in day-to-day work or take on complete workflows. But these agents only have access to information in Salesforce, limiting the context they can work from. Integrating ServiceNow and Salesforce means AI agents in Salesforce have access to what’s happening in ServiceNow records.

ITSM: Salesforce tickets resolved in ServiceNow

ITSM has similar challenges as customer support ticket escalation, with success metrics often being based on the speed at which tickets are resolved, the number of tickets resolved in a specific period, and the smoothness of escalations. A ServiceNow-Salesforce integration doesn’t just make escalations smoother, it ensures all the context a ticket has in Salesforce lands in ServiceNow without any manual copying and pasting. Tickets land in ServiceNow, where IT teams can work on them, and when they’re closed, teams working in Salesforce find out automatically.

Change management with ITIL approvals

For customer-facing teams in Salesforce, a change in process or systems is often straightforward. A request is made, it’s evaluated, and it’s implemented. Service desks using ServiceNow rely on ITIL change management and a more rigorous workflow. An integrated system for change management within your organization ensures any internal transition is properly documented, approved, and communicated quickly.

Salesforce change requests for the team that builds it

Many organizations do significant custom development work to get their Salesforce workspace working exactly how they need. Allowing Salesforce users to send requests to ServiceNow through an integration can help developers maintain visibility on all that work.

ServiceNow-Salesforce integration best practices

No matter which integration you pick, consider the following best practices.

  1. Start with a small pilot project between a few records in ServiceNow and Salesforce. This allows you to test integrations and adjust them before you deploy them more broadly.
  2. Evaluate the results of a pilot project before implementing integrations at scale. Look for places where integrations save your teams time as well as situations where they might not be as effective as you expected.
  3. Consider whether your chosen integration platform is accessible enough for business users or whether you need to restrict it further to technical teams.
  4. Regularly review the integrations you use, at least yearly. Compare capability, price, and connector availability with other vendors.

What breaks in a ServiceNow-Salesforce integration and how to fix it

Even a well-researched integration can run into problems once real data starts moving between tools.

Duplicate records

You escalate one Salesforce case and end up with two or three matching incidents in ServiceNow. This usually happens when the integration can’t tell that a record already has a match, either because nothing stores the link between them or because both tools are set up to create new records.

How to fix it: Store each record’s ID in the other tool, like a Salesforce Case Number field on the ServiceNow incident, and use it to check for an existing match before creating anything. Then decide which tool creates new records for each workflow, and limit creation to that side.

Updates that loop or overwrite each other

A field keeps flipping between two values, or a support agent’s update disappears minutes after they make it. That’s what happens when two people edit the same field in different tools, or when two one-way flows each treat the other’s update as a new change to send back.

How to fix it: Pick a source of truth for each field. Fields one team owns, like a ServiceNow incident’s Assignment Group, can sync one way. For fields that need a true two-way sync, use an integration that tracks which changes it made itself, so updates don’t bounce back.

Fields that don’t line up

Statuses land in the wrong state, or a field arrives empty. ServiceNow and Salesforce rarely share the same field values or types. An incident’s State might have seven options, while a case’s Status has four. A ServiceNow reference field might have no direct equivalent in Salesforce.

How to fix it: Map values explicitly rather than relying on matching names, and decide what each value should become in the other tool. Where field types don’t match, create a custom text field to hold the value instead of forcing it into an incompatible one.

Records that fail to create

The integration reports success, but no new record appears, or it returns a validation error. Both tools let admins require fields and add validation rules. Sometimes those rules apply to records created through the API. Sometimes they only apply in the interface, which leaves incomplete records behind.

How to fix it: List every required field and validation rule on the tables and objects you’re syncing. Then make sure each one is either mapped or given a default value in your integration.

Closed records that stop updating

A Salesforce case keeps changing after the matching incident closes, but nothing reaches ServiceNow. Closed records are often locked by permissions or business rules, so integrations can’t write to them.

How to fix it: Sync final statuses and resolution notes before records close. If cases regularly reopen, plan a workflow for it, like reopening the incident or creating a new one linked to the original.

Permission and access errors

The integration can see some records but not others, or it can’t connect at all. Integrations act through a user account, so they’re limited by that account’s roles and permissions. Some Salesforce editions also don’t include API access, which most integrations depend on.

How to fix it: Create a dedicated integration user with read, create and update rights on every table and object in your sync. Before choosing a method, confirm your Salesforce edition includes API access.

Comments that land in the wrong place

An internal work note shows up in a customer-facing case comment, or comment edits never reach the other tool. Both tools separate public and internal comments, but integrations don’t always map these visibility settings the way you’d expect. Many integrations also only sync new comments, not edits to existing ones.

To fix this, map ServiceNow work notes to Salesforce internal comments and public comments to public comments. Test with a sample record before syncing anything a customer could see. Ask your team to add a new comment rather than edit an old one when something changes. 

Assignees that don’t match

Records sync without an owner or they’re assigned to the wrong person. Integrations usually match users across tools by matching email addresses, so mismatched emails or users with accounts in just one tool can break assignee mapping.

This can be fixed by ensuring team members use the same email in both tools. If team members don’t have accounts in both tools, ensure your integration won’t sync assignees.

Setting up a two-way sync with Unito

Step 1: Connect ServiceNow and Salesforce to Unito

Screenshot of the Unito flow builder connecting Salesforce and ServiceNow
Unito’s flow builder allows you to connect more than 60 tools, including Salesforce, ServiceNow, Jira, and Asana.

Unito will need to connect to a ServiceNow account that has create, read, update and delete (or CRUD) permissions for the records or tables that you want to sync. 

Users can connect Unito to ServiceNow with either OAuth2 or a Username and Password. For details on how to connect using OAuth2, check out this guide.

On the Salesforce side, make sure that the account used has permission to authorize third-party integrations. A quick list of permissions can be found here.

Once the accounts are correct, go to your Unito dashboard and select Connect a New Tool from the top bar and follow the prompts. A detailed guide can be found here.

Step 2: Pick a flow direction for incidents and cases

Screenshot of the Unito flow builder setting a flow direction to create new objects and records in Salesforce and ServiceNow
This 2-way flow will automatically create new Salesforce objects based on ServiceNow records, and new ServiceNow records based on Salesforce objects.

Unito syncs in either one or two directions. A one-way flow will behave much like the built-in ServiceNow spoke, but can be set to go either to or from ServiceNow. A two-way flow means that a change on either side will update on the other, ensuring that the data in both tools is always in sync and the same.

Step 3: Set rules for which cases and incidents sync

Set rules in Unito to sync Salesforce and ServiceNow in a 2-way integration
In this example, any Salesforce case created after July 22, 2024 with the custom field ServiceNow Assignment Group set to Product, will tell Unito to create a matching incident in ServiceNow.

Rules determine what syncs and what doesn’t. Using the drop-down options provided in the interface, select the rules for how you want your flow to function at a larger scale.

You could choose to filter out work items with specific labels, automatically set them to a specific status, or only sync items created after a specific date.

Step 4: Map Salesforce case fields to ServiceNow incident fields

Configuring fields to sync Salesforce cases to ServiceNow incidents with Unito's 2-way integration
Each pair of fields can have its own sync direction. This manages conflict resolution easily by setting a source and destination for all updates. In the case of 2-way updates, the most recent change will take effect.

Finally, choose what fields sync to each other across the tools. Unito can do this automatically in most situations. For more detailed customizability, it can be done manually, which lets you choose exactly which information moves where. Some fields can also be set to be one-way or two-way at this level.

Step 5: Launch your ServiceNow-Salesforce flow

Once you map your fields, your flow is ready to launch. After an initial sync, Unito will check for changes in real-time.

FAQ: ServiceNow-Salesforce integration

Can you use ServiceNow as a CRM?

Sort of! ServiceNow can be used as a CSM which contains features that allow it to act as a CRM and sales system, despite being primarily an ITSM software. It may not be as effective as a dedicated CRM, but it has some functionality in common with CRM systems.

Is ServiceNow the same as Salesforce?

No, ServiceNow is a cloud-based application platform (PaaS) service, while Salesforce is a cloud-based CRM platform. ServiceNow serves as a platform for creating custom applications and automating workflow, while Salesforce is primarily focused on customer relationship management.

Contrasting Salesforce’s customer-centric focus, ServiceNow streamlines internal business processes. This platform is designed to enhance productivity across multiple departments and improve overall IT services management. It employs AI and machine learning to:

  • automate risk assessment
  • smart ticket routing
  • predict success of IT changes
  • provide AI tools like chatbots

These features optimize the handling of IT issues and enhance user experiences.

What is an integration between Salesforce and ServiceNow?

A Salesforce-ServiceNow integration is software that moves data between records in the two tools, such as Salesforce cases and ServiceNow incidents, so an update in one shows up in the other. ServiceNow’s own option is the Salesforce spoke, which requires an Integration Hub subscription on top of your ServiceNow license.

You can also use third-party software to integrate Salesforce and ServiceNow. Some examples of this software include:

  • Unito
  • Zapier
  • Workato
  • Tray.io
  • Mulesoft

What’s the fastest way to connect Salesforce and ServiceNow?

The fastest way is a no-code, two-way sync platform like Unito, which ops, IT, or RevOps teams can set up themselves. ServiceNow’s Salesforce spoke needs a ServiceNow admin or developer working in Flow Designer, plus an Integration Hub subscription. An iPaaS like MuleSoft or Workato needs an integration developer to build one flow per direction.

Will ServiceNow overtake Salesforce?

There are currently no signs that ServiceNow will overtake Salesforce. According to some numbers, ServiceNow has over 7,700 customers while Salesforce has over 150,000. Additionally, ServiceNow reported $10.98 billion in revenue in 2024 while Salesforce reported $37.89 billion in revenue that year.

Which platforms integrate with ServiceNow and Salesforce together?

Three kinds of platforms connect ServiceNow and Salesforce: ServiceNow’s Integration Hub with its Salesforce spoke, iPaaS tools like MuleSoft and Workato, and two-way sync platforms like Unito. Automation tools like Zapier can also pass data between them, one direction per Zap. The right pick depends on who will maintain the integration and whether updates need to flow both ways.

Is ServiceNow part of Salesforce?

ServiceNow is not part of Salesforce. It’s a separate, distinct software platform. While there is some overlap between them, since both tools can be used to manage customer issues and service requests, they’re different platforms run by different companies.

Can Salesforce integrate with ServiceNow?

Yes, there are multiple ways to integrate Salesforce with ServiceNow. Here are a few of your options for integrating these tools:

Does Salesforce compete with ServiceNow?

Yes, Salesforce competes with ServiceNow to some extent. Both can be used to handle support tickets and manage business processes within customer support teams. That said, many organizations use both ServiceNow and Salesforce, since they’re specialized in distinct areas.

Why should I integrate customer service operations?

Customer data, product catalogs, and service catalogs are the lifeblood of both Salesforce and ServiceNow, yet often exist in frustrating silos. Integration solutions like Unito can ensure this vital information is always up-to-date and consistent by syncing Salesforce and ServiceNow data. This eliminates discrepancies that cause delays and customer frustration.

For example, if someone in your organization changes a customer address in Salesforce, that change can be automatically synced to a matching record in ServiceNow. Similarly, product catalog synchronization can enable sales teams and support reps to see the same product details and availability, and prevent miscommunications and failed orders. This allows you to :

  • Coordinate across teams with accurate customer data: Imagine if your IT department could create ServiceNow incidents that automatically create corresponding Salesforce cases. Then, manual changes to one would appear instantly in the other, ensuring seamless visibility between platforms. Meanwhile, customer support agents can provide accurate, timely information to end users as the internal IT department works on each incident, ticket, or record.
  • Handle escalations with full context: Conversely, critical customer insights or escalations captured within Salesforce can be relayed back to the ServiceNow team as synced records. So the IT department can more effectively diagnose and resolve underlying issues. A no-code, 2-way solution is optimal for minimizing data-related human error, supporting the customer experiences in a large-scale enterprise through automation, and simplifying data sharing between departments.

Ready to sync ServiceNow and Salesforce?

Meet with a product expert and see what Unito can do for your workflows.

Book a Demo

ʕ•ᴥ•ʔ