--- sourceDocument: Australia Workflow Data Fabric sourceDocumentLink: https://www.servicenow.com/docs/r/integrate-applications Release : - australia ft:locale : - en-US ft:publication_title : - Australia Workflow Data Fabric ft:clusterId : - crint bundleId : - crint workflow : - Creator --- # Integration Hub Remote Process Sync # Integration Hub Remote Process Sync {#ariaid-title1} * Release version: Australia * * Updated March 12, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 allows you to establish one-way or bidirectional integrations across multiple ServiceNow instances, ensuring that your business process workflows remain synchronized. This feature requires an Integration Hub subscription and enables service providers to automatically keep customer instances in sync by using Workflow Studio subflows to automate processes across all customers. Show full answer Show less ## Key Features * **Cross-instance automation:** Automate business processes that span multiple ServiceNow instances, keeping all stakeholders updated. * **Data synchronization control:** Manage synchronization and correlation of records, attachments, and journal fields across instances. * **Reliable data delivery:** Uses a standalone correlation engine and queueing system to ensure ordered delivery of updates to remote instances. * **Error and outage management:** Built-in execution engine in Workflow Studio helps troubleshoot and manage issues in multi-instance automated processes. * **Domain separation support:** Enables synchronization in domain-separated environments with domain-aware configuration and data handling, ensuring records and flows execute in appropriate domains. ## Roles and Permissions Remote Process Sync includes predefined roles to control access: * **ihprocesssync:** Manage process sync definitions and related records. * **ihprocesssyncapi:** Access Remote Process Sync APIs exclusively. * **ihprocesssyncrunas:** Run inbound and outbound flows, requiring access to the relevant tables for record creation or updates. ## Practical Considerations Before implementing Remote Process Sync, evaluate it against other multi-instance integration options like Instance Data Replication and the Remote Instance spoke. Remote Process Sync is designed for complex, high-level business process integrations and replaces the older eBonding spoke. When ready, follow the guide on getting started with Remote Process Sync to build and manage integrations effectively. 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](https://www.servicenow.com/content/dam/servicenow-assets/public/en-us/doc-type/legal/snc-addendum-integrationhub.pdf). 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. ## Benefits {#integrationhub-remote-process-sync__section_jqv_vwy_zmb} 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. {#integrationhub-remote-process-sync__ul_uj1_ywy_zmb} ## Roles {#integrationhub-remote-process-sync__section_wsk_br5_fnb} By default, Remote Process Sync provides the following roles that you can assign to users:{#integrationhub-remote-process-sync__table_pqm_bmf_qnb__entry__2} | 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. | [ ] {#integrationhub-remote-process-sync__table_pqm_bmf_qnb} ## Domain separation {#integrationhub-remote-process-sync__section_nyq_m35_fnb} 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. {#integrationhub-remote-process-sync__ul_qwh_jlf_qnb} 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. {#integrationhub-remote-process-sync__ul_dqb_plf_qnb} {#integrationhub-remote-process-sync__ol_i2t_hlf_qnb} ## Getting started {#integrationhub-remote-process-sync__section_rsh_mmf_qnb} 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 [Instance Data Replication](https://www.servicenow.com/docs/access?context=instance-data-replication&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US) 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 When you're ready to start building and managing a Remote Process Sync integration, learn the basics of [Getting started with Remote Process Sync](https://www.servicenow.com/docs/n1mCBBfvN4T5kVSaepzYLg "Learn the basics of setting up a Remote Process Sync integration in order to link the automated processes among two or more ServiceNow instances together.").