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 Create Card operation for the 📝 CARD resource in this n8n node allows you to create a new card (task item) within a specified list on a Planka board. This is useful for automating task creation, ticketing, or workflow management processes where new cards need to be programmatically added to project boards.
Common scenarios:
- Automatically creating tasks from form submissions.
- Integrating with other systems (e.g., CRM, support tools) to generate cards for follow-up actions.
- Batch-adding cards based on external triggers or schedules.
Example:
When a new customer support request is received via email, an n8n workflow can use this node to create a corresponding card in the "Support Requests" list of your Planka board.
Properties
| Name | Type | Meaning |
|---|---|---|
| List ID | string | The ID of the list where the new card will be created. |
| Name | string | The title or name of the card. |
| Description | string | A detailed description of the card's content or purpose. |
| Due Date | dateTime | The due date/time for the card (optional). |
| Position | number | The position/order of the card within the list (default: 1). |
| Is Due Date Completed | boolean | Whether the due date is marked as completed (optional, default: false). |
Output
The node returns the details of the newly created card in the json field. The structure typically includes:
{
"id": "string",
"name": "string",
"description": "string",
"dueDate": "string|null",
"position": number,
// ...other card properties as provided by the Planka API
}
- The exact fields depend on the Planka API response but will always include at least the card's ID and the values you provided.
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 List ID: If the List ID does not exist, the API will return an error. Double-check that the List ID is correct.
- Missing Required Fields: The Name and List ID are required. Omitting them will cause the node to fail.
- Authentication Errors: Incorrect or missing API credentials will result in authorization errors.
Error messages:
"List not found": The provided List ID is invalid."Unauthorized": Check your Planka API credentials configuration."Validation failed": One or more required fields are missing or incorrectly formatted.
How to resolve:
- Ensure all required fields are filled.
- Verify the List ID exists in your Planka instance.
- Confirm your n8n credentials for Planka are set up correctly.
