Webhook Events

A webhook subscribes to one or more of the events below. When an event fires for the webhook’s project, Hawzu delivers the envelope with event set to the name and data set to the shape shown here. Where applicable, data includes the acting user’s email as actor.

Defects

Event	Fires when	data
defect.created	a defect is created	{ defect_code, title, status, severity, priority }
defect.status_changed	a defect’s status changes	{ defect_code, from, to, actor }
defect.assigned	a defect’s assignee changes	{ defect_code, from, to, actor }
defect.deleted	a defect is deleted	{ defect_code, actor }

Test runs & executions

Event	Fires when	data
run.created	a test run / execution is created	{ execution_id, title, execution_type, release_id, actor }
run.completed	a run is marked complete	{ execution_id, from, to }
run.resumed	a completed run is reopened	{ execution_id, from, to }
run.deleted	a run / execution is deleted	{ execution_id, title, execution_type, release_id, actor }

Requirements

Event	Fires when	data
requirement.created	a requirement is created	{ requirement_code, title, workflow_status, actor }
requirement.status_changed	a requirement’s workflow status changes	{ requirement_code, from, to, actor }
requirement.deleted	a requirement is deleted	{ requirement_code, actor }

Releases

Event	Fires when	data
release.created	a release is created	{ release_id, title, status, actor }
release.status_changed	a release’s status changes	{ release_id, from, to, actor }
release.deleted	a release is deleted	{ release_id, actor }

Note

status_changed events use your project’s configured status vocabulary, so from and to are whatever status names that project uses.

Next steps

• Managing webhooks — subscribe to these events.
• Webhooks overview — verify the signature on each delivery.