How posting to Slack works
You send Bangers a thought: a voice note, a message, a piece of business context. The team drafts a message written for your Slack channel, in your voice. You review it, ask for changes if it's off, and approve it. Once approved, it posts to the channel on schedule.
Slack is also one of the places you can talk to Bangers directly: the same account that posts to your channel can receive your ideas and feedback in a Slack conversation, if you've set that integration up. That's separate from posting to a channel: a direct message to Bangers is how you feed it context and drafts, while a channel post is the finished, approved piece landing where your team or customers actually see it.
What Bangers knows about Slack
The drafting playbook treats Slack as a chat surface: 300 to 900 characters, conversational, a blank line between beats, no hashtags, no emoji spam, and it only ends on a question if the question is the actual point of the message. Bangers targets that length for Slack posts even though the underlying connection technically accepts far more. Slack itself starts truncating messages around 40,000 characters, and Bangers rejects anything over that hard ceiling before sending, but the drafting playbook never aims to fill it.
Threading is native here: when a draft has multiple parts, the parts after the first post as replies in a real Slack thread under the first message, the way Slack threading actually works, not simulated as separate top-level messages.
Slack publishing through Bangers doesn't currently support media: no photos or videos, generated or uploaded. Text only for now.
Connecting it
Connecting Slack takes two fields: a bot token and a channel ID.
The bot token comes from a Slack app you create at api.slack.com/apps, with the chat:write scope, installed to your workspace. Copy the Bot User OAuth Token it gives you (it starts with xoxb-). The channel ID comes from the target channel itself: open it, click its name, then About, and copy the Channel ID shown there. Before it'll work, invite the bot to that channel with /invite @yourbot. Slack rejects posts from a bot that hasn't been invited.
Bangers checks the token is live and that the channel is visible to the bot before saving the connection.
If you connect more than one Slack channel, say, a public updates channel and a smaller internal one, each gets its own channel ID, though they can share the same bot token from the same Slack app if it's already invited to both. Removing the bot from a channel with /kick or revoking the app's access from your workspace's app management screen is enough to stop Bangers from posting there.
When it fails
Every post needs your approval before it goes anywhere. If a publish fails after approval (the bot was removed from the channel, the token was revoked, the channel was archived), you're notified in Telegram within a minute with the reason, and you can retry. Every message is checked against the character limit before sending, so a thread doesn't end up half-posted.
Frequently asked questions
Does Bangers use real Slack threads, or does it just post separate messages? Real threads. Parts after the first are posted as replies to the first message, the way Slack's own threading works, not as unconnected top-level posts.
What do I need to set up in Slack before connecting?
A Slack app with the chat:write scope installed to your workspace, and the bot invited to the specific channel you want Bangers to post in, using /invite @yourbot in that channel.
Can Bangers post images to Slack? Not yet. Slack publishing through Bangers is text-only right now.