Ninox Trigger icon

Ninox Trigger

Starts the workflow when Ninox events occur

Ninox Trigger

AI-generated

Overview

The Ninox Trigger node starts an n8n workflow when changes occur in Ninox database records. It is designed to poll Ninox for record updates in a specified team, database, and table, triggering the workflow with the updated records. This node is useful for automating processes that depend on real-time or near-real-time data changes in Ninox, such as syncing data to other systems, sending notifications, or updating dashboards.

Use Case Examples

  1. Trigger a workflow whenever a new record is added or updated in a specific Ninox table.
  2. Automate data synchronization between Ninox and another application by triggering on record changes.

Properties

Name Meaning
Poll Times Specifies the schedule for polling Ninox for record changes, supporting various intervals like every minute, hour, day, week, month, custom cron expressions, or every X minutes/hours.
Team Name or ID The Ninox team to monitor for record changes. Can be selected from a list or specified via expression.
Database Name or ID The Ninox database within the selected team to monitor for record changes. Can be selected from a list or specified via expression.
Table Name or ID The Ninox table within the selected database to monitor for record changes. Can be selected from a list or specified via expression.

Output

JSON

  • sequence - The sequence number of the record update, used to track the latest processed change.
  • id - The unique identifier of the Ninox record.
  • updated - Indicates if the record was updated.
  • fields - The data fields of the Ninox record.

Dependencies

  • Ninox API with API key credential

Troubleshooting

  • Ensure the Ninox API credentials are correctly configured and have access to the specified team, database, and table.
  • If no records are returned, verify that the teamId, databaseId, and tableId parameters are correctly set and that there are recent updates in Ninox.
  • Check the polling schedule to ensure it matches the expected frequency of record changes.

Links

Discussion