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

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Identify New Attachments action

# Identify New Attachments action {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
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.

## Roles and availability {#identify-new-attachments-action__section_lqz_vvn_mnb}

Available as a ServiceNow Core
Remote Process Sync action.{#identify-new-attachments-action__action-subcategory}

Subscription requirements
:   This action requires an Integration Hub subscription. For more information, see [Request Integration Hub](https://www.servicenow.com/docs/1cjQKW5ssBIKAcJMt12j6w "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=brazil&pubname=brazil-build-workflows&ft:locale=en-US).

## Retry policy {#identify-new-attachments-action__section_jjm_f3z_tgc}

The Identify New Attachments 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 {#identify-new-attachments-action__section-inputs}

Provide a value for each input that your action needs. To add
dynamic values, you can also drag and drop pills from the Data panel or select them from the
pill picker.{#identify-new-attachments-action__inputs-description}

Attachments
:   Data type: Array of Objects

    Array containing a list of
    attachment objects to evaluate.

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.

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 {#identify-new-attachments-action__section-outputs}

These outputs appear in the Data panel. You can use them as inputs
elsewhere in your flow.
{#identify-new-attachments-action__outputs-description}

Attachments
:   Data type: Array of Objects

    Array containing information about the attachments to
    synchronize.
    {#identify-new-attachments-action__attachments-ph2}

Count
:   Data type: Integer

    Number of attachments
    identified.

*[\>]: and then