Hat nordOFFICE eine API?

Ja, auf zwei Wegen zu denselben Werkzeugen: eine klassische REST-API mit OpenAPI-3.1-Dokument (HTTPS + JSON, Bearer-Token) und eine Schnittstelle nach dem Model Context Protocol (MCP, JSON-RPC 2.0 über HTTPS) für KI-Systeme. Darüber stehen über 1010 Werkzeuge aus allen Modulen bereit — Lesen, Suchen, Anlegen, Ändern und die Fachaktionen des jeweiligen Moduls. Ein Zugang gilt für beide Wege.

Gibt es ein OpenAPI-Dokument?

Ja. Jede Instanz liefert unter /rest/v1/openapi.json ein OpenAPI-3.1-Dokument, zugeschnitten auf den abfragenden Zugang: Es enthält nur die Operationen, die dieser Zugang tatsächlich ausführen darf. Es lässt sich direkt in n8n, Make, Postman oder einen Codegenerator importieren und für Werkzeuge mit Operationslimit nach Gruppen filtern. Dazu gibt es unter /rest/v1/docs eine lesbare Referenz im Browser.

Kann ich nordOFFICE mit n8n, Make oder Zapier verbinden?

Ja. Am einfachsten über die REST-API: OpenAPI-Dokument importieren oder einen Knoten „HTTP Request“ mit Bearer-Token anlegen. Neuere n8n-Fassungen bringen zusätzlich einen eigenen MCP-Client-Knoten mit, dem Adresse und Token reichen. Für wiederkehrende Abläufe wie Export, Abgleich oder Benachrichtigung ist kein eigener Programmierauftrag nötig.

Sieht ein Zugang mehr Daten als der Benutzer selbst?

Nein. Jeder Zugang läuft mit den Rechten genau des Benutzers, der ihn angelegt hat, und kann zusätzlich eingeschränkt werden — etwa auf „Nur lesen“. Was der Benutzer nicht darf, kann auch die Schnittstelle nicht. Nicht freigegebene Module existieren für den Zugang gar nicht.

Was kostet die Schnittstelle?

Nichts — das Modul „KI-Zugriff (MCP)“ ist kostenlos. Es ist Grundmodul jeder nordOFFICE-Bestellung; ein Superuser Ihrer Instanz kann es jederzeit abschalten. Gebühren pro Aufruf fallen ebenfalls nicht an.

Your data stays reachable.
From the outside too.

nordOFFICE comes with an open interface — as a REST API with an OpenAPI document for automation services such as n8n and Make and for your own programs, and as an MCP connector for AI systems such as Claude and ChatGPT. More than 1,010 tools from every module, one account for both routes, no per-call fee.

REST API · OpenAPI 3.1 Model Context Protocol Bearer token HTTPS + JSON The user's permissions Hosting in Germany

One account, three use cases.

One account serves AI programs (MCP) and classic automation (REST) — you decide per account how far it reaches.

AI without exporting data

Claude, ChatGPT or Claude Code work directly on the live data: summarise tickets, prepare quotes, run analyses. Your data stays in nordOFFICE throughout — nothing is copied into somebody else's tool.

Automation without a programmer

n8n, Make or Zapier fetch figures, create customers from a form, move tasks or report deadlines into the team chat. An “HTTP Request” node is enough — or you import the OpenAPI document straight away.

Connecting your own systems

A shop, production planning or a specialist application hands data to nordOFFICE or reads it out — over REST with JSON, with client code generated from the OpenAPI document. No intermediate layer, no file import, no overnight reconciliation.

Connected in five minutes.

Create a token in the settings, enter the address, call it. There is no sign-in handshake — the server is stateless and every request stands on its own. Two routes, one tool catalogue: REST for scripts and automation, MCP for AI clients.

REST 1 — fetch the OpenAPI document (only what this account is allowed to do)

curl https://ihre-instanz.nordoffice.app/rest/v1/openapi.json \
  -H "Authorization: Bearer nomcp_IHR_TOKEN"

REST 2 — read with GET, write with POST

curl "https://ihre-instanz.nordoffice.app/rest/v1/tools/kunden_liste?suchbegriff=Muster&limit=5" \
  -H "Authorization: Bearer nomcp_IHR_TOKEN"

curl -X POST https://ihre-instanz.nordoffice.app/rest/v1/tools/journal_eintrag_anlegen \
  -H "Authorization: Bearer nomcp_IHR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"kundeId":324,"text":"Telefonat zur Vertragsverlängerung","dauerMinuten":15}'

MCP 1 — which tools does this account have?

curl -N https://ihre-instanz.nordoffice.app/mcp \
  -H "Authorization: Bearer nomcp_IHR_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

MCP 2 — call a tool

curl -N https://ihre-instanz.nordoffice.app/mcp \
  -H "Authorization: Bearer nomcp_IHR_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call",
       "params":{"name":"kunden_liste",
                 "arguments":{"suchbegriff":"Muster","limit":5}}}'

REST: Responses come as JSON, errors consistently as {"error":"…"} with the matching status; GET …/rest/v1/catalog lists the tools available to that access. Deleting and sending operations first return a preview and only run after explicit confirmation. MCP: The header Accept must name both types; the response arrives as an event stream — the payload is in the line beginning with data: . Both addresses and the complete tool list are available in your instance under Settings → AI access (MCP); it follows the modules that are enabled and your permissions.

Tools from every module.

Reading and searching, creating, changing, deleting — plus each module's own domain actions.

Collaboration

Customers, contacts, tickets, email, chat, telephony, calendar, appointment booking, tasks, follow-ups, knowledge, files.

Business

Sales, quotes & invoices, contracts, projects with their time records, events, vouchers, reports and analyses.

Marketing

Newsletters, email sequences, surveys and live polls — from the recipient list to the delivery status.

HR

Personnel files and skills, working time, travel expenses, vehicle fleet, academy and learning room.

All modules in detail

Open does not mean unprotected.

REST and MCP use exactly the same permission checks as the interface — there is no second, laxer route into the data. The OpenAPI document, too, shows only what that particular account is allowed to do.

Never more than the user

Every account runs with its user's permissions and can only narrow them further, never widen them. Modules that are not enabled do not exist for the account at all.

Read-only by default

New accounts may initially only read. You enable write access deliberately — per account, changeable at any time.

Sending requires confirmation

Sending mail, invitations, binding bookings and permanent deletion first require a preview and then an explicit confirmation — from a script as well.

Revocable at any time

Every account is visible on its own, is logged with its last use and can be revoked with one click. Tokens are held only in encrypted form as a checksum.

Frequently asked questions

Does nordOFFICE have an API?

Yes, in two ways to the same tools: a classic REST API with an OpenAPI 3.1 document (HTTPS + JSON, bearer token) and an interface following the Model Context Protocol (MCP) for AI systems. Over 1,010 tools from all modules are available through it. One access covers both routes.

Is there an OpenAPI document?

Yes. Every instance serves it at /rest/v1/openapi.json an OpenAPI 3.1 document tailored to the requesting access: it contains only the operations that access may actually perform. It can be imported directly into n8n, Make, Postman or a code generator and filtered by group for tools with an operation limit. In addition there is /rest/v1/docs a readable reference in the browser — without third-party scripts, straight from your instance.

REST or MCP — which should I take?

REST when a program, a script or an automation service is talking: plain HTTPS with JSON and an OpenAPI document to import or generate from. MCP when an AI system is talking: Claude, ChatGPT and the like understand by themselves what each tool does, because it carries its own description. Both lead to the same tools with the same permissions — you can switch at any time or use both in parallel.

Can I connect nordOFFICE to n8n, Make or Zapier?

Yes. The simplest way is the REST API: import the OpenAPI document or use an “HTTP Request” node with the header Authorization: Bearer … Newer n8n versions additionally ship a dedicated MCP client node that only needs the address and token. Export, reconciliation or notifications therefore need no development work.

Does an account see more than the user does?

No. Every account runs with the permissions of exactly the user who created it and can be narrowed further — to “read only”, for instance. Whatever the user is not allowed to do, the interface cannot do either.

What does the interface cost?

Nothing — the module AI access (MCP) is free of charge. It is a core module of every nordOFFICE order; a superuser of your instance can switch it off at any time. There are no per-call fees either.

Does that apply to on-premise operation as well?

Yes. The interface belongs to the application, not to the hosting — it is available in the cloud instance just as it is when running on your own infrastructure.

Have a connection in mind?

Request demo access and try the interface out with real sample data — or tell us what you have in mind.

Request a demo All modules

Your data stays reachable.From the outside too.