Vikunja icon

Vikunja

Get data from Vikunja's API

Overview

This node integrates with the Vikunja API to update an existing Project View within a specified project. A Project View in Vikunja represents a customized way of displaying tasks, such as in list, Gantt chart, table, or Kanban board formats. Updating a Project View allows users to modify its title, view type, bucket configuration, and filtering options.

Common scenarios for this node include:

  • Renaming a project view to better reflect its purpose.
  • Changing the display style of tasks (e.g., switching from a list to a Kanban board).
  • Adjusting how buckets are configured or filtered to tailor task organization.
  • Setting default or done buckets to automate task status management.

Practical example: A project manager wants to update the "Sprint Backlog" view from a simple list to a Kanban board and set a specific bucket as the default for new tasks. This node can perform that update programmatically.

Properties

Name Meaning
Project Title or ID The target project to operate on. You can select it from a searchable list or specify its ID directly.
Project View ID The identifier of the project view you want to update. Must be provided as an ID string.
Project View Title The new title for the project view. This is a required field when updating.
View Kind The type of view to display tasks. Options are: List, Gantt, Table, Kanban.
Bucket Configuration Mode How buckets are configured in the view. Options are: None (no buckets), Manual (user-defined buckets), Filter (buckets defined by filters).
Additional Fields (Options) A collection of optional settings:
• Default Bucket ID: ID of the bucket where new tasks without a bucket are added (default is leftmost bucket).
• Done Bucket ID: ID of the bucket marking tasks as done.
• Project View Filter: A filter expression to limit visible tasks.

Output

The node outputs JSON data representing the updated Project View object returned by the Vikunja API. This typically includes fields such as the view's ID, title, kind, bucket configuration mode, default and done bucket IDs, and any applied filters.

No binary data output is involved.

Dependencies

  • Requires an active connection to the Vikunja API endpoint.
  • Needs an API authentication token credential configured in n8n to authorize requests.
  • The base URL for the API is taken from the credential configuration.
  • No other external dependencies are required.

Troubleshooting

  • Invalid Project or View ID: If the specified project or project view ID does not exist or is incorrect, the API will return an error. Verify IDs by using the search functionality or checking in Vikunja.
  • Missing Required Fields: The node requires the project, project view ID, and project view title fields. Omitting these will cause validation errors.
  • Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to update project views.
  • API Endpoint Issues: Confirm the base URL is correct and accessible from your environment.
  • Filter Syntax Errors: If using the Project View Filter option, ensure the filter expression syntax matches Vikunja's expected format to avoid errors.

Links and References

Discussion