Planka

Overview

The Get Board operation for the 📋 BOARD resource in this n8n node retrieves detailed information about a specific board from a Planka instance, given its unique Board ID. This is useful for automating workflows that need to fetch board metadata, display board details, or use board data as input for further processing (e.g., listing cards, synchronizing boards with other systems, or reporting).

Practical examples:

• Fetching board details to display in dashboards.
• Using board information as context for creating or updating related entities (like lists or cards).
• Integrating Planka board data into project management reports.

Properties

Output

The output will be a single json object containing all available details of the requested board. The exact structure depends on the Planka API, but typically includes fields such as:

{
  "id": "string",
  "name": "string",
  "position": number,
  "projectId": "string",
  // ...other board properties as provided by Planka
}

• Each execution returns one item per input, with the board's full detail in the json field.

Dependencies

• Planka API: Requires access to a running Planka instance.
• API Credentials: You must configure the plankaApi credentials in n8n for authentication.
• n8n Configuration: No special environment variables are required beyond standard credential setup.

Troubleshooting

Common issues:

• Invalid Board ID: If the Board ID does not exist, the node will throw an error or return an error message in the output if "Continue On Fail" is enabled.
• Authentication Errors: Missing or incorrect API credentials will result in authentication failures.
• Network Issues: Connectivity problems between n8n and the Planka server can cause request failures.

Error messages and resolutions:

• "Request failed with status code 404": The specified Board ID does not exist. Double-check the ID.
• "Unauthorized" or "401": Check your Planka API credentials in n8n.
• "An unknown error occurred": Inspect the Planka server logs and ensure the API endpoint is reachable.

Links and References

• Planka GitHub Repository
• n8n Documentation: Custom Nodes
• Planka API Reference (if available)