Vikunja icon

Vikunja

Get data from Vikunja's API

Overview

This 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, archived status, favorite status, and identifier. This is useful in scenarios where project details need to be kept current or adjusted based on evolving requirements, for example updating a project’s title after a rebranding or marking a project as archived when it is no longer active.

Practical examples:

  • Renaming a project to reflect a new phase or focus.
  • Archiving completed projects to keep the workspace clean.
  • Changing the project color to visually categorize projects by priority or team.
  • Setting a project as favorite for quick access.

Properties

Name Meaning
Project Title or ID The target project to update, selectable from a list or specified by its unique ID.
Project Title The new title/name for the project.
Additional Fields Optional fields to further customize the project:
- Description A textual description providing more details about the project.
- Project Color The color associated with the project, represented as a hex color code (e.g., #000000).
- Archived Boolean flag indicating whether the project is archived (true) or active (false).
- Favorite Boolean flag indicating whether the project is marked as a favorite (true) or not (false).
- Identifier A unique short identifier used for building task identifiers related to this project.

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, color, archived status, favorite status, and identifier reflecting the latest state after the update operation.

No binary data output is involved.

Dependencies

  • Requires an API key credential for authenticating requests to the Vikunja API.
  • Needs the base URL of the Vikunja instance configured in the node credentials.
  • Relies on the Vikunja REST API being accessible and operational.

Troubleshooting

  • Common issues:
    • Invalid project ID or title may cause the update to fail.
    • Network connectivity problems can prevent communication with the Vikunja API.
    • Insufficient permissions or invalid API credentials will result in authorization errors.
  • Error messages:
    • "Project not found" indicates the specified project ID does not exist; verify the ID or select from the list.
    • "Unauthorized" or "Forbidden" suggests issues with API credentials; check that the API key is valid and has necessary permissions.
    • "Invalid input" errors may occur if required fields like project title are missing or malformed; ensure all mandatory fields are correctly filled.

Links and References

Discussion