Webhooks & Notifications

Currently, the timeout is set to 5 seconds. Making this customisable would allow for services that take longer than 5 seconds to respond, ensuring that longer running services could still receive these webhooks successfully.

We would like to generate CircleCI webhooks for events such as when a workflow starts and a pipeline starts.

Missing a webhook event for a workflow being on hold caused by an approval job.

Summarized from https://discuss.circleci.com/t/organization-wide-webhooks/2200 : Currently we are setting the same webhook for many projects. It would be handy to have an option for organization-wide webhooks, that is, webhook notifications that apply to every project of the organization. As an example we currently set the exact same Slack hook for every project, and it is very easy to forget doing that when adding new projects. GitHub introduced the exact same feature a while ago and it’s been an incredible help for us. CCI-I-568

Proposed Feature: Display a list of recent attempted webhook deliveries, with error and payload details.

When an organization hits their concurrency limit, jobs are queued. It would be useful to be notified when jobs are being queued due to concurrency limits.

Hi, my webhook triggers twice. in __ow_headers and "http"->headers "x-request-id" and "cf-ray" are different for both triggered hooks, but all the other things are exactly the same. It brings problems to me, I only need one trigger... (In Project settings there is only one trigger..)

The webhook test should send through the body of the last webhook that would have been, or was, fired. Or at least it should send through the same schema. It's somewhat painful to test handling of the webhook when you need to wait for a job or workflow to complete to get the contents of a normal webhook.

Use case: I have a deployment hook for render.com which deploys my app on every successful build. Issue: At the moment whenever any branch passes, the webhook is triggered and the hosting platform deploys main branch to their service. Wasting resources and allowing for potential downtime every time a branch is puched to CircleCI. Request: I want the webhook to only be triggered when main branch passes. Filter webhooks to only be triggered for certain branches.

The webhook payload does not seem to include information about the person/account that triggered the build. Including something similar to the CIRCLE_USERNAME env var would be really helpful in extending / simplifying the automation we've built around deployments. From CircleCI docs: CIRCLE_USERNAME – "The GitHub or Bitbucket username of the user who triggered the pipeline."