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
The node integrates with the Vikunja API to manage webhooks associated with projects. Specifically, the Update Webhook operation allows users to modify an existing webhook's configuration for a given project. This includes changing the target URL where webhook events are sent, updating the secret used for signing requests, and adjusting which events trigger the webhook.
This node is beneficial in automation workflows where you need to dynamically update webhook endpoints or their settings without manually accessing the Vikunja interface. For example, if your application endpoint changes or you want to add/remove event triggers programmatically, this node can handle those updates seamlessly.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The project on which the webhook operates. You can select from a list of projects or specify a project ID directly. |
| Webhook ID | The identifier of the webhook you want to update. |
| Webhook Target URL | The new URL where webhook notifications will be sent. |
| Secret | Optional secret string used to sign webhook requests via HMAC for security verification. |
| Events | List of webhook event types that should trigger this webhook. 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 updated webhook object as returned by the Vikunja API. This typically includes fields such as the webhook ID, target URL, secret (if stored), subscribed events, and metadata about the webhook.
If the node supports binary data output, it is not indicated here; thus, the output is purely JSON-based reflecting the webhook resource state after update.
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 credentials.
Troubleshooting
- Invalid Project or Webhook ID: Ensure the provided project and webhook IDs exist and are accessible with the current API credentials.
- Unauthorized Errors: Verify that the API key or token has sufficient permissions to update webhooks.
- Invalid URL Format: The webhook target URL must be a valid URL; otherwise, the API may reject the request.
- Empty Event List: If no events are selected, the webhook might not trigger; ensure at least one event is specified.
- Secret Misconfiguration: If using the secret for signing, confirm that the receiving endpoint can verify HMAC signatures as per Vikunja documentation.