Planka

Overview

The Remove Member from Card operation for the 📝 CARD resource in this n8n node allows you to unassign a user from a specific card in Planka, an open-source project management tool. This is useful in workflows where you need to automate the removal of card assignees, such as when a task is completed, reassigned, or when cleaning up memberships programmatically.

Practical examples:

• Automatically remove a user from a card when their related task is marked as done.
• Unassign users from cards as part of a bulk clean-up process.
• Integrate with HR or onboarding/offboarding processes to ensure users are removed from all cards upon leaving a team.

Properties

Note: The "User ID" property is required for this operation.

Output

The output will be a JSON object reflecting the result of the API call to remove the member from the card. Typically, this may include confirmation of the removal or details about the updated card membership status. If an error occurs and "Continue On Fail" is enabled, the output will contain an error field with the error message.

Example success output:

{
  "success": true,
  "message": "Member removed from card"
}

Example error output (if Continue On Fail is enabled):

{
  "error": "User not found on card"
}

Dependencies

• Planka API: Requires access to a running Planka instance with API enabled.
• API Credentials: You must configure the plankaApi credentials in n8n for authentication.

Troubleshooting

Common issues:

• Invalid User ID: If the provided User ID does not exist or is not assigned to the card, the API may return an error.
• Card Not Found: If the card does not exist, the operation will fail.
• Insufficient Permissions: The API credentials used must have permission to modify card memberships.

Error messages and resolutions:

• "User not found on card": Ensure the User ID is correct and that the user is currently a member of the card.
• "Card not found": Double-check the Card ID being used in the workflow.
• "Unauthorized": Verify that your Planka API credentials are valid and have sufficient permissions.

Links and References

• Planka GitHub Repository
• n8n Documentation: Custom Nodes
• Planka API Reference (if available)