---
title: "Relay Pull Attachment Action"
slug: "relay-pull-attachment-action"
updated: 2025-09-05T15:06:40Z
published: 2025-09-05T15:06:40Z
canonical: "docs.relaynetwork.com/relay-pull-attachment-action"
excludeFromExternalSearch: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.relaynetwork.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Relay Pull Attachment Action

The **RelayPullAttachmentAction**, is used to pull a Relay Power-up file attachment submission (e.g. images, files). Once downloaded, the action will automatically create a new Salesforce **ContentDocument** and link it to the object specified by the **Linked Entity Id** property.

This flow action is always executed in a background job. If an error occurs during the attachment download, a record will be created in the [RelayLog__c](/docs/relaylog-c) custom object.

WARNINGThis action makes an external callout to Relay Network. Please be aware of any impacts this has against your Sales*f*orce API limits. [Salesforce Callout Limits](https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_callouts_timeouts.htm)

## Action Properties

| Field | Description |
| --- | --- |
| RelayPowerups__c event | A Relay power-up event record with the **Name** field value of **Powerups Data Artifact Available**. Typically, this is the record that triggered the flow. This event record contains specific details about the file attachment. |
| Description | A description of the file attachment. This will populated on the created **ContentDocument** record. |
| DocumentLink Share Type | The permission granted to the user of the shared file in a library. This is determined by the permission the user already has in the library. If this field is not provided, then the value of **V** will be used. Valid values are: - **V** — Viewer permission. The user can explicitly view but not edit the shared file. This is the default value if not provided. - **C** — Collaborator permission. The user can explicitly view and edit the shared file. You can retrieve the ShareType for ContentDocumentLink, but you can't create a ContentDocumentLink with a ShareType of C from an Apex trigger. - **I** — Inferred permission. The user’s permission is determined by the related record. For shares with a library, this is defined by the permissions the user has in that library. Inferred permission on shares with libraries and file owners is available in API versions 21.0 and later. Inferred permission on shares with standard objects is available in API versions 36.0 and later. See Salesforce docs: [ContentDocumentLink](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_contentdocumentlink.htm) |
| Document Link Visibility | Specifies whether this file is available to all users, internal users, or shared users. If this field is not provided, then the default value of **AllUsers** will be used. Valid values are: - **AllUsers** — The file is available to all users who have permission to see the file. This is the default value if not provided. - **InternalUsers** — The file is available only to internal users who have permission to see the file. - **SharedUsers** — The file is available to all users who can see the feed to which the file is posted. SharedUsers is used only for files shared with users, and is available only when an org has private org-wide sharing on by default. The SharedUsers value is available in API version 32.0 and later. See Salesforce docs: [ContentDocumentLink](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_contentdocumentlink.htm) |
| Linked Entity Id | **Required**. This field identifies the Salesforce entity (record) that will be linked to the **ContentDocument***.* For example, this could be the **Id** field of a Person Account object. See Salesforce docs: [ContentDocumentLink](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_contentdocumentlink.htm) |

## Action Property Dialog

![](https://cdn.us.document360.io/6738087b-455d-402f-b70a-a44a4231547e/Images/Documentation/rn-sfdc-flow-properties-relay_pull_attachment.png)

## Action Response Variable

This action returns a custom Relay object **RelayPullAttachmentAction.PullAttachmentResponse.**

| Field | Description |
| --- | --- |
| statusCode | Valid values are: - **202:** Accepted, the attachment will be downloaded in a background job. The **statusMessage** field will contain the value **Accepted**. - **400:** There was an error with one of the request parameters. Review the **statusMessage** field for a description of the error. |
| statusMessage | A description related to the returned **statusCode**. |

The business **feed** is a new, personalized business to consumer channel that offers the rich usability and familiarity of scrolling feeds with the timeliness of SMS texting. The feed is a mobile web application that requires no app downloads.

## Related

- [Example 6: Save Relay Power-up Attachment to Salesforce](/example-6-save-relay-power-up-attachment-to-salesforce.md)
- [RelayLog__c](/relaylog-c.md)