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 remove an existing link share associated with a project. This is useful for scenarios where shared access to a project needs to be revoked, such as when a collaboration ends or when tightening security by disabling public or external links.
Practical examples include:
- Revoking a shared link that was previously sent to external collaborators.
- Cleaning up outdated or unused link shares to maintain project confidentiality.
- Automating project access management workflows by programmatically deleting link shares.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The target project to operate on. You can select a project from a searchable list or specify its ID directly. |
| Link Share ID | The unique numeric identifier of the link share you want 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 or an empty object indicating success.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Vikunja API.
- Needs an API authentication token credential configured in n8n to authorize requests.
- The base URL for the Vikunja API must be set correctly in the credentials.
Troubleshooting
Common Issues:
- Invalid or missing Link Share ID: Ensure the Link Share ID corresponds to an existing link share within the specified project.
- Incorrect Project ID or selection: Verify the project exists and the ID or selection mode is correct.
- Authentication errors: Confirm that the API key or token is valid and has sufficient permissions.
- Network or connectivity problems: Check the API URL and network access.
Error Messages:
- 404 Not Found: The specified link share or project does not exist. Double-check IDs.
- 401 Unauthorized: Authentication failed; verify API credentials.
- 400 Bad Request: Input parameters may be malformed or missing; ensure all required fields are provided.
Resolving these typically involves verifying input values, checking API credentials, and ensuring the Vikunja service is reachable.