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 retrieve data related to various resources, including webhooks. Specifically, for the Webhook resource and the Get Many operation, it fetches multiple webhook entries associated with a specified project. This is useful when you want to list all webhooks configured for a particular project in Vikunja, enabling automation workflows that depend on webhook configurations or monitoring.
Practical examples include:
- Automatically syncing webhook configurations from Vikunja into another system.
- Auditing or reporting on all webhooks set up for a project.
- Triggering downstream processes based on the list of active webhooks.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The project to operate on. You can select a project from a searchable list or specify its ID. |
The property supports two modes:
- From List: Select a project interactively from a searchable dropdown.
- ID: Provide the project ID directly as a string.
Output
The node outputs JSON data representing the collection of webhooks retrieved from the specified project. Each item in the output corresponds to a webhook object as returned by the Vikunja API, typically including details such as webhook URL, events subscribed to, and other configuration metadata.
If the node supports binary data output (not indicated here), it would represent any binary content related to webhooks, but this node primarily deals with JSON data.
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 communicate with the Vikunja REST API endpoints.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing an incorrect project ID or selecting a non-existent project will result in errors or empty results.
- Network connectivity problems may prevent the node from reaching the Vikunja API.
Error messages:
- Authentication errors usually indicate invalid API keys; verify and update credentials.
- "Project not found" or similar errors suggest the project ID does not exist or is inaccessible.
- Timeout or connection errors require checking network access and Vikunja server availability.