OpenHuman GuideOpenHuman Guide

Connectors

OpenHuman Integrations

OpenHuman connects to 118+ apps and services via one-click OAuth. Learn what is available, how the OAuth flow works, and how to secure your connected accounts.

Install guidePrivacy checklist

OpenHuman Integrations

Practical notes for evaluating a fast-moving open-source AI assistant.

Practical, source-linked OpenHuman guidance

Integration Overview

OpenHuman's connector ecosystem is one of its strongest features. One-click OAuth connects your email, calendar, code repos, documents, chat, and more. After the initial exchange, tokens are encrypted and stored locally.

  • 118+ integrations via one-click OAuth.
  • Tokens stored AES-256 encrypted in the local vault.
  • Background sync every ~20 minutes for active connectors.
  • TokenJuice compression reduces LLM context usage by 70-80%.

Communication

Stay on top of conversations across multiple platforms.

  • Email: Gmail, Outlook, Yahoo Mail, and generic IMAP/SMTP.
  • Chat: Slack, Discord, Telegram, WhatsApp (via bridge), and Microsoft Teams.
  • Meetings: Google Meet (with mascot participation), Zoom, and Microsoft Teams.
  • Social: Twitter/X (read-only), LinkedIn (limited), and Reddit.

Productivity

Connect your task management and document tools.

  • Documents: Google Drive, Dropbox, OneDrive, Notion, and Obsidian vault.
  • Tasks: Todoist, Trello, Asana, Linear, Jira, and Monday.com.
  • Calendar: Google Calendar, Outlook Calendar, and Apple Calendar.
  • Notes: Notion, Apple Notes, Evernote, and OneNote.

Development

Keep your codebase context in the assistant's memory.

  • Version control: GitHub, GitLab, and Bitbucket.
  • CI/CD: GitHub Actions, GitLab CI, and Jenkins.
  • Monitoring: Sentry, Datadog, and PagerDuty.
  • Cloud: AWS, Google Cloud, and Azure (limited read-only connectors).

Business

Connect business-critical tools for financial and CRM context.

  • Payments: Stripe and PayPal (read-only transaction data).
  • CRM: HubSpot, Salesforce, and Pipedrive.
  • Finance: QuickBooks, Xero, and Plaid.
  • Marketing: Mailchimp, ConvertKit, and HubSpot Marketing.

How OAuth Works

Understanding the OAuth flow helps you evaluate the security model.

  • You click 'Connect' in OpenHuman and are redirected to the service's OAuth consent screen.
  • After authorization, the service sends an access token to a TinyHumans-hosted proxy app.
  • The proxy forwards the token to your local OpenHuman instance.
  • Your local instance encrypts the token with AES-256 and stores it in the vault.
  • Future API calls use the stored token directly from your machine — the proxy is only involved in the initial exchange.

TokenJuice Compression

When OpenHuman fetches data from integrations, it does not dump raw API responses into the LLM context. TokenJuice compresses the data first.

  • HTML to Markdown conversion removes formatting overhead.
  • URL shortening reduces token count for link-heavy content.
  • Non-ASCII removal strips unnecessary characters.
  • Deduplication removes repeated content across similar items.
  • Key-info extraction surfaces only the most relevant fields.
  • Result: 70-80% reduction in tokens sent to the LLM, reducing cost and latency.

Security Best Practices

With 118+ integrations available, security is paramount.

  • Minimize connectors: only connect services you actually need.
  • Audit OAuth scopes: read every permission screen and reject broader scopes than necessary.
  • Revoke unused connectors: periodically review and remove integrations you no longer use.
  • Use a dedicated test account: evaluate OpenHuman with non-critical data first.
  • Monitor vault access: the Obsidian vault is inspectable — review what is stored periodically.
  • Enable local AI where possible: keep inference on-device for sensitive data processing.