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 Update Board operation in the Planka n8n node allows you to modify the details of an existing board within your Planka workspace. This is useful for keeping board information up-to-date, such as renaming a board or changing its position/order within a project.
Common scenarios:
- Renaming a board after a project phase changes.
- Reordering boards to reflect new priorities.
- Automating board updates as part of a workflow when certain triggers occur (e.g., after a project milestone).
Practical example:
You might use this node in an automation that updates the name and position of a board whenever a related record in another system (like a CRM or project management tool) is changed.
Properties
| Name | Type | Meaning |
|---|---|---|
| Board ID | String | The unique identifier of the board to update. |
| Name | String | The new name to assign to the board. |
| Position | Number | The new position/order of the board. |
Output
The output will be a JSON object representing the updated board. The structure typically includes fields such as:
{
"id": "string",
"name": "string",
"position": number,
// ...other board properties as returned by the Planka API
}
- If the update is successful, the output contains the full details of the updated board.
- If there is an error and "Continue On Fail" is enabled, the output will include an
errorfield with the error message.
Dependencies
- External Service: Requires access to a running Planka instance with API enabled.
- Authentication: Needs valid Planka API credentials configured in n8n under the credential type
plankaApi. - n8n Configuration: No special environment variables are required beyond standard credential setup.
Troubleshooting
Common issues:
- Invalid Board ID: If the provided Board ID does not exist, the API will return an error.
- Missing Required Fields: Both "Board ID" and "Name" are required; omitting them will cause the operation to fail.
- Insufficient Permissions: The API credentials must have permission to update boards.
Error messages:
"Board not found": Check that the Board ID is correct and exists in your Planka instance."Unauthorized": Ensure your API credentials are valid and have sufficient permissions."Validation failed": Make sure all required fields are filled and values are in the correct format.
How to resolve:
- Double-check the Board ID and ensure it matches an existing board.
- Verify your API credentials in n8n.
- Ensure all required input fields are provided and correctly formatted.
