ProjectFlow icon

ProjectFlow

Manage ProjectFlow items, comments and attachments

Actions14

Attachment → Upload

AI-generated

Summary

Uploads a binary file from the incoming n8n item to a ProjectFlow item as an attachment, via a multipart POST to /api/v1/items/{itemId}/attachments.

Inputs

  • authentication — Credential type: Personal Token (default) or OAuth2. Determines the credential and base URL used.
  • itemId (required) — ID of the ProjectFlow item the file is attached to.
  • binaryPropertyName (required) — Name of the input binary field holding the file (default 'data'). Execution fails for that item if the field doesn't exist.

Output shape

One or more JSON items per input item, containing the ProjectFlow API's response to the upload (typically the created attachment record). An array response is split into multiple output items. Each is paired to its input item.

The file is sent as multipart form field 'files', using the binary's original file name (fallback 'file') and MIME type. The exact response fields aren't defined in the node. With Continue On Fail enabled, failed items return {error: message} instead of stopping the workflow. Input binary data is not passed through to the output.

Examples

Example 1: Attach a file downloaded by an HTTP Request node to a ProjectFlow bug item.

Authentication: Personal Token; Item ID: the bug's ID (or an expression); Input Binary Field: data.

Example 2: Attach an email attachment received via a trigger to an item.

Item ID: ={{$json.itemId}}; Input Binary Field: attachment_0.

Links

Discussion