Meeting Plugins for Google Meet, Microsoft Teams, and Zoom

OpenClaw provides distinct plugins for Google Meet, Microsoft Teams meetings, and Zoom. All three use Chrome to join, share the same participation modes, and can run Chrome on the Gateway host or a paired node. Their platform URLs, installation methods, and platform-specific features differ.

These plugins handle meeting participation. They are distinct from messaging channels like the Microsoft Teams channel and the Voice call plugin.

Choose a plugin

Select Google Meet when meeting creation, Google API artifacts, or a Twilio phone path is required. Choose Teams or Zoom for direct browser guest participation on those platforms. The Teams and Zoom plugins cannot create meetings, dial in, call the vendor API, or capture audio/video recordings.

Choose a mode

All three plugins share the same modes:

Use transcribe when the agent only needs meeting text. Use agent for normal OpenClaw reasoning and tools. Use bidi when low-latency direct voice is more important than routing each turn through the regular agent.

The bounded live transcript remains available only in transcribe mode. In all three modes, browser joins also persist completed caption rows and a derived summary to the shared state database. Leaving the meeting finalizes visible captions and writes the summary; use openclaw transcripts to list, inspect, or export it. This durable notes path does not change the live agent-consult transcript or create an audio/video recording.

Automatic notes are on by default. Set transcripts.enabled: false to disable durable notes globally. An explicitly selected transcribe session retains its bounded live-caption tail without writing durable rows. Caption availability still depends on the meeting platform, account, language, and host policy.

Prepare Chrome and audio

Chrome can run on the Gateway host or on a paired node. A remote Chrome node must allow browser.proxy plus the platform command:

For agent or bidi mode through Chrome, run Chrome on macOS and install the shared audio dependencies on that same host:

brew install blackhole-2ch sox
sudo reboot
system_profiler SPAudioDataType | grep -i BlackHole
command -v sox

The Gateway host still owns the OpenClaw agent and model credentials when Chrome runs on a paired node. Configure a realtime transcription provider and OpenClaw TTS for agent mode, or a realtime voice provider for bidi mode. The platform guides contain the provider and audio-command options.

Install or disable plugins

Install Google Meet separately; it is enabled by default after installation. Teams meetings and Zoom are included with OpenClaw and enabled by default:

# Google Meet only
openclaw plugins install npm:@openclaw/google-meet

Disable any meeting plugin you do not use:

openclaw plugins disable google-meet
openclaw plugins disable teams-meetings
openclaw plugins disable zoom-meetings

Restart the Gateway if your plugin-management path does not restart it automatically. Then run the platform setup check before joining.

Verify and join

Treat any failed setup check as a blocker for that transport and mode. For an observe-only smoke test, select transcribe mode and confirm that status reports an in-call session before expecting caption text.

For talk-back smoke tests, verified speech requires more than bytes accepted by the playback command. The shared command-pair bridge correlates a bounded waveform fingerprint from the current output generation with audio returning on the BlackHole microphone capture path; Google Meet, Teams, and Zoom do not report speechOutputVerified: true when only the output-byte counter advances or unrelated participant audio is present.

Handle platform policy prompts

Browser automation handles the normal guest-name, prejoin camera and microphone, join, in-call, and leave controls. It does not bypass platform or organizer policy.

• Google Meet may require Google sign-in, host admission, or a browser permission decision.
• Microsoft Teams may require tenant sign-in, email verification, or organizer admission.
• Zoom may require authentication, email verification, a passcode, CAPTCHA completion, or host admission; an account can also disable browser join.

When a join or status result reports manualActionRequired, complete the reported step in the same OpenClaw Chrome profile before retrying. Repeatedly opening new tabs does not resolve an account, tenant, lobby, or CAPTCHA gate.

Only join meetings where the operator is authorized to add an agent. Tell participants when local policy or consent rules require disclosure of automated participation, transcription, or synthesized speech.

Discord voice chat

Discord voice channels provide native, audio-only realtime conversation without browser meeting automation. OpenClaw can join a voice channel, listen, route turns through an OpenClaw agent or realtime voice model, and speak replies. It does not send or receive camera video or screen sharing, even when people use video in the same Discord channel, so Discord voice is a related live-conversation surface rather than a fourth browser meeting plugin.

Platform guides

• Google Meet plugin
• Microsoft Teams meetings plugin
• Zoom meetings plugin
• Manage plugins
• Browser control