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
The node integrates with the Vikunja API to retrieve data related to projects, tasks, labels, teams, and webhooks. Specifically, for the Project - Get operation, it fetches detailed information about a single project identified either by its title or ID. This is useful in automation workflows where you need to access project metadata or details dynamically, such as syncing project info with other tools, generating reports, or triggering actions based on project attributes.
Practical examples:
- Automatically retrieving project details when a new task is created to enrich task data.
- Fetching project information to display in dashboards or notifications.
- Using project metadata to conditionally route workflow execution.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The project to operate on. You can select a project from a searchable list or specify its ID directly. This identifies which project’s data will be retrieved. |
The property supports two modes:
- From List: Search and select a project by name.
- ID: Provide the unique identifier of the project.
Output
The node outputs JSON data representing the full details of the specified project as returned by the Vikunja API. This typically includes fields such as project ID, title, description, creation date, update date, and possibly associated metadata like user permissions or linked resources.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to a Vikunja instance via its REST API.
- Needs an API authentication token credential configured in n8n to authorize requests.
- The base URL of the Vikunja API must be set in the credentials configuration.
Troubleshooting
Common issues:
- Invalid or missing project ID: Ensure the project exists and the ID is correct.
- Authentication errors: Verify that the API key/token is valid and has sufficient permissions.
- Network connectivity problems: Confirm that the Vikunja API endpoint is reachable from the n8n environment.
Error messages:
- 404 Not Found: The specified project does not exist. Double-check the project ID or selection.
- 401 Unauthorized: Authentication failed. Check API credentials.
- 500 Internal Server Error: Server-side issue; retry later or check Vikunja server status.