Connect GitHub, Cloudflare, and your work apps

WALO uses GitHub for approved commits and Cloudflare Pages for the main deploy path. AI drafts the plan, WALO shows the staged package in WhatsApp, the owner approves, Cloudflare deploys from Git, and Browser Agent checks prove the result before the owner is told it is done.

Checking GitHub...

GitHub

Needed for repo commits, pull requests, and approved code packages. Private repos require repo/content write permission from your GitHub OAuth app.

Connect GitHub OAuth

Create GitHub fine-grained token with repository contents read/write.

Connected on its own page

Cloudflare

Primary deploy and domain lane: Cloudflare Pages, DNS, email authentication, BIMI, IndexNow files, Workers, Turnstile, and approved deploy actions.

Open Cloudflare Connect

Checking Vercel...

Vercel legacy

Only use this for older projects already deployed on Vercel. New WALO push flow should use GitHub plus Cloudflare Pages.

Connect Vercel OAuth

Create Vercel token for project/deploy access.

Checking Microsoft...

Microsoft

Connect Outlook, calendar, OneDrive, and Office files so WALO can draft replies, schedule, and prepare docs after approval.

Connect Microsoft

Checking Yelp...

Yelp

Official Yelp uses Leads/R2R OAuth when Yelp approves the app. Until then, email lead capture still texts the lead, labels it, and drafts the reply.

Connect Yelp OAuth Use email lead capture

Partner scopes requested: leads, r2r, r2r_get_businesses, r2r_business_owner.

Ready

Browser Agent

Playwright-style browser checks for login flows, pages, screenshots, console errors, 404s, mobile layout, and preview verification 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.

Final submit rule: the model does not blindly push code. WALO turns a user prompt into a staged package, shows the repo/files/risk, waits for commit <id> or another explicit approval, then the WALO action runner submits through GitHub and Cloudflare first, or a legacy connector only when that project already needs it.

1. PromptUser pastes Codex/Claude code or asks for a site change.

2. StageWALO picks the repo, prepares a branch or patch, and explains the diff. Agent templates can also export a PDF for the owner and JSON for Git.

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.

Build an agent template

Type the basics. WALO turns this into a saved lane: repo, deploy target, browser checks, and approval rule.

Template name

GitHub repo

Work branch

Deploy target

Allowed folders

Browser checks

Copy-ready JSON

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

WhatsApp walkthrough: text WALO and ask for setup. WALO can offer choices like GitHub, Cloudflare, Browser Agent, or template setup, with Vercel shown only for legacy projects, then explain why each one matters before you connect it. For Git, it walks the user to GitHub, saves the repo/branch rules, and only commits after the owner approves the staged package.

From WhatsApp, text connect code, connect browser, agent templates, or connect yelp to get setup links. Then text commits to see staged packages and commit <id> to approve one.