Overview
This node acts as a trigger for VictoriaOS events, allowing workflows in n8n to start when specific events occur in VictoriaOS. It listens for events such as task creation, task updates, task completion, and task deletion. This is useful for automating processes based on task lifecycle changes in VictoriaOS, for example, sending notifications when a task is completed or updating other systems when a task is created or modified.
Use Case Examples
- Trigger a workflow when a new task is created in VictoriaOS to notify a team via email.
- Start a workflow to update a project management tool when a task is completed in VictoriaOS.
- Automate cleanup or logging actions when a task is deleted in VictoriaOS.
Properties
| Name | Meaning |
|---|---|
| Eventos | The specific VictoriaOS events that will trigger this workflow. Multiple events can be selected, such as task creation, update, completion, or deletion. |
| Descripción del Webhook | An optional description to identify the webhook within VictoriaOS. |
Output
JSON
body- The JSON payload received from the VictoriaOS webhook event, representing the event data.
Dependencies
- Requires an API key credential for VictoriaOS API authentication.
Troubleshooting
- If the webhook does not trigger, verify that the webhook is correctly registered in VictoriaOS and that the selected events match those sent by VictoriaOS.
- Ensure the API credentials are valid and have the necessary permissions to create and manage webhooks in VictoriaOS.
- Common errors include failure to create or delete the webhook due to network issues or invalid credentials. Check the API endpoint URL and credentials configuration.
- If no events are selected, the webhook will not trigger; ensure at least one event is chosen.
Links
- VictoriaOS Webhooks API Documentation - Official documentation for managing webhooks in VictoriaOS.