Plane

Overview

This node interacts with the Plane API to manage issue attachments within projects. Specifically, for the Issue Attachment resource and the Upload operation, it uploads a binary file as an attachment to a specified issue in a project.

Common scenarios where this node is beneficial include:

• Automatically attaching screenshots, logs, or other files to issues created or updated in a project management workflow.
• Integrating external systems that generate files needing to be linked to issues for better traceability.
• Enhancing issue tracking by programmatically adding relevant documents or media.

Practical example:

• After an error is detected in an application, a screenshot or log file is uploaded automatically to the corresponding issue in Plane, providing developers immediate access to diagnostic data.

Properties

Name	Meaning
Project ID	The unique identifier of the project containing the issue to which the attachment belongs.
Issue ID	The unique identifier of the issue to which the attachment will be uploaded.
Binary Property	The name of the binary property on the input item that contains the file data to upload.

Output

The output JSON contains the response from the Plane API after uploading the attachment. This typically includes metadata about the uploaded asset such as its ID, filename, URL, and other related information confirming successful upload.

If the node processes multiple items, the output is an array of such responses, one per uploaded file.

The node does not output binary data itself; it only uploads binary data received as input and returns the API's JSON response.

Dependencies

• Requires an active Plane API credential configured in n8n to authenticate requests.
• Input data must contain binary file data under the specified binary property.
• Uses HTTP POST requests with multipart/form-data encoding to upload files.

Troubleshooting

• No binary data exists on item!
  This error occurs if the input item does not contain any binary data. Ensure that the input to the node includes binary data (e.g., from a previous node like "Read Binary File").

• No binary data property "[name]" exists on item!
  The specified binary property name does not exist on the current item. Verify that the binary property name matches exactly the name of the binary field containing the file.

• API errors during upload
  Could be due to invalid project or issue IDs, insufficient permissions, or network issues. Confirm that the provided IDs are correct and that the API credentials have appropriate access rights.

• Continue On Fail behavior
  If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output array.

Links and References

• Plane API Documentation (general reference for endpoints and authentication)
• n8n documentation on working with binary data
• n8n documentation on credentials setup