fmnfc

FileMaker NFC UID plug-in

fmnfc

Read an NFC card UID from a FileMaker script.

Set Variable [ $uid ; Value: NFC_ReadUID( waitMilliseconds ) ]

fmnfc is a small FileMaker plug-in for direct PC/SC NFC reader calls.
It reads the UID; your FileMaker solution decides what to do next.

No purchase required. The current sample package is a placeholder for flow testing.

Operational note

A prototype version of this plug-in has been in use at a hospital since June 2024.

It is installed on 100+ machines and supports FileMaker login workflows for staff health-check questionnaires and doctors who work across multiple wards.

Use cases

Use the UID where FileMaker already works.

The plug-in stays narrow: read the card UID and return it to FileMaker. That keeps the business rules in your own solution.

Attendance

Start staff clock-in and clock-out scripts from a card tap.

Reception

Look up visitors, members, or patients from a known card UID.

Asset tracking

Bind cards or tags to equipment records and movement logs.

Access workflows

Use UID lookup as the first step in FileMaker-controlled access logic.

FileMaker automation

Trigger scripts, layouts, and record updates from local NFC reads.

How it works

A simple local chain.

01

Connect a reader

Use a PC/SC-compatible NFC reader on Windows or Apple Silicon Mac.

02

Call the plug-in

Your FileMaker script asks fmnfc to wait for a card and read the UID.

03

Use the UID

FileMaker receives the UID and applies your lookup, logging, or workflow logic.

04

Keep licensing local

A signed fmnfc-license.json file sits next to the plug-in in the Extensions folder.

Features

Narrow on purpose.

fmnfc is not trying to become an access-control platform. It gives FileMaker one practical NFC function and leaves the workflow design to you.

Windows support with PC/SC readers
macOS support for Apple Silicon Macs
FileMaker scripting friendly UID handoff
Signed local JSON license file
Standard fmnfc-license.json file name
Plug-in adjacent license placement
One machine, one license
No per-solution licensing mode

Who I am

Built by a FileMaker developer for a narrow edge case.

I work in healthcare IT in Japan and build FileMaker tools for practical business workflows. fmnfc comes from a real FileMaker environment where NFC card UID reading was needed to simplify local login flows.

The product stays intentionally small: read the UID reliably, return it to FileMaker, and let each solution handle its own business logic.

Pricing

One annual license.

For one machine running the fmnfc plug-in. The signed license file sits next to the plug-in and is renewed annually.

$199/year

Included

  • One machine license
  • Signed license JSON
  • Windows and Apple Silicon Mac support
  • Sample download access
Buy now

Annual license for one machine.

License integrity

Simple local license file.

The license is delivered as a signed JSON file. Place fmnfc-license.json next to the plug-in, restart FileMaker, and the plug-in validates the license locally.

  • Standard file name: fmnfc-license.json
  • Placed next to the FileMaker plug-in by the user
  • Validated locally by the plug-in
  • No manual key paste inside FileMaker

FAQ

Practical details before you test.

Which NFC readers are compatible?

Use PC/SC-compatible NFC readers. Exact reader recommendations will be tightened as real launch feedback comes in.

Which FileMaker versions are supported?

The plug-in is designed for modern local FileMaker workflows. Version-specific support notes will be finalized with the production sample.

What platforms are supported?

Windows is supported. macOS support is for Apple Silicon Macs only. Intel Macs are not a supported target.

How many machines does one license cover?

One license covers one machine. Per-solution licensing is not supported.

Where does the license file go?

Use the standard file name fmnfc-license.json and place it next to the plug-in in the FileMaker Extensions folder.

What is included in the sample?

The current downloadable sample is a placeholder ZIP containing HelloWorld.md. It is available for flow testing before the production sample is published after domain bind.

Do I need a license to download the sample?

No. The sample download page is available without purchase.

How do I get support?

Use the contact address published with the launch materials. During early launch, support policy will stay lightweight and practical.

Next step

Try the sample first.

Download the sample package, confirm the FileMaker flow, then license the machine that needs it.