-
Can My Grok Bot Talk to Someone Else’s Grok Bot? 5 Ways to Try
Can my Grok Bot talk directly to a friend’s or coworker’s Grok Bot? Not directly, as far as the official help pages show. Bots can message each other, but the help pages only describe a Bot handing work to other Bots on the same person’s account, and a personal Bot only chats with its owner. To get two people’s Bots working together, pass the work through something you both use: a shared Team Bot, a Slack channel, email, a webhook, or a Trello board.
Heads up: we couldn’t test any of this hands-on. This is our own community guide, not an official one. Each method says how solid it is.
1. A shared Team Bot (the simplest option if you’re on the same team)
Officially supported. On Team and Enterprise plans, one person can share a Bot with teammates, much like sharing a doc. Each person’s chat with it is private, and it acts for whoever is talking to it.
-
Choose Share at the top right of the Bot’s chat.
-
Under Who has access, pick your team, your organization, or People you invite.
-
Teammates find it under + in the sidebar, then Browse shared Bots.
Good to know: your team needs at least one other member before you can share a Bot. If the owner or a Manager adds the Team Bot to Slack, then in a Slack thread or DM it acts for whoever mentioned it. It can hand work to that person’s own Bots, and their replies come back to the same thread. In your own DM with a Team Bot, you can also have it message other Team Bots you can use. Each reply uses the Grok Bot usage of the person it’s answering.
2. A shared Slack channel
The pieces are documented, but putting them together this way is our idea. When you connect the Slack app, your Bot posts as you, not as a separate bot, and only in channels you can post in. Separately, a routine can start when a word or phrase shows up in a Slack channel.
Try this:
-
Both people connect Slack to their own Grok Bot and join the same channel.
-
Agree on a tag word for handoffs, for example HANDOFF-TO-SAM.
-
Each person asks their own Bot for a routine, for example: “When a message in #our-channel contains HANDOFF-TO-SAM, read it and tell me what it asks. Never post back to Slack without my approval.”
-
To hand something over, ask your Bot to draft a Slack message with the tag. Check it, then send it.
Good to know: the other person sees your Bot’s post as coming from you. The changelog says routines can also watch a private channel, DM, or group DM while you’re still a member. According to the Grok Bot team, if you tag your own Bot in a channel, it works on a separate computer that doesn’t have your files. For anything that needs your files, ask it in your DM with it or in the app.
3. Email between Bots
Officially documented pieces. Each person can claim one email address ending in @mail.grokbot.com for their Bots. Your Bots can send and receive email there, and a routine can run when email arrives, optionally only from certain senders.
-
Ask your Bot, “Get yourself an email address.” It asks what name you want and shows an approval card. Nothing is claimed until you approve.
-
Or open Connect apps, choose Email, type a name under Choose a name, and choose Create address.
Try this: swap addresses with the other person. Each of you asks your own Bot for a routine that runs when mail arrives from the other Bot’s address. When you want to hand something off, ask your Bot to email the other Bot.
Good to know:
-
Email from a routine always waits as a draft until you press Send. There’s no way to have it sent unattended.
-
A Bot treats email from other people as information, not instructions. The other Bot reads your message, but its owner’s instructions decide what it does.
-
Your address takes tags like yourname+handoff@mail.grokbot.com, and a routine on a tag runs only for mail sent to that tag. Anyone can write to a tag, so keep a sender filter on the routine.
-
You get one address, and it can’t be renamed or deleted, so pick the name carefully.
-
On a team account, an admin has to turn on Agent Email first.
-
Some people have reported email triggers that wouldn’t save. If that happens to you, try a routine that checks the inbox on a schedule instead, or contact support.
4. A webhook
Setup is officially documented. A webhook is a private web address that starts one of your routines when something sends a message to it.
-
Ask your Bot to add a webhook trigger to a routine.
-
Open the routine in the desktop app. The Webhook section shows POST to (the address), key (the secret), and header (ready to copy). Click a field to copy it.
-
Whatever sends the call must include the key. A 200 reply means the run started, not that it finished. Check the Bot’s chat for the result.
Try this: give the other person your webhook address and key so their Bot or their own tools can start your routine. We haven’t seen an official guide for one person’s Bot calling another person’s webhook, so treat this as an experiment.
Good to know: the key is the part to protect, because anyone who has it can start your routine. Pause the routine to refuse calls. If the key gets out, Grok Bot staff say to delete the routine and make it again, which gives you a new address and key.
5. A shared Trello board as a handoff list
Lightly documented. The official @bot account announced in October that Grok Bot connects to Trello. A connected app can only do what your own account can already do. Trello isn’t on the official list of things that can start a routine.
Try this:
-
Each person connects Trello to their own Grok Bot from Connect apps, with their own Trello login.
-
Make one board you can both use, with lists like “For Sam’s Bot” and “Done.”
-
To hand something off, ask your Bot to add a card to the other person’s list.
-
The other person asks their Bot for a routine that checks their list on a schedule, such as twice a day. Schedules must be at least five minutes apart.
Good to know: we didn’t find an official guide on exactly what the Trello app can do. Check that your Bot can add and move cards on a test board before you rely on it.
What doesn’t work, as far as official sources show
-
Messaging someone else’s personal Bot directly. A personal Bot only chats with its owner.
-
A personal Bot handing work to other Bots from a Slack channel thread. A Team Bot can do that.
-
Team Bots in Slack Connect channels, with Slack guests, or in other Slack workspaces.
Stay safe
-
Keep sending behind your approval. By default, Bots draft outgoing email and Slack messages for you to review. Leave that on for any handoff setup, so your Bot never sends something to another person without you seeing it first.
-
Watch out for loops. Two Bots that answer each other can keep going back and forth. Only act on messages with your agreed tag word, tell each Bot never to reply to the other Bot on its own, and use the widest schedule that’s still useful. There’s no switch to stop Bots messaging each other, so tell your Bot, “Don’t message other Bots. Ask me first,” and ask it to remember that.
-
Each Bot answers to its own owner. Word your routines so your Bot reports to you instead of acting on whatever the other Bot asks.
-
Never share passwords or logins between people. Each person connects their own Slack, Trello, and email. Treat a webhook key like a password and only give it to someone you trust.
-
Keep an eye on usage. Every Bot reply counts toward your usage, including messages between Bots. A trigger on a busy Slack channel can use a week of usage in a day. All of your routines together can run up to 300 times an hour, and each one up to 200 times.
-
On a team, an admin can turn off messaging between Bots altogether.
Grok Bot help page:
https://docs.x.ai/grok-bot/chat-and-collaboration
docs.x.ai
Message and collaborate | SpaceXSI Docs
Message Grok Bot like a teammate with clear outcomes and decision boundaries.
-
Sorry, there were no replies found.
Log in to reply.