Source
HubSpot, joined to the documents
HubSpot knows who the company is and where the relationship got to. The documents know what was actually decided. Nemosyne reads the records as records, typed fields stored exactly as they are, and resolves them to the same companies and people the documents name, so the two stop being separate stories.
What it captures.
- Companies, contacts and deals — the entities your documents also talk about.
- Deal stages and their history, which is what lets a CRM position be compared with a document.
- Notes and descriptions, which are prose and are read.
How it behaves.
- Authentication
- OAuth, against your HubSpot account.
- Permissions
- Firm-wide — see below.
- Scope
- The account the credential belongs to.
- A document
- A record. A company, a contact or a deal each count as one.
- Sync
- Continuous; only what changed is re-read.
- Writes
- None. HubSpot stays the system of record for the pipeline.
What this means for permissions.
HubSpot is read firm-wide, exactly like Salesforce. The connector reads at account scope rather than reproducing HubSpot's permission model, so anything it captures is visible to everyone in your memory, whatever HubSpot's own teams and permissions say. Weigh that before connecting an account that holds records some colleagues should not see.
What we enforce, and the limits we publish →Questions this raises.
- Will it change our records?
- No. Nothing is written back, and nothing inside the memory overwrites anything either — the record is append-only.
Connect it to what you already use.
Free for three people and about a hundred documents. No card, no expiry.
Start free →See also SharePoint · Google Drive · Salesforce · Slack · Gmail