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
- Task Actions
- Team Actions
- Webhook Actions
Overview
This node integrates with the Vikunja API to manage project data. Specifically, the "Delete" operation under the "Project" resource allows users to remove a project from their Vikunja workspace by specifying the project either via its title (selected from a list) or directly by its ID.
Common scenarios for this node include:
- Automating cleanup of completed or obsolete projects.
- Integrating project deletion into larger workflows where project lifecycle management is required.
- Removing test or temporary projects created during automated testing or data migration.
Example use case: A user wants to delete a project named "Marketing Campaign 2024" after the campaign ends. They can select the project from a searchable list or provide its ID to delete it automatically as part of a scheduled workflow.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The project to delete. Can be selected from a searchable list of existing projects or specified directly by its ID. This property is required. |
The "Project Title or ID" property supports two modes:
- From List: Search and select a project by its title.
- ID: Provide the unique identifier of the project directly.
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 about the deleted project. No binary data output is involved.
Dependencies
- Requires an active connection to the Vikunja API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL for the Vikunja API must be set correctly in the credential configuration.
Troubleshooting
Common issues:
- Providing an invalid or non-existent project ID will cause the deletion to fail.
- Insufficient permissions or incorrect API credentials may result in authorization errors.
- Network connectivity problems can prevent communication with the Vikunja API.
Error messages and resolutions:
- "Project not found": Verify the project ID or ensure the project exists.
- "Unauthorized" or "Forbidden": Check that the API key or token has the necessary permissions.
- Timeout or network errors: Confirm network access to the Vikunja server and correct API URL.