IT|EN
PAC SOFTWARE DOCS

PAC Taxonomy Bridge for WooCommerce

Technical documentation for real-time WooCommerce product taxonomy notifications to Claris FileMaker through the FileMaker Data API.

Free 1.0.4 · Professional settings verified on 1.0.1 · Updated October 2026

WooCommerce taxonomy event

PAC Taxonomy Bridge

FileMaker Data API

FileMaker workflow

1. Overview

PAC Taxonomy Bridge for WooCommerce notifies Claris FileMaker when supported WooCommerce taxonomy objects are created, updated or deleted. It covers product categories, global product attributes and the terms used as values of global attributes.

Free uses one FileMaker database, layout and script for all three scopes. The script receives compact JSON containing the WooCommerce object ID and taxonomy scope, such as {“id”:37,”ambito”:”categoria”}.

Professional shares one connection, database and layout, then selects a dedicated Category, Attribute or Attribute Value script automatically. It also adds licensed delivery controls, retries, custom certificate verification and diagnostics.

FileMaker remains in control.

The bridge calls your FileMaker script. It does not create tables, map fields or impose a record structure.

2. Key benefits

Real-time notifications

Send supported category, global attribute and attribute-value changes when they occur.

Compact Free parameter

Receive the object ID and scope, then retrieve only the data your workflow needs.

Scope-specific scripts

Route the three scopes to dedicated FileMaker scripts with Professional.

Direct integration

Connect WordPress to the FileMaker Data API without external synchronization middleware.

3. How it works

PAC Taxonomy Bridge listens for supported WooCommerce taxonomy events and executes the configured FileMaker script.

WooCommerce

Fires a supported taxonomy create, update or delete hook.

Bridge

Builds the notification and identifies the scope.

FileMaker Data API

Authenticates and runs the target script in the configured layout context.

FileMaker

Reads Get ( ScriptParameter ) and runs the integration workflow.

Typical flow:
  1. Fires a supported taxonomy create, update or delete hook.
  2. Builds the notification and identifies the scope.
  3. Authenticates and runs the target script in the configured layout context.
  4. Reads Get ( ScriptParameter ) and runs the integration workflow.

You remain in control.

Free builds id and ambito JSON and uses one script. Professional uses the shared connection and selects the scope-specific script. FileMaker controls retrieval, record matching and the final business outcome.

4. Requirements

To use PAC Taxonomy Bridge for WooCommerce, confirm the following requirements:

WordPress: Version 6.4 or later with PHP 7.4 or later.

WooCommerce: Installed and active. The public package does not declare a minimum WooCommerce version.

Encryption: PHP Sodium or OpenSSL AES-256-GCM support for saved-password encryption.

FileMaker Server: Data API enabled, hosted database reachable over HTTPS and an account with fmrest plus the required file, layout and script access.

Receiving script: A FileMaker script that understands the installed edition’s parameter contract.

Professional scheduler: A functioning scheduler for background delivery and retries; the public description names Action Scheduler.

The sources do not declare a minimum FileMaker Server version. Confirm the selected Data API version against the real environment.

5. Installation

Install PAC Taxonomy Bridge, configure the FileMaker destination and validate the full path before enabling live notifications.

1

Obtain the plugin

Install Free from WordPress.org or the entitled Professional package.

2

Activate

Activate it while WooCommerce is active.

3

Open settings

Go to WooCommerce > Settings > Integrations.

4

Configure FileMaker

Enter the shared connection and destination values.

3

Activate

the plugin

5

Test

Validate authentication, script execution and taxonomy delivery.

Tests execute a real FileMaker script. Use a controlled destination and keep automatic delivery disabled until validation is complete.

6. Configuration

Open WooCommerce > Settings > Integrations > PAC Taxonomy Bridge for WooCommerce.

Where to find the settings

WooCommerce

Settings

Integrations

PAC Taxonomy Bridge for WooCommerce

Configure the shared FileMaker connection, the FileMaker destination, the supported taxonomy scopes, Professional delivery controls, certificate verification and diagnostics.

Free uses one Database, Layout and Script for every supported scope. Professional shares Database and Layout and selects a dedicated script for Category, Attribute or Attribute Value.

6.1 Connection settings

Enable controls automatic notifications. FileMaker server is the HTTPS base URL without /fmi/data/ or a trailing slash. Data API version offers v1, v2 and vLatest and defaults to v1.

The values below are examples. Use your own FileMaker Server connection details.

Connection settings

Enable

On

On by default in Free. Test controls remain available while automatic delivery is off.

FileMaker Server

https://fm.example.com

HTTPS base URL, no /fmi/data/ suffix.

Data API version

v1

Available: v1, v2, vLatest.

Username / password

Dedicated least-privilege account

Leaving the password blank keeps the saved encrypted value.

HTTP timeout

30 seconds

Accepts 5–120 seconds.

6.2 FileMaker destinations

Free destination

One script reads both id and ambito.

Category script

Default shown: taxonomy_category.

Attribute script

Default shown: taxonomy_attribute.

Attribute Value script

Default shown: taxonomy_attribute_value.

FileMaker remains in control.

In Professional, the correct script is selected automatically from the taxonomy scope. Database and Layout remain shared.

6.3 Supported events and script.param

Supported create, update and delete hooks identify the WooCommerce object and taxonomy scope.

Product category

Create, update and delete hooks. ambito: categoria.

Global attribute

Create, update and delete WooCommerce attribute hooks. ambito: attributo.

Global attribute value

Create, update and delete terms from global pa_ taxonomies. ambito: valore_attributo.

Local attributes

Attributes stored only on an individual product are outside this event set.

FileMaker remains in control.

Free examples: {“id”:37,”ambito”:”categoria”}, {“id”:4,”ambito”:”attributo”} and {“id”:91,”ambito”:”valore_attributo”}. Free does not include the operation or object fields.

6.4 Professional delivery and retries

Professional adds licensed delivery controls and retry behavior.

Delivery mode

The verified Professional interface shows Immediate.

Automatic retries

The verified Professional interface shows 3.

Payload mode

Diagnostics identify the Professional mode as event_json.

Confirmed boundary

Exact event_json fields, retry timing and retryable error classes are not published because the available sources do not confirm them.

FileMaker processing should tolerate delayed and repeated delivery.

6.5 Certificate verification

Free verifies the FileMaker certificate with an available CA bundle. Professional adds a Certificate verification selector and a Custom CA certificate field. The verified default is On — verify with public CA bundle.

Certificate policy

Keep verification enabled in production. Use a custom CA only when the FileMaker Server chain requires it, and never publish private certificate material.

6.6 Diagnostics and testing

Use the built-in tests to isolate connection, authentication, script and end-to-end problems.

Last communication

Shows the latest recorded result and includes Clear status.

Connection test

Authenticates without executing a FileMaker script.

Script test · Free

Passes a chosen parameter directly to script.param and reports Data API and script results.

End-to-end taxonomy test

Uses a positive WooCommerce ID and Category, Attribute or Attribute Value scope.

Professional diagnostics

Reports runtime versions, encryption backend, connection targets, scripts, delivery mode, payload mode and last status.

Cleanup on uninstall

Optional and off by default; removes plugin settings and runtime data when WordPress deletes the plugin.

FileMaker remains in control.

Recommended order: test connection, test the script, send a known taxonomy ID and scope, verify the FileMaker result, save, enable, then test controlled live changes.

7. Free vs Professional

Choose the edition that matches the workflow. Both keep the business logic inside FileMaker.

Capability
Free
Professional
Three taxonomy scopes
✓
✓
Create/update/delete hooks
✓
✓
Direct FileMaker Data API connection
✓
✓
One shared database and layout
✓
✓
Compact id + ambito JSON
✓
—
Dedicated script per scope
—
✓
Automatic retries
—
✓
Custom verification / custom CA
—
✓
Advanced diagnostics
—
✓

Professional payload fields beyond the confirmed event_json mode are intentionally not asserted.

8. Professional features

Professional adds scope-specific routing, delivery controls, retries, certificate options, licensing and diagnostics.

Professional does not define the FileMaker schema or synchronize changes back to WooCommerce.

Scope-specific scripts

Automatically select Category, Attribute or Attribute Value script.

Delivery controls

Immediate delivery is verified in the current settings.

Automatic retries

Retry failed deliveries using Professional controls.

Custom CA support

Validate an internal certificate authority.

License status

Freemius authorizes Professional runtime features for the installation.

Advanced diagnostics

Inspect additional connection and delivery information.

9. FileMaker side implementation

Prepare the FileMaker entry point that receives and validates taxonomy notifications.

The bridge executes your script through the FileMaker Data API. Your solution remains responsible for validation, record matching and business logic.

1

Integration account

Grant only the required Data API privileges.

2

Target layout

Provide a stable context for script execution.

3

Read the parameter

Parse and validate JSON from Get ( ScriptParameter ).

4

Resolve scope

Accept only categoria, attributo or valore_attributo.

5

Apply logic

Match records by stable WooCommerce IDs and make writes repeat-safe.

6

Return a result

Use FileMaker script results and non-zero script errors deliberately.

Implementation note

Do not infer create, update or delete from the Free parameter. A deleted object may no longer be retrievable, so retain enough FileMaker-side identity to reconcile it from ID and scope.

10. Real-world example

Global attribute value renamed

A WooCommerce administrator renames a global attribute value. The bridge identifies its ID and valore_attributo scope. Free calls the shared script with compact JSON; Professional routes the event to the configured Attribute Value script. FileMaker validates the input, matches its stored WooCommerce ID and applies the business workflow.

Global attribute value renamed

A WooCommerce administrator renames a global attribute value.

Bridge identifies scope

The bridge identifies its ID and valore_attributo scope.

Free delivery

Free calls the shared script with compact JSON.

Professional delivery

Professional routes the event to the configured Attribute Value script.

FileMaker workflow

FileMaker validates the input, matches its stored WooCommerce ID and applies the business workflow.

This is an example architecture, not automatic field mapping supplied by the plugin.

11. Security and reliability

Protect the direct WordPress-to-FileMaker route with HTTPS, least privilege and repeat-safe processing.

Delivery goes to the configured FileMaker Server; PAC Age does not proxy taxonomy data.

HTTPS

Use a certificate trusted by the selected verification policy.

Least privilege

Restrict the FileMaker API account to required files, layouts and scripts.

Encrypted password

Free uses libsodium or OpenSSL AES-256-GCM with a key derived from the WordPress authentication salt.

Response validation

Free validates HTTP status, Data API codes and scriptError and attempts logout.

Repeat safety

Make FileMaker writes idempotent for later events and Professional retries.

Direct route

Delivery goes to the configured FileMaker Server; PAC Age does not proxy taxonomy data.

12. Troubleshooting

Use these checks to isolate common connection, certificate, authentication, script and taxonomy-delivery problems.

Check the HTTPS URL, DNS, network access, Data API and hosted database.

Check hostname, expiry and trust chain; verify the saved custom CA in Professional.

Confirm credentials, fmrest and file, layout and script privileges.

Verify the exact database, layout and script names and inspect the test result.

Check Enable and confirm the object belongs to a supported global taxonomy scope.

Use stored ID and scope to archive or reconcile without requiring a successful lookup.

The test validates a positive ID and supported scope; use a known object and verify FileMaker.

The Free lock prevents concurrent sends only. Keep FileMaker processing repeat-safe.

13. FAQ

Product categories, global product attributes and terms in global attribute taxonomies.

No dedicated event is documented for attributes stored only on one product.

JSON containing id and ambito.

No. Create, update and delete hooks use the same compact contract.

Professional uses different scripts but the verified settings share one database and layout.

No external middleware or catalog polling is required; Professional scheduling must still function.

The documented direction is WooCommerce-to-FileMaker notification.

No. It uses the FileMaker Data API.

14. Changelog

Version 1.0.4

WordPress.org translation-handling and documentation updates; no functional taxonomy-delivery change.

Version 1.0.3

Detailed FileMaker test diagnostics and improved Free end-to-end testing.

Professional settings reference 1.0.1

Shared connection, three scripts, delivery mode, retries, certificate controls, tests and diagnostics.

Version 1.0.1

Help tooltips, select fix, aligned field sizing and improved Italian admin descriptions.

Version 1.0.0

Initial release.

Explore the PAC WooCommerce bridge family and related integration tools.

PAC Product Bridge for WooCommerce

Notify FileMaker about product and variation lifecycle changes.

PAC Order Bridge for WooCommerce

Connect supported WooCommerce order events to FileMaker.

PAC WooCommerce Bridge Suite

Explore the PAC bridge family for taxonomy, product and order integrations.

Need help?

Use diagnostics and tests first. For a custom FileMaker workflow, contact PAC Age.

PAC Age support

PAC Taxonomy Bridge for WooCommerce · Technical documentation

Item #1