You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
📢 Important Update – Slack Discontinuing Legacy Custom Bots
SAP Slack
#slack-at-sap-updates
Important update to support for legacy custom bots!
Beginning March 31, 2025, Slack will discontinue support for legacy custom bots, used for the Real Time Message API and Web API methods. This means that any legacy custom bots installed in your workspace or org will no longer work.
If you want your integration to continue working, you will need to create a modern Slack app instead. Slack has also reached out directly to developers with more information, and users can refer to the Discontinuing support for legacy custom bots and classic apps page for next steps.
We currently have a bot that sends Slack notifications when issues are labeled. Since Slack is discontinuing legacy custom bots, we need to:
1. Verify if our notification bot relies on legacy custom bots.
2. Assess the impact of this change on our workflow.
3. Develop a migration plan to a modern Slack app if necessary.
This is a critical change that might break our notifications if not addressed before the deadline. Immediate investigation is required.
📋 Next Steps
• Check if our bot uses the Real Time Message API or Web API methods with legacy custom bots.
• If affected, determine required changes for migrating to a modern Slack app.
• Implement and test the necessary updates.
• Ensure the new implementation is in place before March 31, 2025.
❗ Action Required ASAP
Please investigate this issue and provide feedback on whether we are impacted. If affected, we need a solution proposal to ensure a smooth transition before the deprecation deadline.
Verify if we use the modern Slack app.
If yes bump all dependencies to the newest version and enable auto bump.
If no, we need to migrate it.
The text was updated successfully, but these errors were encountered:
dekiel
added
the
breaking change
The issue/PR contains some breaking changes or changes influencing the development process
label
Mar 4, 2025
📢 Important Update – Slack Discontinuing Legacy Custom Bots
We currently have a bot that sends Slack notifications when issues are labeled. Since Slack is discontinuing legacy custom bots, we need to:
1. Verify if our notification bot relies on legacy custom bots.
2. Assess the impact of this change on our workflow.
3. Develop a migration plan to a modern Slack app if necessary.
This is a critical change that might break our notifications if not addressed before the deadline. Immediate investigation is required.
📋 Next Steps
• Check if our bot uses the Real Time Message API or Web API methods with legacy custom bots.
• If affected, determine required changes for migrating to a modern Slack app.
• Implement and test the necessary updates.
• Ensure the new implementation is in place before March 31, 2025.
❗ Action Required ASAP
Please investigate this issue and provide feedback on whether we are impacted. If affected, we need a solution proposal to ensure a smooth transition before the deprecation deadline.
The text was updated successfully, but these errors were encountered: