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
- Team Actions
- Task Actions
- Webhook Actions
Overview
This node integrates with the Vikunja API to manage webhooks associated with projects. Specifically, the "Delete" operation under the "Webhook" resource allows users to remove a webhook from a specified project. This is useful for automating the cleanup or management of webhook configurations in Vikunja, such as when a webhook is no longer needed or must be replaced.
Practical examples include:
- Automatically deleting outdated or unused webhooks during project maintenance.
- Removing webhooks as part of a workflow that decommissions projects or integrations.
- Managing webhook lifecycle programmatically without manual intervention in the Vikunja UI.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The target project where the webhook exists. You can select a project from a searchable list or specify its ID directly. |
| Webhook ID | The unique identifier of the webhook to delete within the selected project. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will confirm whether the webhook was successfully deleted or provide error information if the deletion failed.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Vikunja API.
- Needs the base URL of the Vikunja instance configured in the credentials.
- The node depends on the Vikunja REST API being accessible and properly configured to allow webhook deletions.
Troubleshooting
Common issues:
- Invalid or missing project ID or webhook ID may cause the operation to fail.
- Insufficient permissions or incorrect API credentials can lead to authorization errors.
- Network connectivity problems or incorrect base URL configuration might prevent communication with the Vikunja API.
Error messages and resolutions:
- "Webhook not found": Verify that the webhook ID and project ID are correct and that the webhook exists.
- "Unauthorized" or "Forbidden": Check that the API key has sufficient permissions and is correctly set up.
- "Network Error" or "Could not connect": Confirm the Vikunja API URL is reachable and correctly entered in credentials.