Actions57
- Team Actions
- Webhook Actions
- 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
Overview
This node integrates with the Vikunja API to retrieve multiple webhook entries associated with a specified project. It is useful for scenarios where you need to list or manage webhooks configured in a particular project within Vikunja, such as monitoring webhook configurations or exporting webhook data for auditing or synchronization purposes.
For example, you might use this node to:
- Fetch all webhooks for a project to display them in a dashboard.
- Automate the backup of webhook configurations.
- Integrate webhook data into other systems by retrieving and processing them in n8n workflows.
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. |
Output
The node outputs an array of webhook objects in the json field of each item. Each webhook object contains details about a webhook configured in the specified project, such as its URL, events it listens to, and other metadata defined by the Vikunja API.
If the node supports binary data output (not indicated here), it would typically represent attachments or files related to webhooks, but this node primarily deals with JSON data representing webhook configurations.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- Needs the base URL of the Vikunja instance configured in the credentials.
- Relies on the Vikunja API being accessible and properly configured to allow webhook retrieval.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Specifying a non-existent project ID or title will result in no data or an error response.
- Network connectivity problems to the Vikunja API endpoint can cause request failures.
Error messages:
- Authentication errors usually indicate invalid API keys; verify and update credentials.
- "Project not found" or similar errors suggest the provided project identifier is incorrect; double-check the project selection.
- Timeout or connection errors require checking network access and Vikunja server status.