Actions46
- 🏢 PROJECT Actions
- 📋 BOARD Actions
- 📝 CARD Actions
- ➕ Create Card
- 🔍 Get Card
- ✏️ Update Card
- 🗑️ Delete Card
- 🏷️ Add Label to Card
- 🚫 Remove Label from Card
- 👤 Add Member to Card
- 🚫 Remove Member from Card
- ✅ Create Task in Card
- 🔄 Update Task
- 🗑️ Delete Task
- 📎 Create Attachment in Card
- ✏️ Update Attachment
- 🗑️ Delete Attachment
- 📋 Get All Card Actions
- 💬 Create Comment on Card
- ✏️ Update Comment
- 🗑️ Delete Comment
- 👤 USER Actions
Overview
The 🗑️ Delete Card operation in the Planka n8n node allows you to permanently delete a card from your Planka project management system. This is useful for automating workflows where cards (tasks, issues, or items) need to be programmatically removed based on certain criteria, such as completion, duplication, or error correction.
Common scenarios:
- Automatically cleaning up completed or obsolete cards.
- Removing cards that were created by mistake.
- Integrating with other systems to synchronize deletions across platforms.
Example use case:
When a task is marked as "archived" in another system, trigger this node to delete the corresponding card in Planka.
Properties
| Name | Type | Meaning |
|---|---|---|
| Card ID | String | The unique identifier of the card to delete. This is required to specify which card will be deleted from Planka. |
Output
- On success, the output will contain the JSON response from the Planka API after deleting the card. Typically, this may be an empty object or a confirmation message, depending on the API's behavior.
- On failure (if "Continue On Fail" is enabled), the output will include an
errorfield with the error message.
Example output (success):
[
{
"json": {}
}
]
Example output (failure, continue on fail):
[
{
"json": {
"error": "Card not found"
}
}
]
Dependencies
- Planka API: Requires access to a running Planka instance.
- API Credentials: You must configure the
plankaApicredentials in n8n for authentication. - n8n Configuration: No special environment variables are needed beyond standard credential setup.
Troubleshooting
Common Issues:
- Invalid Card ID: If the provided Card ID does not exist, the API will return an error (e.g., "Card not found").
- Authentication Failure: If the API credentials are missing or incorrect, the request will fail with an authentication error.
- Insufficient Permissions: The user associated with the API key must have permission to delete cards.
Error Messages and Resolutions:
"Card not found": Ensure the Card ID is correct and the card exists."Unauthorized"or"Forbidden": Check your API credentials and user permissions."An unknown error occurred": This is a generic fallback; check network connectivity and API status.
