Most teams already decide things in Slack or Discord. Connect one channel and everything Toby's AI marketing team says in #team shows up there, under each agent's name. Ask "@Leo, where are we on SEO?" and Leo answers in the channel, like a colleague would.
Toby
Leo
IrisExactly what the connector does today. Reads happen right away; anything that changes, publishes or sends something waits for your approval.
Every message the team posts in #team (answers, recommendations, drafts ready to review) appears in the channel you picked, signed with the agent's name and role, like "Mia · Meta Ads". Messages you write in Toby show up there too.
Anyone in the channel can write to the team. Mention an agent by name ("@Mia, why did the cost per lead go up?") to pick who answers; otherwise Toby takes it and brings in the right teammate. On Slack, an 👀 reaction shows the team is on it.
Send the bot a private message to talk one-to-one, the same way you would open a DM in Toby. Start with "@Leo" or "@Iris" to reach a specific agent; Toby answers by default.
Toby's daily brief and weekly report land in the channel at the usual time, and measured results from #wins appear there too, so the whole team sees what worked.
When an action needs your go-ahead (publishing a post, sending an email, creating a page), the channel gets a short summary and a link. You approve in Toby: nothing is published or spent from a chat message.
TobyCMOAnswers messages that don't name anyone, delegates to the right specialist, and posts the daily brief and the weekly report in the channel.
LeoSEO & GEOLike every specialist, answers when mentioned: "@Leo, which pages lost clicks this month?" gets an answer from Search Console data, in the channel.
IrisData analystTurns quick questions into numbers ("@Iris, how did the newsletter do?") and explains what moved, with the figures from your connected tools.
Examples on fictional businesses, in the app's exact format. Numbers are examples, not promises: yours come from your own data.
TobySlack · #marketingExample
LeoSlack · reply in channelExample
KaiSlack · approval requestExample
LeoSlack · #winsExampleAbout 10 minutes
Permission to install an app in your Slack workspace (or to add a bot to your Discord server).
Slack: on api.slack.com/apps, choose Create New App → From an app manifest and paste the manifest Toby gives you. Install it to your workspace.
Copy the Bot token (starts with xoxb-), then create an App-level token with the connections:write scope (starts with xapp-).
In the channel you want to use, type /invite @Toby, then copy the channel ID from the channel details.
In Toby, open Integrations → Slack → Connect, paste the two tokens and the channel ID. Toby checks them right away.
Discord instead: create a bot in the Discord developer portal, turn on Message Content Intent, add it to your server, then paste its token and the channel ID in Integrations → Discord.
One channel per connection. That channel plays the role of #team. Mentioning the bot elsewhere gets a short reply pointing to the right channel.
Approvals happen in Toby, not in the chat. It is deliberate: publishing, sending and spending stay one click away from the full preview.
Messages start flowing about a minute after connecting, the time for Toby to open the connection.
Cards become text. Recommendations, drafts and charts are summarized in the message with a link to the full version in Toby.
If a token is revoked (app deleted, token reset), the connection shows an error in Integrations: reconnect it with the new token.
For approvals, yes: approving a post, an email or a page happens in Toby, where you see the full preview. For questions, briefs, reports and day-to-day discussion, the channel is enough.
Yes. Anyone who can write in the connected channel can ask the team something, and the answer is posted in the channel for everyone. The team sees their display name, so it knows who is asking.
No. It only listens to the channel you connected and to direct messages sent to the bot. In other channels, it only reacts if someone mentions it, to point them to the right channel.
No. Slack works in Socket Mode and Discord through its gateway: Toby opens the connection itself, so there is nothing to host or expose.
The same rules as in Toby apply. When the team is paused or the daily cost cap is reached, Toby says so in the channel instead of running the request.
Whichever your team already uses. Both work the same way: one channel mirrors #team, people mention agents by name, and direct messages to the bot work.
Other integrations
Use cases and guides
Create your account, paste your URL and get your growth audit, your Brand Brain and your first three recommendations, already prepared.
7-day free trial, then $99/month per company. Cancel anytime. Already have an account? Sign in