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 within the Vikunja task management system. Specifically, the "Assign a User to a Task" operation allows you to assign a particular user to an existing task by specifying the task's ID and the user's ID. This is useful in workflows where task delegation or assignment needs to be automated, such as project management automation, team collaboration setups, or syncing user-task assignments from other systems.
For example, after creating a task via another node or external trigger, you can use this operation to assign it immediately to a responsible team member by their user ID.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the task to which a user will be assigned. Required. |
| User ID | The unique identifier of the user who will be assigned to the specified task. Required. |
Output
The node outputs JSON data representing the result of the assignment operation. Typically, this includes confirmation that the user was successfully assigned to the task, along with any updated task details returned by the Vikunja API.
If the node supports binary data output (not indicated here), it would represent related file attachments or media associated with the task, but for this operation, the output is purely JSON.
Dependencies
- Requires access to the Vikunja API endpoint.
- Requires an API authentication token credential configured in n8n to authorize requests.
- The base URL for the API is taken from the credential configuration.
- The node sends JSON-formatted HTTP requests and expects JSON responses.
Troubleshooting
Common Issues:
- Invalid or missing Task ID or User ID will cause the API request to fail.
- Authentication errors if the API key or token is incorrect or expired.
- Network connectivity issues to the Vikunja server.
- Attempting to assign a user who does not exist or is not part of the project/team.
Error Messages:
- "Unauthorized" or "Authentication failed": Check API credentials and permissions.
- "Task not found": Verify the Task ID is correct and the task exists.
- "User not found": Verify the User ID is valid and the user exists in Vikunja.
- "Bad Request": Ensure all required parameters are provided and correctly formatted.
Resolving these typically involves verifying input values, checking API credentials, and ensuring the Vikunja service is reachable.
Links and References
- Vikunja API Documentation
- Vikunja Official Website
- n8n Documentation on Creating Custom Nodes