Clawdbot gives you a text-based way to handle routine Google Ads work without living in the dashboard. It runs on a machine you control, stays online in the background, and responds through chat apps like Telegram, WhatsApp, or iMessage. For marketers, that means less clicking around for reports and more time spent on decisions.
What Clawdbot actually is
Clawdbot is an open-source AI assistant that runs continuously on your own hardware. It is not a SaaS product. It is not a browser add-on. It is an AI agent operating on a computer you manage.
You message it through Telegram, WhatsApp, iMessage, or another chat app. It can control a computer, open tools, gather information, write drafts, and send updates back by text.
For Google Ads teams, the appeal is simple: instead of signing in for every small task, you can send a message and get the result back.
If you would rather watch the process, there is also a 20-minute YouTube video that covers the full setup.
Gear and accounts you need first
Before you install anything, make sure you have the basics.
Hardware choices
Pick one:
- Mac Mini. Any model works, including the $600 base version
- An unused old laptop
- A VPS server for $5/month on Hetzner or DigitalOcean
Software requirements
- Node.js 22 or newer
- An AI API key from Claude, OpenAI, or another provider
Accounts to have ready
- Telegram, WhatsApp, or another messaging app
- The Google Ads account you want it to work with
Install the software
1. Put Node.js on the machine
If Node.js is not already installed, use the command for your operating system.
Mac
brew install node
Linux
sudo apt install nodejs npm
Windows
Download it from:
https://nodejs.org
Then verify the version:
node --version
You should see v22 or above.
2. Install Clawdbot
Open your terminal and run either the installer script or the npm package.
Installer script
curl -fsSL https://clawd.bot/install.sh | bash
Manual install
npm install -g clawdbot@latest
3. Launch onboarding
Start the setup wizard with:
clawdbot onboard --install-daemon
The wizard handles the main configuration steps.
Walk through the onboarding flow
Setup usually takes about 30 minutes.
During onboarding, you will make three main choices.
Pick an AI model provider
Options include:
- Anthropic (Claude) — recommended for best results
- OpenAI (ChatGPT)
- Local models if you have a powerful GPU
Connect a messaging channel
Telegram is the easiest option to configure.
You will:
- Create a bot token through Telegram's BotFather
- Scan a QR code or paste in the token
Install it as a background service
Using the daemon option keeps Clawdbot running in the background. It will also start automatically when the computer boots.
Give it access to Google Ads
Clawdbot works by controlling the screen and clicking through the interface. It signs in to Google Ads the same way a person would.
You have two ways to set this up.
Option 1: Sign in once on that machine
- Open a browser on the machine running Clawdbot
- Visit
ads.google.com - Log in with your Google account
- Leave the session signed in
Once that is done, Clawdbot can open Google Ads when you ask.
Option 2: Use a separate Google account
This is the safer route.
- Create a new Gmail account for Clawdbot
- Add that account as a user in Google Ads with read-only or standard access
- Sign in to the Clawdbot machine with that account
This keeps your personal inbox and credentials separate from the automation setup.
Run your first test
Open the messaging app you connected and send a simple request such as:
Hey, can you open Google Ads and tell me how my campaigns performed yesterday?
Clawdbot will typically:
- Open a browser
- Go to Google Ads
- Pull the relevant data
- Send back a summary
Expect the first run to take a minute or two. Later requests are usually faster.
Jobs it handles well in Google Ads
Clawdbot is most useful for research, reporting, and light analysis. These are the tasks that tend to work well.
Daily performance checks
Message:
Send me yesterday's Google Ads performance
It can pull:
- Spend
- Conversions
- CPA
- ROAS
Then it sends a short summary back to you.
Search term reviews
Message:
Export my search terms from the last 7 days and flag anything that looks like wasted spend
It can export the report, review the terms, and suggest negative keywords.
Auction insights and competitor checks
Message:
Check auction insights for my top 3 campaigns
It can navigate to auction insights, gather the data, and identify who is competing in those auctions.
Fresh ad headline ideas
Message:
Write 5 new headlines for my [product] campaign based on what's converting
It can inspect current ads, look at what is performing, and draft new headline variations.
Weekly client reporting
Message:
Build a weekly report for [client name] with last 7 days performance, save it to Notion
It can pull the metrics, format the report, and place it into your Notion workspace.
Landing page feedback
Message:
Review [landing page URL] and tell me what's wrong with it
It can open the page, look for conversion issues, and return a list of recommended fixes.
Account organization checks
Message:
Look at my campaign structure and flag any naming or organization issues
It can review account setup and point out things like:
- UTM gaps
- Inconsistent naming
- Structural issues
Google Ads script troubleshooting
Message:
Here's a Google Ads script that's not working: [paste script]. What's wrong with it?
It can read the script and identify likely errors.
Where it falls short
It helps to be realistic. Clawdbot is useful, but it is not the right tool for everything.
| Limitation | What that means |
|---|---|
| Real-time monitoring | It checks when asked. It does not watch the account 24/7 and instantly alert you when something breaks |
| UI changes | It can click through the interface, but it is slower and can make mistakes. Better for research than bulk edits |
| API-heavy workflows | Because it controls a screen, it is not ideal for fast, repeatable, high-reliability actions. Use Google Ads scripts or the API for those |
| High-risk access | Do not hand it admin rights on large-budget accounts until you trust the setup |
Smart ways to use it safely
Create a dedicated email address
Set up a separate Gmail account just for the AI assistant. Add that account to Google Ads, Notion, and any other connected tools. It keeps access cleaner and safer.
Start with read-only work
Begin with reporting and analysis. Let it pull data and summarize findings before you rely on it for account changes.
Use a VPS if you travel often
A $5/month server lets the assistant stay online from anywhere. Your laptop does not need to stay open.
Schedule morning briefs
You can send a request like:
Every morning at 7am, send me a summary of yesterday's Google Ads performance
Once configured, it can handle that automatically.
Turn it into an external memory system
Send ideas, notes, and observations throughout the day. It can sort them into folders and help build a knowledge base.
Cost breakdown
Here is the pricing mentioned in the source material.
| Item | Cost |
|---|---|
| Clawdbot software | Free (open source) |
| Hardware (Mac Mini) | $600 one-time (or use existing computer) |
| VPS server | $5/month |
| Claude API | Pay-per-use (~$20-50/month for heavy use) |
| Claude Max subscription | $200/month (unlimited) |
You can keep the setup under $10/month if you use a low-cost VPS and a pay-per-use API plan.
Useful links
- Website:
https://clawd.bot - GitHub:
https://github.com/clawdbot/clawdbot - Documentation:
https://docs.clawd.bot - Creator: Peter Steinberger (
@steipeteon X)
Quick setup recap
- Choose a machine that can stay online all day and night
- Install Node.js
- Install Clawdbot
- Run the onboarding wizard
- Connect Telegram or another messaging app
- Sign in to Google Ads on the machine
- Start sending tasks by text
The setup takes about 30 minutes. After that, it runs in the background and can handle repetitive Google Ads work without needing constant dashboard time.
Key takeaways
- Clawdbot is an open-source AI assistant that runs on hardware you control
- It works through chat apps like Telegram, WhatsApp, and iMessage
- For Google Ads, it is strongest at reporting, analysis, drafts, and routine checks
- Telegram is the easiest messaging setup option
- Node.js 22 or newer is required
- Use read-only or standard access first, not admin access on sensitive accounts
- For bulk changes or API-style workflows, Google Ads scripts or the API are still the better choice