Nextcloud Deck icon

Nextcloud Deck

Verwalten Sie Ihre Nextcloud Deck-Boards, Stacks, Karten und mehr

Overview

The node "Nextcloud Deck" allows managing Nextcloud Deck resources such as Boards, Stacks, Cards, Comments, and Attachments. Specifically, the operation "Kommentar Abrufen" (Retrieve Comment) under the "Kommentar" (Comment) resource fetches comments associated with a card in a Nextcloud Deck board.

This node is useful for automating workflows that involve project management or task tracking within Nextcloud Deck. For example, you can retrieve comments on cards to analyze feedback, generate reports, or trigger notifications based on comment content.

Properties

Name Meaning
Board Select a Board from a list or specify its ID (must be a number).
Stack Select a Stack from a list or specify its ID (must be a number).
Karte (Card) Select a Card from a list or specify its ID (must be a number).
Kommentar ID The ID of the comment to retrieve (required when getting, updating, or deleting a comment).
  • Board, Stack, and Karte are resource locators that allow choosing either from a searchable list or by entering a numeric ID directly.
  • Kommentar ID is a string representing the unique identifier of the comment.

Output

The output JSON contains the data returned by the comment retrieval operation. This typically includes all details of the specified comment such as its content, author, timestamps, and any metadata provided by the Nextcloud Deck API.

If multiple input items are processed, the output will be an array of JSON objects each representing a comment's data.

The node does not output binary data for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Nextcloud Deck API.
  • The node depends on Nextcloud Deck being accessible via its API endpoint.
  • No additional external services are required beyond the Nextcloud Deck instance.

Troubleshooting

  • Invalid IDs: Ensure that Board, Stack, Card, and Comment IDs are numeric where required. Validation regex enforces this.
  • Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
  • Resource not found: If the comment or related resources do not exist or are inaccessible, the node will throw an error.
  • Continue on Fail: If enabled, errors for individual items will be captured in the output JSON under an error field instead of stopping execution.

Links and References

Discussion