Actions57
- Team Actions
- Webhook Actions
- 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
Overview
This node integrates with the Vikunja API to manage projects and other resources. Specifically, for the Project - Delete operation, it allows users to delete a project from their Vikunja instance by specifying the project either via selection from a list or by providing its ID directly.
Common scenarios where this node is beneficial include:
- Automating cleanup of completed or obsolete projects.
- Integrating project lifecycle management into broader workflows.
- Managing projects programmatically without manual intervention in the Vikunja UI.
For example, a user might set up an automation that deletes projects older than a certain date or removes test projects created during development cycles.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The project to delete. Can be selected from a searchable list of existing projects or specified by its unique ID. |
The property supports two modes:
- From List: Search and select a project by title.
- ID: Provide the exact project ID as a string.
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 operation failed.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to a Vikunja API instance.
- Needs an API authentication token credential configured in n8n to authorize requests.
- The base URL for the Vikunja API must be provided in the credentials configuration.
Troubleshooting
Common Issues:
- Providing an invalid or non-existent project ID will cause the deletion to fail.
- Insufficient permissions or incorrect API credentials can lead to authorization errors.
- Network connectivity issues may prevent communication with the Vikunja API.
Error Messages:
- "Project not found": Verify the project ID or selection is correct.
- "Unauthorized" or "Forbidden": Check API credentials and permissions.
- Timeout or network errors: Ensure the API URL is reachable and correct.
Resolving these typically involves verifying input values, checking API credentials, and ensuring network access.