Google Meet troubleshooting

​

Live test checklist

openclaw googlemeet setup
openclaw nodes status
openclaw googlemeet test-speech https://meet.google.com/abc-defg-hij \
  --transport chrome-node \
  --message "Say exactly: Google Meet speech test complete."

• googlemeet setup is all green, and includes chrome-node-connected when Chrome-node is the default transport or a node is pinned.
• nodes status shows the selected node connected, advertising both googlemeet.chrome and browser.proxy.
• The Meet tab joins, and test-speech returns Chrome health with inCall: true.

openclaw googlemeet setup
openclaw nodes status --connected
openclaw nodes invoke \
  --node parallels-macos \
  --command googlemeet.chrome \
  --params '{"action":"setup"}'

openclaw googlemeet setup
openclaw googlemeet join https://meet.google.com/abc-defg-hij \
  --transport twilio \
  --dial-in-number +15551234567 \
  --pin 123456

• googlemeet setup includes green twilio-voice-call-plugin, twilio-voice-call-credentials, and twilio-voice-call-webhook checks.
• voicecall is available in the CLI after Gateway reload.
• The returned session has transport: "twilio" and a twilio.voiceCallId.
• openclaw logs --follow shows DTMF TwiML served before realtime TwiML, then a realtime bridge with the initial greeting queued.
• googlemeet leave <sessionId> hangs up the delegated voice call.

​

Troubleshooting

​

Agent cannot see the Google Meet tool

openclaw plugins list | grep google-meet
openclaw googlemeet setup

​

No connected Google Meet-capable node

openclaw plugins install npm:@openclaw/google-meet
openclaw plugins enable browser
OPENCLAW_ALLOW_INSECURE_PRIVATE_WS=1 \
  openclaw node run --host <gateway-lan-ip> --port 18789 --display-name parallels-macos

openclaw devices list
openclaw devices approve <requestId>
openclaw nodes status

{
  gateway: {
    nodes: {
      commands: { allow: ["browser.proxy", "googlemeet.chrome"] },
    },
  },
}

OPENCLAW_ALLOW_INSECURE_PRIVATE_WS=1 \
  openclaw node install \
  --host <gateway-lan-ip> \
  --port 18789 \
  --display-name parallels-macos \
  --force

openclaw googlemeet setup
openclaw nodes status --connected

​

Browser opens but agent cannot join

​

Meeting creation fails

• API creation: oauth.clientId and oauth.refreshToken (or matching OPENCLAW_GOOGLE_MEET_* env vars) are present, and the refresh token was minted after create support was added; older tokens may lack meetings.space.created, so rerun openclaw googlemeet auth login --json.
• Browser fallback: defaultTransport: "chrome-node" and chromeNode.node point at a connected node with browser.proxy and googlemeet.chrome; the OpenClaw Chrome profile on that node is signed in and can open https://meet.google.com/new.
• Browser fallback retries: reuse an existing .../new or Google account prompt tab before opening a new one; retry the tool call rather than manually opening another tab.
• Manual action: if the tool returns manualAction, use browser.nodeId, browser.targetId, browserUrl, and manualAction.message to guide the operator; do not retry in a loop.
• Audio-choice interstitial: if Meet shows “Do you want people to hear you in the meeting?”, leave the tab open. OpenClaw should click Use microphone or (create-only) Continue without microphone and keep waiting for the generated URL; if it cannot, the error should mention meet-audio-choice-required, not google-login-required.

​

Agent joins but does not talk

openclaw googlemeet setup
openclaw googlemeet doctor

openclaw googlemeet recover-tab
openclaw googlemeet recover-tab https://meet.google.com/abc-defg-hij

​

Twilio setup checks fail

export TWILIO_ACCOUNT_SID=AC...
export TWILIO_AUTH_TOKEN=...
export TWILIO_FROM_NUMBER=+15550001234

{
  plugins: {
    entries: {
      "voice-call": {
        enabled: true,
        config: {
          provider: "twilio",
          fromNumber: "+15550001234",
          publicUrl: "https://voice.example.com/voice/webhook",
        },
      },
    },
  },
}

{
  plugins: {
    entries: {
      "voice-call": {
        config: {
          tunnel: { provider: "ngrok" },
          // or
          tailscale: { mode: "funnel", path: "/voice/webhook" },
        },
      },
    },
  },
}

openclaw googlemeet setup --transport twilio
openclaw voicecall setup
openclaw voicecall smoke

openclaw voicecall smoke --to "+15555550123"

openclaw voicecall smoke --to "+15555550123" --yes

​

Twilio call starts but never enters the meeting

openclaw googlemeet join https://meet.google.com/abc-defg-hij \
  --transport twilio \
  --dial-in-number +15551234567 \
  --dtmf-sequence ww123456#

• openclaw googlemeet doctor <session-id>: confirm the delegated Twilio call ID, whether DTMF was queued, and whether the intro greeting was requested.
• openclaw voicecall status --call-id <id>: confirm the call is still active.
• openclaw voicecall tail: confirm Twilio webhooks are arriving at the Gateway.
• openclaw logs --follow: look for the Twilio Meet sequence: Google Meet delegates the join, Voice Call stores and serves pre-connect DTMF TwiML, Voice Call serves realtime TwiML for the Twilio call, then Google Meet requests intro speech with voicecall.speak.
• Re-run openclaw googlemeet setup --transport twilio; a green setup check is required but does not prove the meeting PIN sequence is correct.
• Confirm the dial-in number belongs to the same Meet invitation and region as the PIN.
• Increase voiceCall.dtmfDelayMs from the 12-second default if Meet answers slowly or the call transcript still shows the PIN prompt after pre-connect DTMF was sent.
• If the participant joins but you do not hear the greeting, check openclaw logs --follow for the post-DTMF voicecall.speak request and either media-stream TTS playback or the Twilio <Say> fallback. If the transcript still shows “enter the meeting PIN”, the phone leg has not joined the Meet room yet, so participants will not hear speech.