WebHook Job Monitoring
Allow people to use the same WebHook Url used for triggering a runbook for querying job status.
Instead of doing a HTTP POST (used for triggering) you could allow a HTTP GET with the JobId as parameter. This would be a lightweight alternative for consuming runbook results no matter client and platform.
Note: Using the same url means same access token which leads to monitoring being possible for the lifetime of the access token.
This is a great idea that we are continuing to review.
Benjamin Goldman commented
what about just making the job status thing a light weight API?
Use the “Get” to retrieve the Job status (completed or failed with error message) from the same Webhook url (with Job id as parameter).