An add-in is a small web page in a side panel next to the document. With HTML, JavaScript and a short manifest it can read and change documents and spreadsheets, talk to your service and use the user's own AI – with permissions the user approves.
Works in Werko Office 0.6.11 or newer on Windows, Mac and Linux.
werko-addin.json names your add-in, the apps it runs in, its panel page and the permissions it needs.
A normal HTML page. Call window.werko to read the selection, write text or fill cells.
Ship a .werkoaddin file (works offline) or host the manifest on your https server (you update it yourself).
Install for testing: in Werko Text or Werko Calc click Add-ins → Install add-in … and choose the file or enter the address.
Before installing, Werko Office shows the user who made the add-in, where it comes from, what it may do and which servers it contacts.
// werko-addin.json { "id": "firma.uebersetzer", "name": "Translator", "version": "1.2.0", "autor": "Company Ltd", "beschreibung": "Translates the selection.", "symbol": "symbol.svg", "programme": ["text", "calc"], "panel": "panel.html", "rechte": ["dokument.lesen", "dokument.schreiben", "ki"], "domains": ["api.firma.example"] }
| Field | Meaning |
|---|---|
id | unique, e.g. company.product (a–z, 0–9, dot, hyphen) |
programme | text = Werko Text, calc = Werko Calc |
panel | file in the package or https:// address; relative to the manifest when installed from an address |
rechte | dokument.lesen, dokument.schreiben, ki |
domains | extra servers the panel may reach, e.g. *.company.example |
symbol | icon in the package or https:// address (optional) |
Every call returns a Promise. A missing permission or a function from the other app rejects with a clear message.
// General await werko.info(); // { programm: 'text'|'calc', version, sprache, addin } await werko.ui.meldung('Done!'); werko.ereignis('auswahl', (a) => console.log(a)); // selection changed // Werko Text await werko.text.auswahl(); // { text, html, leer } dokument.lesen await werko.text.dokument(); // { text, html } dokument.lesen await werko.text.auswahlErsetzen('New text'); // dokument.schreiben await werko.text.einfuegen('<b>Hello</b>'); // at the cursor // Werko Calc await werko.calc.auswahl(); // { adresse: 'B2:C4', blatt, werte } await werko.calc.bereich('A1:C10'); // { adresse, blatt, werte, formeln } await werko.calc.bereichSetzen('A1', [['Month', 'Sales'], ['Jan', 1200], ['Total', '=SUM(B2:B2)']]); await werko.calc.blaetter(); // { blaetter: [...], aktiv } // The user's AI (their provider and key – your add-in never sees the key) ki await werko.ki.fragen('Summarise: …', { system: 'Answer in English.' });
Each add-in runs in its own sandboxed view with its own storage – no Node.js, no file access.
Werko Office checks each window.werko call against the permissions in the manifest.
Network access is limited to the panel's origin and the domains you list. Everything else is blocked.
Before installing, the user sees vendor, source, permissions and servers – and can switch off or remove add-ins anytime.
node addin-paket.mjs my-addin/Not directly. Office add-ins use Microsoft's Office.js API and usually a Microsoft account. The idea is the same – a web page in a side panel – so porting a simple Office add-in is usually a matter of replacing a few calls (for example Word.run → werko.text, Excel.run → werko.calc).
Give them the .werkoaddin file or the address of your manifest. A catalogue of add-ins on werkooffice.com is planned – tell us about your add-in at office@werko.app.
No. Developing and distributing add-ins is free. You decide whether your own service behind the add-in is paid.
Werko Text and Werko Calc today. Werko PDF, Werko Show and Werko Mail will follow.