Gearset

You can set an outgoing webhook as part of continuous integration jobs in Gearset. This is documented <a href="https://docs.gearset.com/en/articles/2652073-outgoing-webhooks-in-continuous-integration-jobs">here</a>.

The standard payload available for CI outgoing webhooks contains information about the CI job and run.

{   "job": {     "name": "dev to uat"   },   "run": {     "status": "Succeeded",     "type": "Deployment",     "start_date_utc": "2020-02-24T16:37:41.899337Z",     "end_date_utc": "2020-02-24T16:39:06.689647Z",   } }

We include the <code>X-Gearset-Event</code> header to specify which event the outgoing webhook was triggered by. For continuous integration job runs, this is set to <code>ci_job_run</code> .

In the standard payload we provide the following:

Run status — <code>string</code>  that can be <code>Error</code>, <code>Succeeded</code>,  or <code>Failed</code>.

Run type — <code>string</code>  that can be <code>Deployment</code>  or <code>Validation</code>.

Run start date — <code>string</code>  in <code>ISO 8601</code>  format <code>datetime UTC</code>.

Run end date —  <code>string</code>  in <code>ISO 8601</code>  format <code>datetime UTC</code>.

- Job name — <code>string</code>. 
- Run status — <code>string</code>  that can be <code>Error</code>, <code>Succeeded</code>,  or <code>Failed</code>. 
- Run type — <code>string</code>  that can be <code>Deployment</code>  or <code>Validation</code>. 
- Run start date — <code>string</code>  in <code>ISO 8601</code>  format <code>datetime UTC</code>. 
- Run end date —  <code>string</code>  in <code>ISO 8601</code>  format <code>datetime UTC</code>.

If you have any questions about setting up your outgoing webhooks, please <a href="https://docs.gearset.com/en/articles/2288721-contacting-gearset-support">reach out to our team</a> using the in-app chat.

Example payload format

Payload format