Actions26
- Board Actions
- Stack Actions
- Karte Actions
- Kommentar Actions
- Anhang Actions
Overview
This node integrates with Nextcloud Deck, a project management tool that organizes tasks into boards, stacks, cards, and more. Specifically, the "Stack Abrufen" (Get Stack) operation under the "Stack" resource allows users to retrieve information about a particular stack within a board.
Typical use cases include:
- Automating retrieval of stack details for reporting or synchronization with other tools.
- Fetching stack data as part of a workflow that manages task progress or status updates.
- Integrating Nextcloud Deck stacks into broader project management pipelines.
For example, you might use this node to get the current state of a stack to trigger notifications when tasks move between stacks or to aggregate stack data for dashboards.
Properties
| Name | Meaning |
|---|---|
| Board | Select a board either from a searchable list or by entering its numeric ID. Represents the container of stacks. |
| Stack | Select a stack either from a searchable list or by entering its numeric ID. Represents the specific stack to retrieve. |
Details:
- Board: Required. You can choose a board from a list fetched dynamically or input its ID directly (must be a number).
- Stack: Required. Similarly, select a stack from a list or provide its numeric ID.
Output
The node outputs JSON data representing the requested stack's details. This typically includes properties such as the stack's name, position/order within the board, and possibly metadata like creation date or associated cards (depending on the API response).
No binary data output is involved in this operation.
Example output structure (simplified):
{
"id": 123,
"name": "To Do",
"position": 1,
"boardId": 45,
"createdAt": "2023-01-01T12:00:00Z"
}
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 Board or Stack ID: If you enter an invalid or non-numeric ID, the node will reject it due to regex validation. Ensure IDs are numeric.
- Resource Not Found: If the specified board or stack does not exist or is inaccessible, the API will return an error. Verify permissions and existence.
- Authentication Errors: Missing or incorrect API credentials will cause authentication failures. Confirm that the API key credential is correctly configured.
- Unknown Resource Error: If the resource parameter is set incorrectly, the node throws an "Unbekannte Ressource" (Unknown Resource) error.
- Continue On Fail: If enabled, errors per item will be returned as JSON objects with an
errorfield instead of stopping execution.