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 Remove Label from Card operation in the Planka n8n node allows you to remove a specific label from a card within your Planka project management system. This is useful for automating workflows where labels are used to categorize, prioritize, or track the status of cards (tasks), and you need to programmatically update these labels based on certain triggers or conditions.
Common scenarios:
- Automatically removing a "To Review" label when a card moves to a "Done" list.
- Cleaning up outdated or incorrect labels as part of a regular maintenance workflow.
- Integrating with other systems to synchronize label changes based on external events.
Practical example:
When a support ticket (card) is resolved, an automation removes the "Urgent" label from the card to reflect its new status.
Properties
| Name | Type | Meaning |
|---|---|---|
| Card ID | String | ID of the card from which to remove the label. |
| Label ID | String | ID of the label to be removed from the card. |
Output
The output will be a JSON object representing the result of the label removal operation. Typically, this includes confirmation of the action or the updated state of the card after the label has been removed. The exact structure depends on the Planka API response, but it generally contains at least the card's details.
Example output:
{
"id": "123",
"name": "Sample Card",
"labels": [
// ...remaining labels after removal
],
// ...other card fields
}
If an error occurs and "Continue On Fail" is enabled, the output will include an error message:
{
"error": "Error message here"
}
Dependencies
- Planka API: Requires access to a running Planka instance.
- API Credentials: You must configure the
plankaApicredentials in n8n for authentication.
Troubleshooting
Common issues:
- Invalid Card ID or Label ID: If either ID does not exist, the operation will fail.
- Insufficient Permissions: The API user must have permission to modify the specified card and its labels.
- Network/API Errors: Connectivity issues or misconfigured API endpoints can cause failures.
Error messages:
"Card not found"or"Label not found": Check that both IDs are correct and exist in Planka."Unauthorized": Ensure your API credentials are set up correctly in n8n."An unknown error occurred": This generic message may appear if the error is not specifically handled; check logs or API responses for more details.
