Integration Hub Remote Process Sync

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Integration Hub Remote Process Sync

    Integration Hub Remote Process Sync enables ServiceNow customers to establish one-way or bidirectional integrations across multiple ServiceNow instances, ensuring that process workflows remain synchronized. This capability is essential for service providers managing multiple customer instances, allowing automated workflows to span across instances and maintain consistency in business processes.

    Show full answer Show less

    This feature requires an Integration Hub subscription and supports complex multi-instance integration scenarios by focusing on high-level business process synchronization rather than simple data replication.

    Key Features

    • Cross-instance Process Automation: Automate and synchronize workflows that span multiple ServiceNow instances, ensuring all stakeholders stay updated.
    • Data Synchronization and Correlation: Manage synchronization of records, attachments, and journal field data accurately across instances.
    • Reliable Data Update Delivery: Utilize a standalone correlation engine and queueing system to guarantee ordered delivery of data updates to remote instances.
    • Error Handling and Troubleshooting: Use the built-in execution engine within Workflow Studio to manage errors and outages within multi-instance automated processes effectively.
    • Domain Separation Support: Synchronize process flows in domain-separated environments with appropriate domain-aware data handling, ensuring security and data segregation.
    • Role-based Access Control: Assign specific roles to users for managing process sync definitions, accessing APIs, and running inbound/outbound flows with necessary permissions.

    Practical Considerations for ServiceNow Customers

    • Subscription Requirement: An Integration Hub subscription is necessary to use Remote Process Sync.
    • Replacing eBonding Spoke: Remote Process Sync replaces the eBonding spoke for instance integration, offering enhanced capabilities for complex business process integration.
    • Comparison with Other Integration Options: Unlike simpler solutions like Instance Data Replication or Remote Instance spoke, Remote Process Sync is designed for sophisticated multi-instance workflows that require high-level process cohesion.
    • Getting Started: Customers should review the fundamentals of building and managing Remote Process Sync integrations to leverage its full capabilities effectively.

    Expected Outcomes

    By implementing Integration Hub Remote Process Sync, ServiceNow customers can expect streamlined and reliable synchronization of business processes across multiple instances. This leads to improved operational efficiency, better data consistency, and enhanced capability to support customer environments at scale with automated workflows that are robust and easier to manage.

    Integration Hub Remote Process Sync enables you to set up one-way or bidirectional integrations among multiple ServiceNow instances, so that your process flows stay in sync.

    Note:
    Integration Hub Remote Process Sync requires an Integration Hub subscription. For more information, see Legal schedules - Integration Hub overview.

    An Integration Hub Remote Process Sync integration lets you span automated workflows for your business process across multiple ServiceNow instances. As a service provider, keep multiple customer instances in sync automatically, using Workflow Studio subflows to automate your process's workflows for all of your customers.

    Keep process flows across multiple instances in sync. For example, automate software request fulfilment among customer and vendor instances.

    Benefits

    Integration Hub Process Sync provides you with these benefits:
    • Automate cross-enterprise automated processes that span multiple instances, keeping various process stakeholders up-to-date
    • Manage how to synchronize and correlate your record, attachment, and journal field data across multiple instances
    • Ensure order delivery for data updates in remote instances, using a standalone correlation engine and queueing system
    • Manage and troubleshoot errors and outages in your automated mutli-instance processes with the built-in execution engine in Workflow Studio.

    Roles

    By default, Remote Process Sync provides the following roles that you can assign to users:
    Role Users with this role can
    ih_process_sync Create, update, or delete process sync definitions and related records.
    ih_process_sync_api Access Remote Process Sync APIs only.
    ih_process_sync_run_as Run outbound and inbound flows associated with a process sync definition. This user must have access to the tables for which any records are created or updated in the flow.

    Domain separation

    You can use Remote Process Sync to synchronize process flows among multiple domain-separated instances. In a domain-separated environment, the following conditions apply:
    1. When building your integration
      • Configuration tables have a sys_domain, and data is domain separated.
      • Configuration tables are meant to be in the same domain as the parent configuration record.
      • Subflows may be chosen from the current or any parent domain.
      • No tables have sys_overrides , and thus cannot override business rules or UI actions from parent domains.
    2. When your integration runs
      • Only records from the configuration domain and associated child domains are captured.
      • Queue tables have a sys_domain. The outbound record is stored in the same domain as the captured source record. The inbound record is stored in the same domain as the Inbound API user in the Remote System record.
      • The outbound subflow runs in the same domain as the queued record.
      • The inbound subflow runs in the same domain as the user specified in the Remote System record's Run Inbound Flows as field.

    Getting started

    Before deciding to move forward with Remote Process Sync as your integration framework, consider how this framework compares to other multi-instance ServiceNow AI Platform® integrations. While solutions such as and the Remote Instance spoke support simple multi-instance integrations, Remote Process Sync supports more complex multi-instance integration use cases, focusing on integrating instances by high-level business processes.
    Note:
    Remote Process Sync replaces the eBonding spoke for integrating instances.
    Figure 1. Comparison of Instance Data Replication, Remote Instance spoke, and Remote Process Sync
    Instance Data Replication and the Remote Instance spoke support simple integrations for an entire table or using ServiceNow AI Platform APIs. Remote Process Sync supports more complex multi-instance integrations.

    When you're ready to start building and managing a Remote Process Sync integration, learn the basics of Getting started with Remote Process Sync.