---
sourceDocument: Australia Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Actions

# Remote Process Sync actions {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Learn how to use actions in outbound and inbound flows for your Integration Hub Remote Process Sync integration.
Remote Process Sync provides you with a collection of Workflow Studio actions that you can use to customize the default [outbound and inbound flow](https://www.servicenow.com/docs/n1mCBBfvN4T5kVSaepzYLg#getting-started-with-remote-process-sync__outbound-flows-and-inbound-flows) templates. These actions let you:

* Create correlations between records on local and remote instances
* Manage attachments between local and remote instances
* Send captured payloads to a remote instance
* Transform inbound payloads to complex objects
{#remote-process-sync-actions__ul_qpj_qff_qnb}

## Remote Process Sync action dependencies {#remote-process-sync-actions__section_kw4_d4l_snb}

Certain Remote Process Sync actions are dependent upon other actions, and thus are
generally intended for you to use together. The following use cases describe situations in
which you might consider using dependent Remote Process Sync actions in your outbound and
inbound flows.  
Correlate a record with a captured payload: Use these actions in the following order to automatically correlate a record with a captured payload to be sent to a remote system:

1. [Look Up Correlation By Local
   Correlation ID](https://www.servicenow.com/docs/dIkKDS_My2nzsp6UJ2hUeA "Look up an active correlation by a specified local correlation ID. The local correlation ID identifies the correlation on the local instance. Remote Process Sync actions and flows use the returned correlation to synchronize a local record with a record on a remote system.") - Use this action to determine if a correlated record exists between your staged local record and a record on the remote system.
2. [Send Captured Payload to
   Remote System](https://www.servicenow.com/docs/zy0z4w10fgajpnjjaaCikQ "Generate a captured payload, and send it to a remote system. This action should follow a Look Up Correlation action. Remote Process Sync flows use the returned correlation to check if a new correlation should be created.") - Use the Correlation Detail output data pill from the Look Up Correlation By Local Correlation ID record as the value for the Correlation Detail input in this action. This enables you to correlate the local record containing the outbound payload to a record on the remote system.

{#remote-process-sync-actions__ol_jh5_t4l_snb}  
Note:  
The Remote Process Sync Outbound Flow Template - Basic provides you with these two actions so that you don't need to set up this correlation yourself.  
Identify and request missing attachments from a remote system: Use these actions in the following order to automatically look up and request attachments from a remote system that don't exist in your local system:

1. [Identify New Attachments](https://www.servicenow.com/docs/NH5_1HnJEIRWZ4td6s~NhA "Identify the attachments already associated with a local record to determine which remote attachments require synchronization. Use the output of this action to request missing attachments from the remote system.") - Use this action to look up any attachments that exist on the remote system but don't exist on your local system for correlated records.
2. [Request Attachments from
   Remote System](https://www.servicenow.com/docs/hvkB4Gl7GQFw6Hrgk7r9Dw "Request the transfer of the identified attachments using the specified correlation. The system moves attachments associated with the record on the remote system to the local system.") - Use this action to request the transfer of identified attachments from the remote system to your local system.
{#remote-process-sync-actions__ol_nxt_dql_snb}