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 Webhook" operation allows users to remove a webhook from a specified project by providing the project identifier and the webhook ID. This is useful in scenarios where you want to stop receiving notifications or callbacks from Vikunja for certain events.
Practical examples include:
- Cleaning up obsolete or test webhooks that are no longer needed.
- Managing webhook lifecycle programmatically as part of project maintenance workflows.
- Automating the removal of webhooks when projects are archived or deleted.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The target project to operate on. You can select a project from a searchable list or specify its ID directly. |
| Webhook ID | The unique identifier of the webhook to delete. Must be provided as a number. |
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 of binary data output for this operation.
Dependencies
- Requires an active connection to the Vikunja API via an API key credential.
- The node expects the base URL of the Vikunja instance to be configured in the credentials.
- No additional external services are required beyond the Vikunja API.
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 before running the node.
- Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to delete webhooks.
- Network Issues: Connectivity problems with the Vikunja server will cause request failures. Check network access and API endpoint availability.
- Permission Denied: If the authenticated user lacks rights to modify the project or webhook, the API will reject the request. Confirm user permissions.
Links and References
- Vikunja API Documentation (for detailed API endpoints and webhook management)
- n8n Documentation on Creating Custom Nodes