Actions57
- Label Actions
- Project Actions
- Add a Team
- Add a User
- Create
- Create a Kanban Bucket
- Create a Link Share
- Create a Project View
- Delete
- Delete a Kanban Bucket
- Delete a Link Share
- Delete a Project View
- Duplicate
- Get
- Get All Link Shares
- Get All Project Views
- Get All Teams
- Get All Users
- Remove a Team From a Project
- Remove a User From a Project
- Update
- Update a Kanban Bucket
- Update a Project View
- Update a Team's Rights on a Project
- Update a User's Rights on a Project
- Team Actions
- Task Actions
- Webhook Actions
Overview
The node integrates with the Vikunja API to manage tasks and other resources. Specifically, for the Task - Delete operation, it allows users to delete a task by specifying its unique Task ID. This is useful in workflows where tasks need to be programmatically removed based on certain conditions or triggers, such as cleaning up completed or obsolete tasks automatically.
Practical examples include:
- Automatically deleting tasks that are marked as done after a certain period.
- Removing tasks created by mistake via an automated process.
- Cleaning up tasks when a related project or label is deleted.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the task to delete. Must be provided as a number. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will confirm whether the deletion was successful or provide details if the task could not be deleted. The exact structure depends on the Vikunja API response but generally includes status information.
No binary data output is expected from this operation.
Dependencies
- Requires an API key credential to authenticate with the Vikunja API.
- The base URL for the Vikunja API must be configured in the node credentials.
- The node uses HTTP requests to communicate with the Vikunja REST API endpoints.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Task ID will result in an error from the API indicating the task was not found.
- Missing or incorrect API credentials will cause authentication failures.
- Network connectivity problems can prevent the node from reaching the Vikunja server.
Error messages and resolutions:
- "Task not found": Verify the Task ID is correct and the task exists.
- "Authentication failed": Check that the API key credential is valid and has necessary permissions.
- Timeout or network errors: Ensure the Vikunja server URL is reachable and there are no firewall restrictions.