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, and cards. Specifically, the "Karte Abrufen" (Get Card) operation allows users to retrieve detailed information about a specific card within a stack on a board.
Typical use cases include:
- Automating task tracking by fetching card details for reporting or synchronization with other tools.
- Integrating Nextcloud Deck cards into workflows that require card metadata or status.
- Building dashboards or notifications based on card updates.
For example, you might use this node to get the current state of a task card before updating it or to pull card details to send reminders or summaries via email.
Properties
| Name | Meaning |
|---|---|
| Board | Select a board from a searchable list or enter its numeric ID manually. Represents the container of stacks and cards. |
| Stack | Select a stack within the chosen board from a searchable list or enter its numeric ID manually. Stacks group related cards. |
| Karte | Select a card from a searchable list or enter its numeric ID manually. The specific card to retrieve. |
All three properties are required to identify the exact card to fetch.
Output
The output is a JSON object representing the retrieved card's data. This typically includes all relevant card details such as title, description, labels, assigned users, due dates, and other metadata managed by Nextcloud Deck.
No binary data output is indicated for this operation.
Example output structure (simplified):
{
"id": 123,
"title": "Task title",
"description": "Detailed description of the task",
"labels": ["urgent", "backend"],
"assignedUsers": [456, 789],
"dueDate": "2024-07-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 needed beyond Nextcloud Deck itself.
Troubleshooting
- Invalid IDs: If the board, stack, or card ID is incorrect or does not exist, the node will throw an error indicating the resource was not found. Verify IDs carefully.
- Authentication errors: Ensure the API key credential is valid and has sufficient permissions to access the requested resources.
- Network issues: Connectivity problems with the Nextcloud server can cause timeouts or failures.
- Permission issues: The authenticated user must have access rights to the specified board, stack, and card.
If the node is set to continue on failure, errors will be returned in the output JSON under an error field.
Links and References
- Nextcloud Deck Official Documentation
- Nextcloud Deck API Reference
- n8n documentation on Creating Custom Nodes