If you use FileMaker for quoting or customer management, you can now hook it into Infigo using a small set of API endpoints. This isn’t a packaged “click-to-connect” integration – it’s an API-driven workflow that your technical team (or our team) can wire up to match your process.
The goal:
let FileMaker handle quoting and customer data, while Infigo handles storefronts, orders and production – with both sides staying in sync.
What this feature actually does
We’ve added a set of API endpoints (via a Megascript configuration) that let an external system like FileMaker:
-
Create or update customers in Infigo
-
Create quotes in Infigo based on FileMaker jobs
-
Fetch orders and outputs from Infigo that are marked as “ready to sync”
There’s no new UI in Infigo for this and no “FileMaker” plugin to click on.
Everything happens through API calls and a bit of configuration on our side.
Typical use case
A common pattern looks like this:
-
Your team creates and manages quotes in FileMaker.
-
When a quote is approved, FileMaker calls Infigo’s API to:
-
create or update the customer in Infigo, and
-
create a matching Infigo quote or job with the right product, quantity and pricing.
-
The customer can then:
-
Once the order is placed, Infigo tags it as “to notify”, so:
-
FileMaker can pull all orders that need syncing,
-
read the order details via the API,
-
and update its own records.
The same approach works with other external systems too – FileMaker is just the example we built this against.
How it works (high level)
There are two moving parts:
1. Event-based tagging inside Infigo
When outputs or orders are created in Infigo, a Megascript can automatically tag them (for example with a value like to-notify on a custom tag field). That tag is your signal that:
“This item needs to be pulled into FileMaker (or another system) via the API.”
Once your external system has processed the order, it can call another endpoint to clear that tag.
2. API endpoints your system can call
We provide API endpoints that allow your system to:
-
Get customers by external ID (your FileMaker ID) or fetch customers who placed orders but don’t yet have an external ID.
-
Create or update customers in Infigo (for example when a new customer is created in FileMaker).
-
Create or update quotes in Infigo using product, quantity, attribute and price data passed from FileMaker.
-
Fetch orders marked as “to notify”, so your system knows which Infigo orders need to be imported.
-
Clear or update orders once they’ve been processed on your side.
All of this is done via POST/GET requests to Infigo – there’s no manual import screen involved.
What you’ll need on your side
Because this is an API-only setup, you’ll need:
You do not need to build a full integration UI – the endpoints are designed for straightforward machine-to-machine calls.
How to get this enabled
This feature requires some configuration on the Infigo side (Megascript setup, tags, plugin configuration). It isn’t turned on by default and isn’t something you’ll see in the standard admin screens.
If you’re interested in using this:
-
Contact Infigo Support or your account manager.
Let them know you’d like to use the FileMaker-style API workflow (or a similar external system sync).
-
Our team can:
-
confirm whether this approach fits your setup,
-
enable and configure the Megascript instance for your storefront, and
-
provide the API endpoint details and payload examples your developers will need.
-
Your technical team can then:
-
wire up FileMaker (or your external system) to call those endpoints,
-
test the end-to-end flow for customers, quotes and orders,
-
and refine it to match your internal workflow.
Summary
-
This is not a ready-made “FileMaker integration” in the UI.
-
It is a set of API endpoints and scripts that make it easier to sync:
-
Everything runs via API calls; you’ll need a bit of development work plus a short setup phase with the Infigo team.
If you’d like to explore this for your workflow, just reach out to Support and we can help you plan and enable it.