WALO.
SEO Pro EZ Calorie Pet Cards Rentals Connect
Login Start free
Connect only what you use
Connect what
you actually use.
Start with the one account WALO needs for your job. Add the rest later. OAuth is the normal path — tokens are the fallback when a provider makes you.

Your live connections

Sign in to WALO to check your accounts. WhatsApp command: connections.

Cloudflare traffic · Google · GitHub · Sign in
Cloudflare Ready
Read site traffic, compare domains, and separate bot-inclusive views from browser measurements.
Google Ready
Gmail, Calendar and Contacts. WALO reads only what you ask about.
Connect Google
From WhatsApp, text connect google.
Microsoft Ready
Outlook mail and calendar, OneDrive and Office files.
Search Console Ready
Real rank data for sites you own. Separate from the Google lane.
Connect Search Console
Open WALO gsc to link it automatically.
GitHub Ready
Read your repositories, commits, issues and pull requests. Review and confirm a PR before merging it.
Open GitHub
Connect securely in the GitHub screen; no token needs to go into a chat.
Yahoo Ready
Account identity through official OAuth. Mail reading stays gated until Yahoo approves it.
Connect Yahoo
Allow Email and Profile only.
Spotify Keys needed
Optional Song Seeker lane. Adds matched tracks to a playlist after approval.
Connect Spotify
Song Seeker works without it.
Browser Agent Ready
Checks pages, screenshots, 404s and forms after an approved runner is connected.
See how it works
Official APIs first. Browser control is for inspection.
The rule
Connecting is not permission.
WALO drafts first, shows exactly what changes, and waits. Nothing writes to code, DNS, payments or a public feed without your word.
1 Ask
Tell WALO what you want changed — a site fix, an SEO pass, an article.
2 Stage
It prepares the change, lists the exact files and the risk, and holds it.
3 Approve
You reply with the approval phrase. Nothing writes before that.
4 Verify
Browser Agent checks the live page, catches 404s, and sends proof back.
From your phone
Say it, don't click it.
Getting connected
Shows what you can link, simplest first
Gmail, Calendar and Contacts
Guided repo and branch picker
Checks your connected services live
Site work
Your recently pushed repositories
Recent commits on a repository
Cloudflare page views by site
Browser measurements with known bots filtered
Approving
List open pull requests
Prepare a merge; review the confirmation first
Cancel a pending merge
Removes the saved connection
Power users only
Save a job setup once.
Pick your repo, folders and checks. Copy the config and hand it to WALO so it stops asking the same questions every time. Skip this entirely if you never touch code.
Your setup
Setup name
GitHub repo
Base branch
Work branch
Deploy target
Folders it may touch
Checks before it lands
walo-template.json 
{
  "type": "walo_agent_template",
  "name": "SEO site fix",
  "git": {
    "provider": "github",
    "repo": "pain2hustle/example-site",
    "base_branch": "main",
    "work_branch": "walo/approved-fixes",
    "allowed_folders": [
      "pages",
      "app",
      "public",
      "content"
    ],
    "submit": "approval_required"
  },
  "deploy": {
    "provider": "Cloudflare Pages from GitHub"
  },
  "browser_agent": {
    "engine": "playwright",
    "checks": [
      "Site must return 200",
      "Mobile width 390 has no overlap",
      "Page must contain the approved headline",
      "Console has no errors"
    ],
    "screenshot": false,
    "console_errors": "fail"
  },
  "approval": {
    "required": true,
    "phrase": "commit <id>"
  }
}
What this does today
The Copy button works right now — it builds the config from your inputs and puts it on your clipboard. Nothing reads it yet. This is an exported planning template. WALO does not execute this configuration from chat. Use the live commands above for connected features.
Connect one thing. See what happens.
Start with the account you touch most. Add the rest when you need them.