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
This node integrates with the Vikunja task management API to create new tasks within a specified project. It is useful for automating task creation workflows, such as adding tasks from form submissions, syncing tasks from other tools, or programmatically generating tasks based on triggers in n8n.
Typical use cases include:
- Automatically creating tasks in a project when an event occurs (e.g., a new customer signup).
- Adding detailed tasks with descriptions, due dates, priorities, and repeat settings.
- Organizing tasks into buckets within projects for better categorization.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The project where the task will be created. Choose from a searchable list of projects or specify a project ID directly. |
| Task Title | The title or name of the task to create. This is required. |
| Bucket ID | (Optional) The ID of the bucket inside the project to place the task into. |
| Description | (Optional) A detailed description of the task. |
| Done | (Optional) Whether the task is marked as completed upon creation (true/false). |
| Due Date Time | (Optional) The due date and time for the task in RFC3339 format. |
| End Date Time | (Optional) The end date and time for the task in RFC3339 format. |
| Favorite | (Optional) Whether the task is marked as a favorite (true/false). |
| Percent Done | (Optional) Progress of the task expressed as a decimal between 0 and 1. |
| Priority | (Optional) Task priority level from 1 (normal) to 5 (highest urgency). |
| Repeat After | (Optional) Number of seconds after which the task repeats. |
| Repeat Mode | (Optional) How the repeating task behaves: repeat after amount, monthly repeat, or repeat from current date. |
| Start Date Time | (Optional) The start date and time for the task in RFC3339 format. |
| Task Color | (Optional) Hex color code to visually identify the task. Default is black (#000000). |
Output
The node outputs JSON data representing the newly created task object as returned by the Vikunja API. This includes all task details such as ID, title, description, status, dates, priority, and any other metadata set during creation.
If the API supports binary data related to tasks (not indicated here), it would be summarized accordingly, but this node primarily deals with JSON task objects.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- The base URL for the Vikunja instance must be configured in the node 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 accessed, verify that the project exists and the API key has permission to access it.
- Missing Required Fields: The "Task Title" and "Project" are mandatory. Ensure these are provided; otherwise, the API will reject the request.
- Date Format Errors: Dates must be in valid RFC3339 format. Incorrect formatting may cause API errors.
- Permission Issues: API authentication failures or insufficient permissions can result in authorization errors. Check API key validity and scopes.
- API Endpoint Unreachable: Network issues or incorrect base URL configuration can prevent communication with the Vikunja server.