Nextcloud Deck icon

Nextcloud Deck

Consume NextCloud Deck API (v.0.1.3)

Overview

This node interacts with the Nextcloud Deck API to manage stacks within boards. Specifically, the 'Get' operation under the 'Stacks' resource retrieves details of a specific stack identified by its Stack ID within a given Board ID. This is useful for users who want to fetch information about a particular stack in their project management or task organization workflows using Nextcloud Deck.

Use Case Examples

  1. Retrieve details of a specific stack by providing the Board ID and Stack ID to integrate stack information into automated workflows.
  2. Use the node to fetch stack data for reporting or synchronization with other tools.

Properties

Name Meaning
Authentication Method of authentication to access the Nextcloud Deck API, either via Access Token or OAuth2.
Board ID The unique identifier of the board containing the stack to retrieve.
Stack ID The unique identifier of the stack to retrieve within the specified board.

Output

JSON

  • id - The unique identifier of the retrieved stack.
  • title - The title or name of the stack.
  • order - The order or position of the stack within the board.
  • type - The type classification of the stack.
  • description - A description or details about the stack.
  • dueDate - The due date associated with the stack, if any.

Dependencies

  • Nextcloud Deck API

Troubleshooting

  • Ensure that the Board ID and Stack ID are correctly provided and correspond to existing entities in Nextcloud Deck.
  • Authentication errors may occur if the access token or OAuth2 credentials are invalid or expired; verify and refresh credentials as needed.
  • API request failures might result from network issues or incorrect API endpoint usage; check connectivity and parameter correctness.

Links

  • Nextcloud Deck - Official site for Nextcloud Deck, the project management tool this node integrates with.
  • Nextcloud Deck API Documentation - Official API documentation for Nextcloud Deck, useful for understanding available endpoints and data structures.

Discussion