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 Task in Card" operation for the 📝 CARD resource in this n8n node allows you to add a new task (also known as a checklist item or subtask) to an existing card within the Planka project management platform. This is useful for breaking down larger work items (cards) into smaller, actionable steps that can be tracked individually.
Common scenarios:
- Automating the creation of tasks when a new card is added.
- Integrating with other systems to automatically generate subtasks based on external triggers (e.g., from support tickets, bug reports, etc.).
- Streamlining workflows by programmatically managing checklists within cards.
Practical example:
When a new feature request card is created in Planka, use this node to automatically add a predefined set of implementation tasks to the card.
Properties
| Name | Type | Meaning |
|---|---|---|
| Card ID | String | The unique identifier of the card where the new task will be created. |
| Task Name | String | The name or title of the task to be added to the card. |
| Task Position | Number | The position/order of the task within the card's task list. |
| Is Completed | Boolean | Indicates whether the task should be marked as completed upon creation. |
Output
The node returns the details of the newly created task in the json field. The structure typically includes:
{
"id": "string", // Unique identifier of the created task
"name": "string", // Name/title of the task
"position": number, // Position/order in the card's task list
"isCompleted": boolean, // Completion status
"cardId": "string", // ID of the parent card
// ...other fields as provided by the Planka API
}
Note: The exact output fields depend on the Planka API response.
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 Card ID: If the provided Card ID does not exist, the API will return an error.
- Missing Required Fields: All required properties (Card ID, Task Name) must be provided.
- Authentication Errors: Incorrect or missing API credentials will result in authorization failures.
Error messages and resolutions:
"Card not found": Verify that the Card ID exists in your Planka instance."Missing parameter: name": Ensure the Task Name property is filled."401 Unauthorized": Check your Planka API credentials configuration in n8n.
