OpenClaw Integrations: Connect Your AI Assistant to Everything
OpenClaw supports 50+ integrations through its skills system. Connect messaging apps, productivity tools, smart home devices, and custom APIs — all through natural language.
How OpenClaw Integrations Work
OpenClaw doesn't require custom plugins or complex SDKs. Every integration is a skill — a markdown file (SKILL.md) that teaches the AI assistant how to interact with an external service. Skills define API endpoints, authentication methods, and usage patterns in plain text.
When you ask OpenClaw something like "remind me at 3pm" or "turn off the living room lights," it matches your request to the right skill and makes the API call on your behalf. No coding required on the user's end.
Integration Categories
Messaging
Slack, Discord, Telegram, and email. Send messages, summarize threads, and manage channels through conversation.
Productivity
Calendars, task managers, note-taking apps, and reminders. Manage your workflow without switching apps.
Smart Home
Home Assistant, Philips Hue, and other IoT platforms. Control devices, set automations, and check sensor readings.
Custom APIs
Any REST API can become an OpenClaw skill. Build custom integrations for internal tools, SaaS products, or personal projects.
Featured Integration: DoNotify Voice Reminders
DoNotify turns OpenClaw into a voice call reminder system. Instead of relying on easily-missed push notifications, DoNotify places actual phone calls to deliver your reminders.
- Immediate and scheduled voice calls
- Natural language — "remind me at 3pm about the meeting"
- Usage tracking built into the skill
- Works on any phone, no app required
How API-Based Skills Work
Every OpenClaw integration follows a consistent pattern. Understanding this pattern helps you evaluate skills and even build your own.
SKILL.md — The Skill Definition
Each skill has a SKILL.md file that describes what the skill does, which API endpoints it uses, and how OpenClaw should call them. This file is written in plain markdown with structured sections for endpoints, parameters, and response handling.
Environment Variables — Authentication
API tokens, keys, and URLs are stored in the env section of openclaw.json. Skills reference these variables in their API calls. Secrets never appear in the skill definition itself.
{
"env": {
"DONOTIFY_API_TOKEN": "your-token-here",
"DONOTIFY_URL": "https://donotifys.com"
}
}Permissions — What Skills Can Do
Skills only have access to the environment variables and network endpoints defined in their configuration. They cannot access your filesystem, other skills' data, or make arbitrary network requests. OpenClaw's permission model ensures each skill is sandboxed to its declared capabilities.
Building Your Own Integration
If you have a service with a REST API, you can create an OpenClaw skill for it. Here's the general workflow:
Map your API endpoints
Identify which API endpoints your skill needs. Document the HTTP method, URL, headers, and request/response format for each.
Write the SKILL.md
Create a markdown file describing your skill's purpose, the API endpoints, required environment variables, and example commands users can say.
Add a package.json (optional)
Include metadata like version, description, and author for ClawHub discoverability.
Test and iterate
Install the skill locally, test with various phrasings, and refine the SKILL.md until OpenClaw reliably understands user intent.
For a real-world example of a complete skill, check out the DoNotify skill setup guide which includes downloadable SKILL.md and package.json files.
Frequently Asked Questions
How do I set up OpenClaw integrations?
Download the skill files into your OpenClaw skills directory, add the required API keys to your openclaw.json config, enable the skill, and restart the gateway. Most skills can be installed in under 5 minutes.
Can I connect OpenClaw to any API?
Yes, any REST API with token-based authentication can be turned into an OpenClaw skill. You write a SKILL.md file describing the API's endpoints and OpenClaw handles the rest. OAuth-based APIs require additional configuration but are also supported.
Are my API keys secure?
API keys are stored locally in your openclaw.json config file, never transmitted to third parties, and only used when the specific skill makes an API call. Each skill is sandboxed and can only access its own declared environment variables.
What happens if an integration's API changes?
You'll need to update the SKILL.md file to reflect the new API endpoints or parameters. Community-maintained skills on ClawHub are typically updated by their authors. For critical integrations, pin to specific skill versions.
Start with Voice Call Reminders
The DoNotify integration is a great first skill. Real phone calls, natural language, five-minute setup.
3 free reminders included • No credit card required
Explore more: OpenClaw Voice Reminders • Best OpenClaw Skills 2026 • DoNotify Setup Guide • Pricing