Step 7 — Clawvisor

Connect Google Workspace (email + calendar)

Google Workspace covers both Gmail and Google Calendar in one OAuth flow.

HyperClaw:

1. Go to Dashboard → Your Claw → Clawvisor
2. Click Google Workspace → Connect
3. A browser tab opens — sign in with your Google account
4. Grant the requested permissions (read/send email, read/write calendar)
5. You'll be redirected back to the dashboard with a green "Connected" status

OpenClaw:

openclaw configure
# Select: Google Workspace
# Select: Gmail + Google Calendar
# A browser tab opens — complete the OAuth flow
# You'll see: "Google Workspace connected successfully"

Verify email:

What are the last 3 unread emails in my inbox? Show me the subject and sender.

Verify calendar:

What do I have scheduled for tomorrow?

Both should return real data from your account. If either fails, see Troubleshooting → Clawvisor.

Once calendar is connected, update your morning brief to include today's events:

Update my morning-brief skill to add a "On the calendar" section with today's events.

Connect Slack

HyperClaw:

1. Dashboard → Clawvisor → Slack → Connect
2. Select the workspace and grant permissions
3. Choose which channels your Claw can read and post to — start with 1–2, not all

OpenClaw:

openclaw configure
# Select: Slack
# Enter your Slack workspace URL (e.g. yourteam.slack.com)
# Complete the OAuth browser flow
# Grant: channels:read, chat:write, channels:history

Verify:

Post "Claw connected ✅" to #[any low-traffic channel].

The message should appear in Slack within a few seconds.

Connect GitHub

GitHub access can be set up via OAuth or a Personal Access Token (PAT). PAT is simpler and easier to scope precisely.

Create a PAT:

1. Go to github.com/settings/tokens → Generate new token (classic)
2. Set expiry (90 days is reasonable)
3. Select scopes: repo (full) or at minimum contents:read, pull_requests:write, issues:write
4. Copy the token

Set the token in your Claw:

HyperClaw:

Set my GitHub token to [paste token]. Store it as GH_TOKEN in my environment.

OpenClaw:

openclaw env set GH_TOKEN=ghp_your_token_here

Verify:

List the open pull requests in [owner/repo-name].

Your Claw should return real PR titles and numbers.

Connect your Claw to Clawvisor (HyperClaw)

Once your services are connected in the Clawvisor dashboard, you need to create the agent connection — this gives your Claw permission to make requests through Clawvisor.

1. Go to Clawvisor → Agents in the sidebar
2. Click Create Agent (or Add Agent)
3. Copy the connection prompt that appears
4. Paste it into your HyperClaw chat — your Claw will send a connection request to Clawvisor
5. Go back to the Clawvisor dashboard — approve the connection when it appears
6. Return to HyperClaw — you should see a confirmation that the connection succeeded
7. Ask your Claw to install the Clawvisor skill:

Install the Clawvisor skill.

Once the skill is installed, your Claw knows how to make requests through Clawvisor, handle task approvals, and manage standing task tokens.

Save connection status and tokens to memory

This step is what makes standing tasks reliable. Isolated cron sessions start fresh every run with no memory of previous sessions — if your Claw has to re-discover what integrations are connected each time, it wastes turns and risks auth failures.

The fix: save your integration config and Clawvisor token to a file your Claw can read on every run, before any cron jobs are scheduled.

cat >> ~/TOOLS.md << 'EOF'
 
## Clawvisor Integrations
 
- Google Workspace (Gmail + Calendar): connected, verified [DATE]
- Slack: [workspace name] — connected, channels: [list the ones granted]
- GitHub: repo-scoped to [owner/repo] — token expiry: [date]
 
## Access notes
- GitHub: repo-scoped, not org-scoped
- Slack: read/post to #[channel1] and #[channel2] only
- Email: read and send only when explicitly instructed
 
## Clawvisor token
- CLAWVISOR_URL: [your ClawVisor endpoint]
- Token: stored in env as CLAWVISOR_AGENT_TOKEN — do not paste here
- Token scope: Gmail read, Calendar read, GitHub repo, Slack read/post
EOF

Then save the token to your environment so every session — including isolated cron runs — can find it:

# OpenClaw — persists across sessions including cron
openclaw env set CLAWVISOR_AGENT_TOKEN=your_token_here
openclaw env set CLAWVISOR_URL=https://your-clawvisor-endpoint

Tell your Claw to save what it knows:

Read TOOLS.md and save the key facts about my Clawvisor integrations to MEMORY.md —
which services are connected, what I've scoped access to, and that the token is in
the CLAWVISOR_AGENT_TOKEN env var. I want every future session to know this without
me having to explain it again.

Your Claw writes a summary to ~/MEMORY.md. Every cron run reads that file in its first turn and immediately knows what tools are available — no re-authentication, no re-discovery.

Set up standing tasks

Standing tasks are scheduled jobs that run automatically on a recurring schedule — no prompting required. Once your integrations are connected and saved to memory, wire them into a daily routine.

OpenClaw — add a standing task via CLI:

# Morning brief — runs daily at 7 AM, posts to Telegram
openclaw cron add \
  --name "Morning brief" \
  --cron "0 7 * * *" \
  --tz "America/New_York" \
  --session isolated \
  --message "Read ~/TOOLS.md for integration config. Run my morning-brief skill for today." \
  --announce \
  --channel telegram
 
# Evening inbox summary — runs weekdays at 6 PM
openclaw cron add \
  --name "Evening inbox summary" \
  --cron "0 18 * * 1-5" \
  --tz "America/New_York" \
  --session isolated \
  --message "Read ~/TOOLS.md. Check my email via Clawvisor. Summarize anything that needs a response today. Post to Telegram." \
  --announce \
  --channel telegram
 
# Daily GitHub PR check — runs at 9 AM on weekdays
openclaw cron add \
  --name "PR check" \
  --cron "0 9 * * 1-5" \
  --tz "America/New_York" \
  --session isolated \
  --message "Read ~/TOOLS.md. List open pull requests assigned to me or awaiting my review. Post a summary to Telegram." \
  --announce \
  --channel telegram

The Read ~/TOOLS.md at the start of each prompt is the key — it primes the isolated session with integration context before any tool calls are made.

HyperClaw — add a standing task via Dashboard:

1. Dashboard → Your Claw → Scheduled Tasks → New Task
2. Set the name, schedule (cron expression or plain English like "every weekday at 7am")
3. Start the prompt with: Read ~/TOOLS.md for integration config. — then add your task
4. Set delivery: Telegram or Slack channel
5. Save — the task starts on its next scheduled trigger

Verify your standing tasks are registered:

List my scheduled tasks. Show the next run time for each one.

Force a test run to confirm output:

# OpenClaw
openclaw cron run "Morning brief" --wait

Or in HyperClaw: Dashboard → Scheduled Tasks → Run Now next to the task.

What each integration contributes to standing tasks:

Your Claw queries these in parallel during each run — the brief takes roughly the same time regardless of how many integrations are connected.