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 update project details. It allows users to modify existing projects by specifying the project either by its title or ID and updating various attributes such as the project title, description, color, archived status, favorite status, and identifier. This node is useful in automation workflows where project metadata needs to be programmatically maintained or synchronized, for example, updating project information based on external triggers or batch processing project updates.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | Select a project from a searchable list or specify its ID directly to identify which project to update. |
| Project Title | The new title for the project. This is a required field when updating a project. |
| Additional Fields | Optional fields to further customize the project update: |
| - Archived | Boolean flag indicating whether the project should be marked as archived. |
| - Description | A textual description of the project. |
| - Favorite | Boolean flag indicating whether the project is set as a favorite. |
| - Identifier | A unique short identifier for the project, used for building task identifiers. |
| - Project Color | The color associated with the project, specified as a hex color code (e.g., #000000). |
Output
The node outputs JSON data representing the updated project object as returned by the Vikunja API. This typically includes all project properties such as ID, title, description, archived status, favorite status, identifier, color, and any other metadata provided by the API. The output can be used downstream in workflows to confirm the update or trigger further actions.
No binary data output is indicated.
Dependencies
- Requires an active connection to the Vikunja API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL for the API must be set correctly in the credentials configuration.
Troubleshooting
Common Issues:
- Invalid project ID or title: Ensure the project exists and the identifier is correct.
- Missing required fields: The "Project Title" is mandatory when updating; omitting it will cause errors.
- Authentication failures: Verify that the API key/token is valid and has sufficient permissions.
- Network or connectivity issues: Confirm the API URL is reachable from the n8n environment.
Error Messages:
- 404 Not Found: The specified project does not exist. Check the project ID or selection.
- 401 Unauthorized: Authentication failed. Recheck API credentials.
- 400 Bad Request: Likely due to missing or invalid input fields. Validate all required properties are correctly set.
Links and References
- Vikunja API Documentation – Official API reference for understanding project resource endpoints and payloads.
- n8n Documentation – For general guidance on setting up credentials and using custom nodes.