Vikunja icon

Vikunja

Get data from Vikunja's API

Overview

This node integrates with the Vikunja API to create a new Project View within a specified project. A Project View in Vikunja is a customizable way to visualize tasks and buckets, such as in list, Gantt chart, table, or Kanban board formats. This operation allows users to define how they want to organize and display their project tasks by setting the view's title, kind, bucket configuration mode, and optional filters.

Common scenarios for this node include:

  • Automating the setup of project views when creating new projects.
  • Standardizing task visualization across teams by programmatically creating consistent views.
  • Dynamically generating filtered views based on project needs or user preferences.

Example use case: Automatically create a Kanban view titled "Sprint Board" for a project to help agile teams track sprint progress visually.

Properties

Name Meaning
Project Title or ID The target project where the new view will be created. You can select from a searchable list of projects or specify the project by its ID.
Project View Title The name/title of the new project view you want to create.
View Kind The type of view to create. Options are: List, Gantt, Table, Kanban. This determines how tasks and buckets are displayed.
Bucket Configuration Mode How buckets are configured in the view. Options: None (no buckets), Manual (manually assigned buckets), Filter (buckets defined by filters).
Default Bucket ID (Optional) The ID of the bucket where new tasks without an assigned bucket will be added. Defaults to the leftmost bucket if not set.
Done Bucket ID (Optional) The ID of the bucket that marks tasks as done. Tasks moved here are marked complete; tasks marked done individually move into this bucket.
Project View Filter (Optional) A filter string to limit which tasks appear in the view based on criteria like status, labels, or other attributes.

Output

The node outputs JSON data representing the newly created Project View object as returned by the Vikunja API. This typically includes details such as the view's ID, title, kind, bucket configuration, and any applied filters.

No binary data output is involved.

Dependencies

  • Requires access to the Vikunja API endpoint, configured via an API URL credential.
  • Requires an API authentication token or key credential to authorize requests.
  • The node uses HTTP requests with JSON payloads to interact with the Vikunja API.

Troubleshooting

  • Authentication errors: Ensure the API credentials (URL and token/key) are correctly configured and have sufficient permissions to create project views.
  • Invalid project or bucket IDs: Verify that the provided project ID exists and that any bucket IDs used are valid within that project.
  • Missing required fields: The "Project Title or ID" and "Project View Title" are mandatory. Omitting these will cause errors.
  • API connectivity issues: Check network connectivity and that the Vikunja server is reachable at the configured URL.
  • Filter syntax errors: If using the Project View Filter, ensure the filter string follows Vikunja's expected syntax to avoid API rejections.

Links and References

Discussion