Ninox icon

Ninox

Read, create, update and delete data from Ninox

Actions30

Record → Ninox Script

AI-generated

Overview

This node allows users to execute custom Ninox Scripts on a specified Ninox team, database, and optionally table. It supports running read-only or modifying queries using Ninox's scripting language, enabling complex data retrieval or manipulation within Ninox databases. Typical use cases include querying records with custom logic, fetching complex data structures, or automating Ninox workflows by running scripts programmatically.

Use Case Examples

  1. Run a Ninox Script to fetch email addresses from a contact table.
  2. Execute a read-only Ninox Script to retrieve aggregated data without modifying the database.
  3. Split script results into individual items for further processing in a workflow.

Properties

Name Meaning
Ninox Team The ID of the Ninox team to access, selectable from a list, URL, or direct ID input.
Ninox Database The ID of the Ninox database to access, selectable from a list, URL, or direct ID input.
Ninox Table The ID of the Ninox table to access, selectable from a list, URL, or direct ID input. Required for some operations but optional for Ninox Script operation.
Read Only Queries Boolean flag to use GET method for read-only queries instead of POST, suitable for queries that do not modify data.
Ninox Script The Ninox Script code to execute as a query. This is required and defines the custom logic to run on Ninox data.
Parse As JSON Whether to parse the entire response as JSON and return it as a single item, useful for complex data structures.
Split Into Items Whether to split the script results into separate items if the result is an array, each element becomes an individual item.
Fetch As Records When splitting into items, treat array values as record IDs and fetch each record individually. Errors if values are not valid record IDs.

Output

JSON

  • result - The output of the Ninox Script execution, which can be a single JSON object, an array of items, or individual records depending on the input options.

Dependencies

  • Requires Ninox API credentials for authentication.

Troubleshooting

  • Ensure the Ninox Team, Database, and Table IDs are valid and accessible with the provided credentials.
  • If using read-only queries, enable the 'Read Only Queries' option to use GET method; otherwise, use POST for modifying queries.
  • When 'Split Into Items' is enabled, ensure the script returns an array; otherwise, the output may not split correctly.
  • If 'Fetch As Records' is enabled, verify that the array elements are valid record IDs to avoid errors.
  • Timeouts or SSL issues can be managed via request options such as timeout duration, proxy settings, and ignoring SSL certificate validation.

Links

Discussion