Slack
Ask Baker about your marketing without leaving Slack
Add Baker to your Slack and choose which channels talk with each company. Mention @Baker in a channel or a direct message to ask about your ads, landing pages and leads, or to prepare a change. Baker answers with your own access in Baker, and nothing a conversation prepares goes live until someone who may publish presses Publish and confirms. A routine set to Auto publish in Baker publishes on its own.
- Answers in the thread
- Prepares changes for you to review
- Publish with a confirm step
- Routine results in your channel
- Everyone keeps their own access
- Built by
- Baker
- Category
- Slack and AI assistants
- Plan
- Every plan
- Connects by
- Adding Baker
- Updated
- November 21, 2026
How it works
From connecting to publishing, in three steps
- 1
Add Baker to Slack
An admin opens Settings → Baker in Slack in Baker, presses Add to Slack and allows Baker in the Slack workspace.
- 2
Choose its channels
Bind the channels that talk with each company and say who reads each one, your team or the client. Invite @Baker to private channels.
- 3
Mention @Baker
Ask in a channel or a direct message. The first time, Baker sends you a private link to connect your Slack account to your Baker account.
What Baker does
Everything Baker does with Slack
-
Answers in the thread
Mention @Baker and it answers from your Google Ads, Meta, LinkedIn and website numbers, in the thread where you asked. Reply in that thread to carry on, with no need to mention it again.
-
Prepares changes for you to review
Ask for a change and Baker prepares it, then posts a card in the thread that lists every change, with Publish and Open in Baker.
-
Publish with a confirm step
Press Publish, read the private question that says what will change, and confirm. Baker tells the thread whether every change went through.
-
Routine results in your channel
A routine can post what it did to the channels you pick, with the changes it prepared, so your team sees it where it already works.
-
Everyone keeps their own access
Each person links their Slack account to Baker once. People who can only view get answers; people who can edit can also publish.
-
Channels shared with a client
Mark a channel as the client's and Baker shows there only what a viewer of the company sees in Baker, including in Slack Connect channels.
-
Remembers what you tell it
Ask Baker to remember a target or a rule and it uses it in later conversations. You can see and delete what it keeps in Settings → Memory.
You approve
Nothing changes in Slack until you press Publish
Baker prepares every change in a chat and shows it to you. It applies only when someone on your team who may publish presses Publish, and if you discard the chat, nothing applies.
Data and permissions
What Baker reads and what it can change
Exactly what Baker uses from your account, when and why. Baker asks only for the permissions this needs.
| What | Baker | When | Why |
|---|---|---|---|
| Messages that mention @Baker | Reads | When you ask | To answer the question you asked. |
| Replies in threads Baker is part of, and your direct messages with Baker | Reads | When you ask | So you can carry on a conversation without mentioning @Baker each time. Other conversations in a channel are ignored. |
| A channel's recent messages, once, when someone mentions @Baker | Reads | When you ask | To find a file posted just before the question. |
| The channels in your workspace, and private channels Baker was invited to | Reads | When you ask | So an admin can choose which channels talk with a company. |
| People's Slack name and email | Reads | When you ask | To show whose Slack account is being linked to Baker, so each person is answered with their own access. |
| Reactions to Baker's messages | Reads | When you ask | Requested with the app for a later feature. Baker does not read reactions today. |
| Answers, change cards and Publish results in the thread | Sends | When you ask | To reply where you asked and to say how a Publish went. |
| Routine results in the channels you chose | Sends | All the time | So your team sees what a routine did and what it prepared. |
| Direct messages to one person | Sends | When you ask | To send your private link to connect your account, or to ask which company you mean in a direct message. |
| Your ads and the other platforms you connected to Baker | Changes | Only when you press Publish | Only after someone who can edit the company presses Publish in Slack or in Baker and confirms. |
What you need
- An admin in Baker to add Baker to Slack and choose its channels.
- Someone allowed to add apps to your Slack workspace.
- A Baker account for each person who talks to Baker in Slack.
- Conversations in Slack use your company's Baker credits, like chats in Baker.
Frequently asked questions
Does Baker read every message in our Slack?
No. Baker reads messages that mention @Baker, replies in threads it is part of and direct messages to it. When someone mentions it, it may look once at the channel's recent messages to find a file posted just before. Everything else in a channel is ignored.
Can Baker publish a change on its own from Slack?
No. Publishing is a button a person presses and then confirms, and Baker checks that the person can edit the company each time. Changes to landing pages, Forms or Knowledge are published from Baker itself. Only a routine someone set to Auto publish in Baker publishes without a press.
Can Baker's answers be wrong?
Yes. Baker's answers are written by AI and can contain mistakes. Check the numbers that matter and read every line of a change card before you press Publish.
What does Baker keep from Slack?
The workspace name, the channels bound to each company and who reads them, which Slack person is which Baker person, the Slack name and email of each person sent a link to connect their account, the conversations in threads Baker is part of with their summaries, direct messages with Baker, and what people ask it to remember. Slack's access key is kept encrypted. Read more in our privacy policy at withbaker.com/privacy.
Can we talk to Baker in a channel shared with our client?
Yes. Bind the channel with The client as who reads it. Everyone there sees only what a viewer of the company sees in Baker, and each person keeps their own access when they publish.
Keep learning
- Set up Baker in Slack Add Baker to your Slack workspace, choose the channels that talk with each company, link your account and publish from a thread.
- Publish your changes What Publish sends live, in what order, how to check it worked, and how to discard a chat's changes instead.
- Set up a routine so Baker works on its own Have Baker do a job on a schedule or when something happens, review what each run prepared, and post results to Slack.
Used together with
- Claude and ChatGPTConnect Claude, ChatGPT or any assistant that supports MCP to Baker. It reads and prepares work as you, and you publish in Baker.
- Google AdsBaker reads your Google Ads accounts, prepares campaigns, keywords, ads and budgets, and changes Google Ads only when you press Publish.
- Meta AdsBaker reads your Meta ad accounts, prepares campaigns, ads, budgets and audiences, and changes Meta only when you press Publish.