One Platform, and how Workflow Data Fabric Connects It

Joe Wilmoth · yesterday

Workflow Data Fabric · Instance to Instance

Read it live. Three ways to connect one instance to another.

Almost nobody runs a single instance. Most organizations run a fleet—one per region, one per business unit, one for the provider and one for the customer, production alongside sub‑production. Three ServiceNow capabilities connect those instances. They look similar on a slide. They behave nothing alike.

Start with the newest one. The ServiceNow Remote Instance Zero Copy Connector reads remote data in place and stores nothing. Reach for the other two only when the data genuinely has to be copied.

The short version

If you only read one section, read this one.

NEWEST

ServiceNow Remote Instance Zero Copy Connector

Read data in a remote instance live, with nothing copied or persisted.

Remote Instance Spoke

Call another instance from a flow when you need something on demand.

Integration Hub Remote Process Sync

Run one business process across many instances, correlated and in order.

Watch the names

The Remote Instance Spoke is Integration Hub, and it copies records. The ServiceNow Remote Instance Connector is Zero Copy, and it copies nothing. Nearly the same name. Opposite behavior.

The three capabilities

1. ServiceNow Remote Instance Zero Copy Connector

When you need the answer, not the data.

The newest of the three. It queries remote tables in real time and stores nothing locally.

Data Fabric Tables read like local tables, so GlideRecord works as expected
Built for data residency—records stay in the instance that owns them
A service account on the remote instance governs which tables you can map
Retrieves only the records the current view needs, then purges them
Read‑only—360 views, dashboards, and workflow decision points
Not a transfer tool. Skip bulk pulls, and never persist what you read

The anchor use case

A provider runs twelve instances, and regulation forbids moving records between them. Designate one central instance, open Zero Copy connections to the rest, and you get consolidated dashboards without a single record leaving the instance that owns it. That is the case where copying is not just inefficient – it is non‑compliant.

Who does what: a connection admin sets up the connection in Zero Copy Connector Hub and grants data stewards access. Data stewards build the Data Fabric Tables. Retrieved records are purged from memory the moment the user closes the list or form.

2. Remote Instance Spoke

When a flow needs something from another instance, once.

Gives Workflow Studio a set of Actions that operate against a remote instance.

Ad‑hoc by design—build it inside a Flow
Reads and writes on demand, so nothing moves until the Flow asks for it
Prebuilt Actions for incident, problem, change, and case records
Cross‑maps record types—export a case as an incident, and back again
Grant minimum permissions. The documentation warns against elevated spoke roles
No queueing or correlation—order and state stay your responsibility

Config gotchas worth saying out loud

Two connection and credential aliases are required, one per instance
Sample transform maps coalesce on sys_id by default, and the Company field is required for those defaults
Time zones can differ between instances, so Flows have to account for it

3. Integration Hub Remote Process Sync

When a process crosses companies and has to stay in step.

Spans one automated business process across multiple instances, one way or both.

Process‑oriented—keeps records, attachments, and journal fields correlated
Guarantees order of delivery through a correlation engine and queues
A network outage delays updates instead of scrambling their sequence
Splits a limited API user from a separate run‑as user for tighter access
Honors domain separation, so providers can run many customers safely

This is the heavy‑duty option: accounts payable, sourcing and procurement, service catalog and ServiceBridge, provider‑to‑customer fulfilment. Many‑to‑many, with no limit on the number of remote instances. The honest limitation is that it is not plug‑and‑play. Every integration is planned and built separately, and managing many inbound and outbound systems is real work.

Inside a Remote Process Sync flow

Every update is captured, queued, correlated, and confirmed.

01

Capture

Selected fields are staged the moment a record changes

02

Queue

The outbound queue holds the payload and preserves sequence

03

Correlate

The remote instance maps the payload onto its own record

04

Confirm

Status, retries, and errors stay visible on both sides

Troubleshooting lives in the queues: IntegrationHub > Remote Process Sync > Outbound Queue and Inbound Queue.

Start with the question

Ask whether you need to own the data. If not, read it live and stop there.

START HERE

Live answer

“I need to read remote data, not own it.”

ServiceNow Remote Instance Zero Copy Connector

THEN

One‑off call

“A flow needs to fetch or push something now.”

Remote Instance Spoke

OR

Shared process

“One process spans companies and must stay in step.”

Integration Hub Remote Process Sync

Describe the outcome in one sentence and listen for which card it lands on. Start at the first one. If you are reading remote data rather than owning it, stop there. And if the sentence describes two cards, you have two integrations—not one hybrid.

Before you commit

Cheap questions now beat expensive rework later. Settle these four before anyone opens Workflow Studio.

1. Do you need the data, or only the answer? Reading beats copying. This one question separates Zero Copy from everything else.

2. Who owns order and state—the platform, or your Flow logic? This separates Remote Process Sync from the Spoke.

3. What is entitled today, and what needs a new subscription? The Spoke and Remote Process Sync need Integration Hub or Workflow Data Fabric. Zero Copy Connectors need Workflow Data Fabric. Confirm entitlement before you design around any of them.

Go to the source

Every claim above traces back to one of these three documentation pages, all Australia release.

Read it live with Zero Copy before you copy it.

The platform is not the hard part. Choosing well is.

Running one of these three in production? Tell us which one you picked and what tipped the decision—the comments are the best place to compare notes.