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 Get Card operation for the 📝 CARD resource in this n8n node retrieves detailed information about a specific card from a Planka instance, given its unique Card ID. This is useful for workflows that need to fetch and process card details, such as displaying card data, synchronizing with other systems, or triggering actions based on card properties.
Practical examples:
- Fetching card details to display them in a dashboard.
- Using card information to update another system (e.g., CRM, project management tool).
- Triggering notifications or automations when a card is accessed or updated.
Properties
| Name | Type | Meaning |
|---|---|---|
| Card ID | String | The unique identifier of the card to retrieve. Required for fetching the card details. |
Output
The output will be a JSON object containing all available details of the requested card as returned by the Planka API. The structure typically includes fields such as:
{
"id": "string",
"name": "string",
"description": "string",
"dueDate": "string",
"position": number,
"isDueDateCompleted": boolean,
// ...other card-specific fields provided by Planka
}
- The exact fields depend on the Planka API response for a card.
- No binary data is produced by this operation.
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 node will throw an error indicating the card was not found.
- Authentication errors: If the API credentials are missing or incorrect, you may receive authentication/authorization errors.
- Network issues: Connectivity problems between n8n and the Planka server can cause request failures.
Error messages and resolutions:
"Card not found": Check that the Card ID is correct and exists in your Planka instance."401 Unauthorized"or"403 Forbidden": Verify your Planka API credentials in n8n."An unknown error occurred": Inspect the input parameters and ensure the Planka service is reachable.
Links and References
- Planka GitHub Repository
- n8n Documentation: Creating Custom Nodes
- Planka API Reference (if available)
