Integrations
Integrations connect external services so the agent can use them directly. A capability (e.g. email) is a named area of behavior an integration provides; skills declare the capabilities they need. A capability’s tools are only in context when an integration providing it is connected and a skill needing it is active.
This differs from MCP: MCP tools are opaque and injected into every turn once connected. Integration capabilities are known in advance, so they route through the same skill-activation mechanism as built-in tools instead of flooding context.
Manage integrations in Settings → Connections → Integrations. Platform integrations (Apple Health, Calendar, Reminders, Location) connect through an iOS permission instead of an account. Connecting one runs its authorization flow and records which capabilities were actually granted, since a user can approve some and deny others — only granted capabilities’ tools appear. Only one connected integration can provide a given capability at a time.
When a connection expires (a revoked OAuth refresh token, an expired Aula session, a rotated mail password), the agent’s tool errors say the user can fix it themselves, and the Connections list flags the integration with a warning icon. The fix is Reconnect on the integration’s detail screen: it re-runs the same connect flow under the existing integration id, refreshing credentials and granted capabilities in place. Capability-provider selections and tool permissions keep pointing at the same integration, unlike a remove and re-add, which mints a new one.
Integration tools appear in the normal permissions screen once connected, defaulting to ask like any external tool.
Available integrations
| Integration | Capability | Auth |
|---|---|---|
email | OAuth | |
| Microsoft | email | OAuth |
| IMAP | email | Manual server credentials |
| Aula | aula | Web-session login (UniLogin/MitID in a WKWebView) |
| Apple Health | health | iOS permission (platform) |
| Apple Calendar | calendar | iOS permission (platform) |
| Apple Reminders | reminders | iOS permission (platform) |
| Location | location | iOS permission (platform) |
Connecting from a chat
A skill with a missing capability can still be found. On first activation, the agent is prompted to confirm with the user. After confirmation, a matching retry can open the connect sheet.
Connecting activates the skill. Declining or cancelling leaves it inactive; a decline is remembered per capability. Already-connected skills activate immediately. See platform integrations.