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-related data. Specifically, the "Delete a Link Share" operation under the "Project" resource allows users to delete an existing link share associated with a project. This is useful for scenarios where shared access to a project via a link needs to be revoked, such as when a project is completed or when access permissions need tightening.
Practical examples:
- Removing public or external access links to a project after its completion.
- Revoking shared links that were mistakenly created or are no longer needed.
- Managing project security by controlling who can access project information through shared links.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The target project to operate on. Can be selected from a searchable list of projects or specified directly by its ID. |
| Link Share ID | The unique numeric identifier of the link share to delete from the specified project. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will confirm whether the link share was successfully deleted. The exact structure depends on the Vikunja API response but generally includes status information.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Vikunja API.
- The base URL for the Vikunja API must be configured in the node credentials.
- The node uses HTTP requests to interact with the Vikunja API endpoints.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Project ID or Link Share ID will cause the deletion to fail.
- Network connectivity problems or incorrect API URL configuration can prevent successful API calls.
- Insufficient permissions associated with the API key may lead to authorization errors.
Error messages and resolutions:
- 404 Not Found: The specified project or link share does not exist. Verify the IDs used.
- 401 Unauthorized: Authentication failed. Check that the API key credential is valid and has necessary permissions.
- 400 Bad Request: Input parameters might be malformed or missing. Ensure all required fields are correctly filled.
- Network Errors: Confirm network connectivity and correct API endpoint URL.
Links and References
- Vikunja API Documentation – Official API reference for understanding available endpoints and request/response formats.
- n8n Documentation – General guidance on using n8n nodes and managing credentials.