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 node is useful for automating project setup workflows, enabling users to programmatically add tailored views to projects based on their needs.

Practical examples include:

  • Automatically creating a Kanban view for a new project to facilitate agile task management.
  • Setting up a Gantt view to visualize project timelines.
  • Defining default and done buckets to streamline task status tracking.

Properties

Name Meaning
Project Title or ID The target project where the new view will be created. Can be selected from a searchable list of projects or specified by its ID.
Project View Title The title/name of the new project view being created.
View Kind The type of view to create. Options are: List, Gantt, Table, Kanban. Determines how tasks and buckets are visually organized.
Bucket Configuration Mode How buckets are configured in the view. Options: None (no bucket configuration), Manual (buckets assigned manually), Filter (buckets filtered automatically).
Additional Fields (Options): - Default Bucket ID: ID of the bucket where new tasks without an assigned bucket are added. Defaults to the leftmost bucket if not set.
- Done Bucket ID: ID of the bucket marking tasks as done; moving tasks here marks them done and vice versa.
- Project View Filter: A filter string to limit which tasks appear in the view.

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 filters applied.

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.
  • Uses internal methods to search for projects and project views to assist in selecting resources.

Troubleshooting

  • Common Issues:

    • Invalid or missing project ID: Ensure the project exists and the correct ID or selection is provided.
    • Insufficient permissions: The API key must have rights to create views in the specified project.
    • Incorrect bucket IDs: Default or done bucket IDs must correspond to existing buckets within the project.
  • Error Messages:

    • "Project not found": Verify the project ID or selection.
    • "Unauthorized": Check API key validity and permissions.
    • "Invalid bucket configuration": Confirm that bucket IDs are valid and belong to the project.

Resolving these usually involves verifying input parameters, ensuring proper API credentials, and confirming resource existence.

Links and References

Discussion