Actions17
- Attachment Actions
- Card Actions
- Pipe Actions
- User Actions
- Webhook Actions
Overview
This node integrates with the Pipefy platform to delete a specific card identified by its unique ID. It is useful in automation workflows where you need to programmatically remove cards from Pipefy, such as cleaning up completed tasks, removing duplicates, or managing data lifecycle within your Pipefy pipelines.
For example, you might use this node to automatically delete cards that have been marked as obsolete or after certain conditions are met in your workflow, helping maintain an organized and up-to-date Pipefy environment.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose the authentication method: "Service Account" or "Personal Access Token" to authorize API calls. |
| Card ID | The unique identifier of the card to delete. This ID can be found in the URL when viewing the card in Pipefy (e.g., https://app.pipefy.com/open-cards/[ID]). Must be exactly 10 characters long. |
Output
The node outputs a JSON array containing the result of the delete operation for each input item. Typically, this will include confirmation of deletion or any error messages returned by the Pipefy API.
No binary data output is produced by this node.
Dependencies
- Requires access to the Pipefy GraphQL API.
- Requires either a service account credential or a personal access token for authentication.
- Proper configuration of these credentials in n8n is necessary for successful API communication.
Troubleshooting
- Invalid Card ID: If the Card ID is incorrect or does not exist, the API will return an error. Verify the Card ID by checking the URL in Pipefy.
- Authentication Errors: Using invalid or expired credentials will cause authentication failures. Ensure that the selected authentication method is correctly configured and the credentials are valid.
- Permission Issues: The authenticated user must have permission to delete cards in the specified Pipefy workspace.
- API Rate Limits: Excessive requests may trigger rate limiting; consider adding delays or handling retries.