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 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 programmatically access or audit all shared links of a project, for example, to manage permissions, track sharing activity, or display shared resources in another system.
Practical scenarios include:
- Automatically listing all public or private shareable links for a project to monitor external access.
- Integrating with other tools to synchronize or report on project sharing status.
- Building dashboards that show which projects have active 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. 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 about an individual link share such as the URL, permissions, expiration, and any metadata provided by the Vikunja API.
If the node supports binary data output (not indicated here), it would represent downloadable content or attachments related to the link shares, but this operation primarily returns structured JSON data.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- Needs the base URL of the Vikunja instance configured in the node credentials.
- The node depends on the Vikunja REST API endpoints for projects and their link shares.
Troubleshooting
- Common issues:
- Invalid or missing project ID: Ensure the project exists and the ID or selection is correct.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network or connectivity problems: Confirm the Vikunja API URL is reachable from n8n.
- Error messages:
- "Unauthorized" or "Authentication failed": Check API credentials.
- "Project not found": Validate the project identifier.
- "Request timeout" or "Network error": Check network settings and API availability.