Slack
Overview
The Slack integration lets your team interact with Buildprint’s AI agent directly from Slack. Mention @Buildprint in any authorized channel or thread and the agent will respond with knowledge of your Bubble app — reading logs, reviewing recent changes, suggesting fixes, and more.
The agent runs as a specific workspace member (the “run-as” user), using their API keys and permissions. All conversations happen in Slack threads and are also visible in Buildprint’s chat history.
Connecting Slack
Go to Settings → Integrations → Slack in your Buildprint workspace.
Click Connect Slack workspace. A popup will ask you to authorize Buildprint in your Slack workspace.
Once authorized, you’ll see your Slack workspace name and connection status.
Who can connect? Only workspace owners and admins can connect or manage the Slack integration.
Reconnecting: If Buildprint adds new capabilities that require additional Slack permissions, you may see a prompt to reconnect. Click Reconnect to re-authorize with the updated permissions. Your channel settings will be preserved.
Configuring the agent
After connecting, configure these settings under the Slack integration page:
Run as user — The workspace member whose API keys the agent uses. Must be an owner or admin with active AI provider credentials (Claude, OpenAI, or OpenCode).
Model — Which AI model the agent uses (e.g. Claude Sonnet, GPT-4o). The available models depend on which providers the run-as user has connected.
Reasoning effort — Controls how much the model “thinks” before responding. Higher effort produces more thorough answers but takes longer. Options: None, Low, Medium, High.
Agent mode — When set to Build, the agent runs in Build mode and can make edits to your Bubble app. When set to Plan, the agent runs in Plan mode (read-only). This requires the editing feature to be enabled for your workspace.
Channel access modes
You control which Slack channels can mention the Buildprint agent and which projects the agent can access in each channel. There are three workspace-level access modes:
Per-channel permissions (default)
The most restrictive option. You explicitly add each channel that should have access, and configure which projects the agent can see in each one.
Channels not added to the list cannot use the bot — mentions will be ignored.
All public channels, custom private
A balanced option. The agent automatically responds in any public channel it’s invited to, with access to all projects. Private channels must be explicitly added and configured, just like the per-channel mode.
This is useful when you want broad access in public channels but tighter control over private discussions.
All channels, all projects
The most permissive option. The agent responds in any channel (public or private) where it’s invited, with access to all projects in the workspace. No per-channel configuration needed.
Managing channel permissions
When using Per-channel permissions or the private-channel portion of All public, custom private:
Click Manage channels to see available channels the bot has been invited to.
Add channels individually or use Select all.
For each channel, choose:
Selected projects — Pick specific projects the agent can access in this channel.
All projects — The agent can access every project in the workspace from this channel.
Remove a channel by clicking the × button.
Note: The bot must be invited to a Slack channel before it appears in the channel list. In Slack, type /invite @Buildprint in the channel you want to use.
How conversations work
When someone mentions @Buildprint in a message:
The bot adds an 👀 reaction to show it’s processing the request.
It reads the surrounding context — recent channel messages or the full thread history.
It resolves which projects the agent can access based on the channel’s configuration.
The AI generates a response and posts it as a reply in the thread.
The 👀 reaction is removed once the response is posted.
If you mention the bot again in the same thread, it continues the same conversation with full context of what was discussed before.
File attachments
You can attach files (screenshots, PDFs, documents, etc.) when mentioning the bot. The agent will download and analyze these files as part of its response.
Limits:
Maximum 30 MB per individual file
Maximum 100 MB total per message
Files that exceed these limits are silently skipped — the agent will still respond to the text portion of your message.
Troubleshooting
The bot doesn’t respond when mentioned
Is the bot invited to the channel? Type
/invite @Buildprintin the channel.Is the channel authorized? If using per-channel permissions, make sure the channel has been added in Settings → Integrations → Slack.
Does the channel have projects assigned? The agent won’t respond if it has no projects to work with. Add at least one project to the channel’s scope.
Is the run-as user’s API key still active? Check that the run-as user has valid provider credentials for the selected model.
The bot says the channel is not authorized
This means the workspace is using per-channel permissions and this channel hasn’t been added yet. Ask a workspace admin to configure Buildprint's channel permissions in the Buildprint Slack integration settings. Additionally, ensure the Slack workspace admin has approved the app if necessary.
The bot says there are no projects available
Either no projects exist in the workspace, or the channel’s scope is set to specific projects that have since been deleted. Update the channel’s project configuration.
I see a “reconnect” warning
Buildprint has added new features that require additional Slack permissions. Click Reconnect to re-authorize. Your existing channel configuration will be preserved.
The bot can access projects it shouldn’t
Check your workspace access mode. If set to All channels, all projects, the bot has access to everything. Switch to Per-channel permissions or All public, custom private for more granular control.