Continuous integration within Gearset is a powerful tool, but what if you need to trigger third-party services as part of your release process? 

Outgoing webhooks allow you to automate this process, so you can kick off Selenium tests (for example) if your CI job runs successfully.

Any service with an API can be triggered directly from within Gearset.

Setting up a CI job with an outgoing webhook

To create a CI job with an outgoing webhook, start by following the usual setup process.  On the Outgoing webhooks tab you can add the URL you’d like Gearset to post to. Choose whether you’d like to use Basic Authentication in the post, then add the payload in either json or xml format.

We'll only post to the url in the event of a successful run of the CI job. And we'll post the payload you provide. We don't currently add any information in about the job name or status, so you'll need to include any references you need in that payload.

Did this answer your question?