Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Ninox

Ninox integration for Flows360 workflows.

CategoryOther
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 21, 2026

Overview

Connect Ninox with Flows360

Ninox integration for Flows360 workflows.

Use the Ninox connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 8 actions and 1 trigger.

Available actions

  • Create Record
  • Update Record
  • Delete Record
  • Upload File
  • Download File from Record
  • Find Record
  • List Files from Record
  • Custom API Call

Available triggers

  • New Record

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Ninox
  • Package: @activepieces/piece-ninox@0.2.0
  • Exact artifact digest: sha256:bbba6c8787788039bd4f7afd56e9d04cf12d679142d5014b5ddf8f2e70677cb1
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Record (createRecord), Creates a new record into a specified table. Classification: read.
  • Update Record (updateRecord), Updates fields on an existing record. Classification: read.
  • Delete Record (deleteRecord), Deletes a record from a table. Classification: read.
  • Upload File (uploadFile), Attach a file to a record. Classification: read.
  • Download File from Record (downloadFileFromRecord), Downloads a file attached to a record. Classification: read.
  • Find Record (findRecord), Finds records by field values. Classification: read.
  • List Files from Record (listFilesFromRecord), List files attached to a specific record (without downloading) for management. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Record, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects9
Supported actions8
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Ninox API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Record Yes No Creates a new record into a specified table.
Update Record Yes No Updates fields on an existing record.
Delete Record Yes No Deletes a record from a table.
Upload File Yes No Attach a file to a record.
Download File from Record Yes No Downloads a file attached to a record.
Find Record Yes No Finds records by field values.
List Files from Record Yes No List files attached to a specific record (without downloading) for management.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Record Yes No polling trigger declared by the pinned package.

Supported actions

Create Record · Read

Creates a new record into a specified table.

create_record · Risk: low · Retry: safe

Inputs

  • teamid · string · Required, Select the team containing the database.
  • dbid · string · Required, Select the database containing the table.
  • tid · string · Required, Select the table
  • fields · object · Required
Update Record · Read

Updates fields on an existing record.

update_record · Risk: low · Retry: safe

Inputs

  • teamid · string · Required, Select the team containing the database.
  • dbid · string · Required, Select the database containing the table.
  • tid · string · Required, Select the table
  • rid · string · Required
  • fields · object · Required
Delete Record · Read

Deletes a record from a table.

delete_record · Risk: low · Retry: safe

Inputs

  • teamid · string · Required, Select the team containing the database.
  • dbid · string · Required, Select the database containing the table.
  • tid · string · Required, Select the table
  • recordId · string · Required
Upload File · Read

Attach a file to a record.

upload_file · Risk: low · Retry: safe

Inputs

  • teamid · string · Required, Select the team containing the database.
  • dbid · string · Required, Select the database containing the table.
  • tid · string · Required, Select the table
  • rid · string · Required
  • file · object · Required, The file to upload to the record.
Download File from Record · Read

Downloads a file attached to a record.

download_file_from_record · Risk: low · Retry: safe

Inputs

  • teamid · string · Required, Select the team containing the database.
  • dbid · string · Required, Select the database containing the table.
  • tid · string · Required, Select the table
  • rid · string · Required
  • file · string · Required
Find Record · Read

Finds records by field values.

find_record · Risk: low · Retry: safe

Inputs

  • teamid · string · Required, Select the team containing the database.
  • dbid · string · Required, Select the database containing the table.
  • tid · string · Required, Select the table
  • searchField · string · Required
  • searchValue · string · Required, The value to search for in the specified field.
List Files from Record · Read

List files attached to a specific record (without downloading) for management.

list_files_from_record · Risk: low · Retry: safe

Inputs

  • teamid · string · Required, Select the team containing the database.
  • dbid · string · Required, Select the database containing the table.
  • tid · string · Required, Select the table
  • rid · string · Required
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New Record · Poll

Triggers when a new record is created in a table.

Inputs

  • teamid · string
  • dbid · string
  • tid · string

Setup

Setup

  1. Add the Ninox connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-ninox@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 8 actions and 1 trigger declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Ninox connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-ninox@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com