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
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 scenarios where you want to stop receiving notifications or callbacks from a particular webhook that is no longer needed or valid.
Practical examples include:
- Cleaning up obsolete webhooks after project changes.
- Removing test or temporary webhooks created during development.
- Managing webhook lifecycle programmatically as part of automation workflows.
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. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- Needs the base URL of the Vikunja instance configured in the credentials.
- The node uses HTTP requests to interact with the Vikunja REST API endpoints.
Troubleshooting
- Invalid Project or Webhook ID: If the provided project or webhook ID does not exist or is incorrect, the API will likely return an error indicating the resource was not found. Verify IDs are correct and accessible.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key and base URL are correctly set in the node's credentials.
- Permission Issues: The authenticated user must have sufficient permissions to delete webhooks on the specified project.
- Network or Connectivity Problems: Failures to reach the Vikunja API endpoint may occur due to network issues or incorrect base URL configuration.
Links and References
- Vikunja API Documentation (for detailed API endpoint info)
- Vikunja Official Website