Integrations · ProductivityConnect LILT to Well
Index LILT translation, project, and linguist so questions about localized asset and workspace context answer themselves in conversation.
What Well pulls from LILT
LILT feeds translation, project, linguist into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke LILT’s access.
| From LILT | In Well | Relation | |
|---|---|---|---|
| Translation | Localized asset | Becomes | |
| Project | Workspace context | Groups under | |
| Linguist | Team member | Resolves to |
- Sync mode
- MCP hybrid
- Refresh
- live + reconciliation reads
- Direction
- LILT → Well
What Well does with your LILT connection
Connect
Connect LILT over OAuth (MCP DCR): Well registers a client through LILT's OAuth Dynamic Client Registration and you approve on LILT's side, so the password never reaches Well; Well holds only a scoped token it can refresh.
Sync
Well brings translation, project, and linguist in from LILT on live events backed by periodic reconciliation reads. The first sync backfills history in the background and the connection stays live after.
Enrich
Well resolves each LILT entity into localized asset, workspace context, and team member, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Available
Your data from LILT lands in the workspace as localized asset, workspace context, and team member you can search, chart, and automate.
Questions LILT unlocks
Ask in plain language. Well answers from your connected LILT connection, resolved against the rest of your stack.
Ask anything about your LILT connection
Ask about your LILT connection…
Connect LILT in three steps
- 01
Authorise LILT via MCP
From Well's Connections panel, search for LILT and click Connect. Well discovers LILT's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on LILT's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp.lilt.com/mcp
- 02
Map your entities
Well's MCP client discovers translation, project, and linguist from LILT that LILT's MCP server exposes and brings them into your workspace using the canonical mappings defined in Well's data-views layer. You can inspect the workspace data model from Settings > Data Model.
- Mappingpreconfigured by Well
- 03
Use the data
Ask questions in conversation, build records tables, or let agents act on LILT records. Because LILT ships through MCP, Well treats every entity it exposes as queryable graph state alongside the rest of your connected tools.
- First syncstarts as soon as connect completes
MCP handshake typically completes under a minute on warm connections. Resource enumeration runs immediately after; full backfill of historical LILT records happens in the background.
How LILT stays secure with Well
Well connects to LILT's MCP server (mcp.lilt.com/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived LILT secret. Tokens are scoped to the translation, project, and linguist LILT exposes and refreshed server-side. Reads only, Well cannot modify or delete LILT records.
- granted
Read LILT records
Resources the LILT MCP server exposes, scoped by your OAuth approval.
- granted
Resolve translation, project, and linguist across your stack
Match identifiers in LILT against the same entities your other connected tools expose, so each record carries cross-tool context.
- refused
Modify or delete LILT records
Not granted; LILT is read-only in Well. Write-back is opt-in per connector when a write surface exists.
- refused
Store LILT passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
Frequently asked questions about LILT and Well
From Well, open Connections, find LILT, and click Connect. Well discovers the OAuth metadata at mcp.lilt.com/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on LILT's side. No client_id or client_secret to paste; the handshake takes roughly a minute.
Well brings in translation, project, and linguist from LILT and reshapes each entity into your workspace: translation becomes localized asset; project becomes workspace context. Every record arrives with the source identifier preserved, so LILT stays the source of truth while Well lets you query the data alongside the rest of your stack.
Each LILT item carries its assignee, which Well resolves into a workspace team member entity. Asking "who on the team owns Globex in LILT right now" returns the assigned people across active LILT items, joined to their workspace identity, so you see ownership across tools in one query.
Well watches for updates to translations and applies them on the next sync, preserving the original workspace identifier so anything downstream (records tables, conversation history, agent runs) keeps pointing at the right localized asset. Edits flow in incrementally; nothing is duplicated, and the LILT source identifier is retained on every revision.
Well combines live LILT events with periodic reconciliation reads of translation, project, and linguist. New rows appear within seconds when LILT pushes them; periodic reads catch anything a push missed. The first connect backfills history from LILT in the background.
Open Connections > LILT in Well and click Disconnect. Well calls LILT's token revocation endpoint and stops calling LILT immediately on its side; provider-side propagation to LILT's admin panel varies by provider. The translation, project, and linguist Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.
LILT records are stored in the region Well operates for your workspace. Specific region details and the steps to change region are available from Support. See /privacy for the current data-handling policy.
Pairs well with LILT
More in Productivity
Asana
Connect Asana to Well to sync tasks, projects, and team workflows.
Atlassian
Connect Atlassian to Well to sync tasks, projects, and team workflows.
Circleback
Connect Circleback to Well to sync tasks, projects, and team workflows.
ClickUp
Connect ClickUp to Well to sync tasks, projects, and team workflows.
Popular cross-category
Ready to connect LILT?
Connect once. Every translation, project, linguist from LILT becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.