Excel data, Ninox apps
Set up once by an admin, used by the whole team, and always showing the current records.
List workbooks
See the workbooks your Microsoft account can open and pick the one to work from.
Search workbooks
Find the workbook you need and connect it to Ninox.
Append a row
Add a record to the workbook without anyone leaving their process.
Update a range
Write status or corrected values back into the cells they came from.
Excel is Microsoft's spreadsheet, and in most companies the place operational lists start. Connecting it lets a Ninox app work from what is already maintained instead of asking anyone to migrate first.
Related categories
Other integrations
No, not for the built-in connectors. You connect accountsfrom the Connections catalogue with guided setup, so your team can startpulling in data right away. When you need more control, you can call connectedservices directly from Ninox Script and build custom logic around them.
Synced tables bring data from external sources into Ninox automatically, so your apps always work with current information. To send changes back out, use the REST API: it creates or updates a record in a single call by matching on a field you choose. Two-way sync that writes changes back to the source is on the roadmap.
Yes. Every API key gets its own scopes for reading or writing records, schema, and permissions, so a key reaches only what it needs instead of your whole workspace. The same read and write rules you set in the builder apply to API access, and scripts run through a key stay limited to the module that key can reach. Ninox is GDPR compliant and ISO 27001 certified.
Your organization does. Admins control whether Ninox AI can access records, and that access is off by default. Your team gets AI help with building while your data stays private until you choose to open it up.
Put your data where the work happens
Connect once, point a table at it, and the records your team already trusts show up in the app they use every day.
