Integrations and sync

Connect Lattuce to Zotero, Google Drive, Weblate, browser extensions, and local tools while keeping data ownership clear.

Lattuce can stay cloud-only in the browser or connect to external tools and standalone clients. Each integration has a different authority boundary: check what is read, what is written, and which account or server owns the credentials.

Integration map

Connection	Main direction	Best use	Verify after setup
Zotero	Zotero → Library, optional metadata write-back	Bibliography and collection metadata	Collection, item keys, and attachment policy
Google Drive	Drive → Library	Import working documents and decks	Source status is ready
Weblate	Writer ↔ translation workspace	Human-reviewed translation segments	Token, project, and segment status
Browser extensions	Browser → Learner or Writer	Capture an article or source URL	Correct destination and private-page policy
MCP / local clients	Client ↔ approved Lattuce tools	Search, digest, and controlled automation	Account, scopes, and pending writes

An integration is healthy only when the imported item can be opened in its destination and its ownership is clear. A successful authorization screen alone does not prove that extraction, sync, or a downstream job completed.

Zotero

Use Library → References → Add references → Zotero to sync bibliographic metadata. Rich import can bring PDF attachments and highlight metadata when enabled. Optional write-back creates or links bibliographic items; it is metadata-only, so use BibTeX export when you need a manual handoff. Verify the selected collection before pushing anything to Zotero.

Google Drive

Library can import supported Google Drive material, including documents and slide or tabular sources when those lanes are enabled. The picker is an import path, not a continuous mirror: confirm the resulting source is ready before attaching it to a paper or course.

Weblate translation

Writer Translate uses a personal Weblate API token from Account settings. Translators work in Weblate; Writer provides the paper context and segment workflow. Keep server-only Weblate and LLM credentials on the service side. See Collaborative translation with Weblate for the full workflow.

Browser extensions

The Learner import extension extracts an article into Learner. The Writer Save Source extension sends a PDF or page URL to Writer’s source catalog. Install only the extension build you trust and avoid sending pages containing secrets or private customer data.

MCP and local sync

The Writer MCP server exposes approved content and action tools to compatible IDEs. Local Notes sync uses a delta queue and a local IndexedDB cache so the standalone shell can keep working during a short connection loss. Review permissions, account identity, and pending writes before using an IDE or shared computer.

Desktop and mobile

The Notes shell can be loaded by the Tauri desktop client and the Capacitor mobile client. Cloud-backed routes need network access; local Notes work can continue in the standalone shell and sync later. Account switching must use the client’s account controls so local data is not mixed between households.

Bring your own keys and self-hosting

Setup sequence

Choose the smallest integration that solves the current handoff.
Authorize it with the intended account and minimum useful scope.
Import one representative item, not the whole collection.
Wait for extraction or sync to finish, then open the destination record.
Record the external identifier and revoke the connection when the account or device changes.

Troubleshooting the boundary

Confirm the correct Lattuce account and workspace.
Check that the external credential has the minimum required scope.
Wait for an imported item to become ready before attaching it.
Inspect the local sync queue or job status for pending work.
Revoke a token in the external service when a device is lost or an account changes.

Browse more in Comparisons & assistant or return to all tutorials.

Docs

Lattuce tutorial · Comparisons & assistant