Overview
The Vikunja Trigger node starts an n8n workflow when specific events occur in a Vikunja project. It listens for webhook events related to projects and tasks, such as project updates, task creation, comments, attachments, and assignee changes. This node is useful for automating workflows that depend on real-time changes within a Vikunja project management environment.
For example, you could use this node to:
- Automatically notify a team chat when a new task is created.
- Sync task updates with another system whenever a task is updated or deleted.
- Trigger follow-up actions when a project is shared or deleted.
Properties
| Name | Meaning |
|---|---|
| Project ID | The ID of the Vikunja project to monitor. You can select from a list or specify an ID directly. |
| Events | The webhook events that will trigger this node. Multiple events can be selected. Available options include: project.deleted, project.shared.team, project.shared.user, project.updated, task.assignee.created, task.assignee.deleted, task.attachment.created, task.attachment.deleted, task.comment.created, task.comment.deleted, task.comment.edited, task.created, task.deleted, task.relation.created, task.relation.deleted, task.updated. |
Output
The node outputs JSON data representing the webhook payload received from Vikunja when one of the selected events occurs. The output is structured as an array of JSON objects, each containing the event data sent by Vikunja.
If binary data were involved, it would be summarized here, but this node only handles JSON webhook payloads.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- Needs network access to receive incoming webhook POST requests from Vikunja.
- The node manages webhook registration on the Vikunja server via its REST API.
Troubleshooting
- Webhook not triggering: Ensure the correct project ID and events are selected. Verify that the webhook URL registered in Vikunja matches the URL provided by n8n.
- API request failures: Check that the API key credential is valid and has sufficient permissions to manage webhooks on the specified project.
- Duplicate webhook registrations: The node checks for existing webhooks before creating new ones, but if manual changes are made on Vikunja, stale webhook IDs might cause issues. Deleting and recreating the webhook via the node can help.
- Unexpected payload format: Confirm that the Vikunja instance version matches the expected webhook payload structure.