Integrations hub

CloudyBot connects to your stack in three ways: native API skills (Notion, Sheets, GitHub, email, calendar, Search Console), messaging channels (WhatsApp on paid plans), and the cloud browser for sites that do not expose an API. Most connections are per-user OAuth or API keys stored encrypted — you attach them once in the dashboard under Settings → Connect, then enable the matching skill on each Specialist.

Notion

Per-workspace integration token. Agents can search pages, read blocks, append content, and query databases with native notion_* tools — no copy-paste from chat.

Open Notion guide →

Google Sheets

Service-account reads and writes for spreadsheet workflows — reports, lead lists, and scheduled updates alongside cron duties.

Open Google Sheets guide →

WhatsApp

Twilio-backed channel: chat from your phone, proactive scheduled delivery, and opt-out compliant sends. Requires a paid plan (not on Free); monthly proactive cap varies by tier — see pricing.

Open WhatsApp guide →

GitHub

OAuth to clone repos under ~/repos/, commit, push, and open issues from chat or scheduled jobs.

Open GitHub guide →

More skills (setup in docs)

These use the same Connect + skill pattern but do not have a separate marketing landing page yet. Step-by-step setup lives under skills docs:

Not available: we do not ship a Telegram channel today — mobile messaging is WhatsApp where your plan supports it.

How integrations fit the product

Integrations are not a Zapier-style recipe library. You hire Specialists (AI roles with duties), enable only the skills each role needs, and let them run on a schedule or from chat. A research Specialist might use Notion + browser; an ops Specialist might use Sheets + WhatsApp delivery.

New to setup? Start at getting started, browse all skills at /docs/skills, or read the Notion walkthrough on the blog. Questions → contact.