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 retrieve various data related to project management. Specifically, for the Project resource and the Get All Link Shares operation, it fetches all link shares associated with a specified project. This is useful when you want to list or manage all shared links that provide access to a project's content.
Common scenarios include:
- Auditing or reviewing all external links shared for a project.
- Managing permissions or visibility by identifying active link shares.
- Integrating with other systems to synchronize or log shared project links.
Example: You have a project "Website Redesign" and want to get all URLs that have been shared externally to ensure no unauthorized sharing has occurred.
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. This identifies which project's link shares will be retrieved. |
Output
The node outputs JSON data containing the list of all link shares for the specified project. Each item in the output typically includes details such as the share URL, permissions, expiration (if any), and metadata about the link share.
If the node supports binary data output, it would relate to downloadable content linked via the shares, but based on the provided code and context, the output is purely JSON describing the link shares.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- Needs the base URL of the Vikunja instance configured in the credentials.
- The node uses HTTP requests to interact with the Vikunja REST API endpoints.
Troubleshooting
- Invalid Project ID or Not Found: If the specified project does not exist or the ID is incorrect, the node may return an error or empty results. Verify the project ID or use the search list mode to select a valid project.
- Authentication Errors: Ensure the API key credential is correctly set up and has sufficient permissions to read project link shares.
- Network Issues: Connectivity problems to the Vikunja server will cause request failures. Check network settings and the API URL configuration.
- Empty Results: If no link shares exist for the project, the output will be an empty array. Confirm that link shares have been created.
Links and References
- Vikunja API Documentation — Official API docs for understanding available endpoints and data structures.
- n8n Documentation — For general guidance on using n8n nodes and credentials setup.