# Trigger on message send in slack **URL:** \ **Category:** Ideas & Features\ **Created:** [October 15, 2025, 5:46pm UTC](https://community.fibery.io/t/trigger-on-message-send-in-slack/9824 "2025-10-15T17:46:08Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\ **Post date:** [October 15, 2025, 5:46pm UTC](https://community.fibery.io/t/trigger-on-message-send-in-slack/9824/1 "2025-10-15T17:46:08Z")
Hey! I’m trying to avoid using the slack message integration out of fear it will depreciate in March. I am wondering if there’s a current way or if the Fibery Slack App could add a setting that creates an entity in Fibery every time a message is sent in a specific channel. Essentially running the “Create Entity” (with the a preset type per channel) for all message in that channel. I think long term this could “solve” the API changes slack is implementing by running on a trigger (message creation) vs syncing all messages. Is there a way to do it right now? And does this make sense as an addition to the Fibery Slack App? I don’t work with slack often, so idk what’s possible and what isn’t. From research: I see there’s Slack Workflows. Looks to be the right place to have this set up, but Fibery isn’t one of the options as apps to choose from in the Workflow Action. Changed to Idea and Feature Tag. ---
**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\ **Post date:** [March 11, 2026, 6:08am UTC](https://community.fibery.io/t/trigger-on-message-send-in-slack/9824/2 "2026-03-11T06:08:35Z")
I am also worried about the Slack deprecation this month…does anyone have any news? Ironically my team was moved on from Slack for about 8 years but we are doing more and more asynchronous work and though the integration would be a better way than texting with each other - have done a lot with Fibery threads but just not the same as being able to quickly IM a partner such as with Slack, texting, What’s App, etc. ---
**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\ **Post date:** [May 28, 2026, 1:38pm UTC](https://community.fibery.io/t/trigger-on-message-send-in-slack/9824/3 "2026-05-28T13:38:54Z")
Completed today. > [@May 28, 2026 / User access improvements, Slack Workflow Steps](https://community.fibery.io/t/may-28-2026-user-access-improvements-slack-workflow-steps/10917): > > It seems we slowed down with releases volume in May turtle, but I hope we will speed up in June again t_rex. User Group members can see each other by default By default, members of the same [User Group](https://the.fibery.io/@public/User_Guide/Guide/User-Groups-47) (e.g., Team or Role) can now see each other, even if you’ve configured strict [user visibility](https://the.fibery.io/@public/User_Guide/Guide/Access-to-Users-497/anchor=Default-visibility--6e5a10ed-da4f-41d1-8310-6a0e446efd71) on the workspace level. This applies to all existing as well as future User Groups. If you don’t like the new behavior, you can disable it in the Access settings of a particular User Group DB: ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [June 1, 2026, 7:48pm UTC](https://community.fibery.io/t/trigger-on-message-send-in-slack/9824/4 "2026-06-01T19:48:29Z")