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
- Task Actions
- Team Actions
- Webhook Actions
Overview
This node integrates with the Vikunja API to manage tasks, projects, labels, teams, and webhooks. Specifically, for the Task resource and the Assign a User to a Task operation, it assigns a specified user to an existing task by sending the user's ID to the API.
This operation is useful in scenarios where task management involves collaboration, and you want to programmatically assign responsibility or ownership of a task to a particular user. For example, in a project management workflow, when a new task is created or updated, this node can automatically assign the appropriate team member based on business rules or triggers.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier (number) of the task to which a user will be assigned. |
| User ID | The unique identifier (number) of the user who will be assigned to the specified task. |
Output
The node outputs JSON data representing the result of the assignment operation as returned by the Vikunja API. This typically includes confirmation details about the task and the newly assigned user. The exact structure depends on the API response but generally contains updated task information reflecting the assignment.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Vikunja API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The base URL for the Vikunja API must be set correctly in the node's credential configuration.
Troubleshooting
Common Issues:
- Invalid or missing Task ID or User ID: Ensure both IDs are correct and correspond to existing entities in Vikunja.
- Authentication errors: Verify that the API key/token is valid and has sufficient permissions.
- Network or connectivity problems: Check that the API URL is reachable from the n8n environment.
Error Messages:
- "Unauthorized" or "Authentication failed": Indicates issues with the API credentials; reconfigure or update them.
- "Task not found": The provided Task ID does not exist; verify the ID.
- "User not found": The provided User ID does not exist; verify the ID.
- "Bad Request": Usually caused by malformed input; ensure all required fields are provided and correctly formatted.
Resolving these typically involves verifying input parameters, checking API credentials, and ensuring network accessibility.