Slack
Connect Slack so the AI can post to your team's channels while it builds. Your published app can post to Slack too, using its own Slack credential (see Notifying a channel from your app).
Mirroring a build chat into a Slack thread has been switched off. Existing links no longer send messages to Slack.
Connecting Slack
- Open Integrations in the dashboard, or App connectors in the Studio, and choose Slack.
- Choose how Berrybell connects:
- Bot (marked Recommended) — installs a bot in your Slack workspace. Messages are posted by the bot rather than as you, and the connection doesn't depend on your own Slack account staying active.
- User — authorizes as you. The AI acts with your identity and your channel access. Because the connection belongs to the workspace, the AI posts as you in every teammate's runs, not only yours.
- Select Connect Slack and approve the request in Slack.
Connecting doesn't ask you to pick a channel. You name the channel when you ask the AI to post.
A bot connection asks Slack for chat:write, chat:write.public,
channels:read and users:read, so it can post to any public channel without
being invited first. A user connection asks for the same minus
chat:write.public, and posts wherever you can. Neither asks to read message
history, files or direct messages.
If the Slack card reads Coming soon, Slack can't be connected yet: there's no Connect Slack button, and Slack has no API-key option to use instead.
The connection belongs to your workspace, so any project in it can use Slack.
Notifying a channel from your app
Ask the AI to tie your app's events to Slack. For example:
- "Post a message to #signups whenever someone joins the waitlist."
- "Notify #orders when a customer completes checkout."
- "Send a Slack alert when a contact form is submitted."
The Slack connection is for the AI while it builds. Its token is never delivered to your published app, so for the app itself to post, it needs its own Slack credential — an incoming-webhook URL for the channel, or a bot token from a Slack app you create — saved in Cloud → Variables as a secret. The AI can write the code that uses it; tell it the variable's name.
Say what you want posted and where, then check the result in the live preview — what gets sent is whatever the AI built, so it's worth confirming the message says what you expect before you publish. A project-wide secret reaches the preview too, in both its lanes, so a test there posts a real message. To send preview tests to another channel, add values scoped to Agent sandbox and to Preview deploy. On a project with environments, a value set for the selected environment also works. See Where a value applies.
Keeping it under control
Like every integration, the AI's use of Slack follows the permissions you set, so you decide what the AI may send and when it should check with you first. Name channels deliberately when you ask the AI to post.
Those permissions don't cover your published app, which posts with its own credential: what it sends is whatever its code does. An incoming webhook always posts to the channel it was created for, whatever channel your request named, so create one for each channel your app should reach.
Next steps
- See all integrations: Integrations overview
- Add data behind your notifications: Databases