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 "Add Member to Card" operation for the 📝 CARD resource in this n8n node allows you to assign a user as a member to a specific card within the Planka project management platform. This is useful for automating team assignments, ensuring that tasks (cards) are properly delegated to users, and integrating Planka with other workflow tools.
Common scenarios:
- Automatically assigning new cards to users based on workflow logic.
- Integrating with external systems (e.g., CRM, helpdesk) to add responsible users to cards when certain triggers occur.
- Bulk-adding members to cards as part of onboarding or project setup automation.
Example:
When a support ticket is created in another system, an n8n workflow can create a corresponding card in Planka and use this operation to assign the responsible support agent as a member of that card.
Properties
| Name | Type | Meaning |
|---|---|---|
| Card ID | String | The unique identifier of the card where the member will be added. |
| User ID | String | The unique identifier of the user to be added as a member to the card. |
Output
The output will be a JSON object representing the result of the "add member to card" action. Typically, this includes details about the card membership that was created, such as IDs and possibly user/card references, depending on the Planka API response.
Example output structure:
{
"id": "membershipId",
"cardId": "cardId",
"userId": "userId",
// ...other fields as returned by Planka API
}
If the operation fails and "Continue On Fail" is enabled, the output will include an error message:
{
"error": "Error message"
}
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 beyond standard credential setup.
Troubleshooting
Common issues:
- Invalid Card ID or User ID: If either ID does not exist, the API will return an error.
- Permission Denied: The authenticated user may lack permission to add members to the specified card.
- User Already a Member: Attempting to add a user who is already a member may result in an error or a no-op, depending on the API.
Error messages:
"Card not found": Check that the Card ID is correct and exists in Planka."User not found": Verify the User ID is valid."Unauthorized": Ensure your API credentials are correct and have sufficient permissions."An unknown error occurred": A generic fallback if the error is not specifically handled.
Resolution steps:
- Double-check Card ID and User ID values.
- Confirm API credentials and permissions.
- Review Planka server logs for more detailed error information if available.
