Actions60
- 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
- Get Many
- 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 Permissions on a Project
- Update a User's Permissions on a Project
- Task Actions
- Team Actions
- Webhook Actions
Webhook → Update
AI-generatedOverview
This node updates an existing webhook in a specified project within the Vikunja API. It allows users to modify webhook details such as the target URL, secret for HMAC signing, and the events that trigger the webhook. This is useful for automating workflows that depend on project-related events, such as task updates or comments, by ensuring the webhook points to the correct endpoint and listens to the desired events.
Use Case Examples
- Updating a webhook's target URL to a new endpoint after a service migration.
- Changing the secret used for signing webhook requests to enhance security.
- Modifying the events that trigger the webhook to include new project or task events.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | Specifies the project to which the webhook belongs. Can be selected from a list or specified by ID. |
| Webhook ID | The unique identifier of the webhook to update. |
| Webhook Target URL | The URL to which the webhook will send requests when triggered. |
| Secret | Optional secret used to sign webhook requests with HMAC for security. |
| Events | The list of events that will trigger the webhook. Multiple events can be selected. |
Output
JSON
webhook_id- The unique identifier of the updated webhook.target_url- The URL to which the webhook sends requests.secret- The secret used for signing webhook requests, if provided.events- The list of events that trigger the webhook.
Dependencies
- An API key credential for authenticating with the Vikunja API.
Troubleshooting
- Ensure the provided Project ID and Webhook ID are correct and exist in the Vikunja system to avoid 'not found' errors.
- Verify that the Webhook Target URL is a valid and reachable URL to prevent request failures.
- If using a secret for HMAC signing, ensure the receiving endpoint can verify the signature correctly to avoid security issues.
- Check network connectivity and proxy settings if requests fail due to network errors.
- If SSL certificate validation is disabled, be cautious of potential security risks.
Links
- Vikunja Webhooks Documentation - Official documentation on how to use and sign webhooks in Vikunja.