Ninox icon

Ninox

Read, create, update and delete data from Ninox

Actions30

Schema → Ninox Script

AI-generated

Overview

This node executes custom Ninox Script queries on a specified Ninox team, database, and optionally a table. It allows users to run read-only or modifying queries using Ninox's scripting language, providing flexibility to interact with Ninox data beyond standard CRUD operations. Common use cases include fetching complex data sets, performing batch updates, or running calculations within Ninox databases.

Use Case Examples

  1. Run a Ninox Script to fetch all contacts with a specific email domain.
  2. Execute a script to update multiple records based on a condition.
  3. Retrieve nested or complex data structures from Ninox and parse them as JSON for further processing.

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. This is optional depending on the operation.
Read Only Queries Whether to use HTTP GET method for read-only queries instead of POST. Enable this for queries that only read data without making changes.
Ninox Script The Ninox Script query to execute, allowing custom scripting to interact with 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, with each element becoming an individual item.
Fetch As Records When splitting into items, whether to treat array values as record IDs and fetch each record individually. Errors if values are not valid record IDs.

Output

JSON

  • data - The raw or parsed response data from the Ninox Script execution.
  • items - Individual items if the response is split into multiple items.

Dependencies

  • Ninox API with API key credential

Troubleshooting

  • Ensure the Ninox Team, Database, and Table IDs are correct and accessible with the provided API credentials.
  • If using read-only queries, enable the 'Read Only Queries' option to use GET method; otherwise, use POST for modifying queries.
  • Parsing as JSON requires the response to be valid JSON; otherwise, parsing will fail.
  • When 'Split Into Items' is enabled, ensure the script returns an array; otherwise, the output may not be as expected.
  • If 'Fetch As Records' is enabled, ensure the array elements are valid record IDs to avoid errors.

Links

Discussion