Source
Integrations — found from sitemap — Vikunja
Checked for Vikunja on 1 Oct 2026
- Page
- https://vikunja.io/help/webhooks/
- Checked
- 1 Oct 2026, 15:57 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:f46a8b26c00125aa65cd473e62d0b6d459b00df6fdd06191333463bbd9868d5f
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Webhooks types Report an error
“Vikunja has two types of webhooks: Project webhooks: Trigger when something happens in a specific project (e.g., a task is created or a comment is added). Set these up from the project settings. User webhooks: Trigger for events directed at you personally, such as task reminders firing or tasks becoming overdue. Set these up from your account settings.”
-
Webhooks basic auth Report an error
“Basic Auth (optional): Click Use Basic Auth? to enter a username and password if the target URL requires it.”
-
Webhooks project events Report an error
“task.created A task was created task.updated A task was updated task.deleted A task was deleted task.assignee.created An assignee was added to a task task.assignee.deleted An assignee was removed from a task task.comment.created A comment was added to a task task.comment.edited A comment was edited task.comment.deleted A comment was deleted task.attachment.created An attachment was added to a task task.attachment.deleted An attachment was removed from a task task.relation.created A relation between tasks was created task.relation.deleted A relation between tasks was removed project.updated The project was updated project.deleted The project was deleted project.shared.user The project was shared with a user project.shared.team The project was shared with a team”
-
Webhooks user events Report an error
“task.reminder.fired A reminder for a task fired task.overdue A task became overdue tasks.overdue Multiple tasks became overdue”
-
Webhooks signing Report an error
“If you set a secret when creating the webhook, Vikunja includes an X-Vikunja-Signature header in every request. This header contains an HMAC-SHA256 signature of the request body, which lets the receiving service verify that the request genuinely came from Vikunja.”
-
Webhooks payload format Report an error
“Every webhook request sends a JSON body with this structure:”
-
Webhooks API Report an error
“To create and manage webhooks programmatically, see the Webhooks API Reference. You can create API tokens in your settings to authenticate with the API.”
-
Webhooks no retry Report an error
“Webhooks are sent once. If delivery fails (e.g., the target URL is unreachable), Vikunja does not retry.”
-
Webhooks link share restriction Report an error
“Webhooks cannot be created via link shares. You need a user account.”
-
Webhooks admin config Report an error
“Instance administrators can configure webhook timeouts and proxy settings. See the webhook configuration options for details.”
Scores citing this record
- The Bootstrapper Integrations
- The Data Protection Officer Integrations
- The Enterprise Architect Integrations
- The Integrator Integrations
- The Skeptic Integrations
- The Skeptic Support & documentation
- The UX Purist Integrations
- The UX Purist Support & documentation