Integrations
Works with what you already have.
nuhaa.ai reads the documents, databases and repositories you already run. Nothing is migrated, no system is replaced, and connecting a source never widens who can see it.
The shape of a connection
Your systems keep their job as the system of record. nuhaa.ai reads from them, and the three products are three ways of asking that governed layer a question.
Specific connectors are scoped and confirmed during implementation. We do not list integrations we have not built.
- Documents
- Contracts, reports, manuals, presentations and scanned files in Arabic and English.
- Policies
- Procedures, standards, delegation of authority and the rules people are asked to follow.
- Data
- Governed databases and warehouses, queried read only and answered in business language.
- Reports
- Periodic packs and dashboards, read for what changed rather than re-rendered.
- Business systems
- The operational platforms that hold your transactions, records and workflow state.
- Knowledge repositories
- Shared drives, portals and libraries where institutional memory accumulates.
What is connected
The systems nuhaa.ai reads today.
Named rather than described, with an honest status against each one. A category with nothing shipped still appears, marked on request, rather than being left off the page.
Every connector inherits the source’s own permissions. Connecting a system never widens who can see what is inside it.
Documents and knowledge repositories
- Direct upload: PDF, Word, PowerPoint, Excel, CSVAvailable
- Scanned documents and images, read page by pageAvailable
- SharePoint, Google Drive, ConfluenceOn request
Policies
- Policy and procedure libraries, uploaded or read from a shared repositoryAvailable
Data
- PostgreSQLAvailable
- Microsoft SQL ServerAvailable
- MySQLAvailable
- OracleAvailable
- SnowflakeAvailable
Reports
- Periodic packs and exported reports, read as documentsAvailable
- BI platforms read directlyOn request
Business systems
- ERP, CRM and operational platformsOn request
Ticketing and workflow
- Service desk and workflow toolsOn request
Integrations are scoped and confirmed during implementation. Nothing is connected without your explicit approval.
What can be connected
Three kinds of source.
Documents and repositories
Contracts, policies, procedures, manuals, reports and presentations, including scanned files, uploaded directly or read from a shared repository.
Databases and warehouses
Governed relational sources, connected read-only and granted table by table, answered in business language rather than in SQL.
Business systems
Operational platforms holding transactions, records and workflow state, connected where an interface exists and scoped to what the use case needs.
Practicalities
The questions an integration architect asks first.
- Sources are connected one at a time, with your approval
- Each source keeps the access rules it already had
- Database access is read-only and granted per table
- Credentials are encrypted at rest and never written to logs
- Arabic and English content lives in one searchable body of knowledge
- A source can be disconnected, and its derived index removed with it
What we will not do
A migration project is the fastest way to turn a six week pilot into an eighteen month programme. nuhaa.ai is deliberately built to read your sources where they are, so the first real answer arrives while the enthusiasm is still there.
We also do not publish a wall of connector logos. If a specific system matters to your use case, ask us directly and you will get a yes, a no, or a date.
We will tell you whether nuhaa.ai can read it today.