Actions22
- Kanban Actions
- Meeting Actions
- Project Actions
- Team Actions
- User Actions
Overview
The node provides integration with a Workspace API, allowing users to update existing Kanban cards within their workspace. Specifically, the "Update Kanban Card" operation lets users modify various fields of a Kanban card such as its title, description, status, due date, completion state, priority, and responsible user details.
This node is beneficial in scenarios where automated workflows need to keep Kanban boards up-to-date based on external triggers or data changes. For example, when a task is completed in another system, this node can update the corresponding Kanban card's status and mark it as done automatically. It can also be used to assign tasks dynamically by changing the responsible user or adjusting priorities based on workflow logic.
Properties
| Name | Meaning |
|---|---|
| Kanban ID | Unique identifier of the Kanban card to update (required) |
| New Title | New title for the Kanban card |
| New Description | New description for the Kanban card; supports HTML formatting |
| New Status | New status value for the Kanban card |
| New Due Date | New due date for the Kanban card in ISO 8601 format |
| New Done | New completion status of the Kanban card (boolean) |
| New Priority | New priority level for the Kanban card; options: High, Normal, Low |
| New Responsible User ID | New user ID to assign responsibility for the Kanban card |
| New Responsible Commitment | New commitment status for the responsible user (boolean) |
Output
The node outputs JSON data representing the updated Kanban card after applying the changes. This output typically includes all the card's properties reflecting the new values set during the update operation.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the Kanban card, but this is not evident from the provided code and properties.
Dependencies
- Requires an API key credential and tenant information to authenticate requests against the Workspace API.
- The base URL for the API is configurable via credentials.
- The node sends HTTP requests with JSON payloads to the Workspace API endpoints.
Troubleshooting
- Missing Kanban ID: The update operation requires the unique Kanban ID. Omitting this will likely cause errors or failed updates.
- Invalid Date Format: The "New Due Date" must be in ISO 8601 format. Providing an incorrect format may result in API rejection.
- Permission Issues: Ensure the API key has sufficient permissions to update Kanban cards; otherwise, authorization errors may occur.
- Invalid User ID: Assigning a non-existent or unauthorized user ID as responsible may cause errors.
- API Connectivity: Network issues or incorrect API URL/tenant settings can prevent successful communication with the Workspace API.
Links and References
- ISO 8601 Date Format
- Workspace API documentation (refer to your Workspace API provider for detailed docs)