# Webhook shows a config was updated but doesnt give info about which secret in config was updated

**URL:** <https://community.doppler.com/t/webhook-shows-a-config-was-updated-but-doesnt-give-info-about-which-secret-in-config-was-updated/903>\
**Category:** Need Help\
**Created:** [January 6, 2023, 4:41am UTC](https://community.doppler.com/t/webhook-shows-a-config-was-updated-but-doesnt-give-info-about-which-secret-in-config-was-updated/903 "2023-01-06T04:41:08Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![ykamdar3](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/ykamdar3/32/644_2.png) [@ykamdar3](https://community.doppler.com/u/ykamdar3)\
**Post date:** [January 6, 2023, 4:41am UTC](https://community.doppler.com/t/webhook-shows-a-config-was-updated-but-doesnt-give-info-about-which-secret-in-config-was-updated/903/1 "2023-01-06T04:41:08Z")

</div>

I am using a webhook such that whenever a config is updated i will be alerted. The webhook however only tells me about the config update but does not tell me which secret in the config was updated.

I am finding it difficult to find this in documentation. Is this by design.

---

<div class="post-metadata">

**Author:** ![watsonian](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/watsonian/32/267_2.png) [@watsonian](https://community.doppler.com/u/watsonian)\
**Post date:** [January 6, 2023, 3:36pm UTC](https://community.doppler.com/t/webhook-shows-a-config-was-updated-but-doesnt-give-info-about-which-secret-in-config-was-updated/903/2 "2023-01-06T15:36:56Z")

</div>

Hi @ykamdar3!

Welcome to the Doppler Community!

Yep, what you’re seeing there is happening by design. The general idea behind the webhooks are to help with operations such as triggering a redeploy, for example. In most cases like that, something along the lines of `doppler run` is used and you don’t really need to know _which_ secret changed. That said, would you mind elaborating on your use-case here? Would having the names of the secrets that changed in the payload help? If so, I can pass that feedback on to our product team.

Regards,  
-Joel

---

<div class="post-metadata">

**Author:** ![ykamdar3](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/ykamdar3/32/644_2.png) [@ykamdar3](https://community.doppler.com/u/ykamdar3)\
**Post date:** [January 7, 2023, 5:12pm UTC](https://community.doppler.com/t/webhook-shows-a-config-was-updated-but-doesnt-give-info-about-which-secret-in-config-was-updated/903/3 "2023-01-07T17:12:43Z")

</div>

Hello @watsonian thank you so much for your prompt response. Yes, having the name of secrets that changed in the payload would definitely help.

My scenario is simple, i have a small team working in IST and another one working in PST. My end goal is to establish cross team communication regarding what secret was changed in a particular config in a project. So everytime a secret is updated i use it as a trigger (via webhook) and run a logic wherein information about that secret gets updated in teams channel. If i can get the secret name in payload i would parse it and then send the secret name as a teams message. I am configuring an integration between Doppler, Logic App and Microsoft teams.

---

<div class="post-metadata">

**Author:** ![watsonian](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/watsonian/32/267_2.png) [@watsonian](https://community.doppler.com/u/watsonian)\
**Post date:** [January 9, 2023, 5:01pm UTC](https://community.doppler.com/t/webhook-shows-a-config-was-updated-but-doesnt-give-info-about-which-secret-in-config-was-updated/903/4 "2023-01-09T17:01:56Z")

</div>

Thanks for sharing your use-case! I’ve gone ahead and shared your feedback with our product team for consideration!

---

<div class="post-metadata">

**Author:** ![ykamdar3](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/ykamdar3/32/644_2.png) [@ykamdar3](https://community.doppler.com/u/ykamdar3)\
**Post date:** [January 10, 2023, 6:35pm UTC](https://community.doppler.com/t/webhook-shows-a-config-was-updated-but-doesnt-give-info-about-which-secret-in-config-was-updated/903/6 "2023-01-10T18:35:43Z")

</div>

Thank you so much @watsonian . Please do let me know if this feedback is accommodated by Product team. Are there any release notes that Doppler releases where i can check this ? I just want to be sure that if this is being accommodated i dont miss it.

---

<div class="post-metadata">

**Author:** ![watsonian](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/watsonian/32/267_2.png) [@watsonian](https://community.doppler.com/u/watsonian)\
**Post date:** [January 10, 2023, 8:11pm UTC](https://community.doppler.com/t/webhook-shows-a-config-was-updated-but-doesnt-give-info-about-which-secret-in-config-was-updated/903/7 "2023-01-10T20:11:28Z")

</div>

We do post some limited release notes at [https://www.doppler.com/changes](https://www.doppler.com/changes), but not everything would show up there. I’m not sure if this would be something that would. I’ve added a note to the internal issue we have on this to post an update here if/when this change is made.

---

<div class="post-metadata">

**Author:** ![thomasp](https://sea2.discourse-cdn.com/flex016/user_avatar/community.doppler.com/thomasp/32/785_2.png) [@thomasp](https://community.doppler.com/u/thomasp)\
**Post date:** [June 16, 2023, 10:18pm UTC](https://community.doppler.com/t/webhook-shows-a-config-was-updated-but-doesnt-give-info-about-which-secret-in-config-was-updated/903/8 "2023-06-16T22:18:14Z")

</div>

The webhook payload now contains a `diff` object with a list of secret names that have been added, removed, and/or updated. You can find an example in our [docs](https://docs.doppler.com/docs/webhooks).
