Socket Mode enables you to build powerful Slack integrations safely behind your company’s firewall and unlocks access to the platform’s most interactive features, from the Events API to Block Kit to Workflow Builder.
Today, millions of daily active users get exponential value from bringing their work into Slack. For developers, this means that as Slack grows, you grow with us, sharing in our goal to improve the way teams collaborate through business-critical integrations.
Capabilities that Socket Mode unlocks
Socket Mode enables a quick and secure way to start building apps without additional infrastructure management.
Previously, anyone could use the Slack platform to build apps based on the standards and protocols of the open web, using HTTP to send and receive messages and other data. This didn’t require any special tooling or software—fundamentally, any Slack app is a web app.
However, for anyone hosting their apps on-premise or behind a firewall, this presented a challenge for integrating with Slack, specifically when routing Slack API data to apps within a restricted environment.
Some customers built proxies to safely transfer packets from the internet to their network. Others created WebSocket connections using the RTM API, but the RTM stream primarily contains message data and doesn’t support many of the richer interactive features of the platform, like Events, Block Kit or shortcuts.
For Bob Bell, a software engineer at Dell Technologies, using Socket Mode means not having to manage additional layers of software.
“This let us replace a layer 7 proxy, which required coordination to set up,” Bell says. “With Socket Mode, we can just immediately start writing a Slack app.”
Develop locally, deploy anywhere
Any app, new or existing, can connect over Socket Mode. The logic stays the same, and the payloads remain identical—regardless of delivery method.
We often recommend tooling like ngrok to manage local development. Now you can enable Socket Mode, connect from your local machine, build out the logic of your app, then deploy to a web server and switch back to HTTP.
Apps can choose the delivery protocol, WebSocket or HTTP. It’s a binary switch that gets flipped for your app that can happen at any point and flip back if necessary. Your app simply needs to be able to handle either HTTP or WebSockets.
With Socket Mode enabled, an app connects to Slack by establishing a secure WebSocket connection. From here, all dispatches from Slack are sent to your app over this WebSocket and nothing is sent via HTTP.
Build better with Bolt
After enabling Socket Mode, all that’s required for your app is a WebSocket connection. There are no new proprietary protocols or custom SDKs required—industry standards all the way.
If you’re building an app without an SDK, fear not! Here’s a quick implementation guide to help you along the way.
To build with Socket Mode, visit our API documentation for an introduction to some core concepts, the new app token, and related sample code.
Need more hands-on support? View our webinar on building with Web Sockets at any time to quickly get up to speed.
We look forward to a whole new class of Slack apps hosted everywhere. Happy building!
We value your questions and feedback. Email us at firstname.lastname@example.org.