Remote Process Sync Outbound Flow Template - Basic

  • Release version: Zurich
  • Updated July 31, 2025
  • 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 Remote Process Sync Outbound Flow Template - Basic

    This template provides a sample Remote Process Sync subflow designed to send outgoing payloads from a local ServiceNow instance to a remote instance. It creates a correlation between a remote record and a local incident record, enabling synchronization of process data across instances. The subflow is customizable by copying and modifying the input to target a different local table as needed.

    Show full answer Show less

    Key Features

    • Global Availability: Available as a Global Remote Process Sync subflow, enabling broad integration scenarios.
    • Integration Hub Subscription Required: Utilizes Integration Hub capabilities, requiring an active subscription and appropriate roles.
    • Flexible Inputs: Inputs include the local record reference, remote system record identifying the target instance, CRUD operation type (Create, Update, Delete), capture definition for generating payloads, process event name, and the payload object containing data changes.
    • Synchronization Control: The parent flow can wait for the subflow to complete before proceeding, ensuring coordinated processing.
    • Outputs for Flow Integration: Provides outputs such as synchronization status (Active or Inactive) and error messages to facilitate error handling and flow control.

    Practical Use for ServiceNow Customers

    ServiceNow customers can leverage this template to implement reliable outbound synchronization of process data between instances. By adapting the local record input, organizations can synchronize various record types beyond incidents. The subflow supports standard CRUD operations and uses process events to maintain consistent synchronization. With output status and error messages, customers can monitor synchronization health and troubleshoot issues effectively.

    A sample Remote Process Sync subflow to send outgoing payloads to a remote instance. This subflow creates a correlation between a remote record and a local incident record. Copy this subflow and edit the input for the local record to the table of your choice.

    Roles and availability

    Available as a Global Remote Process Sync subflow.

    Subscription requirements
    This action requires an Integration Hub subscription. For more information, see Request Integration Hub and Legal schedules - IntegrationHub overview.
    Role requirements
    This action requires roles granted by delegated development or assigned to the user. For more information, see User access to Workflow Studio flows.

    Inputs

    Provide a value for each input that your action needs. To add dynamic values, you can also drag pills from the Data panel or select them from the pill picker.

    Wait for Completion
    Data type: True/False

    Option to require the parent flow to wait for the subflow to complete. If enabled, the parent flow cannot proceed to the next action until the subflow completes.

    Local Record
    Data type: Record

    Reference to a record on the local instance you are synchronizing with another instance. The data pill contains all the field values for the specified record. For example, a case record on the local instance.

    Remote System
    Data type: Record

    Reference to the Process Sync Remote System record for the remote instance you are synchronizing processes with. This record identifies the instance that receives outbound synchronization changes or that sent inbound synchronization changes.

    CRUD Operation
    Data type: Choice

    Database operation that triggered the process event. The available options are Create, Update, or Delete.

    Trigger/Capture Definition
    Data type: Record

    Reference to the Capture Definition record that the system uses to create an outbound payload. The data pill contains all the field values for the specified record. For example, a capture definition for case records.

    Process Event
    Data type: String

    Name of the process event to run. The name is the same on each instance that participates in process synchronization. For example, case-to-incident.

    Payload
    Data type: Object

    Object containing changes generated by a capture definition. For example, a list of field changes for a case record on the local instance. The system transforms this object to a JSON string to send it to a remote instance.

    Outputs

    These outputs appear in the Data panel. You can use them as inputs elsewhere in your flow.

    Status
    Data type: Choice

    Synchronization state of records. The available options are Active or Inactive. Active records are being synchronized. Inactive records are not synchronized.

    Error Message
    Data type: String

    Error returned by the action.