# Slack Integration Improvement Idea

**URL:** <https://community.apollographql.com/t/slack-integration-improvement-idea/6750>\
**Category:** GraphOS\
**Tags:** federation\
**Created:** [September 21, 2023, 2:53pm UTC](https://community.apollographql.com/t/slack-integration-improvement-idea/6750 "2023-09-21T14:53:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andrei\_Patseev](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/andrei_patseev/32/4600_2.png) [@Andrei\_Patseev](https://community.apollographql.com/u/Andrei_Patseev)\
**Post date:** [September 21, 2023, 2:53pm UTC](https://community.apollographql.com/t/slack-integration-improvement-idea/6750/1 "2023-09-21T14:53:56Z")

</div>

Hello! We received a slack notification about the schema change today (image 1), but the message was empty. Actual change was about deprecation of the field on the schema, but even on apollo studio platform you could not see the fact that field was deprecated.

Idea is - to display this information both on Studio and on Slack messages.

 ![Screenshot 2023-09-21 at 16.52.15](https://us1.discourse-cdn.com/flex019/uploads/apollographql/original/2X/7/77d1eaf70e9d30d6bfda03f5b33d2b36c776882f.png)

---

<div class="post-metadata">

**Author:** ![Justin\_Gonzalez](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/justin_gonzalez/32/5359_2.png) [@Justin\_Gonzalez](https://community.apollographql.com/u/Justin_Gonzalez)\
**Post date:** [February 6, 2025, 8:48pm UTC](https://community.apollographql.com/t/slack-integration-improvement-idea/6750/2 "2025-02-06T20:48:18Z")

</div>