ServiceNow now offers many ways to connect your instance to the world around it, and most of them sit under Workflow Data Fabric. Their names overlap more than their jobs do. Here’s a plain guide to what each one is for, checked against ServiceNow’s documentation in October 2026.

Integration Hub: connect ServiceNow to other apps

Integration Hub lets you build reusable integrations with third-party systems and call them from flows in Workflow Studio. It comes with about 200 prebuilt spokes, including Jira and Jira Service Management, plus REST, SOAP and script steps for anything else, and webhooks for inbound calls. It needs a separate subscription, and usage is measured in transactions. See how it compares with Unifi.

Remote Process Sync: keep processes in step between ServiceNow instances

Part of Integration Hub, Remote Process Sync creates one-way or two-way integrations between ServiceNow instances, synchronising records, attachments and journal fields with its own queueing for ordered delivery. ServiceNow positions it for service providers managing many customer instances, and it replaces the legacy eBonding spoke. See how it compares with Unifi.

Service Exchange: a provider and consumer model between instances

Service Exchange, formerly Service Bridge, connects ServiceNow instances in a provider and consumer model: the provider publishes catalog items and tasks, and each side works in its own instance. See how it compares with Unifi.

Instance Data Replication: copy data between instances

Instance Data Replication synchronises data updates across ServiceNow instances, to keep the same data consistent in more than one place.

Zero Copy Connectors: read data where it lives

Zero Copy Connectors fetch real-time data from external sources without copying it into your instance, so workflows and AI agents can use it in place. Read the explainer.

Stream Connect: stream events through Kafka

Stream Connect links Apache Kafka environments directly with your instance, for real-time data streaming in both directions.

External Content Connectors: bring outside content into AI Search

External Content Connectors let AI Search reach content and metadata in repositories such as Confluence Cloud and SharePoint Online.

Scripted REST APIs and the Table API: how other systems reach your data

When another system needs your ServiceNow data, the platform’s Table API and Scripted REST APIs are standard routes. Easy API, coming soon, builds governed APIs on your instance with no code. They can match the Table API, so existing integrations keep working, and you decide what each user and service can reach, so the Table API itself can stay switched off.

Where eBonding fits

Most of these tools move data or automate steps. eBonding is different: you and a customer or supplier each work the same ticket in your own system, and every update has to reach the other side, in order, and be confirmed. When the other side runs ServiceNow, Remote Process Sync and Service Exchange are options. When they run Jira, Freshservice or something else, or each customer wants the integration to follow its own process, that’s the job Unifi is built for.

Not sure which you need? Start a conversation.