WALO
Simple setup. Connect only what you use.

Connect what you use

Start with the account WALO actually needs for your job. Cloudflare helps with domains and sites. GitHub is only for approved site or code changes. Google or Microsoft are only for email, calendar, files, and Search Console. OAuth is the normal path; tokens are fallback tools.

Checking GitHub...

GitHub

Only needed when you want WALO to stage and commit site, article, or code changes after approval.

Connect GitHub OAuth
Use OAuth first. Fine-grained tokens are fallback for advanced/private setup.
Connected on its own page

Cloudflare

Best first connection for domains, DNS, email trust, Cloudflare Pages, Turnstile, IndexNow, and approved deploy work.

Open Cloudflare Connect
Checking Vercel...

Vercel legacy

Only use this for older projects already on Vercel. New WALO site work should use Cloudflare when possible.

Connect Vercel OAuth
Use OAuth first. Tokens are fallback only for old projects that cannot complete through OAuth.
Checking Microsoft...

Microsoft

Only needed if you want WALO to help with Outlook, calendar, OneDrive, or Office files.

Connect Microsoft
Checking Yelp...

Yelp

Only needed for official Yelp lead workflows after partner approval. Email lead capture works as the simple backup.

Connect Yelp OAuth Use email lead capture
Partner scopes requested: leads, r2r, r2r_get_businesses, r2r_business_owner.
Ready

Browser Agent

Optional verification lane. WALO can check pages, screenshots, 404s, mobile layout, and forms after an approved change.

See in Headquarters
Uses official APIs for final writes when available. Browser control is for inspection, testing, and UI-only fallback with approval.

Find the repo

After GitHub is connected, WALO can pull your repos so you can pick one instead of pasting names.

Find code fast

Search connected GitHub code, get the file and line, then use that exact location in your WALO request.

Connect GitHub, pick a repo, then search.
Simple rule: connecting an account does not mean WALO can run wild. WALO drafts first, shows what will change, then waits for approval before sensitive actions like code, DNS, deploys, payments, or public posting.
1. AskUser asks WALO for a site change, article, SEO fix, or setup help.
2. StageWALO prepares the change, shows the files and risk, and keeps it pending.
3. ApproveUser replies with the exact approval command before anything writes.
4. VerifyBrowser Agent checks the preview/live page, catches 404s, and sends proof back.

Save a simple job setup

Optional power-user setup. Save the repo, folders, checks, and approval rule once so WALO does not ask the same questions every time.

Copy-ready JSON

Users can save this, send it to a helper, or let WALO commit it into Git after approval.


    

  

  
WhatsApp walkthrough: text connect, oauths, or connect all. WALO gives the simple options first and only shows advanced setup when needed.

  
From WhatsApp, text connect to start. For site work, text git setup, connect browser, or agent templates.