Planka icon

Planka

Interact with Planka API

Actions46

Overview

The Update Card operation for the 📝 CARD resource in this n8n node allows you to modify the details of an existing card within a Planka board. This is useful for keeping card information up-to-date, such as changing its name, description, due date, position in the list, or marking the due date as completed.

Common scenarios:

  • Renaming a card after requirements change.
  • Updating the card's description with new information.
  • Adjusting the due date or marking it as completed.
  • Reordering cards within a list by changing their position.

Practical example:
You might use this node in an automation where, after a form submission or a status update in another system, you want to automatically update the corresponding card in Planka to reflect the latest information.

Properties

Name Type Meaning
Card ID string The unique identifier of the card to update.
Name string The new name/title for the card.
Description string The updated description text for the card.
Due Date dateTime The new due date for the card (if applicable).
Position number The new position of the card within its list.
Is Due Date Completed boolean Whether the card's due date should be marked as completed (true/false).

Output

The output will be a single object (per input item) under the json field, containing the updated card data as returned by the Planka API. The structure typically includes all card properties, such as:

{
  "id": "string",
  "name": "string",
  "description": "string",
  "dueDate": "string|null",
  "position": number,
  "isDueDateCompleted": boolean,
  // ...other card fields as provided by Planka
}

Note: The exact fields depend on the Planka API response.

Dependencies

  • External Service: Requires access to a running Planka instance with API enabled.
  • Authentication: Needs valid Planka API credentials configured in n8n under the credential type plankaApi.

Troubleshooting

Common issues:

  • Invalid Card ID: If the provided Card ID does not exist, the API will return an error.
  • Missing Required Fields: Omitting required fields like Card ID or Name will result in validation errors.
  • Permission Denied: The API credentials used must have permission to update the specified card.

Error messages and resolutions:

  • "Card not found": Check that the Card ID is correct and exists in your Planka instance.
  • "Missing required parameter": Ensure all required fields are filled in the node configuration.
  • "Unauthorized": Verify that your Planka API credentials are correctly set up in n8n.

Links and References

Discussion