Actions17
- Attachment Actions
- Card Actions
- Webhook Actions
- Pipe Actions
- User Actions
Overview
This node interacts with the Pipefy GraphQL API to delete a specific card identified by its Card ID. It supports authentication via either a Service Account or a Personal Access Token. This node is useful in automation workflows where you need to programmatically remove cards from Pipefy, such as cleaning up completed tasks or managing project boards.
Use Case Examples
- Automatically delete a card when a related task is marked as done in another system.
- Remove outdated or duplicate cards from a Pipefy board as part of a scheduled cleanup process.
Properties
| Name | Meaning |
|---|---|
| Authentication | Selects the authentication method to use for API requests, either Service Account or Personal Access Token. |
| Card ID | The unique identifier of the card to delete. This ID can be found in the card's URL in Pipefy (e.g., https://app.pipefy.com/open-cards/\[ID\]). This property is required. |
Output
JSON
success- Indicates whether the card deletion was successful (true or false).message- A message providing additional information about the deletion result, such as confirmation or error details.
Dependencies
- Requires authentication credentials: either a Service Account API key or a Personal Access Token for Pipefy API access.
Troubleshooting
- Ensure the Card ID is correct and exists in Pipefy; an invalid or non-existent Card ID will cause the deletion to fail.
- Verify that the selected authentication method is valid and the credentials have sufficient permissions to delete cards.
- Common error messages may include authorization errors if the token is invalid or expired, or not found errors if the card does not exist.
Links
- Pipefy GraphQL API Documentation - Official documentation for the Pipefy API, including how to authenticate and manage cards.