Connect Ninox integrations
VerifiedLow-code database and workflow platform, connected to WEXTL workflows and AI agents. Keep connected systems current whenever important Ninox data changes. When Watch New Records fires, follow with Download a File or Find a Record.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Supported triggers and actions for Ninox integration
Triggers can detect changes in Ninox and run actions that can create, search or modify data inside Ninox automatically[3], exactly how you set them.
- Watch New Records Polls a table on your schedule and fires for each record created since the last check. Use Limit to set how many of the newest records the first check takes.
- Watch Updated Records Checks a table on a schedule and fires for every record that was created or modified since the previous check. Use Limit to cap the newest records returned on the first check.
- Download a File Fetches the content of an attachment on a record. Output holds the File, its File Name and Content Type.
- Find a Record Looks in a table for the first record whose fields equal every value of Filters. Use Choice Style to set how choice fields are returned.
- Get a Database Retrieves one Ninox database with its Settings, Schema and Version. Add the Schema Password for a password protected schema, otherwise Ninox answers with an encrypted schema.
- Get a Record Shows a single record of a table with its fields, Created At and Modified At. Use Choice Style to switch how choice fields are returned.
- Get a Table Pulls the definition of one table in a database, giving its ID, Name and Fields.
- Get a Team Finds one Ninox team and returns its ID and Name.
- List Database Changes Lists what changed anywhere in a database after a sequence number, taken from the seq of an earlier answer or of a record. The output holds Updates, Removes and the next Sequence.
- List Databases Shows the databases of a team, each with its ID and Name. Use Limit to set the maximum number of databases returned.
- List Record Files Shows the files attached to one record, each with its Name, Content Type, Size and Modified Date. Use Limit to cap how many files are returned.
- List Table Changes Lists the changes in one table made after a sequence number. Use Since Sequence to set where to start. Each result gives the Updates, the Removes and a fresh Sequence.
- List Tables Enumerates the tables inside a database with their ID, Name and Fields. Use Limit to decide how many tables come out.
- List Teams Retrieves Ninox teams, each with an ID and Name. Use Limit to bound the number of teams.
- Run a Query Executes a read-only Ninox script against a database and returns its Result. Use Query to write the script, such as a select on one table.
- Search Records Returns records from a table, each as its own result. Narrow them with Filters or a Script Filter, sort with Order By, keep only those above an ID using Only After Record ID, and set Limit for the count.
- Create a Record Inserts a row in a Ninox table, with one input per field of the chosen Table. Use Extra Fields for references or multiple choice columns. Returns the new ID and Sequence.
- Create or Update a Record With an ID Writes a record to a Ninox table at one numeric Record ID. A free ID creates the record and an existing ID updates it. Extra Fields cover columns the form lacks.
- Delete a File Deletes one attachment from a record. Turn on Confirm to acknowledge that the file cannot be recovered afterwards.
- Delete a Record Deletes a record in a table. Switch Confirm on to confirm the call, because a deleted record cannot be undone.
- Delete Records Removes many records from a table in one request. Use Confirm to approve it, as the deletion is permanent.
- Make an API Call Sends a free-form request to the Ninox REST API, signed with your saved credential.
- Run a Script Runs a Ninox script that may create, change or delete data and returns its Result. Turn on Confirm to run it, because the changes cannot be undone. On a private cloud the key needs the admin role.
- Update a Record Changes fields on a record that already exists. Use Clear Fields to empty fields, which wins over values filled in on the form, and Extra Fields for columns that form does not offer.
- Upload a File Adds a file to the attachments of a record. Map File from an earlier step such as a download or an email attachment, and use File Name to store it under another name.
How to integrate Ninox in automation workflow?
Ninox in three steps: start with "Watch New Records", connect one credential, then add your next step.
How Ninox connects and integrates with WEXTL
Save and approve your credentials once. WEXTL® stores authorization information encrypted and reuses the authentication whenever Ninox app is called in workflows. That allows your database automations to run without your attention, per defined schedule[7]. See the integration guide[6] for a detailed list of fields that Ninox supports.
Full Ninox API documentationThe following table illustrates what fields Ninox integration require during authorization flow inside our workflow builder[4].
Connect Ninox
API Key*Text
••••••••
Server Address*Text
••••••••
| Field | Type | Help |
|---|---|---|
API KeyRequired | password | In Ninox open Settings, then Integrations, and click New API Key. Public cloud owners find Settings at admin.ninox.com. The key reaches every database you own. On a private cloud give the key the admin role, because the team, database and table lists need it. |
| Server Address | text | Leave empty for Ninox public cloud. For a private cloud or on-premises server enter the server address, for example https://mycompany.ninoxdb.de or https://mycompany.ninoxdb.com. Enter only the host and port. Ninox adds the /v1 part for you. |
Connect Ninox to popular apps on WEXTL
Enter a name of the other app you want to sync with Ninox below. Click on selected app to explore integration options with Ninox. If the app you search for is not available in WEXTL yet, you can use HTTP node[10] instead to integrate it directly.
Example automation with Ninox integration
Select Watch New Records trigger from Ninox - this will be a starting point in your automation. Whenever event happens in Ninox, workflow will start[7] from Watch New Records node.
Search for Create or Update a Record With an ID, connect it as the next step of integration sequence. You can use filters between Watch New Records and Create or Update a Record With an ID, so only important data pass from Watch New Records to the next step. WEXTL gives you full control over the process of Ninox automation. All parts of workflow are visible on the canvas[4].
Ninox on WEXTL has 25 modules for crafting database automations. Explore Ninox documentation for more.
- NinoxWatch New Records
- Google BigQueryPerforms action
OR
- Google BigQueryTriggers
- NinoxCreate or Update a Record With an ID
Frequently asked questions
Common questions about automating Ninox in your workflows.
What triggers does Ninox support?
Ninox has 2 triggers, including "Watch New Records" and "Watch Updated Records". Triggers are start points of the workflow, and automations may start from them.
What actions can I run in Ninox?
Integration has 23 actions, including "Download a File", "Find a Record", and "Get a Database", and more. Refer to our Ninox Documentation for detailed inputs and outputs.
Do I need to write code to build automations?
No. The 24 Ninox modules, like "Download a File", are forms on the canvas: pick a field, map data from an earlier step. Code is optional[4].
Is the integration secure?
Yes. You fill in the Ninox credential once. WEXTL encrypts it at rest, and only your team can use it.
How does WEXTL integrate with Ninox?
Through the official Ninox API: 24 modules, plus "Make an API Call" for any endpoint they don't cover[3].
Can I use webhooks with Ninox?
Ninox doesn't push events here, so "Watch New Records" and "Watch Updated Records" check on the schedule you set. Anything Ninox posts to a URL can start a Custom Webhook node.
Why use WEXTL platform for Ninox automation?
WEXTL is an AI-first visual canvas: describe the Ninox flow in plain words and AI wires the nodes[4].
References
List of sources used to gather information about the Ninox integration.
- Ninox integration source code, module specs and credentials implementation.
- Internal Ninox integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official Ninox vendor API documentation, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® Visual Workflow Builder, anonymized data from our technical support team.
- WEXTL® Apps Library
- WEXTL® Ninox App Documentation
- WEXTL® Workflow Scheduler
- WEXTL® HTTP node documentation
How we write and maintain Ninox app documentation
Explore how WEXTL® crafted Ninox integration page documentation. Used sources, the role of AI, and how the team validates the result.





















