Planka

Overview

The Get All Card Actions operation for the 📝 CARD resource in this n8n node retrieves a list of all actions performed on a specific card within Planka (an open-source project management tool). Actions may include comments, status changes, assignments, and other activity logs related to the card. This is useful for tracking the history and collaboration around a card, auditing changes, or triggering automations based on card activity.

Practical scenarios:

• Auditing who made changes to a card and when.
• Building activity feeds or notifications for team members.
• Integrating with reporting tools to analyze card usage and workflow patterns.

Properties

Output

The output is an array of objects, each representing an action performed on the specified card. Each object is returned under the json field.

Typical structure:

[
  {
    "json": {
      "id": "actionId",
      "type": "comment", // or other action types
      "createdAt": "2024-06-01T12:34:56Z",
      "userId": "userId123",
      "cardId": "cardId456",
      "data": { /* action-specific data */ }
      // ...other fields depending on 'withDetails'
    }
  },
  ...
]

• If With Details is enabled, additional nested information about users, attachments, etc., may be included.

Dependencies

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

Troubleshooting

Common issues:

• Invalid Card ID: If the provided Card ID does not exist, the node will throw an error such as Card not found.
  • Resolution: Double-check the Card ID value.
• Insufficient Permissions: If the API credentials lack permission to view the card or its actions, you may receive a 403 Forbidden or similar error.
  • Resolution: Ensure your API user has access to the relevant board/card.
• Network/API Errors: Connectivity issues or incorrect API base URL can result in errors like ENOTFOUND or ECONNREFUSED.
  • Resolution: Verify the Planka instance URL and network connectivity.

If "Continue On Fail" is enabled, errors will be returned in the output as:

{
  "json": {
    "error": "Error message here"
  }
}

Links and References

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

This operation is ideal for anyone needing to monitor, audit, or react to all activities on a Planka card directly from n8n workflows.