---
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


---

# Get Attachment Metadata for Local Record action

# Get Attachment Metadata for Local Record action {#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 Get Attachment Metadata for Local Record action

The Get Attachment Metadata for Local Record action allows ServiceNow users to retrieve a list of attachments linked to a specific local record.
This functionality is crucial for synchronizing attachments between local and remote records, ensuring data consistency across instances.
Show full answer Show less  

## Key Features

* **Integration Hub Requirement:** This action necessitates an Integration Hub subscription for proper functionality.
* **Role Requirements:** Users must have specific roles granted by delegated development to access this action.
* **Retry Policy:** The action utilizes the RPS Push Attachment Policy to manage failed requests, ensuring reliable synchronization.
* **Input Parameters:**
  * **Local Record:** Reference to the record on the local instance.
  * **Strategy:** Choose between 'All' (all attachments) or 'Deltas' (only changed attachments).
  * **Remote System:** Reference to the Process Sync Remote System record for the target remote instance.
  * **Correlation Detail:** Object containing correlation information for local and remote IDs.
  * **Attachments:** Array of objects representing the attachments to evaluate.
  * **Max Attachment Size:** Sets a limit on attachment size in megabytes to prevent errors during synchronization.
  * **Allowed Extensions:** Specifies the attachment file types that can be included.

## Key Outcomes

By utilizing this action, ServiceNow customers can effectively manage and synchronize attachments between local and remote records, enhancing data integrity and operational efficiency. The outputs of this action include detailed information about the attachments to facilitate further processing in workflows.  
Get the list of attachments associated with a specified local record. Use the output of this action to synchronize the attachments of a local record with the attachments of a remote record.

## Roles and availability {#get-attachment-metadata-local-record-action__section_lqz_vvn_mnb}

Available as a ServiceNow Core
Remote Process Sync action.{#get-attachment-metadata-local-record-action__availability-subcategory}

Subscription requirements
:   This action requires an Integration Hub subscription. For more information, see [Request Integration Hub](https://www.servicenow.com/docs/6Lp3j2DAY4g6m~ROtVcCKw "ServiceNow Integration Hub enables you to build reusable integrations with third-party systems and call them from anywhere in the ServiceNow AI Platform. For example, you can call external systems using integration APIs from the Action Designer Script step or run the Script step on the ServiceNow MID Server. You can also activate protocol steps such as REST, SOAP, and PowerShell.") and [Legal schedules - IntegrationHub overview](https://www.servicenow.com/content/dam/servicenow-assets/public/en-us/doc-type/legal/snc-addendum-integrationhub.pdf).

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](https://www.servicenow.com/docs/access?context=user-access-flow-designer&version=australia&pubname=australia-build-workflows&ft:locale=en-US).

## Retry policy {#get-attachment-metadata-local-record-action__section_qk4_n3z_tgc}

The Get Attachment Metadata for Local Record action uses the RPS Push Attachment Policy to retry failed requests at regular intervals. To view or edit this policy, navigate to the Retry Policies \[sys_retry_policy\] table at AllIntegrationHubConnections \& CredentialsRetry Policies.

## Inputs {#get-attachment-metadata-local-record-action__section-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.{#get-attachment-metadata-local-record-action__inputs-description}

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.

Strategy
:   Data type: Choice

    Level of attachment detail to gather. The available options are All or Deltas. Use
    the All option to gather all synchronized attachments. Use the Deltas option to gather
    only attachments that have changed since the last synchronization.

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.

Correlation Detail
:   Data type: Object

    Object containing correlation
    information about a synchronized record. The object identifies the local and remote
    correlation IDs associated with a local record.

Attachments
:   Data type: Array of Objects

    Array containing a list of
    attachment objects to evaluate.

Max Attachment Size (MB)
:   Data type: Integer

    Integer specifying the maximum uncompressed attachment size that can be included in the list of attachments, in megabytes.

    You can use this field to limit attachment sizes and avoid errors that may result
    from syncing very large attachments.

    Leave this field blank to use the platform limit for attachment sizes.

Allowed Extensions
:   Data type: List

    List containing the attachment extensions that can be included in the list of attachments. Leave this field blank to use the platform restrictions.

## Outputs {#get-attachment-metadata-local-record-action__section-outputs}

These outputs appear in the Data panel. You can use them as inputs
elsewhere in your flow.{#get-attachment-metadata-local-record-action__outputs-description}

Attachments: Data type: Array of Objects

Array containing information about the attachments to
synchronize.

*[\>]: and then