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


---

# Import a package version attachment

# Import a package version attachment in RPA Hub {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Import package version attachments automatically instead of manually uploading a package version attachment, by selecting the Import Attachment button on a package version.

## Before you begin

Perform the following tasks before you import a package version attachment:

* Ensure that you've completed the tasks that are related to migrating your data from a lower environment to a higher environment. For more information, see [Migrating your data from a lower environment to a higher environment in RPA Hub](https://www.servicenow.com/docs/~Gnhskj3_22Rndj8pp2Zag "As a system administrator, after you restructure the RPA Hub tables to extend the Application file (sys_metadata), you can use the update set capability to migrate your data from a lower (non-production) environment to a higher (production) environment for real-time use.").
* Ensure that the sn_rpa_fdn.allow_manual_upload_of_automation_package system property is marked as true. If you have the admin role, you can edit this system property.
* Ensure that there is no valid attachment associated to the package version.
* Verify that the life-cycle stage of the package version isn't set to Retired.
* Create an active connection in the RPA Automation Package connection and credential alias. Ensure to provide the lower (non-production) environment in the Connection URL field. For more information, see [Create an HTTP(s) connection](https://www.servicenow.com/docs/access?context=create-https-connection&version=brazil&pubname=brazil-platform-security&ft:locale=en-US).
{#import-attachment-package-version__ul_cgx_mdx_gxb}

Role required: sn_rpa_fdn.rpa_release_manager or sn_rpa_fdn.rpa_admin

## About this task

The maximum package size is determined by the com.glide.attachment.max_size system property. For more information about this system property, [Maximum allowed attachment size](https://www.servicenow.com/docs/access?context=sc-max-allowed-attachment-size&version=brazil&pubname=brazil-platform-security&ft:locale=en-US).

Perform this task if you are automatically migrating the package attachment (automation zip file) from a lower (non-production) to a higher (production) environment.

Another way to import package version attachments automatically is via triggering the Import Package Version Attachment Subflow in Workflow Studio. For more information, see [Workflow Studio actions and subflow in RPA Hub](https://www.servicenow.com/docs/FX0I6PkBXL8cOAh00m_fwQ "Two-way integration of actions and subflows in Workflow Studio and RPA Hub for a seamless robot execution.").

## Procedure

1. Navigate to AllRobotic Process AutomationRPA Hub Workspace.
2. Select the list icon (![List icon.]()).
3. On the Lists tab, under Build, select Packages.
4. Open a package whose package version you want to import.
5. On the Package Versions tab, select a version that you want to import.
6. Select Import Attachment.
7. In the Confirmation dialog box, select Import Attachment.

## Result

After the attachment is uploaded successfully or if an error occurs while uploading the attachment, an email notification is sent to the user who performs this import attachment action.

## What to do next

For a quick integrity check, verify the HashCode of a package version again. For more information, see [Verify the HashCode of a package version in RPA Hub](https://www.servicenow.com/docs/zdSfLHhNxIauHu3xjIgusg "Verify the HashCode of a package version in RPA Hub so that you can validate the HashCode of the manually uploaded automation zip file with the associated package version record.").

*[\>]: and then