Integrations
Integrations are optional adapters around your local workspace. Open Settings → Integrations to see what is available on the current platform and server.
Connection lifecycle
Section titled “Connection lifecycle”- Open an integration page and read its data-egress description.
- Supply the required token, file, account, or pairing code.
- Use Test where available before enabling sync.
- Choose whether incoming material lands in Captures for review or is created directly.
- Run the first sync manually and inspect the resulting Objects.
- Enable background sync only after the mapping is correct.
Credentials are handled by the host’s secure storage rather than ordinary browser local storage. Disconnecting an integration removes its saved credential; it does not automatically delete Objects already imported.
Available integrations
Section titled “Available integrations”| Integration | Connection | What it does |
|---|---|---|
| Readwise | Access token | Creates one Weblink per source and places highlights in its body |
| Telegram | Bot token | Captures messages, including supported voice/photo payloads, from a bot you create |
| Kindle | Local file | Imports My Clippings.txt; the file stays on the device |
Email and WhatsApp capture are marked planned in the built-in catalog. They appear only when a configured hosted capture gateway advertises and authorizes them; do not assume they are available on every server.
Calendar accounts and feeds
Section titled “Calendar accounts and feeds”Calendar connections live under Settings → Calendar feeds rather than the general integration catalog. They can import or subscribe to ICS data, and configured account adapters may expose Google, Microsoft, or CalDAV calendars. Read the direction shown by the setup page: feed subscription is read-only, while account-backed behavior can have separate options for pushing local Events.
Privacy checklist
Section titled “Privacy checklist”- A Test request contacts the service named on the integration page.
- Sync sends the minimum request required by that service but necessarily reveals the connected account/token and requested remote data.
- Incoming content becomes local Objects and then follows your workspace’s sync policy.
- An outbound webhook deliberately sends its configured payload outside Lar.
- Removing a remote account does not retract data already copied into Lar or sent to the service.
For intake behavior, see Capture channels.