Send ticket events to Slack, Microsoft Teams or your own system with webhooks Last updated: Nov 16, 2026
Webhooks post what happens in your Vertask workspace to the addresses you choose, within a minute. Use them to announce new tickets in Slack or Microsoft Teams, or to feed your own systems with signed JSON.
Add an endpoint
- Go to Workspace Settings > Webhooks.
- Click Add endpoint. You can have up to 10.
- Choose the Type: Generic JSON, Slack or Microsoft Teams.
- Enter an optional name and the Address: an https address on the public internet.
- Tick the events to send.
- Optionally tick Only tasks with priority High or above. It applies to task and reply events; new clients, assets and contracts are always sent.
- Click Save.
Events
- Task created (ticket.created)
- Task updated: status, priority, assignee, custom fields (ticket.updated)
- Task resolved (ticket.closed)
- Reply or internal note added (comment.created)
- Client added (client.created)
- Asset added (asset.created) and Asset updated (asset.updated)
- Contract ending soon (contract.expiring)
Checking a delivery
Each delivery to a Generic JSON endpoint is a POST with a JSON body and these headers:
- X-Vertask-Event: the event, for example ticket.created.
- X-Vertask-Delivery: a new id for each delivery. A retry keeps the body's event_id, so you can drop a repeat.
- X-Vertask-Signature: sha256= followed by the HMAC-SHA256 of the raw body, keyed with the endpoint's secret. Compute it on your side and compare.
Retries
A response other than 2xx, or none within 5 seconds, is retried after 1 minute, 5 minutes, 30 minutes, 2 hours and 12 hours. After 20 failures in a row the endpoint is switched off and the account holder is emailed.
Privacy
Private tasks are never sent. Comment events on other tasks include internal notes for JSON endpoints; Slack and Microsoft Teams posts leave the words of a note out.
Related: Manage API access and keys and Connect Vertask to Zapier.