Actions60
- 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
- Get Many
- 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 Permissions on a Project
- Update a User's Permissions on a Project
- Task Actions
- Team Actions
- Webhook Actions
Webhook → Create
AI-generatedOverview
This node creates a webhook in the Vikunja project management system. It allows users to specify a project by title or ID, set a target URL for the webhook, optionally provide a secret for HMAC signing, and select which events should trigger the webhook. This is useful for integrating Vikunja with other systems by receiving real-time notifications about project and task changes.
Use Case Examples
- Create a webhook to notify an external system when tasks are created or updated in a specific project.
- Set up a webhook with a secret to securely receive signed webhook requests for project updates.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The project to operate on, specified either by selecting from a list or by providing an ID. |
| Webhook Target URL | The URL to which webhook requests will be sent. |
| Secret | Optional secret used to sign webhook requests with HMAC for security. |
| Events | The webhook events that will trigger this webhook target, such as task creation or project updates. |
| Request Options | Options to control request behavior such as batching, SSL validation, proxy, and timeout settings. |
Output
JSON
id- The unique identifier of the created webhook.projectId- The ID of the project the webhook is associated with.targetUrl- The URL to which the webhook will send requests.secret- The secret used for signing webhook requests, if provided.events- The list of events that trigger the webhook.
Dependencies
- An API key credential for authenticating with the Vikunja API
Troubleshooting
- Ensure the project ID or title is valid and accessible with the provided credentials.
- Verify the webhook target URL is reachable and correctly formatted.
- If using a secret, ensure the receiving system can handle HMAC signed requests as per Vikunja's documentation.
- Check network settings if using proxy or if SSL issues occur, especially if 'Ignore SSL Issues' is disabled.
Links
- Vikunja Webhooks Documentation - Official documentation on how to use and sign webhook requests in Vikunja.