ProjectFlow icon

ProjectFlow

Manage ProjectFlow items, comments and attachments

Actions14

Attachment → Download

AI-generated

Summary

Downloads a file attachment from a ProjectFlow item and returns it as binary data on the output item.

Inputs

  • authentication — Credential type to use: Personal Token (default) or OAuth2. The base URL comes from the selected credential.
  • itemId (required) — ID of the ProjectFlow item that owns the attachment.
  • attachmentId (required) — ID of the attachment to download.
  • binaryPropertyName (required) — Name of the output binary field that receives the file. Defaults to 'data'.

Output shape

One output item per input item. The JSON contains { itemId, attachmentId }. The file is in the binary field named by 'Put Output File in Field'. The item is paired to its input item.

The request is GET /api/v1/items/{itemId}/attachments/{attachmentId}/download, and the response is read as raw bytes. The binary data is built from the buffer alone, so the original filename and MIME type from ProjectFlow are not set explicitly. The attachment's metadata is not returned. If 'Continue on Fail' is enabled, a failed item yields { error: message } instead of stopping the workflow.

Examples

Example 1: Save an item's attachment to cloud storage

Set Item ID and Attachment ID (for example from a previous Get Item step) and leave the output field as 'data'. Then connect an upload node that reads the 'data' binary field.

Example 2: Download attachments for many items in one run

Use expressions for Item ID and Attachment ID, such as {{$json.itemId}} and {{$json.attachmentId}}. The node runs once per input item and returns one file per item.

Links

Discussion