nara fits into your stack. Not the other way around.
nara connects to ServiceNow, Jira, Zammad, Confluence, Microsoft Graph, and Microsoft Teams. Every integration can run strictly read-only on request, and the outbound sync is easy to switch off.
Where your IT support already lives today.
ServiceNow
Continuous sync in both directions, including incidents with attachments. Sync status visible per table, historical records loaded via backfill.
Jira
Issues from Jira are connected so agents work with what your teams already maintain there.
Zammad
With Zammad as your ticket system, nara works directly on your cases as well.
Confluence
Knowledge articles are imported and become typed objects in nara Memory. Pages turn into searchable, linked knowledge.
Microsoft Graph
Access to SharePoint, calendars, and the directory. nara knows documents, appointments, and responsibilities.
Microsoft Teams
nara answers chats and native voice calls directly in Teams. Your employees stay where they are.
ServiceNow, taken seriously.
The ServiceNow integration syncs continuously in both directions and reads incidents including attachments. You see the sync status per table, and the backfill loads historical records. Before anything is written, a dry run shows what would happen, without anything happening. What this sync delivers in practice is shown by our anonymized analysis of six years of ServiceNow incidents from a European manufacturing group: evaluated via ticket sync, attachment extraction, and embeddings. The results are on the analysis page.
Read-only or read-write: you decide.
Strictly read-only
Both directions
Outbound sync switched off, nara writes nothing into your systems
Continuous sync in both directions, for example with ServiceNow
Full read access for analysis, knowledge, and answers
A dry run shows in advance what would be written, without writing
The right mode to start with and for evaluation
Sync status visible per table at any time
Not publicly reachable? Not a problem.
Systems that are only reachable internally are connected through the Edge Connector: it runs in your network and connects outbound only, with no open ports and no firewall changes. And for everything without a ready-made integration, there is the tool registry. Your own systems are added there in typed form, with defined parameters and result schemas, so agents use them just as reliably as any standard integration.
Frequently asked questions about integrations
Can nara read only, without ever writing?
Yes. Every integration can run strictly read-only, and the outbound sync can be switched off.
How do we check what nara would write?
With the dry run. It shows what a sync would change without writing into your system.
Do old tickets come along too?
Yes. The backfill loads historical records so nara does not start from zero.
Our system is not on the list. Now what?
Your own systems are added through the tool registry, typed and with result schemas. Systems that are only reachable internally are connected through the Edge Connector.
Does our team have to learn a new tool?
Not for requests. nara answers chats and native voice calls directly in Microsoft Teams.
Your stack, plus nara.
In a demo, we show the connection to your systems, strictly read-only on request. To see how deep such an analysis goes, take a look at the analysis page first.