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 update an existing webhook associated with a project. It allows users to modify the webhook's target URL, secret for HMAC signing, and the events that trigger the webhook. This is useful in scenarios where you want to change how your application receives notifications about project-related activities such as task updates, comments, or project sharing.
Practical examples include:
- Changing the endpoint URL where webhook payloads are sent after a project migration.
- Updating the secret key used to verify webhook authenticity.
- Adjusting which events (e.g., task creation, comment edits) should trigger the webhook notifications.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The project to operate on. Can be selected from a searchable list of projects or specified by its ID. |
| Webhook ID | The identifier of the webhook to update. Must be provided as a number. |
| Webhook Target URL | The new URL where webhook requests will be sent. |
| Secret | Optional secret string used to sign webhook requests with HMAC for security verification. |
| Events | List of webhook event types that will trigger this webhook. Options include project and task related events such as project.updated, task.created, task.comment.edited, etc. |
Output
The node outputs JSON data representing the updated webhook object returned by the Vikunja API. This typically includes details such as the webhook ID, target URL, subscribed events, and possibly metadata like creation or update timestamps.
If the node supports binary data output, it is not indicated here; thus, only JSON output is expected.
Dependencies
- Requires an active connection to the Vikunja API via an API URL and an API authentication token configured in n8n credentials.
- The node depends on the Vikunja API being accessible and the user having appropriate permissions to update webhooks on the specified project.
Troubleshooting
- Invalid Project or Webhook ID: Errors may occur if the provided project or webhook ID does not exist or the user lacks access rights. Verify IDs and permissions.
- Invalid Target URL: Ensure the webhook target URL is a valid and reachable endpoint.
- Authentication Errors: If the API key or token is missing or invalid, the request will fail. Confirm credential configuration.
- Event Selection Issues: Providing no events or invalid event names might cause the update to fail or result in unexpected behavior. Select at least one valid event.
- Secret Misconfiguration: If using the secret for HMAC signing, ensure both sender and receiver handle the signature correctly to avoid verification failures.