Third-party Integrations (118+)
OpenHuman ships with backend-proxied access to 118+ third-party services. Connecting any of them through the managed path is a one-click OAuth flow inside the app, there are no API keys to wire by hand, and no plugin marketplace to navigate.
Under the hood, the connector layer is powered by Composio. In the default managed mode, OpenHuman's backend owns the Composio API key, OAuth token brokering, rate limits, and trigger webhook fan-out.
Once a service is connected, it shows up in four places at once:
- As an agent tool, the model can call it directly.
- As a memory source, auto-fetch syncs it into the Memory Tree every twenty minutes.
- As a profile signal, your activity across services feeds your personalization.
- As a trigger source, live events flow into the Triggers pipeline and can fire off agent actions automatically.
Some of what's in the catalog
| Category | Examples |
|---|---|
| Email & calendar | Gmail, Outlook, Google Calendar, Apple Calendar |
| Docs & storage | Google Docs, Google Drive, Notion, Dropbox, Airtable |
| Code & dev | GitHub, Linear, Jira, Figma |
| Comms | Slack, Discord, Microsoft Teams, Telegram, WhatsApp |
| CRM & sales | Salesforce, HubSpot |
| Commerce & payments | Stripe, Shopify |
| Project management | Asana, Trello |
| Social | Twitter / X, Spotify, YouTube |
How connections work
Click Connect on any integration. A browser window opens for OAuth. Once you sign in, the connection becomes active and OpenHuman starts syncing it through auto-fetch on the next 20-minute tick.
Messaging channels
Three integrations are special. OpenHuman uses them to talk back to you, not just read from them:
- Telegram. the primary messaging channel. Two-way: send and receive messages, manage chats, search history, create groups.
- Discord. send and receive messages via Discord.
- Web. a browser-based chat interface within the desktop app.
Set your default under Settings → Automation & Channels → Messaging Channels.
Skills
Beyond third-party services, OpenHuman has skills, small sandboxed modules that run inside the app, fetch external data, run on a schedule, transform information, and respond to events.
Privacy boundary
OpenHuman's core never calls any third-party API directly. All requests go through the OpenHuman backend, which handles OAuth tokens and rate limiting. Your tokens never sit on disk in plaintext on your machine, and the agent only sees the results of tool calls, not the credentials.
See also
- Triggers - Live events from connected integrations and how they fire agent actions.
- Memory Tree - Where synced data ends up.