Actions32
- Card Actions
- Organization Actions
- Pipe Actions
- Phase Actions
- Table Actions
- Table Record Actions
- User Actions
- Webhook Actions
Overview
This node integrates with the Pipefy API to manage various resources such as cards, organizations, users, pipes, phases, tables, table records, and webhooks. Specifically for the Card resource and the Upload Attachment operation, it allows users to upload a file as an attachment to an existing card in Pipefy.
Common scenarios where this node is beneficial include automating project management workflows by programmatically adding attachments (e.g., documents, images) to task cards, enabling seamless collaboration and record-keeping within Pipefy boards.
Example use case: Automatically attaching a generated PDF report or image to a specific card when certain conditions are met in your workflow.
Properties
| Name | Meaning |
|---|---|
| File | The file to upload as an attachment. This should be provided as a string representing the file content or a reference to the file. |
Output
The output JSON contains details about the uploaded attachment, including:
id: The unique identifier of the attachment.filename: The name of the uploaded file.url: The URL where the attachment can be accessed.created_at: Timestamp of when the attachment was created.
This output confirms that the attachment was successfully added to the specified card.
Dependencies
- Requires an active connection to the Pipefy API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The node sends GraphQL requests to
https://api.pipefy.com/graphql.
Troubleshooting
Common issues:
- Invalid or missing card ID: Ensure the card ID parameter is correctly set and refers to an existing card.
- Incorrect file input: The file property must be properly formatted; if referencing binary data, ensure it is correctly encoded or accessible.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network or API downtime: Check connectivity and Pipefy service status.
Error messages:
- Errors returned from the API will typically indicate the cause, such as "card not found" or "invalid file format."
- If the node throws an error related to request failure, check the API key and network settings.
To resolve errors, verify all input parameters, confirm API credentials, and consult Pipefy API documentation for any restrictions on file uploads.