Skip to main content

Webhooks

Updated over 2 months ago

⚠️Webhooks are available in Startup, Business, and Enterprise subscriptions

Webhooks in Qase allow you to create a connection between your own resources and Qase so that when a specific event takes place in Qase, it also sends a request to an endpoint you defined for that particular event.

Setting up a webhook is easy - navigate to the Settings of a project where webhooks will be needed, then select Webhooks and hit "Create new webhook":

Webhooks can be enabled and disabled as needed:

A webhook will be automatically disabled based on the following conditions:

  • the endpoint where webhook is sent does not return any response within 15 seconds of the payload being sent

  • within 2 days period of time, the webhook was not able ​to send a successful request to the specified endpoint

When a webhook is disabled due to failed attempts above, you will receive an email notification about it.

There are a few parameters you need to define for a new webhook:

  • Basic:

    • Title: a name for your webhook.

    • Endpoint: a URL address that is configured on your side and is accessible to the public web; this address will be where Qase sends a request upon a defined event happening.

    • Secret: we are sending this text as an X-Qase-Secret header so that you can authenticate your webhook.

  • Events: in this section, you will set up a trigger for Qase to send a request to the endpoint; there are several to choose from, and it is also possible to enable multiple event-triggers for a single endpoint.

      • Create test case

      • Update test case

      • Delete test case

      • Clone test case

      • Create test suite

      • Update test suite

      • Delete test suite

      • Clone test suite

      • Create test plan

      • Update test plan

      • Delete test plan

      • Create shared step

      • Update shared step

      • Delete shared step

      • Create milestone

      • Update milestone

      • Delete milestone

      • Create custom field

      • Update custom field

      • Delete custom field

      • Test run start

      • Test run aborted

      • Test cases added to run

      • Delete test run

      • Complete test run

      • Public link turned on

      • Create defect

      • Resolve defect

      • Delete defect

      • Create test review

      • Update test review

      • Approval status change

      • Reviewer added

      • Reviewer removed

      • Merge test review

      • Reopen test review

      • Comment test review

      • Decline test review

      • Delete test review

    • Results:

      • Create test run results

      • Update test run results

      • Delete test run results

Did this answer your question?