Pipefy icon

Pipefy

Interact with Pipefy GraphQL API
Join our community

Actions17

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. Instead, the node uploads binary data to a presigned URL generated by Pipefy, which securely authorizes the upload.

Common scenarios include:

  • Automating the process of attaching documents, images, or other files to Pipefy cards.
  • Integrating external systems that generate files and need to push them into Pipefy workflows.
  • Using Pipefy's presigned URLs to handle large file uploads efficiently.

Example: You have a PDF report generated in your workflow and want to attach it to a Pipefy card. First, create a presigned URL with another operation, then use this node to upload the PDF binary data to that URL.

Properties

Name Meaning
Authentication Choose between authenticating with a Service Account or a Personal Access Token.
Presigned URL The presigned URL provided by Pipefy where the file will be uploaded.
ℹ️ You can get the presigned URL with the "Create presigned URL" operation. Informational notice guiding users to obtain the presigned URL before uploading.
Binary Field Name The name of the input field containing the binary data (file) to upload.

Output

The node outputs a JSON array where each item corresponds to one input item processed. The JSON output typically contains the response from the upload operation, which may be minimal since the actual upload is done via HTTP PUT to the presigned URL.

If the node supports binary data input, it does not output binary data itself but uses the binary data from the specified field to perform the upload.

Dependencies

  • Requires a valid authentication method: either a service account credential or a personal access token for Pipefy.
  • The user must first obtain a presigned URL from Pipefy (usually via a separate operation).
  • The node depends on n8n’s binary data handling capabilities to read the file content from the specified binary field.

Troubleshooting

  • Missing or invalid presigned URL: Ensure the presigned URL is correctly obtained and passed to the node. An incorrect or expired URL will cause upload failures.
  • Binary field not found or empty: Verify that the binary field name matches the input data and contains valid file data.
  • Authentication errors: Confirm that the selected authentication method is properly configured with valid credentials.
  • Upload failure due to network issues: Check connectivity and ensure the presigned URL endpoint is reachable.
  • File size limits: Be aware of any file size restrictions imposed by Pipefy or the presigned URL.

Links and References

Discussion