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
- Team Actions
- Task Actions
- Webhook Actions
Overview
The node integrates with the Vikunja API to update an existing project. It allows users to modify various attributes of a project such as its title, description, color, and status flags like archived or favorite. This node is useful in automation workflows where project details need to be programmatically maintained or synchronized, for example, updating project metadata based on external triggers or batch editing projects.
Practical examples:
- Automatically archiving projects that have been inactive for a certain period.
- Updating project titles or descriptions based on changes from another system.
- Changing project colors or identifiers to reflect new categorization schemes.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The target project to update. Can be selected from a searchable list or specified by ID. |
| Project Title | The new title for the project. This is required when updating a project. |
| Additional Fields | Optional fields to further customize the project update: |
| - Archived | Boolean flag indicating if the project should be marked as archived. |
| - Description | A textual description of the project. |
| - Favorite | Boolean flag indicating if the project should be marked as a favorite. |
| - Identifier | A unique short identifier for the project, used for building task identifiers. |
| - Project Color | Hex color code representing the project's color. |
Output
The node outputs JSON data representing the updated project object returned by the Vikunja API. This typically includes all project properties such as ID, title, description, archived status, favorite status, identifier, and color. The output can be used downstream in workflows for further processing or logging.
No binary data output is involved.
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 communicate with the Vikunja REST API endpoints.
Troubleshooting
- Invalid Project ID or Title: If the project cannot be found or identified, ensure the correct project ID or title is provided. Using the "From List" mode helps avoid typos.
- Authentication Errors: Verify that the API key credential is valid and has sufficient permissions to update projects.
- API Endpoint Issues: Confirm the base URL is correctly set without trailing slashes and that the Vikunja server is reachable.
- Required Fields Missing: The "Project Title" field is mandatory for updates; omitting it will cause errors.
- Invalid Field Values: Ensure color codes are valid hex strings and boolean fields are properly set.