# Ninox integrations: records, tables and fields

> Create records, create a table and create a field in Ninox. Connect Ninox to the rest of your data and analytics stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/ninox-integrations/
**Categories:** Data and analytics
**Connects through:** HTTP Connector

## Overview

Ninox is a low-code database platform where teams build custom business apps from tables, views, forms and reports. Tray.ai connects to Ninox through the HTTP Connector, so your workflows can call the Ninox API alongside the rest of your stack.

## Use cases

### Records

Read, create, update, and delete records in Ninox from any Tray.ai workflow. The Ninox API covers calls such as get records and get a record.

- Get records
- Get a record
- Create records

### Tables

Read, create, update, and delete tables in Ninox from any Tray.ai workflow. The Ninox API covers calls such as list tables and get a table.

- List tables
- Get a table
- Create a table

### Fields

Read, create, update, and delete fields in Ninox from any Tray.ai workflow. The Ninox API covers calls such as list fields and create a field.

- List fields
- Create a field
- Update a field

### Views

Read and create views in Ninox from any Tray.ai workflow. The Ninox API covers calls such as list views and create a view.

- List views
- Create a view
- Export a view to XLSX

### Reports

Read and create reports in Ninox from any Tray.ai workflow. The Ninox API covers calls such as list reports and create a report.

- List reports
- Create a report
- Print a report

## Challenges Tray.ai solves

### Keeping Ninox credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Ninox credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Ninox API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Ninox API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Ninox?

Yes. Tray.ai connects to Ninox through the HTTP Connector, which calls the Ninox API directly. Any call the Ninox API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Ninox?

The Ninox API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Ninox connector?

Ninox runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Ninox connector from the Ninox API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/