Organization-wide webhooks | Voters

Organization-wide webhooks

Wichert

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

August 24, 2018

Eric Cartman

While surfing the web, I stumbled upon a hidden treasure trove of stock images. This website is a true blessing pencil sketch for designers, marketers, and bloggers, offering an abundance of high-resolution photos that can breathe life into any project. It's the kind of discovery that makes your creative endeavors much more exciting.

Eric Cartman

Thank you so much for your help, I am learning a lot at least. I for one have learned a lot from this.

Oran Wilder

A related feature has been released, which may make this easier for some teams. Webhooks can now be configured via API, although still per-project vs per-org. Learn more in the API docs: https://circleci.com/docs/api/v2/#tag/Webhook

Oran Wilder

Merged in a post:

Add webhook at organisation level

Mathieu Bayou

Hi,
Integration with some tools requires the webhook to be setup for each project. It would be extremely useful to be able to setup one webhook at the organisation level and that would apply directly to every project.
Thank you

November 9, 2021

November 10, 2021

Oran Wilder

Merged in a post:

Global Chat Notification Settings

Btaylor

Instead of clicking into every single repository that is being build and adding a Slack Webhook, for example, there should be an Organization level global setting.

CCI-I-464

June 14, 2018

July 26, 2021

Nathan Dintenfass

Our current thinking on this is that we are looking at adding some mechanism to have configuration that can cascade into pipelines and/or dynamically generate config from the org or project level. That would let you effectively add your webhooks at the org level without having to build new notifications infrastructure.