Skip to content
Connections

There is nothing to connect — whatever you meet or call with.

Thalassa listens to the sound on your own computer, so the application makes no difference: Zoom, Teams, Meet, Webex, GoTo, RingCentral, Whereby, Proton Meet, Jitsi, Slack, Discord, WhatsApp, Telegram, Signal, Messenger, FaceTime, Viber, LINE, KakaoTalk, WeChat, Zalo — or a phone on speaker.

It does not join your meeting, it is not a participant, and it asks your meeting platform for nothing. Whatever you use — a conferencing service, a team chat, a messenger, a phone on speaker — there is nothing to set up, no admin approval to chase and no IT ticket to raise. The names above are examples, not a list of integrations: there is no integration to have.

Optional connections to your own systems — what they do

These pull in your own documents and context. Google Workspace and Microsoft 365 are included from Premium; Professional reads the calendar and brings in documents.

Status as of 15 October 2026.

System Connection Reading & writing data
MCP tool providers Available now Yes — tool by tool, after your confirmation
Google Workspace Available Reads calendar and contacts for meeting preparation; brings documents you pick in Google Drive into your knowledge base
Microsoft 365 / Outlook Available Reads calendar, contacts and the email history for the meeting; saves reply drafts in Outlook that you send yourself; searches documents in OneDrive and SharePoint and brings them into your knowledge base

If a system you rely on is missing, tell us through the contact form.

CRM and matter management — available from Premium

Salesforce, Microsoft Dynamics 365, HubSpot and Clio Manage are included in Premium and Enterprise; iManage Work is available on our side and needs setup at your firm. You connect your own account in the desktop app’s settings. Before the conversation Thalassa reads the account, its contacts, open opportunities and recent activities into your briefing. After the conversation it writes back what you confirm: the meeting note, the conversation as a logged activity, follow-up tasks with due dates, and new contacts or leads. It never writes on its own, and it changes no existing record.

Status as of 15 October 2026.

System Connection Reading & writing data
Salesforce Available from Premium Reads accounts, contacts, opportunities and activities within your Salesforce permissions; after your confirmation writes the note, activity, follow-up tasks, contacts and leads
Microsoft Dynamics 365 Available from Premium Reads accounts, contacts, opportunities and activities within your Dynamics 365 permissions; after your confirmation writes the note, activity, follow-up tasks, contacts and leads
HubSpot Available from Premium Reads companies, contacts, deals and activities you own; after your confirmation writes the note, activity, follow-up tasks, contacts and leads
Clio Manage Available from Premium Reads contacts, matters and activities; after your confirmation writes the note, activity, follow-up tasks and contacts
iManage Work Available on our side – setup required on the customer side Searches documents in iManage Work and brings them into your knowledge base

Every retrieval is capped: at most 10 accounts per search, 25 contacts, 10 open opportunities or matters and 15 activities. Where there is more, Thalassa marks the list as shortened instead of leaving the rest out silently.

Salesforce

  • Reads: accounts (name, industry, website), contacts (name, title, email, phone), open opportunities (name, stage, amount, close date), tasks and events. Object permissions, field-level security and sharing rules of your org apply exactly as they do in Salesforce.
  • Writes: the meeting note, the conversation as an activity, follow-up tasks with due dates, and new contacts and leads, linked to the account, opportunity or contact — after you confirm. No changes to existing records, no deletions.
  • Your Salesforce administrator sets up Thalassa’s External Client App in your org and gives connecting users “API Enabled”, read access to accounts, contacts, opportunities, tasks and events, and permission to create notes, tasks, activities, contacts and leads. Your edition needs API access: Enterprise, Performance, Unlimited or Developer, or Professional with the API add-on.

Microsoft Dynamics 365

  • Reads: accounts, contacts, opportunities and activities of the Dynamics 365 Sales environment you choose. Every request runs as you, so your security role decides which records Thalassa sees.
  • Writes: the meeting note, the conversation as an activity, follow-up tasks with due dates, and new contacts and leads on an account or opportunity — after you have seen the text word for word and confirmed it. No emails, no changes to existing records, no deletions.
  • Your administrator: if your organisation has turned off user consent, an administrator grants consent once for the tenant in Microsoft Entra ID. Connecting users need a licence with access to Dynamics 365 Sales and a security role that can read these tables and create notes, tasks, activities, contacts and leads; the usual sales role covers it.

HubSpot

  • Reads: companies, contacts and deals for which you are the record owner, and up to five notes, calls and meetings each that are attached to the company. Unassigned records and records of other owners are not shown.
  • Writes: the meeting note, the conversation as an activity, follow-up tasks with due dates, and new contacts and leads on a company or deal you own — after you confirm. No changes to existing records, no deletions.
  • Connecting: a Super Admin of the HubSpot account or a user with “HubSpot Marketplace Access”. During installation HubSpot shows a warning because Thalassa is not listed in the HubSpot Marketplace; that is expected. The connection needs read access to all companies, contacts and deals in the account and permission to create notes, tasks, activities, contacts and leads; the limit to your own records is applied by Thalassa on its server.

Clio Manage

  • Reads: contacts, matters and activities. No billing data, no documents, no bulk export.
  • Writes: the meeting note, the conversation as an activity, follow-up tasks with due dates, and new contacts on the matter or contact — after you confirm. If the text changes after your confirmation, the confirmation no longer applies. No changes to existing records, no deletions.
  • Your Clio administrator gives connecting users in Clio Manage read access to contacts, matters and activities, and permission to create notes, tasks, activities and contacts.

iManage Work

  • Brings in: documents you search for and pick in iManage Work, into your knowledge base — read within the permissions of your iManage account. Thalassa changes nothing in iManage Work itself.
  • Your firm enables Thalassa in its iManage Control Center; users then connect their account in the desktop app’s settings. This step on the customer side is required.

MCP: connect tool providers

Any system that offers an MCP endpoint can be connected today — document and matter management, compliance, CRM and sales, management tools, and your own internal or AI systems. You are no longer waiting for a separate integration per system: one connector, and every provider with an MCP endpoint is within reach. Included in every plan, alongside the connections above. Add a tool provider in the desktop app's settings, load its catalog and choose the tools available to the assistant.

Supported providers expose tools through MCP Streamable HTTP. The assistant can propose tool calls for answers and briefings. Before each call, the app or overlay shows the provider, tool and exact inputs for your confirmation. Tools may read or change information, depending on the provider. Text and structured results are supported; local stdio servers, OAuth discovery and binary results are not. The existing text-resource import remains available separately.

Connections you configure yourself; data goes to the destination you choose. The desktop app connects directly to your chosen server. Retrieved text is indexed and searched on your device. Selected excerpts used in answers and briefings follow the existing request path through Thalassa's backend and the configured model service, with the source shown. See the privacy policy.