Skip to content

Connectors

A connector brings your data in from another service, such as your watch, and saves it as ordinary entries in your collections.

Google Health first

Google Health brings in what your Fitbit or other Google-connected device records: sleep, activity, heart rate and runs.

Google Health sends data to the connector. The connector saves entries into your Sleep and Activity collections and keeps the raw data.Google Healthyour watch’s dataThe connectorsealed, with only thepermissions you allowedSleep26 Oct: 7 h 10 minActivitysteps, heart rateRaw datakept, as it came
The data lands in ordinary collections, so search, views, privacy and your folder work on it as usual.

Where it runs

Plan When it fetches
Free while the app is open on your device
Pro while the app is open, and on a schedule in the cloud, with every device off (part of Cloud Sync)

How a connector stays safe

A connector is a plugin: a small add-on that teaches the app something new.

  • You sign in to the service (for Google Health, with Google).
  • Before it starts, it shows what it may read and write, in plain words. You approve it, and you can change it later.
  • Its code runs sealed: it can only use what you allowed.
  • Every entry it writes goes through the same checks as your own taps, so you can undo it.
  • Verified means we reviewed and signed it. We write the Google Health connector ourselves.
  • If a connector ever turns bad, we can switch it off on every device at once.

Data sent by webhook

Some services, such as Whoop, send data to us instead of being asked (a webhook is that kind of message). On Pro, Cloud Sync receives it in the cloud. On Free, the data waits in the cloud, in a small, sealed webhook inbox, until your device collects it. Nothing is lost while your laptop is off.

  • Your webhook address is private to you.
  • We check the sender. When a service signs its messages, we check the signature.
  • Size and rate limits apply.
  • What arrives is data, never an order to the AI. It lands as entries, like any other connector data.

MCP connectors for agents (later)

An agent can also use an MCP connector: tools that another service offers to AI apps (MCP is a standard way for an AI app to call tools). For example, a GitHub MCP connector can list your issues or open a new one.

  • Every MCP tool call goes through the outbox, like sending an email. By default, a call the agent makes on its own waits for your Approve tap.
  • A tool you marked read only runs without a tap. It can still leak what it reads: its maker gets what the AI sends it. Mark only tools you trust that read and change nothing, such as “list issues”.
  • By default, a tool that changed since you approved it is blocked until you approve it again. Cloud MCP servers run in their own container. See AI safety settings.

Later connectors

Mail, calendar, Slack, GitHub and documents. Each one lands its data in ordinary collections, the same way.