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 Membership operation for the 📋 BOARD resource in this n8n node allows you to update the role (permissions) of a member within a specific board in Planka. This is useful for managing team collaboration by promoting or demoting users' access levels (e.g., from Editor to Admin or vice versa) on a board.
Common scenarios:
- Changing a user's permissions after their responsibilities change.
- Automating permission updates as part of onboarding/offboarding workflows.
- Ensuring only authorized users have admin rights on sensitive boards.
Practical example:
If a user needs to be promoted to an admin on a project board, this node operation can be used in an automated workflow to update their membership role accordingly.
Properties
| Name | Type | Meaning |
|---|---|---|
| Membership ID | String | The unique identifier of the board membership to update. |
| Role | Options | The new role to assign to the member. Possible values: "Admin", "Editor". |
Output
The output will be a JSON object representing the updated board membership. The structure typically includes fields such as:
{
"id": "string",
"userId": "string",
"boardId": "string",
"role": "string",
"canComment": true,
// ...other membership details
}
id: The membership's unique identifier.userId: The user's unique identifier.boardId: The board's unique identifier.role: The updated role ("admin" or "editor").canComment: Indicates if the user can comment (if applicable).
Note: The exact structure may vary depending on the Planka API response.
Dependencies
- Planka API: Requires a valid Planka instance accessible via HTTP(S).
- API Credentials: You must configure the
plankaApicredentials in n8n with appropriate access rights.
Troubleshooting
Common issues:
- Invalid Membership ID: If the provided Membership ID does not exist, the API will likely return a "Not Found" error.
- Insufficient Permissions: If your API credentials lack permission to update memberships, you'll receive an authorization error.
- Role Value Error: Supplying an invalid value for the Role property will result in a validation error.
Error messages and resolutions:
"Membership not found": Check that the Membership ID is correct and exists in Planka."Unauthorized"or"Forbidden": Ensure your API credentials have sufficient privileges."Invalid role": Use only the allowed options: "admin" or "editor".
