Pipefy

Overview

This node allows uploading a file as an attachment to Pipefy using a presigned URL. It is useful when you want to add files to Pipefy cards or other entities that support attachments without directly handling file storage or API multipart uploads. The node expects binary data from the input and uploads it to the provided presigned URL, which is typically generated by another operation.

Practical examples:

• Uploading a document or image to a Pipefy card after generating a presigned URL.
• Automating file attachments in workflows where files are processed or generated dynamically.
• Integrating external file sources with Pipefy by first obtaining a presigned URL and then uploading the file content.

Properties

Output

The node outputs a JSON array containing the results of the upload operation for each input item. Each output item corresponds to one input item and includes the response or status from the upload process.

If the node handles binary data, it uses the specified binary field name to read the file content but does not output binary data itself; instead, it returns JSON indicating success or failure of the upload.

Dependencies

• Requires a valid presigned URL to upload the file.
• Requires authentication either via a service account credential or a personal access token credential configured in n8n.
• The node depends on the Pipefy API ecosystem, specifically the ability to generate presigned URLs (usually via another Pipefy operation).
• No additional external libraries beyond those bundled with the node are required.

Troubleshooting

• Common issues:

  • Invalid or expired presigned URL: The upload will fail if the URL is no longer valid or has expired.
  • Incorrect binary field name: If the specified binary field does not exist in the input data, the upload cannot proceed.
  • Authentication errors: Using incorrect or expired credentials will prevent the node from functioning properly.

• Error messages and resolutions:

  • "Presigned URL is invalid or expired": Verify that the presigned URL is freshly generated and correctly passed to the node.
  • "Binary data not found in the specified field": Check that the input data contains binary data under the exact field name provided.
  • Authentication failures: Ensure that the selected authentication method is properly configured with valid credentials.

Links and References

• Pipefy API Documentation
• How to create presigned URLs in Pipefy
• n8n Documentation on Binary Data Handling