What is Service Bridge?
ServiceNow Service Bridge is a powerful integration capability that enables multiple ServiceNow instances (such as Provider and Consumer instances) to communicate and collaborate seamlessly. It allows organizations, service providers, and partners to exchange service requests, tasks, and updates without leaving their own environments.
- It enables cross-instance collaboration between Provider and Consumer
- Supports two-way synchronization of tasks like Cases, Incidents, etc.
- Eliminates the need for custom integrations
- Provides real-time visibility and transparency across organizations
In simple terms, Service Bridge allows users to request services, track progress, and receive updates while providers fulfill the work in their own instance.
- Consumers can raise requests from their own portal
- Providers work on tasks in their own instance
- Updates are synchronized in real-time across both instances
Remote Catalog Items in Service Bridge
One of the key features of Service Bridge is Remote Catalog.
What is Remote Catalog?
Remote Catalog allows a Provider to publish catalog items (or record producers) so that Consumers can request them directly from their own instance.
How it works:
- Catalog items are created and maintained in the Provider instance
- These items are published to Consumer instances
- Consumers can request services without logging into the Provider instance
Key capabilities:
- Requests are submitted from the Consumer portal
- A Provider Task is created in both instances
- Fulfillment happens in the Provider instance
- Consumers can track progress in their own instance
Benefits:
- No need to replicate catalog items across instances
- Centralized management by Provider
- Seamless user experience for Consumers
How Service Bridge Works (Example Flow)
Below is a real-world example explaining how Service Bridge works between Consumer and Provider instances.
Step 1: Request Submission (Consumer Instance)
- A user logs into the Consumer portal
- Submits a request using a Remote Catalog Item
- A Provider Task is created in the Consumer instance
At the same time:
- A corresponding Provider Task is also created in the Provider instance
Step 2: Task Creation & Processing (Provider Instance)
- Using a Flow (Flow Designer / Workflow)
- The Provider Task triggers creation of a Case / Incident / Task in the Provider instance
- The Provider team works on this task
Example:
- Consumer raises a request for “Product Support”
- Provider receives it and creates a Case
- Provider agent starts working on the Case
Step 3: Synchronization Between Instances
Service Bridge ensures bi-directional synchronization:
- When the Provider updates the Case
→ The Provider Task in Provider instance is updated - These updates are then synced to:
→ Provider Task in Consumer instance - Updates include:
- State changes
- Comments
- Work notes
- Resolution details
This is achieved using Remote Task and synchronization mechanisms, which ensure data consistency across instances.
Step 4: Visibility for Consumer
- The Consumer user can:
- Track request status
- View updates in real time
- Interact via comments
- The Provider and Consumer both work in their own instances, but see synchronized data
End-to-End Example
Let’s understand with a simple scenario:
- A user in the Consumer instance submits a request
- A Provider Task is created in both Consumer and Provider instances
- A Case is created in the Provider instance via Flow
- The Provider works on the Case
- Updates (State, Comments, Resolution) are synced:
- Provider Case → Provider Task (Provider)
- Provider Task (Provider) → Provider Task (Consumer)
- The Consumer user receives updates and tracks progress
- Once resolved, the request is completed with full visibility
