Overview
This node enables managing Pipefy cards by performing various operations such as creating, updating, retrieving, searching, moving between phases, and deleting cards. Specifically, the Delete Card operation removes a card from Pipefy based on its unique identifier.
Common scenarios for using this node include automating workflow cleanups by deleting obsolete or completed cards, integrating Pipefy with other systems to maintain synchronized data, or building custom management tools that require programmatic control over Pipefy cards.
For example, you might use this node in an automation that deletes cards after a project phase is completed or when certain conditions are met in another system.
Properties
| Name | Meaning |
|---|---|
| Card ID | The unique identifier of the card to delete. This is required to specify which card should be removed. |
Output
The output JSON contains the result of the delete operation with the following fields:
success(boolean): Indicates whether the deletion was successful.cardId(string): The ID of the card that was requested to be deleted.message(string): A human-readable message indicating success ("Card deleted successfully") or failure ("Failed to delete card").
No binary data is output by this operation.
Example output:
{
"success": true,
"cardId": "123456",
"message": "Card deleted successfully"
}
Dependencies
- Requires an API key credential for authenticating with Pipefy's API.
- Requires a second API authentication token credential specific to the n8n Tools integration.
- The node uses internal utility functions to format dates and validate required fields.
- The Pipefy GraphQL API is used under the hood to perform the delete operation.
Troubleshooting
- Missing Card ID: If the Card ID property is not provided or empty, the node will throw an error indicating that the Card ID is required.
- API Authentication Errors: Ensure that valid API credentials are configured in n8n; otherwise, requests to Pipefy will fail.
- Deletion Failure: If the card does not exist or cannot be deleted due to permissions, the
successfield will be false and the message will indicate failure. - Network Issues: Connectivity problems with the Pipefy API can cause errors; verify network access and API availability.