Last updated:
Quick answer
When “Add Bot” or template install fails, paste the public template link into a Bot you already trust and ask it to add that template as a coworker; if you are at a bot limit, remove an unused Bot first. Grant only the connectors the new coworker needs, run a shared-computer security audit first, and keep spend, send, and delete behind approval.
At a glance
All outcome figures are estimates from cited sources, not independent verification by us.
- What it is allowed to do
- Read-only
Only reads, researches, or summarizes. It never drafts outbound content or changes anything.
- Time saved (estimate)
- Not measured yet
- Difficulty
- Beginner
- Tools needed
- Grok Bot
- Typical cost
- Grok Bot: paid plan usage per vendor pricing; template giveaways are often free to install but usage still counts against your plan.
Reviewed Oct 19, 2026
Basis (estimate): Not stated in sources.
What does this setup do?
Install a public Grok Bot template (for example Side Hustle–style giveaways people share on X) when the in-app “Add Bot” button errors, without copying proprietary template prompts, then onboard the new coworker with minimum connectors and approval gates.
Who is it for?
Grok Bot users who see “couldn’t add bot,” install failures, or bot-count limits when trying a shared template link, not people looking for guaranteed income from a template alone.
How do you set it up?
Tools
- Grok Bot account with at least one Bot you already use
- Public template URL from the author (link only. You do not need their private prompt pack)
- Optional: separate read-only auditor Bot (see shared-computer security audit setup)
Steps
- Copy the public template or giveaway link (for example from the author’s X post). Do not paste proprietary prompt packs from paid products.
- Open a Bot you already trust. Paste the link and ask it to add that Bot as a coworker using the product’s coworker flow (community workaround when Add Bot fails).
- If install still fails, check whether you hit a bot limit. Archive or remove an unused Bot, then retry.
- Before granting connectors, run or review the shared-computer security audit setup; connect only what this coworker’s first job needs.
- Tell the new coworker what it may not do: no spend, no outbound send, no delete, no publish without your explicit approval each time.
- Assign one narrow first task for about a week; note usage cost and how long you spend reviewing output before expanding scope.
Example output
Illustrative. Your results will differ.
- Your bot set up and connected in under 10 minutes
- Tested with a sample task before going live
- You stay in control of what it can touch.
Where to paste this prompt
Grok Bot: Grok Bot → Routine or scheduled task template
Copy-paste prompt
Adapt bracketed fields to your situation.
I want to add a public Grok Bot template as a coworker. The Add Bot button failed for me.
Template link (public URL only): [paste template or giveaway URL]
Using Grok Bot’s coworker features, walk me step by step to add this template Bot to my account. If the UI blocks install, suggest the workaround of adding via an existing Bot I trust.
Rules for you:
- Do not reproduce or invent proprietary template prompts from paid products. Only use what the public link allows.
- Do not connect new connectors or change approval settings without listing each change and waiting for my yes.
- After install, propose the minimum connectors for one narrow first job: [describe job in one sentence].
- Remind me to remove an unused Bot if I am at a bot limit.
Do not spend money, send messages, or delete anything.Newsletter
Get the free starter pack
Free starter pack with five beginner copy-paste prompts after you confirm, plus three sourced setups in your inbox each week. Unsubscribe anytime.
What usually goes wrong?
Where agents tend to stall on this job. More patterns in Where AI gets stuck.
- “Couldn’t add bot” and similar errors often mean a failed install or account limit. Retry after removing an unused Bot, not after pasting secrets into chat.
- Public templates do not create an audience or distribution; revenue demos in launch threads often reflect the author’s following, not a typical outcome for installers.
- We document install steps and guardrails only. We do not reproduce proprietary template contents from paid or private packs.
- Every coworker shares the same cloud computer as your other Bots. Treat connector grants as high risk until the security audit looks clean.
Which chat tools work with this prompt?
Paste the prompt into any of these assistants (free or paid tiers).
- Grok Bot
Common questions
- How do I add a Grok Bot template when Add Bot fails?
- Public replies describe pasting the template link into an existing Bot you trust and asking it to add the template as a coworker, then retrying after clearing an unused Bot if you hit a limit.
- What does "couldn't add bot" mean?
- It usually means the install did not complete. Often a transient error or a bot-count limit. Remove or archive an unused Bot and retry; do not paste passwords or API keys into chat while debugging.
- Do I hit a limit on how many Grok Bots I can have?
- Many users report a cap in public threads when adding templates; free an unused slot before installing another coworker. Check current limits in Grok Bot settings. We do not publish a fixed number.
- Should a new template Bot get all my connectors?
- No. Grant only the minimum connectors for one narrow first job. Run the shared-computer security audit setup first and expand access only after review.
- Will a Side Hustle template make money without an audience?
- Not by itself. Templates help you run a workflow; distribution and sales still depend on your reach, offer, and follow-up. We do not promise income from installing a template.
Where should you go next on this site?
What tips make it smoother?
- Install through a Bot you already use before fighting the storefront Add Bot button. This matches public thread workarounds.
- Pair with the shared-computer security audit on a schedule before and after adding coworkers.
- Keep the first job read-only or draft-only (research lists, outlines) until approvals behave predictably.
Where do the claims come from?
Summaries use public sources linked below, not independent verification. How setups are picked.
- Read @AlexFinn’s write-up (x.com)
@AlexFinn: Oct 2026 template giveaway wave; replies describe install failures, bot limits, and adding via an existing Bot / coworker (paraphrased on this page).
- Read original on docs.x.ai
Official: approvals, shared computer, connector hygiene.
Related setups
- Bot shared-computer security audit
Before you give Bot Bots more connectors or routines, run a read-only audit of what every Bot on your account can see on the shared cloud computer.
- Route Bot tasks to your Claude and ChatGPT subscriptions
Install Claude Code and OpenAI Codex CLIs on Bot’s shared cloud computer, sign in with your own Anthropic and OpenAI subscriptions, then set routing rules so writing, coding, and browser-heavy jobs hit the model you already pay for, without pasting the setup into Codex or Claude Code directly.
- iPhone Action Button opens one bot
Map the iPhone Action Button (or Back Tap) to a Shortcut that opens one specific Bot chat instantly, so you are not hunting the sidebar when you want the same agent every time.