Pipefy icon

Pipefy

Interact with Pipefy GraphQL API
Join our community

Actions17

Overview

This node interacts with the Pipefy platform via its GraphQL API. Specifically, for the Attachment resource and the Create Presigned URL operation, it generates a presigned URL that allows uploading an attachment file to Pipefy securely without requiring direct authentication in the upload request.

Common scenarios where this node is beneficial include:

  • Automating file uploads to Pipefy cards or processes.
  • Integrating external systems that generate files needing to be attached to Pipefy items.
  • Enabling secure, temporary access URLs for file uploads without exposing credentials.

For example, you might use this node to create a presigned URL for a report generated by another system, then upload that report as an attachment to a Pipefy card.

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 organization identifier within Pipefy where the attachment will be associated. Can be selected from a list or specified via expression.
Filename The name of the file to be uploaded as an attachment. This will be the filename shown in Pipefy.
ℹ️ 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 data returned includes the presigned URL itself, which can be used to upload the file directly to Pipefy's storage.

The output JSON structure typically contains fields such as:

  • url: The presigned URL string for uploading the attachment.
  • Possibly other metadata related to the upload session or attachment.

No binary data is output by this node; it only provides the URL for subsequent upload actions.

Dependencies

  • Requires valid authentication credentials for Pipefy API, either via a service account or personal access token.
  • Needs network access to Pipefy's GraphQL API endpoint.
  • The node relies on n8n's credential management to securely store and use the API keys.

Troubleshooting

  • Invalid Authentication: If the provided API key or token is invalid or expired, the node will fail to generate the presigned URL. Ensure credentials are correct and have necessary permissions.
  • Organization Not Found: Selecting or specifying an incorrect organization ID may cause errors. Verify the org ID exists and is accessible by the authenticated user.
  • Filename Issues: Providing an empty or invalid filename may cause the API to reject the request. Always specify a valid filename.
  • Network Errors: Connectivity issues to Pipefy API endpoints will prevent URL generation. Check internet connection and firewall settings.

Links and References

Discussion