Caspio icon

Caspio

Interact with Caspio REST API.
Join our community

Actions21

Overview

This node allows users to download attachments from Caspio data sources, specifically from either a Table or a View. It is useful in scenarios where you need to retrieve and process file attachments stored within Caspio records, such as downloading user-uploaded documents or images for further automation or analysis.

Use Case Examples

  1. Downloading a PDF attachment from a specific record in a Caspio Table.
  2. Retrieving an image file stored in a Caspio View for use in another workflow.

Properties

Name Meaning
Data Source Type Select whether the attachment source is a Table or a View in Caspio.
Table Specify the Caspio Table to use as the attachment source. This property is required if 'Table' is selected as the Data Source Type.
View Specify the Caspio View to use as the attachment source. This property is required if 'View' is selected as the Data Source Type.
Attachment Field Name or ID Select or specify the attachment field from which to download the file. This field dynamically loads options based on the selected data source and table/view.
Record PK ID Provide the primary key ID of the record from which to download the attachment. This is required to identify the specific record.
Binary Property Name of the binary property where the downloaded attachment data will be stored in the workflow output.

Output

Binary

Contains the downloaded attachment file data stored under the specified binary property name.

JSON

  • attachmentData - The downloaded attachment file data in binary format.

Dependencies

  • Requires Caspio OAuth2 API credentials for authentication to access Caspio REST API.

Troubleshooting

  • Ensure the correct Data Source Type (Table or View) is selected to match the attachment source.
  • Verify the Table or View name is valid and accessible with the provided credentials.
  • Make sure the Attachment Field Name corresponds to a valid attachment field in the selected Table or View.
  • The Record PK ID must be accurate to locate the specific record containing the attachment.
  • Check that the binary property name is unique and does not conflict with other binary data in the workflow.

Links

Discussion