Overview
The Ninox Trigger node for n8n starts workflows when events (specifically, record changes) occur in a Ninox database table. It is designed to poll a specified team, database, and table within Ninox, and trigger the workflow whenever records are updated. This node is useful for automating processes that need to react to data changes in Ninox, such as syncing records with other systems, sending notifications, or performing follow-up actions.
Practical examples:
- Automatically send an email when a new record is added or updated in a Ninox table.
- Sync updated Ninox records to another database or CRM.
- Trigger downstream automation in n8n when specific data changes in Ninox.
Properties
| Name | Type | Meaning |
|---|---|---|
| Team Name or ID | options | The ID of the Ninox team to access. You can select from a list or specify an ID using an expression. Required to identify which team's databases to monitor. |
| Database Name or ID | options | The ID of the Ninox database to access. Select from a list or specify via expression. Only shown after selecting a team. Required to identify which database's tables to monitor. |
| Table Name or ID | options | The ID of the Ninox table to access. Select from a list or specify via expression. Only shown after selecting both team and database. Required to identify which table's records to monitor for changes. |
Output
The output is a JSON array where each item represents a Ninox record that has changed since the last poll. Each object in the array contains the fields of the updated record as provided by the Ninox API. The structure of each record will depend on your Ninox table schema but typically includes standard Ninox record properties such as id, sequence, and any custom fields defined in your table.
Example output:
[
{
"id": "12345",
"sequence": 6789,
"field1": "value1",
"field2": "value2"
// ...other fields as defined in your Ninox table
}
]
- If no records have changed, the node returns
null.
Dependencies
- External Service: Requires access to the Ninox API.
- Credentials: Needs a configured Ninox API credential (
ninoxApi) in n8n. - Environment Variables: Optionally supports a custom base URL for the Ninox API via credentials.
Troubleshooting
Common issues:
- Missing or incorrect credentials: Ensure that the Ninox API credentials are correctly set up in n8n.
- Invalid Team/Database/Table selection: Make sure the selected IDs exist and the user has access rights.
- No records returned: If no records are updated since the last poll, the node will not trigger. For testing, use manual mode to fetch the latest record.
- API rate limits or errors: If the Ninox API returns errors, check your API usage and permissions.
Common error messages:
- "Cannot read property 'id' of undefined" — Likely due to missing or incorrect selection of team, database, or table.
- "401 Unauthorized" — Check your Ninox API credentials.
- "404 Not Found" — The specified team, database, or table does not exist or is inaccessible.