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 920 tools from every module, one account for both routes, no per-call fee.
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.
curl https://ihre-instanz.nordoffice.app/rest/v1/openapi.json \ -H "Authorization: Bearer nomcp_IHR_TOKEN"
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}'
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"}'
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":"…"} mit passendem Status;
GET …/rest/v1/catalog listet die Werkzeuge des Zugangs. Löschende und sendende Operationen liefern zuerst
eine Vorschau und laufen erst nach ausdrücklicher Bestätigung.
MCP: The header Accept muss beide Typen nennen; die Antwort kommt als Ereignisstrom — die
Nutzdaten stehen in der Zeile, die mit data: beginnt. Beide Adressen und die vollständige Werkzeugliste
stehen in Ihrer Instanz unter 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.
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?
Is there an OpenAPI document?
/rest/v1/openapi.json ein OpenAPI-3.1-Dokument, zugeschnitten auf den abfragenden Zugang: Es enthält nur die Operationen, die dieser 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 — ohne Fremdskripte, direkt aus Ihrer Instanz.REST or MCP — which should I take?
Can I connect nordOFFICE to n8n, Make or Zapier?
Authorization: Bearer … anlegen. Neuere n8n-Fassungen bringen zusätzlich einen eigenen MCP-Client-Knoten mit, dem Adresse und Token reichen. Für Export, Abgleich oder Benachrichtigungen ist damit kein Programmierauftrag nötig.Does an account see more than the user does?
What does the interface cost?
Does that apply to on-premise operation as well?
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.