Vikunja Trigger
AI-generatedOverview
The Vikunja Trigger node starts an n8n workflow when specific events occur in a Vikunja project. It listens for webhook events related to project and task changes, such as project deletion, task creation, or comment updates. This node is useful for automating workflows based on real-time changes in a Vikunja project, for example, triggering notifications, updating external systems, or logging activity.
Use Case Examples
- Trigger a workflow when a task is created in a specific project to send a notification email.
- Start a workflow when a project is deleted to archive related data.
- Automate updates in a CRM system when a task comment is edited.
Properties
| Name | Meaning |
|---|---|
| Project ID | The ID of the Vikunja project to monitor for events. This is required to specify which project the webhook should be attached to. |
| Events | The list of webhook events that will trigger this node. Users can select multiple events such as task creation, deletion, comment edits, and project sharing events. |
Output
JSON
body- The JSON payload received from the Vikunja webhook event, containing details about the event that triggered the workflow.
Dependencies
- An API key credential for Vikunja API authentication is required to manage webhooks.
Troubleshooting
- If the webhook does not trigger, verify that the Project ID is correct and that the webhook URL is accessible from Vikunja.
- Ensure the selected events match the events generated by Vikunja for the project.
- Common errors include failure to create or delete webhooks due to incorrect API credentials or network issues. Verify API credentials and network connectivity.
Links
- Vikunja Webhook API Documentation - Official documentation for managing webhooks in Vikunja, useful for understanding event types and webhook setup.