Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →Connect to Zuora Data Using the Script Function in Claris FileMaker Pro
Use the CData ODBC Driver for Zuora and the Script function in FileMaker Pro to connect to Zuora and work with Zuora data in your FileMaker application.
Claris FileMaker is a low-code database application development tool that enables users to create custom apps for managing and organizing data. It combines a powerful relational database engine with an intuitive interface, allowing both technical and non-technical users to design and deploy applications across desktop, web, and mobile platforms.
In this article, we'll explore how to use the CData ODBC Driver for Zuora and FileMaker scripting to connect to Zuora data.
Create an ODBC Data Source for Zuora
If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.
Zuora uses the OAuth standard to authenticate users. See the online Help documentation for a full OAuth authentication guide.
Configuring Tenant property
In order to create a valid connection with the provider you need to choose one of the Tenant values (USProduction by default) which matches your account configuration. The following is a list with the available options:
- USProduction: Requests sent to https://rest.zuora.com.
- USAPISandbox: Requests sent to https://rest.apisandbox.zuora.com"
- USPerformanceTest: Requests sent to https://rest.pt1.zuora.com"
- EUProduction: Requests sent to https://rest.eu.zuora.com"
- EUSandbox: Requests sent to https://rest.sandbox.eu.zuora.com"
Selecting a Zuora Service
Two Zuora services are available: Data Query and AQuA API. By default ZuoraService is set to AQuADataExport.
DataQuery
The Data Query feature enables you to export data from your Zuora tenant by performing asynchronous, read-only SQL queries. We recommend to use this service for quick lightweight SQL queries.
Limitations- The maximum number of input records per table after filters have been applied: 1,000,000
- The maximum number of output records: 100,000
- The maximum number of simultaneous queries submitted for execution per tenant: 5
- The maximum number of queued queries submitted for execution after reaching the limitation of simultaneous queries per tenant: 10
- The maximum processing time for each query in hours: 1
- The maximum size of memory allocated to each query in GB: 2
- The maximum number of indices when using Index Join, in other words, the maximum number of records being returned by the left table based on the unique value used in the WHERE clause when using Index Join: 20,000
AQuADataExport
AQuA API export is designed to export all the records for all the objects ( tables ). AQuA query jobs have the following limitations:
Limitations- If a query in an AQuA job is executed longer than 8 hours, this job will be killed automatically.
- The killed AQuA job can be retried three times before returned as failed.
When you configure the DSN, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.
Connect and Sync Zuora data with FileMaker Using Scripts
In this section, we walk through the steps to connect live Zuora data to FileMaker using the CData ODBC Driver for Zuora and the Script function. During the initial import, FileMaker brings in all data from the external data source. From the second import onward, it updates only the data that has changed in the external source (a differential update). You can also replace the data in the current record order and schedule these differential updates for automated syncing.
You can download and install the latest version of FileMaker Pro for your Mac/Windows/Linux systems from this link.
Connect and sync Zuora data with FileMaker using scripts
Scripting in FileMaker automates complex tasks and workflows by running a sequence of actions with a single command. By using scripting to integrate with Zuora, you can automatically connect to, import, update, and replace Zuora data within your FileMaker applications, streamlining data management and improving efficiency.
First-time importing and adding Zuora data using script
In this section, we'll use scripts to import Zuora data into FileMaker by following these steps:
- Open FileMaker Pro. Navigate to Create from the left panel and select Blank > Create.
- Enter a filename of your choice and click Save.
- In the Manage Database window, go to the Tables tab and create or rename the table where you want to display the Zuora data.
- In the Fields tab, create and add the fields you want to use in the table.
- In the Relationships tab, add table relationships if there are multiple tables, then click OK.
- To reopen and modify the table structure, go to File > Manage > Database.
- Navigate to Scripts > Script Workspace.
- Select New Script to open a new script workspace.
- From the Steps panel on the right, select Records > Import Records > Insert into Script.
- In the Specify Data Source dropdown, choose ODBC Data.
- Select CData Zuora Sys from the Select ODBC Data Source window, and click Continue. Enter your Zuora credentials and click OK.
- In the Specify ODBC SQL Query dialog, enter the SQL query in the SQL text editor to import the desired Zuora data.
- Alternatively, select Query Builder to open the SQL Query Builder window. Choose the target table from the Tables section and relevant columns from the Columns section. Click Insert into SQL Query after each selection to auto-generate the query. You can also manually edit the query using WHERE and ORDER BY clauses or the designated tabs. Click OK to finalize the query.
- Click OK.
- In the Specify import order option, click Specify and enter the Zuora credentials.
- In the Specify Import Order window, define the import order for the target fields you added earlier. Select Add between the source and target fields to insert the Zuora data as new records in the table. Click Import.
- The script now appears in the workspace. Click Run to execute the script and process the import.
- FileMaker imports the Zuora data as a table.














Update or Replace Imported Zuora data Using a Script
After importing the Zuora data into FileMaker, use scripts to update or replace any changes made in Zuora by following this process:
- Go back to the Script Workspace by following the steps mentioned in the earlier section.
- Select the existing script, click the settings button, choose Specify under Specify Import Order, and re-enter the Zuora credentials to authenticate.
- In the Specify Import Order window, choose Update between source and target to update the imported Zuora data. This updates the target's found set with Zuora data values from selected fields when the match fields have the same values. You must define at least one match field in the mapping and select the checkbox Add remaining data as new records. Click Import.
- Alternatively, choose the Replace option instead of Update, based on your use case. This replaces the selected fields in the target's found set with Zuora data in the current record order. Click Import.
- FileMaker adds the script to the workspace. Click Run to execute the script and process the import query.
- FileMaker imports the updated or replaced Zuora data as a table.




Get Started Today
Download a free 30-day trial of CData ODBC Driver for Zuora to integrate Zuora data into Claris FileMaker and work with Zuora data in your FileMaker applications.
Reach out to our Support Team if you have any questions.