Using api-gateway Skill to Connect OpenClaw to 100+ External Services: From Notion to Google Calendar
Why I Started Using api-gateway Every time I needed to connect an external service, the process was painful: find API docs, register a dev account, generate …
- Added to the lab
- Downloads
- 0
- Human review
- Human reviewed
Why I Started Using api-gateway
Every time I needed to connect an external service, the process was painful: find API docs, register a dev account, generate a key, read the OAuth flow, write auth code. A Notion integration alone took half a day. SFD Lab Agents frequently need to read Notion tasks and write Google Calendar events — that accumulated frustration adds up.
Then I found OpenClaw's api-gateway skill — a managed OAuth solution from Maton.ai that claims 100+ service support. Tried it for a few days, it solved most of the problems. This is an honest practical review.
What Is api-gateway?
One sentence: it's a managed OAuth middleware layer. You don't manage API keys, refresh tokens, or permission scopes — Maton handles that layer, and OpenClaw Agents call through a unified interface.
Supported services include: Google Workspace (Gmail, Calendar, Drive, Sheets), Microsoft 365 (Outlook, Teams, OneDrive), GitHub, Notion, Slack, Airtable, HubSpot, Salesforce, and many more SaaS tools.
Important security note: MATON_API_KEY is just your identity authentication with Maton — it does NOT equal your authorization for Google/Notion. Each service requires separate OAuth with the user actively authorizing. That's the right design: one key leak shouldn't compromise everything.
Installation and Setup
The skill itself needs no installation — just use it in your OpenClaw workspace. First-time setup requires configuring MATON_API_KEY from your maton.ai account dashboard.
Once configured, say "Help me connect Notion" in OpenClaw — it runs through OAuth and gives you an auth link. Complete authorization in your browser and the connection is established. Future requests of the same type don't need re-authorization.
In Practice: Sync Notion Tasks to Google Calendar
I actually use this at SFD Lab. Project management is in Notion, scheduling in Google Calendar — manual sync was too time-consuming.
After connecting both services, the Agent instruction looks roughly like:
Read all "In Progress" tasks from this week in the Notion "Task List" database. Sync their deadlines and names to Google Calendar as events. If a Calendar event with the same name already exists, skip it.
The Agent: calls Notion API → filters current week + in-progress → calls Calendar API to check existing events → batch-creates new events. 10 tasks take roughly 15-20 seconds, mostly OAuth round-trip latency.
In Practice: GitHub Issues → Airtable Board
Dev tasks are in Gitea, but client feedback is in GitHub issues (legacy split). I need to periodically sync GitHub issues to Airtable for the non-technical team.
Instruction: "Read all open issues in sfd-lab/client-feedback, categorize by label (bug/feature/question), write to Airtable 'Client Feedback' table with fields: title, URL, labels, created, status."
api-gateway handles this stably. It automatically retries on 429 rate limit errors — that detail saves considerable effort.
Pitfalls
Think carefully about permission scope before authorizing. First time I authorized Google Calendar with full permissions — then realized the Agent could delete my calendar events. Re-authorized with read/write only, no delete. Be granular with OAuth permissions.
No alert when tokens expire. Maton refreshes access tokens, but if a user manually revokes authorization on the Google side, the next call fails without warning. Add a daily heartbeat check on critical integrations.
Some services have incomplete API coverage. Notion's block-level operations (inserting content at specific positions within a page) weren't exposed in api-gateway — had to fall back to calling Notion's native API directly. api-gateway is best for standard "read data + write data" operations.
Best Use Cases
Honestly, api-gateway's biggest value is lowering the barrier to connecting services. For non-developers or people who don't want to deal with OAuth, it gets things working fast. For developers, direct SDK integration is sometimes more flexible, but api-gateway's value is unified management — all service authorizations in one place rather than scattered across .env files.
Best for: rapid prototyping, cross-service data flows, and non-technical team onboarding. Complex business logic: build your own API layer instead.