Pipefy icon

Pipefy

Interact with Pipefy GraphQL API

Actions17

Overview

This node interacts with the Pipefy platform to create a presigned URL for an attachment. A presigned URL is a temporary link that allows secure upload or access to a file without requiring direct authentication. This operation is useful when you want to upload files to Pipefy attachments securely and efficiently, for example, automating document uploads related to cards or processes in Pipefy.

Practical scenarios include:

  • Automating the upload of invoices or receipts as attachments to Pipefy cards.
  • Generating secure upload links for users or systems to add files without exposing credentials.
  • Integrating external file storage workflows with Pipefy by generating URLs for file transfer.

Properties

Name Meaning
Authentication Method of authenticating with Pipefy API: either using a Service Account or a Personal Access Token.
Org Name or ID The identifier of the organization within Pipefy where the attachment will be created. Can be selected from a list or specified via expression.
Filename The name of the file to be attached. This will be the filename displayed on the Pipefy field.
ℹ️ This will be the name of the file displayed on Pipefy field. Informational notice clarifying that the filename property sets the display name of the attachment in Pipefy.

Output

The node outputs a JSON array containing the result of the presigned URL creation. The key information typically includes the generated presigned URL which can be used to upload the file securely. The output structure will have fields relevant to the presigned URL details (such as URL string, expiration time, etc.), although exact keys are not explicitly shown in the source code.

No binary data output is indicated for this operation.

Dependencies

  • Requires valid authentication credentials for Pipefy, either via a service account or personal access token.
  • Needs access to the Pipefy GraphQL API.
  • The node depends on n8n's ability to load organization options dynamically (getOrgs method).
  • No additional external dependencies beyond the Pipefy API and n8n environment.

Troubleshooting

  • Common issues:
    • Invalid or expired authentication tokens will cause authorization failures.
    • Incorrect organization ID may lead to errors or empty results.
    • Missing or invalid filename could cause the API to reject the request.
  • Error messages:
    • Authorization errors suggest checking the provided API credentials.
    • Validation errors on filename or org ID require verifying input values.
  • Resolution tips:
    • Ensure the correct authentication method is selected and credentials are valid.
    • Use the dynamic dropdown to select a valid organization or verify the expression syntax.
    • Provide a non-empty, valid filename string.

Links and References

Discussion