Integrations

Connect OpenClaw to productivity apps, browsers, developer tools, search providers, media services, and remote devices through plugins, tools, and skills.

Integrations are the user-facing result of three extension layers:

• tools let the agent act
• skills teach service-specific workflows
• plugins add runtime capability and credentials

Do not assume every integration has a first-party integrations command. Many are installed as skills or plugins, then exposed through normal tools.

Productivity Apps

Common productivity integrations include:

• Gmail
• Google Calendar
• Google Drive
• Slack
• Discord
• Linear
• GitHub
• Obsidian or local note vaults
• Apple Notes or Reminders through suitable local tools

The pattern is consistent:

1. install or enable the capability
2. authorize credentials safely
3. define what the agent may do
4. test with a read-only action
5. add automation only after manual use works

Google Workspace Example

Google Workspace support is typically delivered through a skill or plugin-backed provider path rather than a single core command.

openclaw skills search google
openclaw plugins list
openclaw doctor

After authorization, use narrow prompts first:

List my next three calendar events. Do not create or edit anything.

Then move to side-effecting tasks such as drafts, labels, or event creation after the permission boundary is clear.

Browser Integrations

The browser tool is the universal fallback for web apps that lack clean APIs.

Use browser automation for:

• authenticated dashboards
• form filling with confirmation
• UI-only admin panels
• research that requires navigation
• pages that do not expose readable static content

Use web_fetch or search providers for static content. Browser automation is more powerful, slower, and riskier.

Developer Tools

Developer integrations often combine tools and skills:

• GitHub or GitLab workflows
• Linear issue management
• release note drafting
• CI/CD notifications through webhooks
• code review rubrics
• ACP-backed coding agents

Keep destructive actions behind confirmation. A good coding or ops integration should make it easy to inspect before applying changes.

Search and Research Providers

OpenClaw supports several search paths through tools and plugins, such as Brave, DuckDuckGo, Exa, Firecrawl, Gemini, Kimi, Ollama, Parallel, Perplexity, SearXNG, Tavily, and provider-specific web-grounded APIs.

Key-free providers and free hosted providers should be explicit choices. Do not rely on surprising fallbacks for production workflows.

Media and Voice Services

Media integrations can add:

• image generation
• video generation
• music generation
• speech-to-text
• text-to-speech
• voice calls
• realtime talk modes

These usually depend on provider credentials, plugin availability, and channel support.

Remote Devices

Nodes extend an OpenClaw Gateway to other devices. A node can expose device-local capabilities such as camera, screen, location, Canvas, talk mode, or platform-specific actions.

Pair nodes deliberately:

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

Integration Design Rules

1. Start read-only.
2. Store secrets outside prompt files.
3. Use SecretRefs or provider auth profiles where possible.
4. Keep skill instructions narrow.
5. Prefer plugins for code-backed capabilities.
6. Add automation after manual tasks are reliable.
7. Log and review side effects.