FileMaker and Ninox Integration
Keep FileMaker and Ninox matched by integrating their events and actions. When database events happen in FileMaker, update the Ninox automatically - without any line of code in visual workflow builder.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about FileMaker and Ninox
Detailed info you need to know about FileMaker and Ninox integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect FileMaker to Ninox
Set up your FileMaker and Ninox integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect FileMaker and Ninox
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow[3]. No coding or API skills required.
STEP 2
Build a workflow
Paste selected FileMaker and Ninox nodes onto the canvas[4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between FileMaker and Ninox. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between FileMaker and Ninox work in WEXTL?
WEXTL exposes actions and triggers for FileMaker and Ninox that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.
Ninox triggersFileMaker actions
Ninox modules
- Create a Record Inserts a row in a Ninox table, with one input per field of the chosen Table. Use Extra Fields for references or multiple choice columns. Returns the new ID and Sequence.
- Create or Update a Record With an ID Writes a record to a Ninox table at one numeric Record ID. A free ID creates the record and an existing ID updates it. Extra Fields cover columns the form lacks.
- Delete a File Deletes one attachment from a record. Turn on Confirm to acknowledge that the file cannot be recovered afterwards.
- Delete a Record Deletes a record in a table. Switch Confirm on to confirm the call, because a deleted record cannot be undone.
- Delete Records Removes many records from a table in one request. Use Confirm to approve it, as the deletion is permanent.
- Download a File Fetches the content of an attachment on a record. Output holds the File, its File Name and Content Type.
- Find a Record Looks in a table for the first record whose fields equal every value of Filters. Use Choice Style to set how choice fields are returned.
- Get a Database Retrieves one Ninox database with its Settings, Schema and Version. Add the Schema Password for a password protected schema, otherwise Ninox answers with an encrypted schema.
- Get a Record Shows a single record of a table with its fields, Created At and Modified At. Use Choice Style to switch how choice fields are returned.
- Get a Table Pulls the definition of one table in a database, giving its ID, Name and Fields.
- Get a Team Finds one Ninox team and returns its ID and Name.
- List Database Changes Lists what changed anywhere in a database after a sequence number, taken from the seq of an earlier answer or of a record. The output holds Updates, Removes and the next Sequence.
- List Databases Shows the databases of a team, each with its ID and Name. Use Limit to set the maximum number of databases returned.
- List Record Files Shows the files attached to one record, each with its Name, Content Type, Size and Modified Date. Use Limit to cap how many files are returned.
- List Table Changes Lists the changes in one table made after a sequence number. Use Since Sequence to set where to start. Each result gives the Updates, the Removes and a fresh Sequence.
- List Tables Enumerates the tables inside a database with their ID, Name and Fields. Use Limit to decide how many tables come out.
- List Teams Retrieves Ninox teams, each with an ID and Name. Use Limit to bound the number of teams.
- Make an API Call Sends a free-form request to the Ninox REST API, signed with your saved credential.
- Run a Query Executes a read-only Ninox script against a database and returns its Result. Use Query to write the script, such as a select on one table.
- Run a Script Runs a Ninox script that may create, change or delete data and returns its Result. Turn on Confirm to run it, because the changes cannot be undone. On a private cloud the key needs the admin role.
- Search Records Returns records from a table, each as its own result. Narrow them with Filters or a Script Filter, sort with Order By, keep only those above an ID using Only After Record ID, and set Limit for the count.
- Update a Record Changes fields on a record that already exists. Use Clear Fields to empty fields, which wins over values filled in on the form, and Extra Fields for columns that form does not offer.
- Upload a File Adds a file to the attachments of a record. Map File from an earlier step such as a download or an email attachment, and use File Name to store it under another name.
- Watch New Records Polls a table on your schedule and fires for each record created since the last check. Use Limit to set how many of the newest records the first check takes.
- Watch Updated Records Checks a table on a schedule and fires for every record that was created or modified since the previous check. Use Limit to cap the newest records returned on the first check.
FileMaker modules
- Create a Record Saves a new record on the chosen layout, taking the field values from Field Data. Use Portal Data to fill portal rows. Returns the Record ID and Modification ID of the new record.
- Delete a Record Deletes a single record. Use Script to run a FileMaker script once the request finishes.
- Duplicate a Record Makes a copy of a record that already exists. Returns the Record ID of the copy together with its Modification ID.
- Edit a Record Changes chosen fields of a record using Field Data. Use Date Formats to pick US, file locale or ISO 8601 dates. Returns the fresh Modification ID.
- Find Records Searches a layout with find criteria, where a row of Query can exclude matches by setting omit to true. Use Limit to cap the number of matches. Each match returns its Field Data and Portal Data.
- Get a Record Fetches one record of a layout by its Record ID. Use Date Formats to choose how dates are written in the result.
- Get Layout Metadata Reads how a layout is built from its fields, portals and value lists, returned as Field Metadata, Portal Metadata and Value Lists. Give a Record ID to include dynamic value lists tied to that record.
- Get the Product Info Reads locale format details of the FileMaker host. Returns its Name, Date Format, Time Format and Timestamp Format.
- List Databases Shows the hosted databases that the Data API can reach, each with its Name. Use Limit to cap how many are returned.
- List Layouts Retrieves the layouts held by the connected database, giving each an Is Folder value next to its Name. Use Limit to restrict the count.
- List Records Pages through the records of a layout, each carrying Field Data. Use Limit to set how many are returned.
- List Scripts Gathers the scripts of the connected database and says whether each is a folder. Set Limit to keep the list short.
- Make an API Call Calls the FileMaker REST API directly with a free-form request under your saved credential.
- Run a Script Executes a FileMaker script in the context of a layout and can hand it a Script Parameter. Returns the Script Error and Script Result.
- Set Global Field Values Sets global fields in the connected database from Global Fields, using fully qualified global field names as the keys.
- Upload Container Data Stores a File in a container field of a record. Use Field Repetition to target a repeating container field, which defaults to 1. Returns the new Modification ID.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with FileMaker and Ninox integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting FileMaker and Ninox.
References
List of sources used to gather information about the FileMaker and Ninox integration.
- FileMaker and Ninox integration source code, module specs and credentials implementation.
- Our FileMaker and Ninox integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for FileMaker and Ninox, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- FileMaker integration information
- Ninox integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted FileMaker and Ninox integration page documentation. Used sources, the role of AI, and how the team validates the result.

