Integrations

Whose machine the data lives on decides what kind of integration it is

Treating file associations, local processes and connectors as one thing is a common starting point for design mistakes. Textrix sorts them into three layers by where the data sits — the first two need no authorisation and work offline; only the third needs an account.

The three-layer model

One question decides it: whose machine holds the data? Yours means layer one or two; someone else’s server with an account means layer three.

Local foldernotes/ · docs/Plain files.md · .docx · .xlsxLocal toolsconnectorsTextrixone local knowledge base

L1 — Files

Data lives in local files

Integration through file formats and open-with behaviour — a double click hands the file to an external tool, without copying or converting.

  • Communication: file format + open with
  • Authorisation: none
  • Examples: Abaqus .inp / .odb, MATLAB .mat, PDF

L2 — Processes

Data lives in a local process

Integration through a local port, a CLI or inter-process communication — no server involved.

  • Communication: local port / CLI / IPC
  • Authorisation: none
  • Examples: Zotero 127.0.0.1:23119, git, python, LSP

L3 — Network

Data lives on someone else’s server

Integration through a remote API, which needs an account — this is what people usually mean by a connector.

  • Communication: remote API
  • Authorisation: account required
  • Examples: arXiv / CrossRef / PubMed / GitHub

One worked example: Zotero is not a connector

It runs on your own machine — so Textrix treats it as a built-in local integration rather than a network service.

Other tools that live in layer two

Zotero is the worked example, not the exception — any tool that runs on your own machine can join the knowledge base the same way: no account, no network.

git

Version your knowledge base with the git already on your machine — history, branches and diffs stay in local processes.

python

Run scripts against your Markdown files through a local interpreter — batch renaming, analysis, anything a CLI can do.

LSP

Language servers speak a local protocol — the same channel editors use, plugged into the workbench without a server round-trip.

Deliberately not built

For these categories, integration has only ever meant three things: file association, command-line invocation and a scripting interface. Turning them into connectors is an anti-pattern.

An Abaqus connector

All the data is in local files and local processes. The right shape is a file association, a command-line invocation and the abaqus python scripting interface.

A MATLAB connector

Same as above — the right shape is a .mat file association. No network service is needed.

Connectors for professional CAE and simulation tools

Integration with this class of software has only ever meant three things: file association, command-line invocation and a scripting interface.

Office IM connectors (v1)

Office work is a deferred audience — pushed back until the network layer vertical is proven.

A connector is not a layer of its own: it is a capability declaration made by a plugin. The plugin manifest states which external services it depends on, and installing the plugin brings those dependencies along. v1 covers a single vertical: academic literature search.

Common questions

Why does Zotero need no network connection?

Because the Zotero desktop app listens on 127.0.0.1:23119 on your own machine, so the conversation with it never leaves the computer. Textrix uses that local channel: no authorisation, works offline.

Do I install connectors separately?

No. A connector is a capability declaration made by a plugin — installing the plugin brings the external services it depends on along with it.

Which external services are supported?

v1 covers one vertical: academic literature search (arXiv, CrossRef, PubMed and similar). Code hosting (GitHub, GitLab) stays. Office-oriented services are deferred.

Related

Keep exploring

Related reading on the model behind this page.

Still in development

Downloads are not open yet. Join the waitlist and we will invite you the moment it opens.

Email-collection mode: submitting opens a pre-filled message in your mail client.