[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fZ5ns9OK9B2Zj39sJ48BfzHQ_yn2ksIDZ_7UR_R6kAGM":3,"$fTyddNhGRWnfE--U1JMDT07HukW7jyZ56BwOTC1YVXeQ":783},{"items":4},[5,29,50,63,75,95,108,121,134,146,165,178,191,205,217,230,243,255,269,282,294,306,319,333,346,358,370,383,395,407,420,432,443,455,467,482,495,506,520,531,543,554,566,576,587,598,610,622,633,645,656,668,679,688,702,713,726,739,751,761,773],{"id":6,"idKnowledge":7,"idDomain":8,"idCluster":9,"slug":10,"title":11,"description":12,"bodyMarkdown":13,"bodyHtml":14,"author":15,"date":16,"createdAt":17,"topics":18,"image":27,"hasDownload":28,"fileName":15,"youtubeId":27},"420","5D194478-0616-4642-8BFC-D0577CBDA297","8FB77283-8FB1-A247-851E-65269E8983E0","3434E0DD-DD9C-7048-9B98-536F3C5E867E","how-to-prevent-dependency-on-one-supplier-or-developer","How to prevent dependency on one supplier or developer","Relying on a single developer for your business-critical software is a serious risk. Here's how IT specialists can regain control and build resilience.","Your core business system runs on a custom application, and exactly one person truly understands it. That developer built it, knows every workaround, and holds the keys — and if they leave, get sick, or simply raise their rates, you have a serious problem. This article gives IT specialists a concrete, actionable plan to identify that dependency, reduce it structurally, and make sure it never sneaks back in.\n\n## Why is sole-developer dependency so dangerous?\n\nIt rarely feels dangerous — until it is. The developer is responsive, the system works, and there's no obvious reason to change anything. Then one day they go quiet. Or they deliver a quote for a small change that's three times what you expected, because they know you have no alternative. Or they retire and hand over a system with no documentation, no test environment, and no one else who can read the code.\n\nThis is called **vendor lock-in at the human level** — and it's more common in custom software environments than most IT managers want to admit. A survey-level observation from the field: organizations running FileMaker, low-code ERP, or legacy custom databases are especially exposed, because these platforms have smaller developer communities and the original builder often \"grew\" the system organically over years, carrying all the institutional knowledge in their head.\n\n\u003Cimg src=\"\u002Fapi\u002Fknowledge\u002Finline-image\u002F3?w=700&f=webp\" alt=\"Single developer holding keys to a complex system, team locked out\" loading=\"lazy\" class=\"w-full sm:w-1\u002F3 sm:float-left sm:mr-7 mb-5 rounded-2xl border border-[#E8E8ED] bg-[#F5F5F7]\" \u002F>\n\n## How do you know if you're already dependent?\n\nAnswer these questions honestly:\n\n- Can anyone on your team — or any other developer you could hire tomorrow — open the system and understand its structure without a guided tour?\n- Is there written documentation of the data model, business logic, and integration points?\n- Do you have access to all credentials: server, database, hosting, licensing, third-party API keys?\n- Have you received a source code backup in the last 90 days that you have actually tested?\n- Could you get a meaningful quote from a second developer without your current one being involved?\n\nIf you answered \"no\" to two or more of these, you are dependent. Not at risk of becoming dependent — already dependent.\n\n## What are the structural causes of this dependency?\n\nDependency doesn't usually happen because of bad intentions. It happens because:\n\n1. **The system grew without governance.** What started as a small database became a mission-critical application, but the process of building it was never formalized. No handover documentation, no architecture decisions recorded.\n2. **Access was never centralized.** The developer manages the hosting, holds the FileMaker license, controls the server credentials. Convenience became control.\n3. **There was no second opinion.** Because the developer was trusted and available, there was never a reason to bring in anyone else. Over time, internal knowledge atrophied.\n4. **Contracts didn't cover IP and escrow.** The code was written for you but ownership was never explicitly transferred, or a source code escrow was never set up.\n\n## How do you reduce the dependency — step by step?\n\n### Step 1: Conduct a dependency audit\n\nBefore you can fix the problem, you need to map it. Spend one focused session listing:\n\n- Every system the developer has built or maintains\n- Every credential or license they hold on your behalf\n- Every integration (APIs, data exports, email connectors) they manage\n- What documentation currently exists and where it lives\n\nThis audit is uncomfortable but essential. It shows you the actual blast radius if the relationship ends tomorrow.\n\n### Step 2: Reclaim all credentials and licenses\n\nThis is non-negotiable and should happen before anything else. Your hosting account, your FileMaker license, your domain, your API keys — all of these should be registered to your organization, not to an individual developer or their agency. If they are not, request the transfer immediately. A professional developer will not resist this.\n\n### Step 3: Demand — and fund — living documentation\n\nDocumentation is not a luxury. Make it a contractual deliverable. At minimum you need:\n\n- A data model overview (what tables exist, what they store, how they relate)\n- A list of all scripts, automations, and scheduled processes with a plain-language description of what each does\n- A description of every external integration and what breaks if it fails\n- A deployment and restore procedure: if the server dies tonight, what are the exact steps to restore service?\n\nIf your current developer pushes back on documenting their own work, that resistance is itself a red flag worth taking seriously.\n\n### Step 4: Introduce a second developer — now, not when you need one\n\nThe worst time to find a backup developer is during a crisis. Introduce a second developer while the system is stable. Give them a small, real task — a report, a minor UI change, a new data export. This does three things: it tests whether the documentation is actually sufficient for an outsider to work from, it builds a relationship before there's urgency, and it sends a quiet signal that you are not captive.\n\n\u003Cimg src=\"\u002Fapi\u002Fknowledge\u002Finline-image\u002F2?w=700&f=webp\" alt=\"Two developers reviewing system documentation together, IT manager observing\" loading=\"lazy\" class=\"w-full sm:w-1\u002F3 sm:float-right sm:ml-7 mb-5 rounded-2xl border border-[#E8E8ED] bg-[#F5F5F7]\" \u002F>\n\n### Step 5: Establish a source code escrow or version control handover\n\nIf your custom software is business-critical, its source code should be in a version-controlled repository (Git is the standard) that *you* own. Every release should be committed. If a formal escrow isn't feasible, at minimum agree contractually that you receive a full source export at every major release and that you test it against a restore procedure.\n\n### Step 6: Write dependency prevention into future contracts\n\nOnce you've reduced your current exposure, lock in the right conditions for future work:\n\n- **IP ownership clause**: all code written for you is your intellectual property upon payment\n- **Documentation deliverable**: documentation is part of the definition of \"done\"\n- **Access policy**: all credentials must be held in your organization's name\n- **Handover clause**: at contract end, the developer is obligated to support a structured handover period\n- **Non-exclusivity**: you explicitly retain the right to engage other developers on the same system\n\n## What if the developer is also your platform vendor?\n\nSome organizations work with a single firm that both builds and hosts their custom software — a FileMaker partner, for example, who also manages the server and holds the license. This compounds the dependency. In this case, the same principles apply, but you need to be explicit: separate the *platform licensing* from the *development relationship* from the *hosting relationship*. These are three distinct things and can be sourced from three distinct providers if needed.\n\nAsking your vendor to help you reduce dependency on them is an awkward conversation — but a trustworthy vendor will welcome it, because it signals a mature client relationship built on choice rather than captivity.\n\n## FAQ\n\n**What if I ask for documentation and my developer quotes me a huge amount of time for it?**\nThat quote is telling you something important: the system is more complex and less structured than you thought, *and* no one has been maintaining a knowledge base. Negotiate a phased documentation plan and treat it as essential infrastructure investment, not optional overhead.\n\n**Is it realistic to have two developers who both know our system?**\nYes — and the goal isn't that both know every line of code. The goal is that a competent second developer can pick up the system, orient themselves using documentation, and make a change without a guided tour. That's the bar to aim for.\n\n**What's the minimum viable version of this if we have no budget right now?**\nFocus on three things first: reclaim all credentials and licenses, get a tested source code backup, and have one honest conversation with a second developer to find out if your system is legible to an outsider. Those three steps cost almost nothing and reveal everything.\n\n**Our developer has been with us for ten years and is completely trustworthy. Do we still need to do this?**\nYes — because this isn't about trust. It's about continuity. Your developer could fall ill, decide to retire, or simply move on. The risk isn't that they'll act badly; it's that the knowledge leaves with them. Protecting against that is fair to both sides.\n\n## A short checklist to get started this week\n\n- [ ] List every system and credential your developer currently holds\n- [ ] Confirm that all licenses and hosting accounts are in your organization's name\n- [ ] Request a current source code export and test it against a restore procedure\n- [ ] Ask your developer to provide or update system documentation\n- [ ] Identify and brief a second developer on a small, real task\n- [ ] Review your current contract for IP ownership and handover clauses\n\n---\n\nDependency on a single developer is not a sign that something went wrong — it's a sign that something worked, for a long time, without enough governance around it. The good news is that it's entirely reversible with structured steps. Start with the audit, reclaim your access, and get a second set of eyes on the system before you need them urgently.","\u003Cp>Your core business system runs on a custom application, and exactly one person truly understands it. That developer built it, knows every workaround, and holds the keys — and if they leave, get sick, or simply raise their rates, you have a serious problem. This article gives IT specialists a concrete, actionable plan to identify that dependency, reduce it structurally, and make sure it never sneaks back in.\u003C\u002Fp>\n\u003Ch2>Why is sole-developer dependency so dangerous?\u003C\u002Fh2>\n\u003Cp>It rarely feels dangerous — until it is. The developer is responsive, the system works, and there's no obvious reason to change anything. Then one day they go quiet. Or they deliver a quote for a small change that's three times what you expected, because they know you have no alternative. Or they retire and hand over a system with no documentation, no test environment, and no one else who can read the code.\u003C\u002Fp>\n\u003Cp>This is called \u003Cstrong>vendor lock-in at the human level\u003C\u002Fstrong> — and it's more common in custom software environments than most IT managers want to admit. A survey-level observation from the field: organizations running FileMaker, low-code ERP, or legacy custom databases are especially exposed, because these platforms have smaller developer communities and the original builder often "grew" the system organically over years, carrying all the institutional knowledge in their head.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fapi\u002Fknowledge\u002Finline-image\u002F3?w=700&f=webp\" alt=\"Single developer holding keys to a complex system, team locked out\" loading=\"lazy\" class=\"w-full sm:w-1\u002F3 sm:float-left sm:mr-7 mb-5 rounded-2xl border border-[#E8E8ED] bg-[#F5F5F7]\" \u002F>\n\n\u003Ch2>How do you know if you're already dependent?\u003C\u002Fh2>\n\u003Cp>Answer these questions honestly:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Can anyone on your team — or any other developer you could hire tomorrow — open the system and understand its structure without a guided tour?\u003C\u002Fli>\n\u003Cli>Is there written documentation of the data model, business logic, and integration points?\u003C\u002Fli>\n\u003Cli>Do you have access to all credentials: server, database, hosting, licensing, third-party API keys?\u003C\u002Fli>\n\u003Cli>Have you received a source code backup in the last 90 days that you have actually tested?\u003C\u002Fli>\n\u003Cli>Could you get a meaningful quote from a second developer without your current one being involved?\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If you answered "no" to two or more of these, you are dependent. Not at risk of becoming dependent — already dependent.\u003C\u002Fp>\n\u003Ch2>What are the structural causes of this dependency?\u003C\u002Fh2>\n\u003Cp>Dependency doesn't usually happen because of bad intentions. It happens because:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>The system grew without governance.\u003C\u002Fstrong> What started as a small database became a mission-critical application, but the process of building it was never formalized. No handover documentation, no architecture decisions recorded.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Access was never centralized.\u003C\u002Fstrong> The developer manages the hosting, holds the FileMaker license, controls the server credentials. Convenience became control.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>There was no second opinion.\u003C\u002Fstrong> Because the developer was trusted and available, there was never a reason to bring in anyone else. Over time, internal knowledge atrophied.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Contracts didn't cover IP and escrow.\u003C\u002Fstrong> The code was written for you but ownership was never explicitly transferred, or a source code escrow was never set up.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2>How do you reduce the dependency — step by step?\u003C\u002Fh2>\n\u003Ch3>Step 1: Conduct a dependency audit\u003C\u002Fh3>\n\u003Cp>Before you can fix the problem, you need to map it. Spend one focused session listing:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Every system the developer has built or maintains\u003C\u002Fli>\n\u003Cli>Every credential or license they hold on your behalf\u003C\u002Fli>\n\u003Cli>Every integration (APIs, data exports, email connectors) they manage\u003C\u002Fli>\n\u003Cli>What documentation currently exists and where it lives\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This audit is uncomfortable but essential. It shows you the actual blast radius if the relationship ends tomorrow.\u003C\u002Fp>\n\u003Ch3>Step 2: Reclaim all credentials and licenses\u003C\u002Fh3>\n\u003Cp>This is non-negotiable and should happen before anything else. Your hosting account, your FileMaker license, your domain, your API keys — all of these should be registered to your organization, not to an individual developer or their agency. If they are not, request the transfer immediately. A professional developer will not resist this.\u003C\u002Fp>\n\u003Ch3>Step 3: Demand — and fund — living documentation\u003C\u002Fh3>\n\u003Cp>Documentation is not a luxury. Make it a contractual deliverable. At minimum you need:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A data model overview (what tables exist, what they store, how they relate)\u003C\u002Fli>\n\u003Cli>A list of all scripts, automations, and scheduled processes with a plain-language description of what each does\u003C\u002Fli>\n\u003Cli>A description of every external integration and what breaks if it fails\u003C\u002Fli>\n\u003Cli>A deployment and restore procedure: if the server dies tonight, what are the exact steps to restore service?\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If your current developer pushes back on documenting their own work, that resistance is itself a red flag worth taking seriously.\u003C\u002Fp>\n\u003Ch3>Step 4: Introduce a second developer — now, not when you need one\u003C\u002Fh3>\n\u003Cp>The worst time to find a backup developer is during a crisis. Introduce a second developer while the system is stable. Give them a small, real task — a report, a minor UI change, a new data export. This does three things: it tests whether the documentation is actually sufficient for an outsider to work from, it builds a relationship before there's urgency, and it sends a quiet signal that you are not captive.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fapi\u002Fknowledge\u002Finline-image\u002F2?w=700&f=webp\" alt=\"Two developers reviewing system documentation together, IT manager observing\" loading=\"lazy\" class=\"w-full sm:w-1\u002F3 sm:float-right sm:ml-7 mb-5 rounded-2xl border border-[#E8E8ED] bg-[#F5F5F7]\" \u002F>\n\n\u003Ch3>Step 5: Establish a source code escrow or version control handover\u003C\u002Fh3>\n\u003Cp>If your custom software is business-critical, its source code should be in a version-controlled repository (Git is the standard) that \u003Cem>you\u003C\u002Fem> own. Every release should be committed. If a formal escrow isn't feasible, at minimum agree contractually that you receive a full source export at every major release and that you test it against a restore procedure.\u003C\u002Fp>\n\u003Ch3>Step 6: Write dependency prevention into future contracts\u003C\u002Fh3>\n\u003Cp>Once you've reduced your current exposure, lock in the right conditions for future work:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>IP ownership clause\u003C\u002Fstrong>: all code written for you is your intellectual property upon payment\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Documentation deliverable\u003C\u002Fstrong>: documentation is part of the definition of "done"\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Access policy\u003C\u002Fstrong>: all credentials must be held in your organization's name\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Handover clause\u003C\u002Fstrong>: at contract end, the developer is obligated to support a structured handover period\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Non-exclusivity\u003C\u002Fstrong>: you explicitly retain the right to engage other developers on the same system\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>What if the developer is also your platform vendor?\u003C\u002Fh2>\n\u003Cp>Some organizations work with a single firm that both builds and hosts their custom software — a FileMaker partner, for example, who also manages the server and holds the license. This compounds the dependency. In this case, the same principles apply, but you need to be explicit: separate the \u003Cem>platform licensing\u003C\u002Fem> from the \u003Cem>development relationship\u003C\u002Fem> from the \u003Cem>hosting relationship\u003C\u002Fem>. These are three distinct things and can be sourced from three distinct providers if needed.\u003C\u002Fp>\n\u003Cp>Asking your vendor to help you reduce dependency on them is an awkward conversation — but a trustworthy vendor will welcome it, because it signals a mature client relationship built on choice rather than captivity.\u003C\u002Fp>\n\u003Ch2>FAQ\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>What if I ask for documentation and my developer quotes me a huge amount of time for it?\u003C\u002Fstrong>\nThat quote is telling you something important: the system is more complex and less structured than you thought, \u003Cem>and\u003C\u002Fem> no one has been maintaining a knowledge base. Negotiate a phased documentation plan and treat it as essential infrastructure investment, not optional overhead.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Is it realistic to have two developers who both know our system?\u003C\u002Fstrong>\nYes — and the goal isn't that both know every line of code. The goal is that a competent second developer can pick up the system, orient themselves using documentation, and make a change without a guided tour. That's the bar to aim for.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What's the minimum viable version of this if we have no budget right now?\u003C\u002Fstrong>\nFocus on three things first: reclaim all credentials and licenses, get a tested source code backup, and have one honest conversation with a second developer to find out if your system is legible to an outsider. Those three steps cost almost nothing and reveal everything.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Our developer has been with us for ten years and is completely trustworthy. Do we still need to do this?\u003C\u002Fstrong>\nYes — because this isn't about trust. It's about continuity. Your developer could fall ill, decide to retire, or simply move on. The risk isn't that they'll act badly; it's that the knowledge leaves with them. Protecting against that is fair to both sides.\u003C\u002Fp>\n\u003Ch2>A short checklist to get started this week\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> List every system and credential your developer currently holds\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> Confirm that all licenses and hosting accounts are in your organization's name\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> Request a current source code export and test it against a restore procedure\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> Ask your developer to provide or update system documentation\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> Identify and brief a second developer on a small, real task\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> Review your current contract for IP ownership and handover clauses\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Chr>\n\u003Cp>Dependency on a single developer is not a sign that something went wrong — it's a sign that something worked, for a long time, without enough governance around it. The good news is that it's entirely reversible with structured steps. Start with the audit, reclaim your access, and get a second set of eyes on the system before you need them urgently.\u003C\u002Fp>\n","","2026-07-24",1784901680000,[19,20,21,22,23,24,25,26],"IT governance","vendor lock-in","custom software","business continuity","FileMaker","developer dependency","software maintenance","IT risk management",null,false,{"id":30,"idKnowledge":31,"idDomain":32,"idCluster":33,"slug":34,"title":35,"description":36,"bodyMarkdown":37,"bodyHtml":38,"author":39,"date":16,"createdAt":40,"topics":41,"image":27,"hasDownload":28,"fileName":15,"youtubeId":27},"114","FD16FD71-F8F4-1245-88A1-ED22B79DDAD5","5D5F3733-6027-284B-BC54-3DAF4A98517A","C9A2E812-0A2C-FC46-929B-A19F9A440E05","eleven-signs-that-your-business-software-is-holding-the-organisation-back","Eleven signs that your business software is holding the organisation back","Spreadsheets, manual re-entry, no APIs — discover the eleven warning signs your business software is slowing growth, and what to do about it.","Your software was the right choice when you bought it. But the business has changed — new products, more staff, new sales channels — and somewhere along the way the system stopped being an engine and started being a brake. This article walks through eleven concrete signs that your current software is holding the organisation back, and what each one really means for your next step.\n\n\u003Cimg src=\"\u002Fapi\u002Fknowledge\u002Finline-image\u002F7?w=700&f=webp\" alt=\"business owner frustrated at screen surrounded by stacked spreadsheet printouts\" loading=\"lazy\" class=\"w-full sm:w-1\u002F3 sm:float-left sm:mr-7 mb-5 rounded-2xl border border-[#E8E8ED] bg-[#F5F5F7]\" \u002F>\n\n## 1. Your team runs the business in spreadsheets, not in the system\n\nThis is the most common sign, and the most dangerous one to normalise. When staff maintain a separate Excel file to track open orders, calculate margins, or manage a planning board — that file *is* the real system. The official software has become a glorified archive. The risk: the spreadsheet lives on one person's laptop, has no audit trail, and breaks the moment that person is on holiday.\n\nAsk yourself: if your most experienced operations person left tomorrow, would the business know where the real numbers are?\n\n## 2. The same data gets typed in more than once\n\nAn order comes in through your webshop. Someone copies it into the ERP. The logistics team re-enters the address into the shipping portal. The finance team keys the same order into the invoicing tool. That is one order, typed four times, by three different people, with three chances to introduce an error. Multiply that by 80 orders a day and you have a full-time job that exists purely because two systems don't talk to each other.\n\nManual re-entry is not a workflow — it is a symptom of missing integrations.\n\n## 3. There are no APIs, so every connection is a human being\n\nModern business runs on connected systems: a CRM, an ERP, an accounting package, a logistics platform, an e-commerce storefront. If your core system has no API — or has one nobody has ever used — then every data exchange between those systems depends on a person copying, pasting, exporting, and importing. That person becomes a single point of failure. And when volume grows, you don't automate — you hire another person to do the same manual job.\n\nAn API connector between your order management system and Exact Online, for example, can eliminate an entire category of daily manual work in a single integration.\n\n## 4. Management reports take days, not minutes\n\nIf producing the monthly management report requires your finance manager to spend two days pulling exports from three systems, stitching them together in Excel, and then manually formatting a PowerPoint — your software is not giving management the information it needs, when it needs it. Decisions get made on last month's data. Trends are spotted late. Opportunities are missed.\n\nA well-configured system should let a manager open a dashboard on a Monday morning and see last week's actuals without asking anyone for anything.\n\n## 5. You can't answer a simple operational question without digging\n\n\"How many units of product X do we have in stock right now, across all locations?\" If that question requires opening three screens, running an export, and cross-referencing a spreadsheet — the answer is: your system doesn't actually know. Real-time operational visibility is not a luxury; it is the foundation of every good decision your team makes in a day.\n\n## 6. Onboarding a new employee takes weeks because the system is so complex\n\nWhen new staff need weeks of training just to use the software — not to learn the *business*, but to learn the *tool* — that complexity is costing you real money. It also signals that the system was never shaped around the way your business actually works. Workarounds have been layered on top of workarounds, and each one needs its own explanation.\n\nGood business software should feel like it was built for your process, not the other way around.\n\n\u003Cimg src=\"\u002Fapi\u002Fknowledge\u002Finline-image\u002F6?w=700&f=webp\" alt=\"tangled web of disconnected system icons with manual arrows between them\" loading=\"lazy\" class=\"w-full sm:w-1\u002F3 sm:float-right sm:ml-7 mb-5 rounded-2xl border border-[#E8E8ED] bg-[#F5F5F7]\" \u002F>\n\n## 7. The system can't keep up with how the business has grown\n\nYou started with five customers and one product line. Now you have 200 customers, four product lines, two warehouses, and a partner channel. But the software is still the same one you bought in year two — and it shows. Performance is slow, workarounds multiply, and features that would save hours don't exist. Growth without a software strategy is growth that eventually stalls.\n\nThis is exactly the tension described in [how to modernize business software without starting over](https:\u002F\u002Floggix.com\u002Fen\u002Fblog\u002Fhow-to-modernize-business-software-without-starting-over): you don't always need to replace everything, but you do need a plan.\n\n## 8. Critical knowledge lives in one person's head (or inbox)\n\nThere is always someone in the organisation who knows how everything works — which customer gets which special price, which supplier needs to be called before 10am, which order type triggers a manual step. When that knowledge lives in someone's head rather than in the system, the business has a fragility problem. When that person is sick, on leave, or eventually moves on, operational chaos follows.\n\nA system that captures process logic — not just data — protects the organisation from key-person dependency.\n\n## 9. You have no audit trail and compliance is becoming a problem\n\nWho changed that price? When was this order modified? Which user approved that discount? If your system cannot answer these questions — or can only answer them after a lengthy manual investigation — then you are exposed. Regulatory pressure (think ISO certification, GDPR data requests, financial audits) is only increasing. An audit trail is not just good practice; in many industries it is becoming a hard requirement.\n\n## 10. Your software vendor is no longer investing in the product\n\nThe last update was two years ago. The support forum is quiet. The vendor's website looks like it hasn't changed since 2017. This is the slow death of a business-critical tool — not dramatic, but very real. Legacy software that is no longer maintained accumulates security vulnerabilities, stops supporting modern operating systems, and eventually becomes impossible to integrate with anything new.\n\nStaying on an unsupported system is not cost-saving — it is deferred risk.\n\n## 11. Your team uses the system as little as possible\n\nThe clearest sign of all: people avoid the system. They find ways to work around it. They save files locally instead of in the system. They WhatsApp each other instead of logging a note. User adoption is not a training problem — it is a design problem. When a system doesn't match the way people actually work, they route around it. And the more they route around it, the less useful the system becomes, until eventually it is just a compliance box that nobody trusts.\n\n---\n\n## Quick self-assessment checklist\n\nRun through these honestly with your operations lead or IT manager:\n\n- [ ] We have more than one \"master\" spreadsheet that people rely on daily\n- [ ] Data is entered manually into more than one system for the same transaction\n- [ ] Our core system has no active API integrations with other tools we use\n- [ ] Producing a management report takes more than a few hours\n- [ ] We can't answer basic stock or pipeline questions in real time\n- [ ] Onboarding a new user to the system takes more than a week\n- [ ] The system hasn't kept pace with our growth in the last 3 years\n- [ ] Key process knowledge lives with one or two individuals, not in the system\n- [ ] We have no reliable audit trail for data changes\n- [ ] Our software vendor is not actively developing or supporting the product\n- [ ] Staff actively avoid using the system where they can\n\n**Score:** 0–2 ticks: healthy system, monitor regularly. 3–5 ticks: friction is starting to cost you — plan a review. 6 or more ticks: your software is actively limiting your growth and the cost of inaction is rising every month.\n\n---\n\n## FAQ\n\n**Does this mean we have to replace everything?**\nNot necessarily. Many organisations get 80% of the benefit by connecting existing systems via API, automating one or two critical manual flows, and rebuilding only the parts of the system that are genuinely broken. A full replacement is sometimes the right answer — but it should be a conscious choice, not a panic decision.\n\n**How long does it take to fix these problems?**\nA targeted API integration between two systems can be live in a few weeks. A broader modernisation — rebuilding a core workflow in a custom system or migrating to a new platform — typically runs three to nine months, depending on complexity. The key is to sequence it: fix the highest-pain point first, prove the value, then continue.\n\n**Who should own this initiative inside the company?**\nSomeone who understands both the business process *and* has authority to make decisions about tooling. In an SME that is often the operations director, the IT manager, or the owner directly. The mistake is treating it purely as an IT project — or purely as a business project. It has to be both.\n\n---\n\nIf several of the signs above feel familiar, the next step is not a software demo — it is an honest mapping of where the real friction sits and what it is costing you per month. Loggix works with business owners and IT managers to do exactly that: mapping processes, identifying the highest-value integrations, and building custom solutions in FileMaker or as web applications that fit the way the business actually works — including AI-assisted workflows where they genuinely save time. If you want a practical conversation about where to start, that is what we are here for.","\u003Cp>Your software was the right choice when you bought it. But the business has changed — new products, more staff, new sales channels — and somewhere along the way the system stopped being an engine and started being a brake. This article walks through eleven concrete signs that your current software is holding the organisation back, and what each one really means for your next step.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fapi\u002Fknowledge\u002Finline-image\u002F7?w=700&f=webp\" alt=\"business owner frustrated at screen surrounded by stacked spreadsheet printouts\" loading=\"lazy\" class=\"w-full sm:w-1\u002F3 sm:float-left sm:mr-7 mb-5 rounded-2xl border border-[#E8E8ED] bg-[#F5F5F7]\" \u002F>\n\n\u003Ch2>1. Your team runs the business in spreadsheets, not in the system\u003C\u002Fh2>\n\u003Cp>This is the most common sign, and the most dangerous one to normalise. When staff maintain a separate Excel file to track open orders, calculate margins, or manage a planning board — that file \u003Cem>is\u003C\u002Fem> the real system. The official software has become a glorified archive. The risk: the spreadsheet lives on one person's laptop, has no audit trail, and breaks the moment that person is on holiday.\u003C\u002Fp>\n\u003Cp>Ask yourself: if your most experienced operations person left tomorrow, would the business know where the real numbers are?\u003C\u002Fp>\n\u003Ch2>2. The same data gets typed in more than once\u003C\u002Fh2>\n\u003Cp>An order comes in through your webshop. Someone copies it into the ERP. The logistics team re-enters the address into the shipping portal. The finance team keys the same order into the invoicing tool. That is one order, typed four times, by three different people, with three chances to introduce an error. Multiply that by 80 orders a day and you have a full-time job that exists purely because two systems don't talk to each other.\u003C\u002Fp>\n\u003Cp>Manual re-entry is not a workflow — it is a symptom of missing integrations.\u003C\u002Fp>\n\u003Ch2>3. There are no APIs, so every connection is a human being\u003C\u002Fh2>\n\u003Cp>Modern business runs on connected systems: a CRM, an ERP, an accounting package, a logistics platform, an e-commerce storefront. If your core system has no API — or has one nobody has ever used — then every data exchange between those systems depends on a person copying, pasting, exporting, and importing. That person becomes a single point of failure. And when volume grows, you don't automate — you hire another person to do the same manual job.\u003C\u002Fp>\n\u003Cp>An API connector between your order management system and Exact Online, for example, can eliminate an entire category of daily manual work in a single integration.\u003C\u002Fp>\n\u003Ch2>4. Management reports take days, not minutes\u003C\u002Fh2>\n\u003Cp>If producing the monthly management report requires your finance manager to spend two days pulling exports from three systems, stitching them together in Excel, and then manually formatting a PowerPoint — your software is not giving management the information it needs, when it needs it. Decisions get made on last month's data. Trends are spotted late. Opportunities are missed.\u003C\u002Fp>\n\u003Cp>A well-configured system should let a manager open a dashboard on a Monday morning and see last week's actuals without asking anyone for anything.\u003C\u002Fp>\n\u003Ch2>5. You can't answer a simple operational question without digging\u003C\u002Fh2>\n\u003Cp>"How many units of product X do we have in stock right now, across all locations?" If that question requires opening three screens, running an export, and cross-referencing a spreadsheet — the answer is: your system doesn't actually know. Real-time operational visibility is not a luxury; it is the foundation of every good decision your team makes in a day.\u003C\u002Fp>\n\u003Ch2>6. Onboarding a new employee takes weeks because the system is so complex\u003C\u002Fh2>\n\u003Cp>When new staff need weeks of training just to use the software — not to learn the \u003Cem>business\u003C\u002Fem>, but to learn the \u003Cem>tool\u003C\u002Fem> — that complexity is costing you real money. It also signals that the system was never shaped around the way your business actually works. Workarounds have been layered on top of workarounds, and each one needs its own explanation.\u003C\u002Fp>\n\u003Cp>Good business software should feel like it was built for your process, not the other way around.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fapi\u002Fknowledge\u002Finline-image\u002F6?w=700&f=webp\" alt=\"tangled web of disconnected system icons with manual arrows between them\" loading=\"lazy\" class=\"w-full sm:w-1\u002F3 sm:float-right sm:ml-7 mb-5 rounded-2xl border border-[#E8E8ED] bg-[#F5F5F7]\" \u002F>\n\n\u003Ch2>7. The system can't keep up with how the business has grown\u003C\u002Fh2>\n\u003Cp>You started with five customers and one product line. Now you have 200 customers, four product lines, two warehouses, and a partner channel. But the software is still the same one you bought in year two — and it shows. Performance is slow, workarounds multiply, and features that would save hours don't exist. Growth without a software strategy is growth that eventually stalls.\u003C\u002Fp>\n\u003Cp>This is exactly the tension described in \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fen\u002Fblog\u002Fhow-to-modernize-business-software-without-starting-over\">how to modernize business software without starting over\u003C\u002Fa>: you don't always need to replace everything, but you do need a plan.\u003C\u002Fp>\n\u003Ch2>8. Critical knowledge lives in one person's head (or inbox)\u003C\u002Fh2>\n\u003Cp>There is always someone in the organisation who knows how everything works — which customer gets which special price, which supplier needs to be called before 10am, which order type triggers a manual step. When that knowledge lives in someone's head rather than in the system, the business has a fragility problem. When that person is sick, on leave, or eventually moves on, operational chaos follows.\u003C\u002Fp>\n\u003Cp>A system that captures process logic — not just data — protects the organisation from key-person dependency.\u003C\u002Fp>\n\u003Ch2>9. You have no audit trail and compliance is becoming a problem\u003C\u002Fh2>\n\u003Cp>Who changed that price? When was this order modified? Which user approved that discount? If your system cannot answer these questions — or can only answer them after a lengthy manual investigation — then you are exposed. Regulatory pressure (think ISO certification, GDPR data requests, financial audits) is only increasing. An audit trail is not just good practice; in many industries it is becoming a hard requirement.\u003C\u002Fp>\n\u003Ch2>10. Your software vendor is no longer investing in the product\u003C\u002Fh2>\n\u003Cp>The last update was two years ago. The support forum is quiet. The vendor's website looks like it hasn't changed since 2017. This is the slow death of a business-critical tool — not dramatic, but very real. Legacy software that is no longer maintained accumulates security vulnerabilities, stops supporting modern operating systems, and eventually becomes impossible to integrate with anything new.\u003C\u002Fp>\n\u003Cp>Staying on an unsupported system is not cost-saving — it is deferred risk.\u003C\u002Fp>\n\u003Ch2>11. Your team uses the system as little as possible\u003C\u002Fh2>\n\u003Cp>The clearest sign of all: people avoid the system. They find ways to work around it. They save files locally instead of in the system. They WhatsApp each other instead of logging a note. User adoption is not a training problem — it is a design problem. When a system doesn't match the way people actually work, they route around it. And the more they route around it, the less useful the system becomes, until eventually it is just a compliance box that nobody trusts.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Quick self-assessment checklist\u003C\u002Fh2>\n\u003Cp>Run through these honestly with your operations lead or IT manager:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> We have more than one "master" spreadsheet that people rely on daily\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> Data is entered manually into more than one system for the same transaction\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> Our core system has no active API integrations with other tools we use\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> Producing a management report takes more than a few hours\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> We can't answer basic stock or pipeline questions in real time\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> Onboarding a new user to the system takes more than a week\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> The system hasn't kept pace with our growth in the last 3 years\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> Key process knowledge lives with one or two individuals, not in the system\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> We have no reliable audit trail for data changes\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> Our software vendor is not actively developing or supporting the product\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> Staff actively avoid using the system where they can\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Score:\u003C\u002Fstrong> 0–2 ticks: healthy system, monitor regularly. 3–5 ticks: friction is starting to cost you — plan a review. 6 or more ticks: your software is actively limiting your growth and the cost of inaction is rising every month.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>FAQ\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Does this mean we have to replace everything?\u003C\u002Fstrong>\nNot necessarily. Many organisations get 80% of the benefit by connecting existing systems via API, automating one or two critical manual flows, and rebuilding only the parts of the system that are genuinely broken. A full replacement is sometimes the right answer — but it should be a conscious choice, not a panic decision.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>How long does it take to fix these problems?\u003C\u002Fstrong>\nA targeted API integration between two systems can be live in a few weeks. A broader modernisation — rebuilding a core workflow in a custom system or migrating to a new platform — typically runs three to nine months, depending on complexity. The key is to sequence it: fix the highest-pain point first, prove the value, then continue.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Who should own this initiative inside the company?\u003C\u002Fstrong>\nSomeone who understands both the business process \u003Cem>and\u003C\u002Fem> has authority to make decisions about tooling. In an SME that is often the operations director, the IT manager, or the owner directly. The mistake is treating it purely as an IT project — or purely as a business project. It has to be both.\u003C\u002Fp>\n\u003Chr>\n\u003Cp>If several of the signs above feel familiar, the next step is not a software demo — it is an honest mapping of where the real friction sits and what it is costing you per month. Loggix works with business owners and IT managers to do exactly that: mapping processes, identifying the highest-value integrations, and building custom solutions in FileMaker or as web applications that fit the way the business actually works — including AI-assisted workflows where they genuinely save time. If you want a practical conversation about where to start, that is what we are here for.\u003C\u002Fp>\n","Jeroen",1784901657000,[42,43,44,45,23,46,47,48,49],"business software","digital transformation","ERP","API integration","process automation","business operations","SME","software modernisation",{"id":51,"idKnowledge":33,"idDomain":32,"idCluster":15,"slug":52,"title":53,"description":54,"bodyMarkdown":55,"bodyHtml":56,"author":15,"date":16,"createdAt":40,"topics":57,"image":27,"hasDownload":28,"fileName":15,"youtubeId":27},"113","how-to-modernize-business-software-without-starting-over","How to modernize business software without starting over","Should you keep investing in FileMaker or replace it? Here's how to modernize an existing system with AI and APIs — without a costly rebuild.","Your FileMaker system has been running your business for years — maybe decades. It knows your processes better than any off-the-shelf package ever could. But now your team is asking about AI, your accountant wants a live link to Exact Online, and somewhere in the back of your mind is the question you can't quite shake: *are we still backing the right horse?*\n\nThis article answers that question directly — and shows you the concrete steps to modernize what you already have, without throwing it away.\n\n## Is FileMaker still a platform worth investing in?\n\nThis is the real question, and it deserves a straight answer: **yes, with context.**\n\nClaris (the Claris International subsidiary of Apple that develops FileMaker) released FileMaker 2024 and is actively developing toward FileMaker 2026. The platform is not being quietly sunset. The 2026 roadmap signals continued investment in modern data connectivity, performance improvements, and — critically — native AI integration. For a business that has years of process logic, custom layouts, and institutional knowledge baked into a FileMaker solution, that continuity matters enormously.\n\nThe more honest framing: the risk is not \"will FileMaker disappear tomorrow.\" The risk is **stagnation** — running a 2015-era implementation in a 2025 world and calling it good enough. That's where businesses get into trouble. The platform is alive; the question is whether *your deployment* is keeping up with it.\n\n## What does \"modernizing\" actually mean in practice?\n\nModernizing does not mean rebuilding. It means closing the gap between what your current system does and what your business now needs — without discarding the logic, data, and customizations that make your system valuable in the first place.\n\nIn practice, modernization usually means one or more of these three things:\n\n1. **Connecting your FileMaker database to the modern tools around it** (your ERP, your CRM, your webshop, your logistics platform) via APIs\n2. **Adding AI capabilities to existing workflows** — inside FileMaker, not as a separate tool\n3. **Upgrading the FileMaker version itself** and cleaning up technical debt in the solution\n\nNone of these require starting from scratch. All three can be done incrementally, in the order that solves your most pressing problem first.\n\n\u003Cimg src=\"\u002Fapi\u002Fknowledge\u002Finline-image\u002F5?w=700&f=webp\" alt=\"Old FileMaker database connected via API to modern cloud tools like ERP and AI\" loading=\"lazy\" class=\"w-full sm:w-1\u002F3 sm:float-left sm:mr-7 mb-5 rounded-2xl border border-[#E8E8ED] bg-[#F5F5F7]\" \u002F>\n\n## Why APIs are the fastest win — and what they actually solve\n\nThe most common pain point we see: an order gets entered into FileMaker, and then re-typed by hand into Exact Online — every single order, every single day. Or a product is updated in your webshop, and someone has to manually mirror that change in the FileMaker inventory record. Twice the work, twice the errors, twice the frustration.\n\nThis is an API problem, and it is entirely solvable without touching the core of your FileMaker solution.\n\nFileMaker has had a mature REST API (the FileMaker Data API) for several years. Modern cloud platforms — Exact Online, Shopify, HubSpot, Microsoft 365, and dozens more — also expose REST APIs. An API connector sits between the two systems and handles the data flow automatically, in real time or on a schedule.\n\n**What this looks like in practice:**\n- An order confirmed in FileMaker is automatically pushed to Exact Online within seconds — no re-entry, no delay\n- A stock mutation in your warehouse app updates the FileMaker inventory record without anyone touching a keyboard\n- A new customer in your webshop is created as a relation in FileMaker the moment they check out\n\nBuilding these connectors does not require rebuilding your FileMaker solution. It requires a clear data model, well-defined triggers, and error handling for edge cases (duplicates, failed pushes, field-mapping mismatches). Those edge cases are where most DIY integrations break — plan for them from the start.\n\n## Can you really add AI to an old FileMaker database?\n\nYes — and this is where the FileMaker 2026 trajectory becomes genuinely exciting for existing deployments.\n\nThe most practical AI integrations right now work through the same API infrastructure described above. OpenAI, Azure OpenAI, and similar services all expose REST APIs. FileMaker can call those APIs directly using a native script step (`Insert from URL`), pass data to the model, and receive a structured response — all without leaving the FileMaker environment.\n\n**Concrete examples of what this enables in an existing FileMaker database:**\n- A service engineer submits a short voice note. FileMaker sends the transcript to a language model and writes a structured service report back into the record — automatically.\n- A customer complaint arrives by email. FileMaker classifies its urgency, extracts the relevant order number, and routes it to the right team member — without a human triage step.\n- A purchasing manager asks in plain language: \"Which suppliers have been delivering late this quarter?\" FileMaker queries its own data and returns a natural-language summary.\n\nNone of these examples require replacing your database. They require connecting it — thoughtfully, with proper authentication and data governance — to AI services that already exist.\n\nFileMaker 2026 is expected to make some of this even more native, reducing the scripting overhead for common AI patterns. But you do not have to wait for 2026 to start: the API-based approach works today, in FileMaker versions going back several years.\n\n\u003Cimg src=\"\u002Fapi\u002Fknowledge\u002Finline-image\u002F4?w=700&f=webp\" alt=\"FileMaker script calling OpenAI API, returning AI result into a database field\" loading=\"lazy\" class=\"w-full sm:w-1\u002F3 sm:float-right sm:ml-7 mb-5 rounded-2xl border border-[#E8E8ED] bg-[#F5F5F7]\" \u002F>\n\n## What should you actually do first? A practical sequence\n\nIf you're a business owner or in-house developer trying to decide where to start, here is a realistic sequence:\n\n1. **Audit your current version and technical debt.** What version of FileMaker are you running? Are there deprecated functions, broken scripts, or layouts that only one person understands? Document this before adding anything new. Upgrading to a current version (FileMaker 2024 as of writing) is the foundation everything else sits on.\n\n2. **Map your manual data handoffs.** For one week, track every time someone copies data from FileMaker into another system — or vice versa. Each of those handoffs is an API integration candidate. Rank them by time cost and error rate.\n\n3. **Pick one integration and build it properly.** Don't try to connect everything at once. Connect one system, build robust error handling, and prove the pattern works. A well-built Exact Online connector taught the team how to build the next one.\n\n4. **Identify one AI use case with a measurable output.** Not \"let's add AI\" — but \"let's automatically classify incoming support tickets and measure whether routing time drops.\" Specific, measurable, bounded.\n\n5. **Plan your FileMaker 2026 upgrade path.** Talk to your developer or partner now about what a migration to the 2026 version will require, so you're not scrambling when it releases. Knowing the delta early makes it a planned project, not a crisis.\n\n## Is there a point where rebuilding *is* the right answer?\n\nHonestly: sometimes, yes. If your FileMaker solution was built by someone who is no longer available, has no documentation, uses a data model that actively fights every new requirement, and the business has fundamentally changed since it was built — a rebuild may be cheaper over a five-year horizon than continuing to patch.\n\nBut that conclusion should come from analysis, not from a vendor telling you your old system is hopeless. The right test: can you clearly describe what you would build differently, and does the cost of the new build — including data migration, retraining, and lost productivity during transition — come out ahead? If you can't answer that clearly, you're not ready to rebuild.\n\nFor most businesses with a functioning FileMaker system, the answer is modernization, not replacement.\n\n## Quick checklist: are you ready to modernize?\n\n- [ ] You know which version of FileMaker you're running and when it was last updated\n- [ ] You've identified at least two manual data handoffs that could be automated via API\n- [ ] You have an in-house developer or external partner who knows the solution's data model\n- [ ] You can name one business process that would benefit from AI — and describe what \"better\" looks like\n- [ ] You have a rough sense of your FileMaker licensing situation and renewal timeline\n- [ ] You've decided whether modernization is an internal project or one that needs outside expertise\n\n## Frequently asked questions\n\n**We're still on FileMaker 17. Is it worth upgrading before adding APIs or AI?**\nYes. Older versions have limitations in the Data API and `Insert from URL` capabilities that will make integrations harder and more fragile. Upgrading first gives you a stable foundation and reduces the risk of building on a version that may soon lose support.\n\n**Our in-house developer built everything. What happens if they leave?**\nThis is a real risk and a common one. The answer is documentation and a second pair of eyes — ideally an external FileMaker developer who reviews the solution, documents the data model, and can step in if needed. Don't wait for a crisis to address this.\n\n**Do we need a new license to use the FileMaker Data API?**\nThe Data API is included in current Claris FileMaker licensing at the server level. If you're on an older perpetual license, check your agreement — you may need to move to a current subscription to access it fully.\n\n**How long does a typical API integration take to build?**\nA well-scoped, single-system integration (e.g. FileMaker ↔ Exact Online for orders and relations) typically takes two to six weeks from scoping to stable production, depending on complexity and the quality of documentation on both sides. Rushing this phase creates fragile connectors that break quietly.\n\n---\n\nModernizing an existing FileMaker system is not a leap of faith — it's a series of deliberate, reversible decisions. The platform has a clear future. The tools to connect it to AI and modern APIs exist today. The question is not whether to invest, but where to invest first — and how to sequence it so each step makes the next one easier.","\u003Cp>Your FileMaker system has been running your business for years — maybe decades. It knows your processes better than any off-the-shelf package ever could. But now your team is asking about AI, your accountant wants a live link to Exact Online, and somewhere in the back of your mind is the question you can't quite shake: \u003Cem>are we still backing the right horse?\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>This article answers that question directly — and shows you the concrete steps to modernize what you already have, without throwing it away.\u003C\u002Fp>\n\u003Ch2>Is FileMaker still a platform worth investing in?\u003C\u002Fh2>\n\u003Cp>This is the real question, and it deserves a straight answer: \u003Cstrong>yes, with context.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Claris (the Claris International subsidiary of Apple that develops FileMaker) released FileMaker 2024 and is actively developing toward FileMaker 2026. The platform is not being quietly sunset. The 2026 roadmap signals continued investment in modern data connectivity, performance improvements, and — critically — native AI integration. For a business that has years of process logic, custom layouts, and institutional knowledge baked into a FileMaker solution, that continuity matters enormously.\u003C\u002Fp>\n\u003Cp>The more honest framing: the risk is not "will FileMaker disappear tomorrow." The risk is \u003Cstrong>stagnation\u003C\u002Fstrong> — running a 2015-era implementation in a 2025 world and calling it good enough. That's where businesses get into trouble. The platform is alive; the question is whether \u003Cem>your deployment\u003C\u002Fem> is keeping up with it.\u003C\u002Fp>\n\u003Ch2>What does "modernizing" actually mean in practice?\u003C\u002Fh2>\n\u003Cp>Modernizing does not mean rebuilding. It means closing the gap between what your current system does and what your business now needs — without discarding the logic, data, and customizations that make your system valuable in the first place.\u003C\u002Fp>\n\u003Cp>In practice, modernization usually means one or more of these three things:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Connecting your FileMaker database to the modern tools around it\u003C\u002Fstrong> (your ERP, your CRM, your webshop, your logistics platform) via APIs\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Adding AI capabilities to existing workflows\u003C\u002Fstrong> — inside FileMaker, not as a separate tool\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Upgrading the FileMaker version itself\u003C\u002Fstrong> and cleaning up technical debt in the solution\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>None of these require starting from scratch. All three can be done incrementally, in the order that solves your most pressing problem first.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fapi\u002Fknowledge\u002Finline-image\u002F5?w=700&f=webp\" alt=\"Old FileMaker database connected via API to modern cloud tools like ERP and AI\" loading=\"lazy\" class=\"w-full sm:w-1\u002F3 sm:float-left sm:mr-7 mb-5 rounded-2xl border border-[#E8E8ED] bg-[#F5F5F7]\" \u002F>\n\n\u003Ch2>Why APIs are the fastest win — and what they actually solve\u003C\u002Fh2>\n\u003Cp>The most common pain point we see: an order gets entered into FileMaker, and then re-typed by hand into Exact Online — every single order, every single day. Or a product is updated in your webshop, and someone has to manually mirror that change in the FileMaker inventory record. Twice the work, twice the errors, twice the frustration.\u003C\u002Fp>\n\u003Cp>This is an API problem, and it is entirely solvable without touching the core of your FileMaker solution.\u003C\u002Fp>\n\u003Cp>FileMaker has had a mature REST API (the FileMaker Data API) for several years. Modern cloud platforms — Exact Online, Shopify, HubSpot, Microsoft 365, and dozens more — also expose REST APIs. An API connector sits between the two systems and handles the data flow automatically, in real time or on a schedule.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What this looks like in practice:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>An order confirmed in FileMaker is automatically pushed to Exact Online within seconds — no re-entry, no delay\u003C\u002Fli>\n\u003Cli>A stock mutation in your warehouse app updates the FileMaker inventory record without anyone touching a keyboard\u003C\u002Fli>\n\u003Cli>A new customer in your webshop is created as a relation in FileMaker the moment they check out\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Building these connectors does not require rebuilding your FileMaker solution. It requires a clear data model, well-defined triggers, and error handling for edge cases (duplicates, failed pushes, field-mapping mismatches). Those edge cases are where most DIY integrations break — plan for them from the start.\u003C\u002Fp>\n\u003Ch2>Can you really add AI to an old FileMaker database?\u003C\u002Fh2>\n\u003Cp>Yes — and this is where the FileMaker 2026 trajectory becomes genuinely exciting for existing deployments.\u003C\u002Fp>\n\u003Cp>The most practical AI integrations right now work through the same API infrastructure described above. OpenAI, Azure OpenAI, and similar services all expose REST APIs. FileMaker can call those APIs directly using a native script step (\u003Ccode>Insert from URL\u003C\u002Fcode>), pass data to the model, and receive a structured response — all without leaving the FileMaker environment.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Concrete examples of what this enables in an existing FileMaker database:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A service engineer submits a short voice note. FileMaker sends the transcript to a language model and writes a structured service report back into the record — automatically.\u003C\u002Fli>\n\u003Cli>A customer complaint arrives by email. FileMaker classifies its urgency, extracts the relevant order number, and routes it to the right team member — without a human triage step.\u003C\u002Fli>\n\u003Cli>A purchasing manager asks in plain language: "Which suppliers have been delivering late this quarter?" FileMaker queries its own data and returns a natural-language summary.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>None of these examples require replacing your database. They require connecting it — thoughtfully, with proper authentication and data governance — to AI services that already exist.\u003C\u002Fp>\n\u003Cp>FileMaker 2026 is expected to make some of this even more native, reducing the scripting overhead for common AI patterns. But you do not have to wait for 2026 to start: the API-based approach works today, in FileMaker versions going back several years.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fapi\u002Fknowledge\u002Finline-image\u002F4?w=700&f=webp\" alt=\"FileMaker script calling OpenAI API, returning AI result into a database field\" loading=\"lazy\" class=\"w-full sm:w-1\u002F3 sm:float-right sm:ml-7 mb-5 rounded-2xl border border-[#E8E8ED] bg-[#F5F5F7]\" \u002F>\n\n\u003Ch2>What should you actually do first? A practical sequence\u003C\u002Fh2>\n\u003Cp>If you're a business owner or in-house developer trying to decide where to start, here is a realistic sequence:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cp>\u003Cstrong>Audit your current version and technical debt.\u003C\u002Fstrong> What version of FileMaker are you running? Are there deprecated functions, broken scripts, or layouts that only one person understands? Document this before adding anything new. Upgrading to a current version (FileMaker 2024 as of writing) is the foundation everything else sits on.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>\u003Cstrong>Map your manual data handoffs.\u003C\u002Fstrong> For one week, track every time someone copies data from FileMaker into another system — or vice versa. Each of those handoffs is an API integration candidate. Rank them by time cost and error rate.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>\u003Cstrong>Pick one integration and build it properly.\u003C\u002Fstrong> Don't try to connect everything at once. Connect one system, build robust error handling, and prove the pattern works. A well-built Exact Online connector taught the team how to build the next one.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>\u003Cstrong>Identify one AI use case with a measurable output.\u003C\u002Fstrong> Not "let's add AI" — but "let's automatically classify incoming support tickets and measure whether routing time drops." Specific, measurable, bounded.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>\u003Cstrong>Plan your FileMaker 2026 upgrade path.\u003C\u002Fstrong> Talk to your developer or partner now about what a migration to the 2026 version will require, so you're not scrambling when it releases. Knowing the delta early makes it a planned project, not a crisis.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2>Is there a point where rebuilding \u003Cem>is\u003C\u002Fem> the right answer?\u003C\u002Fh2>\n\u003Cp>Honestly: sometimes, yes. If your FileMaker solution was built by someone who is no longer available, has no documentation, uses a data model that actively fights every new requirement, and the business has fundamentally changed since it was built — a rebuild may be cheaper over a five-year horizon than continuing to patch.\u003C\u002Fp>\n\u003Cp>But that conclusion should come from analysis, not from a vendor telling you your old system is hopeless. The right test: can you clearly describe what you would build differently, and does the cost of the new build — including data migration, retraining, and lost productivity during transition — come out ahead? If you can't answer that clearly, you're not ready to rebuild.\u003C\u002Fp>\n\u003Cp>For most businesses with a functioning FileMaker system, the answer is modernization, not replacement.\u003C\u002Fp>\n\u003Ch2>Quick checklist: are you ready to modernize?\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> You know which version of FileMaker you're running and when it was last updated\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> You've identified at least two manual data handoffs that could be automated via API\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> You have an in-house developer or external partner who knows the solution's data model\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> You can name one business process that would benefit from AI — and describe what "better" looks like\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> You have a rough sense of your FileMaker licensing situation and renewal timeline\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> You've decided whether modernization is an internal project or one that needs outside expertise\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Frequently asked questions\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>We're still on FileMaker 17. Is it worth upgrading before adding APIs or AI?\u003C\u002Fstrong>\nYes. Older versions have limitations in the Data API and \u003Ccode>Insert from URL\u003C\u002Fcode> capabilities that will make integrations harder and more fragile. Upgrading first gives you a stable foundation and reduces the risk of building on a version that may soon lose support.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Our in-house developer built everything. What happens if they leave?\u003C\u002Fstrong>\nThis is a real risk and a common one. The answer is documentation and a second pair of eyes — ideally an external FileMaker developer who reviews the solution, documents the data model, and can step in if needed. Don't wait for a crisis to address this.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Do we need a new license to use the FileMaker Data API?\u003C\u002Fstrong>\nThe Data API is included in current Claris FileMaker licensing at the server level. If you're on an older perpetual license, check your agreement — you may need to move to a current subscription to access it fully.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>How long does a typical API integration take to build?\u003C\u002Fstrong>\nA well-scoped, single-system integration (e.g. FileMaker ↔ Exact Online for orders and relations) typically takes two to six weeks from scoping to stable production, depending on complexity and the quality of documentation on both sides. Rushing this phase creates fragile connectors that break quietly.\u003C\u002Fp>\n\u003Chr>\n\u003Cp>Modernizing an existing FileMaker system is not a leap of faith — it's a series of deliberate, reversible decisions. The platform has a clear future. The tools to connect it to AI and modern APIs exist today. The question is not whether to invest, but where to invest first — and how to sequence it so each step makes the next one easier.\u003C\u002Fp>\n",[23,58,45,59,60,61,62],"business software modernization","AI in FileMaker","ERP connectors","FileMaker 2026","custom software strategy",{"id":64,"idKnowledge":65,"idDomain":15,"idCluster":15,"slug":66,"title":67,"description":68,"bodyMarkdown":69,"bodyHtml":70,"author":39,"date":16,"createdAt":71,"topics":72,"image":74,"hasDownload":28,"fileName":15,"youtubeId":27},"111","6B5C81AB-1CE6-E144-85EE-54E5BCE763CA","filemaker-development-zonder-kostbare-migratie","FileMaker development without costly migration","FileMaker development modernises existing systems with integrations, automation and apps, without unnecessary costly replacements or business downtime.","A FileMaker solution that has been supporting quotes, planning, inventory, projects, or customer data for years is rarely the problem. The problem arises when employees have to re-enter data, a connection with accounting is missing, or critical processes depend on one person who knows which button to press and when. In that case, replacement is not automatically the best choice. Often the fastest and most sensible route lies in targeted expansion.\n\n## What FileMaker development should deliver for your business\n\nFileMaker development is not just about new screens, scripts, or tables. It is about translating an existing workflow into software that requires less manual effort, causes fewer errors, and aligns better with the systems that have since become part of your business operations.\n\nFor many organisations, FileMaker is the heart of operations. It contains knowledge that does not fit into a standard package: exceptional pricing agreements, specific calculation rules, product variants, planning logic, or internal approval steps. Rebuilding that knowledge on a different platform is costly and carries risk. Targeted further development preserves that value while removing the limitations of an older solution.\n\nThe right question, therefore, is not: should we move away from FileMaker? The better question is: which parts of the process deserve modernisation, and which parts are already functioning well? That distinction prevents a large migration project when a connection, an improved workflow, or mobile data entry could already deliver the desired result.\n\n## Start with the bottleneck, not the technology\n\nA good development process starts with concrete signals from day-to-day practice. Perhaps orders are still confirmed by email and then manually re-entered. Perhaps the finance team exports data to a spreadsheet every week before entering it into the accounting package. Or field staff call the office because they cannot access current project information on the go.\n\nThese are not isolated frustrations. They often point to a process in which data changes hands between systems or owners too frequently. FileMaker can maintain control in that situation, but only if it is properly connected to the rest of the landscape.\n\nStart by mapping out, for each process, where data originates, who uses it, what decision follows, and where duplicate entry occurs. Also look at exceptions. Automating a standard route is useful, but the real value often lies in handling deviating orders, missing data, or non-standard invoicing arrangements correctly.\n\nA practical first phase typically produces a limited, clear list: what must stay, what must be simplified, and which actions can be eliminated. This keeps development manageable. You avoid a desire to modernise turning into an unbounded project with constantly new ideas.\n\n### Choose improvements with a visible impact\n\nPrioritise based on business impact, not technical appeal. A new dashboard may be useful, but an automated check that prevents incorrect prices from being invoiced may have a faster financial effect. The same applies to an integration that synchronises customer data: it saves time, but above all it must create a single reliable source of truth.\n\nSmall improvements can also be strategic. A cleaned-up data model, consistent status values, or a clear permissions structure makes future expansions much easier. Not every improvement is immediately visible to end users, but some form the foundation for safer and more maintainable software.\n\n## A modern FileMaker environment is connected\n\nA FileMaker database does not have to be an isolated internal system. Through [API integrations](https:\u002F\u002Floggix.com\u002Fapis\u002F), it can exchange information with accounting software, CRM systems, e-commerce platforms, transport services, payment providers, and document storage. Which integration makes sense depends on the process and the quality of the available interfaces.\n\nConsider an order that is automatically forwarded to an ERP or [accounting system](https:\u002F\u002Floggix.com\u002Fblog\u002Fexact-online-koppelen-aan-filemaker-zo-automatiseer-je-facturen-veilig-en-foutloos\u002F) after approval. Or customer data that is updated from a central CRM, so that sales, planning, and administration all work with the same information. Another common application is retrieving shipping statuses or generating documents based on data already held in FileMaker.\n\nHowever, an integration is not a one-off technical action. Agreements must be in place about which application is the leading system, how changes are processed, and what happens when an external service is temporarily unavailable. Without those decisions, automation can actually introduce new errors — for example, duplicate records or discrepancies between systems.\n\n### API integrations require control and recovery\n\nA good integration records what has been sent, received, and potentially rejected. Employees must be able to see why an invoice was not forwarded, without having to search through technical log files. A recovery route is also needed: can a failed submission be retried, and by whom?\n\nSecurity should be part of the design from the outset. API keys, access permissions, and personal data require careful management. This applies particularly when a solution shares data with external parties or gives employees outside the office access. Convenience is valuable, but not if it means everyone can see or modify more than necessary.\n\n## Adding web and mobile where the work takes place\n\nNot every user needs to work in the same FileMaker screen. For a warehouse employee, a simple mobile entry interface for receiving or counting stock may be a much better fit. A customer portal can give clients insight into orders, documents, or project statuses without granting them access to the internal database. For managers, a [web application](https:\u002F\u002Floggix.com\u002Fblog\u002Fwebapp-op-filemaker-data-slim-aanpakken\u002F) may be sufficient for handling approvals.\n\nThis is often more effective than a single comprehensive interface for all roles. A specialised web or mobile application can display exactly the data and actions a person needs at that moment. This reduces the likelihood of errors and lowers the amount of explanation required for new employees.\n\nThe trade-off lies in management and usage. An additional app is only worthwhile if it genuinely simplifies a specific process. If employees primarily work at a desk and the existing FileMaker client fits well, expanding that environment is often the smarter choice. If work takes place on location, requires offline capability, or needs straightforward external access, a separate app may be the better option.\n\n## Modernising without disrupting operations\n\nThe biggest concern when modifying a business-critical database is understandable: what if day-to-day work comes to a halt? That is why phased modernisation usually works better than a single large switchover on one date.\n\nAn initial version might, for example, be limited to one department, one integration, or one process step. Users then test with familiar real-world situations, not just sample data. Their feedback quickly reveals where a screen involves too many steps, a notification is unclear, or an exception has been overlooked.\n\nTechnical preparation also deserves attention. Check the quality of existing data, legacy scripts, accounts, permissions, and server configuration. A system may have functioned well for years and still contain historically grown exceptions. These do not all need to be removed immediately, but they must be known before new functionality is built on top of them.\n\nA careful plan therefore includes a test environment, backups, a fallback scenario, and clear acceptance criteria. When is a process truly complete? Not when it works technically, but when an employee can correctly handle both a standard and an exceptional situation without additional work outside the system.\n\n## Using AI only where the outcome is verifiable\n\nPractical AI can support FileMaker processes — for example, by summarising notes, classifying incoming requests, suggesting responses, or extracting data from documents. The best applications start with a well-defined task and a verifiable outcome.\n\nAn AI function that summarises an email for a project file can save time, as long as an employee can review the summary. Automatically recognising data on a purchase invoice can speed up data entry, as long as discrepancies are flagged before they have financial consequences. For decisions involving pricing, contracts, or compliance, human review is often essential.\n\nAI is therefore not a replacement for an unclear process. If input, roles, and exceptions are not well defined, AI will at best make that ambiguity visible more quickly. Simplifying the process first, then automating in a targeted way, generally produces better results.\n\n## Choose a partner who also understands the existing system\n\nA FileMaker specialist must not only be able to build new functionality, but also read, assess, and safely extend existing solutions. That requires an understanding of data models, scripts, security, hosting, integrations, and the day-to-day impact of a change on users.\n\nAt Loggix, the emphasis is therefore on modernisation that fits the operation. Sometimes that means a small correction or a reliable API integration. Sometimes it requires a rebuilt module, a mobile addition, or a platform that can scale towards a SaaS-like model. The scope of the solution must follow from the problem, not from a predetermined technical approach.\n\nThe most valuable next step is often straightforward: choose one process that demonstrably costs time, causes errors, or hinders growth. Examine what already works within it, what is missing, and which improvement employees will notice immediately. This keeps your FileMaker environment from becoming a system you handle with caution out of fear of change — and makes it a business asset that moves forward with your organisation in a targeted way.","\u003Cp>A FileMaker solution that has been supporting quotes, planning, inventory, projects, or customer data for years is rarely the problem. The problem arises when employees have to re-enter data, a connection with accounting is missing, or critical processes depend on one person who knows which button to press and when. In that case, replacement is not automatically the best choice. Often the fastest and most sensible route lies in targeted expansion.\u003C\u002Fp>\n\u003Ch2>What FileMaker development should deliver for your business\u003C\u002Fh2>\n\u003Cp>FileMaker development is not just about new screens, scripts, or tables. It is about translating an existing workflow into software that requires less manual effort, causes fewer errors, and aligns better with the systems that have since become part of your business operations.\u003C\u002Fp>\n\u003Cp>For many organisations, FileMaker is the heart of operations. It contains knowledge that does not fit into a standard package: exceptional pricing agreements, specific calculation rules, product variants, planning logic, or internal approval steps. Rebuilding that knowledge on a different platform is costly and carries risk. Targeted further development preserves that value while removing the limitations of an older solution.\u003C\u002Fp>\n\u003Cp>The right question, therefore, is not: should we move away from FileMaker? The better question is: which parts of the process deserve modernisation, and which parts are already functioning well? That distinction prevents a large migration project when a connection, an improved workflow, or mobile data entry could already deliver the desired result.\u003C\u002Fp>\n\u003Ch2>Start with the bottleneck, not the technology\u003C\u002Fh2>\n\u003Cp>A good development process starts with concrete signals from day-to-day practice. Perhaps orders are still confirmed by email and then manually re-entered. Perhaps the finance team exports data to a spreadsheet every week before entering it into the accounting package. Or field staff call the office because they cannot access current project information on the go.\u003C\u002Fp>\n\u003Cp>These are not isolated frustrations. They often point to a process in which data changes hands between systems or owners too frequently. FileMaker can maintain control in that situation, but only if it is properly connected to the rest of the landscape.\u003C\u002Fp>\n\u003Cp>Start by mapping out, for each process, where data originates, who uses it, what decision follows, and where duplicate entry occurs. Also look at exceptions. Automating a standard route is useful, but the real value often lies in handling deviating orders, missing data, or non-standard invoicing arrangements correctly.\u003C\u002Fp>\n\u003Cp>A practical first phase typically produces a limited, clear list: what must stay, what must be simplified, and which actions can be eliminated. This keeps development manageable. You avoid a desire to modernise turning into an unbounded project with constantly new ideas.\u003C\u002Fp>\n\u003Ch3>Choose improvements with a visible impact\u003C\u002Fh3>\n\u003Cp>Prioritise based on business impact, not technical appeal. A new dashboard may be useful, but an automated check that prevents incorrect prices from being invoiced may have a faster financial effect. The same applies to an integration that synchronises customer data: it saves time, but above all it must create a single reliable source of truth.\u003C\u002Fp>\n\u003Cp>Small improvements can also be strategic. A cleaned-up data model, consistent status values, or a clear permissions structure makes future expansions much easier. Not every improvement is immediately visible to end users, but some form the foundation for safer and more maintainable software.\u003C\u002Fp>\n\u003Ch2>A modern FileMaker environment is connected\u003C\u002Fh2>\n\u003Cp>A FileMaker database does not have to be an isolated internal system. Through \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fapis\u002F\">API integrations\u003C\u002Fa>, it can exchange information with accounting software, CRM systems, e-commerce platforms, transport services, payment providers, and document storage. Which integration makes sense depends on the process and the quality of the available interfaces.\u003C\u002Fp>\n\u003Cp>Consider an order that is automatically forwarded to an ERP or \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Fexact-online-koppelen-aan-filemaker-zo-automatiseer-je-facturen-veilig-en-foutloos\u002F\">accounting system\u003C\u002Fa> after approval. Or customer data that is updated from a central CRM, so that sales, planning, and administration all work with the same information. Another common application is retrieving shipping statuses or generating documents based on data already held in FileMaker.\u003C\u002Fp>\n\u003Cp>However, an integration is not a one-off technical action. Agreements must be in place about which application is the leading system, how changes are processed, and what happens when an external service is temporarily unavailable. Without those decisions, automation can actually introduce new errors — for example, duplicate records or discrepancies between systems.\u003C\u002Fp>\n\u003Ch3>API integrations require control and recovery\u003C\u002Fh3>\n\u003Cp>A good integration records what has been sent, received, and potentially rejected. Employees must be able to see why an invoice was not forwarded, without having to search through technical log files. A recovery route is also needed: can a failed submission be retried, and by whom?\u003C\u002Fp>\n\u003Cp>Security should be part of the design from the outset. API keys, access permissions, and personal data require careful management. This applies particularly when a solution shares data with external parties or gives employees outside the office access. Convenience is valuable, but not if it means everyone can see or modify more than necessary.\u003C\u002Fp>\n\u003Ch2>Adding web and mobile where the work takes place\u003C\u002Fh2>\n\u003Cp>Not every user needs to work in the same FileMaker screen. For a warehouse employee, a simple mobile entry interface for receiving or counting stock may be a much better fit. A customer portal can give clients insight into orders, documents, or project statuses without granting them access to the internal database. For managers, a \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Fwebapp-op-filemaker-data-slim-aanpakken\u002F\">web application\u003C\u002Fa> may be sufficient for handling approvals.\u003C\u002Fp>\n\u003Cp>This is often more effective than a single comprehensive interface for all roles. A specialised web or mobile application can display exactly the data and actions a person needs at that moment. This reduces the likelihood of errors and lowers the amount of explanation required for new employees.\u003C\u002Fp>\n\u003Cp>The trade-off lies in management and usage. An additional app is only worthwhile if it genuinely simplifies a specific process. If employees primarily work at a desk and the existing FileMaker client fits well, expanding that environment is often the smarter choice. If work takes place on location, requires offline capability, or needs straightforward external access, a separate app may be the better option.\u003C\u002Fp>\n\u003Ch2>Modernising without disrupting operations\u003C\u002Fh2>\n\u003Cp>The biggest concern when modifying a business-critical database is understandable: what if day-to-day work comes to a halt? That is why phased modernisation usually works better than a single large switchover on one date.\u003C\u002Fp>\n\u003Cp>An initial version might, for example, be limited to one department, one integration, or one process step. Users then test with familiar real-world situations, not just sample data. Their feedback quickly reveals where a screen involves too many steps, a notification is unclear, or an exception has been overlooked.\u003C\u002Fp>\n\u003Cp>Technical preparation also deserves attention. Check the quality of existing data, legacy scripts, accounts, permissions, and server configuration. A system may have functioned well for years and still contain historically grown exceptions. These do not all need to be removed immediately, but they must be known before new functionality is built on top of them.\u003C\u002Fp>\n\u003Cp>A careful plan therefore includes a test environment, backups, a fallback scenario, and clear acceptance criteria. When is a process truly complete? Not when it works technically, but when an employee can correctly handle both a standard and an exceptional situation without additional work outside the system.\u003C\u002Fp>\n\u003Ch2>Using AI only where the outcome is verifiable\u003C\u002Fh2>\n\u003Cp>Practical AI can support FileMaker processes — for example, by summarising notes, classifying incoming requests, suggesting responses, or extracting data from documents. The best applications start with a well-defined task and a verifiable outcome.\u003C\u002Fp>\n\u003Cp>An AI function that summarises an email for a project file can save time, as long as an employee can review the summary. Automatically recognising data on a purchase invoice can speed up data entry, as long as discrepancies are flagged before they have financial consequences. For decisions involving pricing, contracts, or compliance, human review is often essential.\u003C\u002Fp>\n\u003Cp>AI is therefore not a replacement for an unclear process. If input, roles, and exceptions are not well defined, AI will at best make that ambiguity visible more quickly. Simplifying the process first, then automating in a targeted way, generally produces better results.\u003C\u002Fp>\n\u003Ch2>Choose a partner who also understands the existing system\u003C\u002Fh2>\n\u003Cp>A FileMaker specialist must not only be able to build new functionality, but also read, assess, and safely extend existing solutions. That requires an understanding of data models, scripts, security, hosting, integrations, and the day-to-day impact of a change on users.\u003C\u002Fp>\n\u003Cp>At Loggix, the emphasis is therefore on modernisation that fits the operation. Sometimes that means a small correction or a reliable API integration. Sometimes it requires a rebuilt module, a mobile addition, or a platform that can scale towards a SaaS-like model. The scope of the solution must follow from the problem, not from a predetermined technical approach.\u003C\u002Fp>\n\u003Cp>The most valuable next step is often straightforward: choose one process that demonstrably costs time, causes errors, or hinders growth. Examine what already works within it, what is missing, and which improvement employees will notice immediately. This keeps your FileMaker environment from becoming a system you handle with caution out of fear of change — and makes it a business asset that moves forward with your organisation in a targeted way.\u003C\u002Fp>\n",1784880800000,[23,73],"API","\u002Fapi\u002Fknowledge\u002Fimage\u002F111\u002F?v=42fff3ad92b9",{"id":76,"idKnowledge":77,"idDomain":15,"idCluster":15,"slug":78,"title":79,"description":80,"bodyMarkdown":81,"bodyHtml":82,"author":39,"date":83,"createdAt":84,"topics":85,"image":94,"hasDownload":28,"fileName":15,"youtubeId":27},"110","A1C5108D-1A83-7C4A-A805-F02FDF6643EE","rag-systeem-voor-een-interne-kennisbank","RAG system for an internal knowledge base","Employees and customers asking the same questions over and over? A RAG system turns your scattered documents into a smart, searchable knowledge base.","Your helpdesk answers the same ten questions every week. A customer calls because they can't find the returns policy. A new employee asks for the third time how the onboarding process works. The answers already exist — they're just buried in a Word document from 2021, a PDF on a shared drive, or an email thread nobody can find anymore. This article explains how a RAG system turns that scattered knowledge into a searchable, answering knowledge base — and when that's the right choice.\n\n\u003Cimg src=\"\u002Fapi\u002Fknowledge\u002Finline-image\u002F10?w=700&f=webp\" alt=\"scattered documents flowing into a single intelligent search interface with answers\" loading=\"lazy\" class=\"w-full sm:w-1\u002F3 sm:float-left sm:mr-7 mb-5 rounded-2xl border border-[#E8E8ED] bg-[#F5F5F7]\" \u002F>\n\n## What exactly is a RAG system?\n\nRAG stands for **Retrieval-Augmented Generation**. It is an architecture in which a language model (such as GPT-4) does not answer from its own training memory, but first retrieves relevant information from *your* own documents — and uses that as the basis for the answer.\n\nThat sounds technical, but the essence is simple:\n\n1. An employee or customer asks a question in plain language.\n2. The system searches your knowledge base for the most relevant passages.\n3. Those passages are passed to the language model.\n4. The language model formulates a clear, contextual answer — based on your own content.\n\nThe difference from a standard chatbot: a RAG system doesn't make things up. Every answer is always traceable to a source from your own documentation.\n\n## Why isn't a standard search function enough?\n\nA classic search function works on keywords. An employee searching for \"travel expense reimbursement\" will only find documents that literally contain those words. But if the policy document refers to \"mileage allowance\" or \"expense claim policy\", the search returns nothing.\n\nA RAG system works with **embeddings** — mathematical representations of the meaning of text, stored in a vector database. Two sentences with the same meaning but different words are recognised as semantically similar. The employee doesn't need to know what the document is called or which words it contains — they simply ask their question.\n\n## How does it work technically under the hood?\n\nA working RAG system consists of several layers:\n\n### 1. Document ingestion\nAll source files — Word documents, PDFs, web pages, FileMaker records, email archives — are read in and split into smaller text blocks (chunks). Each block is accompanied by metadata: file name, date, department, version number.\n\n### 2. Generating embeddings\nEach text block is converted into an embedding vector via a language model (for example OpenAI `text-embedding-3-large` or a local variant via Ollama). These vectors are stored in a vector database such as **Pinecone**, **Qdrant**, **Weaviate**, or simply **pgvector** in PostgreSQL.\n\n### 3. Retrieval on a search query\nWhen a user asks a question, that question is itself also converted into a vector. The system then searches for the text blocks whose vector is closest — these are the most semantically relevant passages.\n\n### 4. Generating the answer\nThe retrieved passages are passed together with the original question as context to an LLM (language model). The model formulates an answer in plain language, including a reference to the source passage.\n\n\u003Cimg src=\"\u002Fapi\u002Fknowledge\u002Finline-image\u002F9?w=700&f=webp\" alt=\"four-step RAG pipeline: documents, embeddings, vector search, LLM answer with source citation\" loading=\"lazy\" class=\"w-full sm:w-1\u002F3 sm:float-right sm:ml-7 mb-5 rounded-2xl border border-[#E8E8ED] bg-[#F5F5F7]\" \u002F>\n\n## When is a RAG system the right choice?\n\nNot every situation calls for RAG. Here is an honest overview:\n\n**RAG works well when:**\n- Your knowledge base consists of many text-based documents that are updated regularly.\n- Questions are open-ended in nature: \"How does our returns process work?\" or \"What is the escalation path for a complaint?\"\n- You want answers to always be traceable to a source.\n- You don't have the time to maintain an FAQ manually.\n\n**RAG is less suitable when:**\n- Questions relate to real-time data (current stock levels, live order status) — that requires a direct database connection, not a document search.\n- Your knowledge base consists of fewer than 50 documents that rarely change — in that case, a simple FAQ page is more efficient.\n- Answers need to be legally binding without a human review.\n\n## How do you build a RAG system step by step?\n\nHere is a practical approach, as we apply it ourselves:\n\n1. **Inventory your knowledge sources.** Where does the knowledge live right now? SharePoint, FileMaker, Google Drive, shared drive, email? Make a list by type and department.\n2. **Define the scope.** Start small: one department, one theme (e.g. HR policy or product questions). Expand later.\n3. **Choose your ingestion pipeline.** Tools such as LangChain, LlamaIndex, or a custom script read in documents, split them into chunks, and store metadata.\n4. **Choose a vector database.** For a first version, pgvector (in PostgreSQL) works well. For scale or advanced filtering, choose Qdrant or Weaviate.\n5. **Choose your LLM.** OpenAI GPT-4o for maximum quality, or a local open-source variant (Mistral, LLaMA 3) if privacy is a hard requirement.\n6. **Build an interface.** This can be a simple chat window embedded in your intranet, a widget on your customer portal, or an integration directly in FileMaker via the Data API.\n7. **Test on edge cases.** Ask questions whose answers you already know. Verify that the system cites sources and does not fabricate answers outside the knowledge base.\n8. **Set up an update process.** Who adds new documents? How often are embeddings regenerated when files change? This is the most underestimated step.\n\n## What are the pitfalls you want to avoid?\n\n**Poor document quality is the biggest risk.** If the source files are outdated, contradictory, or poorly structured, the RAG system will give poor answers — with the confidence of an AI. \"Garbage in, garbage out\" applies here doubly.\n\n**Chunk size has a major impact.** Chunks that are too large contain noise; chunks that are too small lose context. A chunk of 300–600 tokens with 10–20% overlap is a good starting point — but always test this on your own documents.\n\n**Users expect perfection.** Communicate internally that the system is an assistant, not an oracle. Build in a feedback button (\"Was this answer helpful?\") so you can monitor and improve quality.\n\n**Access rights are not an afterthought.** If HR documents and internal financial reports are in the same knowledge base, you must ensure that a customer service employee does not receive answers based on confidential materials. Segment your vector database by audience or role.\n\n## How do you integrate this into an existing FileMaker environment?\n\nFileMaker has no built-in vector database, but the integration is straightforward via the **Data API** and **Perform Script on Server** with cURL calls. In practice, it works like this:\n\n- An employee asks a question in a FileMaker layout.\n- FileMaker sends the question via a cURL script to an external RAG API (a custom Python backend or a service such as OpenAI Assistants with file search).\n- The answer and source reference are returned to FileMaker and displayed on the same screen.\n- Optionally: the question asked and the rating are logged in a FileMaker table for quality monitoring.\n\nThis makes it possible to integrate AI answers into existing workflows — without employees having to switch between systems.\n\n\u003Cimg src=\"\u002Fapi\u002Fknowledge\u002Finline-image\u002F8?w=700&f=webp\" alt=\"FileMaker screen sending a question via API to RAG backend, answer returning with source label\" loading=\"lazy\" class=\"w-full sm:w-1\u002F3 sm:float-left sm:mr-7 mb-5 rounded-2xl border border-[#E8E8ED] bg-[#F5F5F7]\" \u002F>\n\n## Frequently asked questions about RAG systems\n\n**Can a RAG system also answer questions about live data, such as current orders?**\nNot via document searches. For that, you combine RAG with a function calling approach: the LLM calls an API that retrieves real-time data. This is a separate architectural layer.\n\n**How secure is it to send company documents to OpenAI?**\nOpenAI does not use API traffic for training data by default. Even so, it is wise to keep sensitive materials separate. If you want full control, opt for a locally running model (Ollama + LLaMA 3).\n\n**How long does it take to get a first RAG knowledge base live?**\nWith a clear scope and existing documents: two to four weeks for a working prototype. A production-ready system with access rights, an update process, and monitoring: allow two to three months.\n\n**What does it cost?**\nOpenAI API costs for a mid-sized company (a few thousand questions per month) typically range between €50 and €200 per month. Infrastructure costs for a vector database are similarly low. The main investment lies in build time.\n\n---\n\nIf you find that the same questions keep coming up — at your helpdesk, your HR department, or through customer contact — a RAG-based knowledge base is one of the most direct ways to resolve that structurally. Loggix helps companies design and build these kinds of AI integrations: from document ingestion and vector database to the connection with FileMaker or a web application, and the practical consultancy to determine which scope and architecture fits your situation.","\u003Cp>Your helpdesk answers the same ten questions every week. A customer calls because they can't find the returns policy. A new employee asks for the third time how the onboarding process works. The answers already exist — they're just buried in a Word document from 2021, a PDF on a shared drive, or an email thread nobody can find anymore. This article explains how a RAG system turns that scattered knowledge into a searchable, answering knowledge base — and when that's the right choice.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fapi\u002Fknowledge\u002Finline-image\u002F10?w=700&f=webp\" alt=\"scattered documents flowing into a single intelligent search interface with answers\" loading=\"lazy\" class=\"w-full sm:w-1\u002F3 sm:float-left sm:mr-7 mb-5 rounded-2xl border border-[#E8E8ED] bg-[#F5F5F7]\" \u002F>\n\n\u003Ch2>What exactly is a RAG system?\u003C\u002Fh2>\n\u003Cp>RAG stands for \u003Cstrong>Retrieval-Augmented Generation\u003C\u002Fstrong>. It is an architecture in which a language model (such as GPT-4) does not answer from its own training memory, but first retrieves relevant information from \u003Cem>your\u003C\u002Fem> own documents — and uses that as the basis for the answer.\u003C\u002Fp>\n\u003Cp>That sounds technical, but the essence is simple:\u003C\u002Fp>\n\u003Col>\n\u003Cli>An employee or customer asks a question in plain language.\u003C\u002Fli>\n\u003Cli>The system searches your knowledge base for the most relevant passages.\u003C\u002Fli>\n\u003Cli>Those passages are passed to the language model.\u003C\u002Fli>\n\u003Cli>The language model formulates a clear, contextual answer — based on your own content.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>The difference from a standard chatbot: a RAG system doesn't make things up. Every answer is always traceable to a source from your own documentation.\u003C\u002Fp>\n\u003Ch2>Why isn't a standard search function enough?\u003C\u002Fh2>\n\u003Cp>A classic search function works on keywords. An employee searching for "travel expense reimbursement" will only find documents that literally contain those words. But if the policy document refers to "mileage allowance" or "expense claim policy", the search returns nothing.\u003C\u002Fp>\n\u003Cp>A RAG system works with \u003Cstrong>embeddings\u003C\u002Fstrong> — mathematical representations of the meaning of text, stored in a vector database. Two sentences with the same meaning but different words are recognised as semantically similar. The employee doesn't need to know what the document is called or which words it contains — they simply ask their question.\u003C\u002Fp>\n\u003Ch2>How does it work technically under the hood?\u003C\u002Fh2>\n\u003Cp>A working RAG system consists of several layers:\u003C\u002Fp>\n\u003Ch3>1. Document ingestion\u003C\u002Fh3>\n\u003Cp>All source files — Word documents, PDFs, web pages, FileMaker records, email archives — are read in and split into smaller text blocks (chunks). Each block is accompanied by metadata: file name, date, department, version number.\u003C\u002Fp>\n\u003Ch3>2. Generating embeddings\u003C\u002Fh3>\n\u003Cp>Each text block is converted into an embedding vector via a language model (for example OpenAI \u003Ccode>text-embedding-3-large\u003C\u002Fcode> or a local variant via Ollama). These vectors are stored in a vector database such as \u003Cstrong>Pinecone\u003C\u002Fstrong>, \u003Cstrong>Qdrant\u003C\u002Fstrong>, \u003Cstrong>Weaviate\u003C\u002Fstrong>, or simply \u003Cstrong>pgvector\u003C\u002Fstrong> in PostgreSQL.\u003C\u002Fp>\n\u003Ch3>3. Retrieval on a search query\u003C\u002Fh3>\n\u003Cp>When a user asks a question, that question is itself also converted into a vector. The system then searches for the text blocks whose vector is closest — these are the most semantically relevant passages.\u003C\u002Fp>\n\u003Ch3>4. Generating the answer\u003C\u002Fh3>\n\u003Cp>The retrieved passages are passed together with the original question as context to an LLM (language model). The model formulates an answer in plain language, including a reference to the source passage.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fapi\u002Fknowledge\u002Finline-image\u002F9?w=700&f=webp\" alt=\"four-step RAG pipeline: documents, embeddings, vector search, LLM answer with source citation\" loading=\"lazy\" class=\"w-full sm:w-1\u002F3 sm:float-right sm:ml-7 mb-5 rounded-2xl border border-[#E8E8ED] bg-[#F5F5F7]\" \u002F>\n\n\u003Ch2>When is a RAG system the right choice?\u003C\u002Fh2>\n\u003Cp>Not every situation calls for RAG. Here is an honest overview:\u003C\u002Fp>\n\u003Cp>\u003Cstrong>RAG works well when:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Your knowledge base consists of many text-based documents that are updated regularly.\u003C\u002Fli>\n\u003Cli>Questions are open-ended in nature: "How does our returns process work?" or "What is the escalation path for a complaint?"\u003C\u002Fli>\n\u003Cli>You want answers to always be traceable to a source.\u003C\u002Fli>\n\u003Cli>You don't have the time to maintain an FAQ manually.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>RAG is less suitable when:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Questions relate to real-time data (current stock levels, live order status) — that requires a direct database connection, not a document search.\u003C\u002Fli>\n\u003Cli>Your knowledge base consists of fewer than 50 documents that rarely change — in that case, a simple FAQ page is more efficient.\u003C\u002Fli>\n\u003Cli>Answers need to be legally binding without a human review.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>How do you build a RAG system step by step?\u003C\u002Fh2>\n\u003Cp>Here is a practical approach, as we apply it ourselves:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Inventory your knowledge sources.\u003C\u002Fstrong> Where does the knowledge live right now? SharePoint, FileMaker, Google Drive, shared drive, email? Make a list by type and department.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Define the scope.\u003C\u002Fstrong> Start small: one department, one theme (e.g. HR policy or product questions). Expand later.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Choose your ingestion pipeline.\u003C\u002Fstrong> Tools such as LangChain, LlamaIndex, or a custom script read in documents, split them into chunks, and store metadata.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Choose a vector database.\u003C\u002Fstrong> For a first version, pgvector (in PostgreSQL) works well. For scale or advanced filtering, choose Qdrant or Weaviate.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Choose your LLM.\u003C\u002Fstrong> OpenAI GPT-4o for maximum quality, or a local open-source variant (Mistral, LLaMA 3) if privacy is a hard requirement.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Build an interface.\u003C\u002Fstrong> This can be a simple chat window embedded in your intranet, a widget on your customer portal, or an integration directly in FileMaker via the Data API.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Test on edge cases.\u003C\u002Fstrong> Ask questions whose answers you already know. Verify that the system cites sources and does not fabricate answers outside the knowledge base.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Set up an update process.\u003C\u002Fstrong> Who adds new documents? How often are embeddings regenerated when files change? This is the most underestimated step.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2>What are the pitfalls you want to avoid?\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Poor document quality is the biggest risk.\u003C\u002Fstrong> If the source files are outdated, contradictory, or poorly structured, the RAG system will give poor answers — with the confidence of an AI. "Garbage in, garbage out" applies here doubly.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Chunk size has a major impact.\u003C\u002Fstrong> Chunks that are too large contain noise; chunks that are too small lose context. A chunk of 300–600 tokens with 10–20% overlap is a good starting point — but always test this on your own documents.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Users expect perfection.\u003C\u002Fstrong> Communicate internally that the system is an assistant, not an oracle. Build in a feedback button ("Was this answer helpful?") so you can monitor and improve quality.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Access rights are not an afterthought.\u003C\u002Fstrong> If HR documents and internal financial reports are in the same knowledge base, you must ensure that a customer service employee does not receive answers based on confidential materials. Segment your vector database by audience or role.\u003C\u002Fp>\n\u003Ch2>How do you integrate this into an existing FileMaker environment?\u003C\u002Fh2>\n\u003Cp>FileMaker has no built-in vector database, but the integration is straightforward via the \u003Cstrong>Data API\u003C\u002Fstrong> and \u003Cstrong>Perform Script on Server\u003C\u002Fstrong> with cURL calls. In practice, it works like this:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>An employee asks a question in a FileMaker layout.\u003C\u002Fli>\n\u003Cli>FileMaker sends the question via a cURL script to an external RAG API (a custom Python backend or a service such as OpenAI Assistants with file search).\u003C\u002Fli>\n\u003Cli>The answer and source reference are returned to FileMaker and displayed on the same screen.\u003C\u002Fli>\n\u003Cli>Optionally: the question asked and the rating are logged in a FileMaker table for quality monitoring.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This makes it possible to integrate AI answers into existing workflows — without employees having to switch between systems.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fapi\u002Fknowledge\u002Finline-image\u002F8?w=700&f=webp\" alt=\"FileMaker screen sending a question via API to RAG backend, answer returning with source label\" loading=\"lazy\" class=\"w-full sm:w-1\u002F3 sm:float-left sm:mr-7 mb-5 rounded-2xl border border-[#E8E8ED] bg-[#F5F5F7]\" \u002F>\n\n\u003Ch2>Frequently asked questions about RAG systems\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Can a RAG system also answer questions about live data, such as current orders?\u003C\u002Fstrong>\nNot via document searches. For that, you combine RAG with a function calling approach: the LLM calls an API that retrieves real-time data. This is a separate architectural layer.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>How secure is it to send company documents to OpenAI?\u003C\u002Fstrong>\nOpenAI does not use API traffic for training data by default. Even so, it is wise to keep sensitive materials separate. If you want full control, opt for a locally running model (Ollama + LLaMA 3).\u003C\u002Fp>\n\u003Cp>\u003Cstrong>How long does it take to get a first RAG knowledge base live?\u003C\u002Fstrong>\nWith a clear scope and existing documents: two to four weeks for a working prototype. A production-ready system with access rights, an update process, and monitoring: allow two to three months.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What does it cost?\u003C\u002Fstrong>\nOpenAI API costs for a mid-sized company (a few thousand questions per month) typically range between €50 and €200 per month. Infrastructure costs for a vector database are similarly low. The main investment lies in build time.\u003C\u002Fp>\n\u003Chr>\n\u003Cp>If you find that the same questions keep coming up — at your helpdesk, your HR department, or through customer contact — a RAG-based knowledge base is one of the most direct ways to resolve that structurally. Loggix helps companies design and build these kinds of AI integrations: from document ingestion and vector database to the connection with FileMaker or a web application, and the practical consultancy to determine which scope and architecture fits your situation.\u003C\u002Fp>\n","2026-07-22",1784705735000,[86,87,88,23,89,90,91,92,93],"AI","RAG","kennisbank","LLM","vectordatabase","bedrijfssoftware","kennismanagement","automatisering","\u002Fapi\u002Fknowledge\u002Fimage\u002F110\u002F?v=a1b103ad1a86",{"id":96,"idKnowledge":97,"idDomain":15,"idCluster":15,"slug":98,"title":99,"description":100,"bodyMarkdown":101,"bodyHtml":102,"author":39,"date":103,"createdAt":104,"topics":105,"image":107,"hasDownload":28,"fileName":15,"youtubeId":27},"108","6CD2CBFD-F10E-A442-B43A-1A7141D99E1F","maatwerk-software-die-uw-processen-vooruithelpt","Custom software that moves your processes forward","Custom software connects your processes, data and teams. Read when custom development is cost-effective and how to modernise existing systems practically and thoughtfully.","A planner who has to retype data three times. An account manager who is unsure which customer information is current. A FileMaker database that is still business-critical but cannot communicate with accounting, a webshop, or a transport partner. These are not isolated IT problems. They are day-to-day process problems for which **custom software** often offers a better solution than yet another spreadsheet or standalone off-the-shelf package.\n\nThe question here is not whether software sounds modern enough. The relevant question is whether your employees can work faster, with fewer errors, and with better insight. Good custom solutions align with how your organisation earns, delivers, plans, and reports. They do not force your processes into a predefined straitjacket.\n\n## What custom software means in practice\n\nCustom software is an application, extension, or platform built around your specific way of working. That can be an entirely new system, but far more often it starts with improving what is already there. Think of an existing FileMaker solution extended with a customer portal, a mobile app for field staff, or a [connection to Exact](https:\u002F\u002Floggix.com\u002Fblog\u002Ffilemaker-koppelen-met-exact-zo-werkt-het\u002F), AFAS, Microsoft 365, a webshop, or a logistics service provider.\n\nThe difference from standard software lies not only in functionality. It lies above all in the fit with day-to-day reality. An off-the-shelf package often includes many features you never use, while a critical exception in your process is precisely what is missing. Custom software focuses on those exceptions, roles, decision points, and data flows that distinguish your organisation or cause unnecessary delays.\n\nThat does not mean everything has to be built from scratch. A pragmatic approach combines existing systems where they work well with targeted development where the greatest gains lie. Your accounting package does not need to be replaced, for example, if a reliable API integration makes the right data available at the right time.\n\n## When custom software becomes cost-effective\n\nCustom software is not automatically the right choice. If your process is straightforward and a proven off-the-shelf solution supports it well, configuration is usually faster and more cost-effective. It becomes interesting when employees routinely have to use workarounds to get their work done.\n\nYou can see this, for example, in manual exports and imports, duplicate data entry, emails that serve as process monitoring, and spreadsheets that hold the actual truth. When different departments each work with their own files or systems, risks arise as well. Not only the risk of errors, but also of delays, unclear responsibilities, and poor management information.\n\nA custom development project is often easy to justify when it resolves one or more of these bottlenecks:\n\n-   recurring manual work that can be automated;\n-   error-prone data transfer between systems;\n-   limited access to current information for employees or customers;\n-   an outdated internal application that still contains valuable business logic;\n-   a growing process that can no longer be managed with separate tools.\n\nThe business case does not have to be solely about hours saved. Less rework, shorter lead times, better customer communication, and reduced dependency on individual employees are at least as relevant. Especially for processes that directly affect quotation, order, delivery, service, or invoicing.\n\n## Start with the work process, not the technology\n\nA good project does not start with the choice of a programming language or a list of screens. It starts with a clear analysis of the work that needs to be done. What event triggers the process? Who enters which data? Where does verification take place? What information is needed to make a decision? And where does it currently go wrong or cost unnecessary time?\n\nIt is wise to distinguish between the desired situation and existing habits. Not every manual step needs to be digitised. Sometimes a process originated because an old system had limitations. When those limitations disappear, the way of working can become simpler.\n\nThen work in manageable portions. Start, for example, with order intake and data validation, then move on to planning and status communication. This produces usable software more quickly and allows your team to give feedback on something concrete. A large project without interim results increases the risk that months are spent building on assumptions that turn out not to hold in practice.\n\nOwnership also deserves attention. Determine who within the organisation makes substantive decisions, who tests, and who is responsible for changes after delivery. Custom software becomes more valuable as it can evolve with your business. That requires clear priorities, documentation, and a manageable technical foundation.\n\n## Existing FileMaker systems are often a good starting point\n\nMany organisations look at an older FileMaker database and see mainly an outdated interface or limited access outside the office. But behind such a solution often lies years of accumulated business knowledge: calculation rules, customer agreements, inventory logic, planning steps, and exceptions that are not recorded anywhere else. Discarding that value and starting over is rarely the cheapest or safest route.\n\nModernisation can be done step by step. A FileMaker solution can be cleaned up, stabilised, and extended with modern interfaces, API integrations, and access management. Certain processes can [move to a web application](https:\u002F\u002Floggix.com\u002Fblog\u002Flegacy-database-omzetten-naar-webapp\u002F), while FileMaker remains the reliable source for core data for the time being. For field staff or warehouse teams, a mobile application can provide exactly the features needed there, without users having to navigate through a full back-office system.\n\nThe technical choice depends on the objective. Sometimes an extension within FileMaker is sufficient. Sometimes a separate web or mobile layer makes more sense — for example, for customers, suppliers, or large numbers of external users. What matters is that the data structure, security, and integrations are set up carefully from the outset. A polished screen solves no problem if the data remains unreliable or processes stall behind the scenes.\n\n## Integrations turn separate systems into one working whole\n\nMost operational gains come not from one extra screen, but from eliminating handover moments. [API integrations](https:\u002F\u002Floggix.com\u002Fapis\u002F) can automatically exchange customer data, orders, inventory, invoices, tickets, or status updates between systems. This means employees no longer need to check which system is leading or manually copy data from one place to another.\n\nFor example, an order from a webshop can automatically enter your internal process, after which inventory, planning, and invoicing are updated. Or a service technician on-site can immediately see the correct installation history and log their work without paper forms. The exact solution differs per organisation, but the principle remains the same: data is recorded correctly once and then used wherever it is needed.\n\nIntegrations do require discipline. Not every integration needs to be real-time, and real-time is not always better. For some processes, a periodic synchronisation is sufficient and easier to manage. Therefore, determine per data flow what speed, error handling, and control are actually required.\n\n## AI is most useful when it improves a concrete step\n\nPractical AI can strengthen custom software, but only when the application is clear. Think of summarising lengthy customer communications, classifying incoming requests, suggesting reply texts, or making technical documents easier to search. The technology should support employees, not create an additional layer of control that costs more time than it saves.\n\nFor processes involving sensitive data, boundaries are essential. Which information may an AI service process? Who reviews a suggestion before it goes to a customer? And how is it recorded which data was used as a source? A small, well-defined pilot within an existing process usually provides more insight than a broad AI project without a clear owner.\n\n## Costs, maintenance, and long-term decisions\n\nThe costs of custom software comprise more than the initial build phase. Analysis, development, testing, hosting, security, support, and future changes are all part of the total picture. On the other hand, a solution that fits your processes precisely often has lower hidden costs than a package that constantly requires manual corrections, additional tools, and workarounds.\n\nTherefore, do not only ask what the first version costs, but also how changes will be managed. Is the solution easy to document? Can new features be added independently? Can integrations be monitored? And does it remain clear which data is leading? A maintainable solution is not necessarily the most extensive solution. A clear, well-defined foundation is often the wisest investment.\n\nAt Loggix, the focus is therefore on modernising without unnecessary disruption. Existing systems — and FileMaker environments in particular — can often continue to deliver value for much longer when they are selectively extended with integrations, apps, and automation.\n\nThe best next step is usually small and concrete: choose one process where errors, waiting time, or duplicate work are felt every day. Map the current data flow, determine what a better approach would deliver, and improve that part first. That way, software does not become a large change programme on paper, but a practical tool that makes every working day noticeably better. Test","\u003Cp>A planner who has to retype data three times. An account manager who is unsure which customer information is current. A FileMaker database that is still business-critical but cannot communicate with accounting, a webshop, or a transport partner. These are not isolated IT problems. They are day-to-day process problems for which \u003Cstrong>custom software\u003C\u002Fstrong> often offers a better solution than yet another spreadsheet or standalone off-the-shelf package.\u003C\u002Fp>\n\u003Cp>The question here is not whether software sounds modern enough. The relevant question is whether your employees can work faster, with fewer errors, and with better insight. Good custom solutions align with how your organisation earns, delivers, plans, and reports. They do not force your processes into a predefined straitjacket.\u003C\u002Fp>\n\u003Ch2>What custom software means in practice\u003C\u002Fh2>\n\u003Cp>Custom software is an application, extension, or platform built around your specific way of working. That can be an entirely new system, but far more often it starts with improving what is already there. Think of an existing FileMaker solution extended with a customer portal, a mobile app for field staff, or a \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Ffilemaker-koppelen-met-exact-zo-werkt-het\u002F\">connection to Exact\u003C\u002Fa>, AFAS, Microsoft 365, a webshop, or a logistics service provider.\u003C\u002Fp>\n\u003Cp>The difference from standard software lies not only in functionality. It lies above all in the fit with day-to-day reality. An off-the-shelf package often includes many features you never use, while a critical exception in your process is precisely what is missing. Custom software focuses on those exceptions, roles, decision points, and data flows that distinguish your organisation or cause unnecessary delays.\u003C\u002Fp>\n\u003Cp>That does not mean everything has to be built from scratch. A pragmatic approach combines existing systems where they work well with targeted development where the greatest gains lie. Your accounting package does not need to be replaced, for example, if a reliable API integration makes the right data available at the right time.\u003C\u002Fp>\n\u003Ch2>When custom software becomes cost-effective\u003C\u002Fh2>\n\u003Cp>Custom software is not automatically the right choice. If your process is straightforward and a proven off-the-shelf solution supports it well, configuration is usually faster and more cost-effective. It becomes interesting when employees routinely have to use workarounds to get their work done.\u003C\u002Fp>\n\u003Cp>You can see this, for example, in manual exports and imports, duplicate data entry, emails that serve as process monitoring, and spreadsheets that hold the actual truth. When different departments each work with their own files or systems, risks arise as well. Not only the risk of errors, but also of delays, unclear responsibilities, and poor management information.\u003C\u002Fp>\n\u003Cp>A custom development project is often easy to justify when it resolves one or more of these bottlenecks:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>recurring manual work that can be automated;\u003C\u002Fli>\n\u003Cli>error-prone data transfer between systems;\u003C\u002Fli>\n\u003Cli>limited access to current information for employees or customers;\u003C\u002Fli>\n\u003Cli>an outdated internal application that still contains valuable business logic;\u003C\u002Fli>\n\u003Cli>a growing process that can no longer be managed with separate tools.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The business case does not have to be solely about hours saved. Less rework, shorter lead times, better customer communication, and reduced dependency on individual employees are at least as relevant. Especially for processes that directly affect quotation, order, delivery, service, or invoicing.\u003C\u002Fp>\n\u003Ch2>Start with the work process, not the technology\u003C\u002Fh2>\n\u003Cp>A good project does not start with the choice of a programming language or a list of screens. It starts with a clear analysis of the work that needs to be done. What event triggers the process? Who enters which data? Where does verification take place? What information is needed to make a decision? And where does it currently go wrong or cost unnecessary time?\u003C\u002Fp>\n\u003Cp>It is wise to distinguish between the desired situation and existing habits. Not every manual step needs to be digitised. Sometimes a process originated because an old system had limitations. When those limitations disappear, the way of working can become simpler.\u003C\u002Fp>\n\u003Cp>Then work in manageable portions. Start, for example, with order intake and data validation, then move on to planning and status communication. This produces usable software more quickly and allows your team to give feedback on something concrete. A large project without interim results increases the risk that months are spent building on assumptions that turn out not to hold in practice.\u003C\u002Fp>\n\u003Cp>Ownership also deserves attention. Determine who within the organisation makes substantive decisions, who tests, and who is responsible for changes after delivery. Custom software becomes more valuable as it can evolve with your business. That requires clear priorities, documentation, and a manageable technical foundation.\u003C\u002Fp>\n\u003Ch2>Existing FileMaker systems are often a good starting point\u003C\u002Fh2>\n\u003Cp>Many organisations look at an older FileMaker database and see mainly an outdated interface or limited access outside the office. But behind such a solution often lies years of accumulated business knowledge: calculation rules, customer agreements, inventory logic, planning steps, and exceptions that are not recorded anywhere else. Discarding that value and starting over is rarely the cheapest or safest route.\u003C\u002Fp>\n\u003Cp>Modernisation can be done step by step. A FileMaker solution can be cleaned up, stabilised, and extended with modern interfaces, API integrations, and access management. Certain processes can \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Flegacy-database-omzetten-naar-webapp\u002F\">move to a web application\u003C\u002Fa>, while FileMaker remains the reliable source for core data for the time being. For field staff or warehouse teams, a mobile application can provide exactly the features needed there, without users having to navigate through a full back-office system.\u003C\u002Fp>\n\u003Cp>The technical choice depends on the objective. Sometimes an extension within FileMaker is sufficient. Sometimes a separate web or mobile layer makes more sense — for example, for customers, suppliers, or large numbers of external users. What matters is that the data structure, security, and integrations are set up carefully from the outset. A polished screen solves no problem if the data remains unreliable or processes stall behind the scenes.\u003C\u002Fp>\n\u003Ch2>Integrations turn separate systems into one working whole\u003C\u002Fh2>\n\u003Cp>Most operational gains come not from one extra screen, but from eliminating handover moments. \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fapis\u002F\">API integrations\u003C\u002Fa> can automatically exchange customer data, orders, inventory, invoices, tickets, or status updates between systems. This means employees no longer need to check which system is leading or manually copy data from one place to another.\u003C\u002Fp>\n\u003Cp>For example, an order from a webshop can automatically enter your internal process, after which inventory, planning, and invoicing are updated. Or a service technician on-site can immediately see the correct installation history and log their work without paper forms. The exact solution differs per organisation, but the principle remains the same: data is recorded correctly once and then used wherever it is needed.\u003C\u002Fp>\n\u003Cp>Integrations do require discipline. Not every integration needs to be real-time, and real-time is not always better. For some processes, a periodic synchronisation is sufficient and easier to manage. Therefore, determine per data flow what speed, error handling, and control are actually required.\u003C\u002Fp>\n\u003Ch2>AI is most useful when it improves a concrete step\u003C\u002Fh2>\n\u003Cp>Practical AI can strengthen custom software, but only when the application is clear. Think of summarising lengthy customer communications, classifying incoming requests, suggesting reply texts, or making technical documents easier to search. The technology should support employees, not create an additional layer of control that costs more time than it saves.\u003C\u002Fp>\n\u003Cp>For processes involving sensitive data, boundaries are essential. Which information may an AI service process? Who reviews a suggestion before it goes to a customer? And how is it recorded which data was used as a source? A small, well-defined pilot within an existing process usually provides more insight than a broad AI project without a clear owner.\u003C\u002Fp>\n\u003Ch2>Costs, maintenance, and long-term decisions\u003C\u002Fh2>\n\u003Cp>The costs of custom software comprise more than the initial build phase. Analysis, development, testing, hosting, security, support, and future changes are all part of the total picture. On the other hand, a solution that fits your processes precisely often has lower hidden costs than a package that constantly requires manual corrections, additional tools, and workarounds.\u003C\u002Fp>\n\u003Cp>Therefore, do not only ask what the first version costs, but also how changes will be managed. Is the solution easy to document? Can new features be added independently? Can integrations be monitored? And does it remain clear which data is leading? A maintainable solution is not necessarily the most extensive solution. A clear, well-defined foundation is often the wisest investment.\u003C\u002Fp>\n\u003Cp>At Loggix, the focus is therefore on modernising without unnecessary disruption. Existing systems — and FileMaker environments in particular — can often continue to deliver value for much longer when they are selectively extended with integrations, apps, and automation.\u003C\u002Fp>\n\u003Cp>The best next step is usually small and concrete: choose one process where errors, waiting time, or duplicate work are felt every day. Map the current data flow, determine what a better approach would deliver, and improve that part first. That way, software does not become a large change programme on paper, but a practical tool that makes every working day noticeably better. Test\u003C\u002Fp>\n","2026-07-18",1784361887000,[23,106],"Maatwerk","\u002Fapi\u002Fknowledge\u002Fimage\u002F108\u002F?v=b5c5bf5290f1",{"id":109,"idKnowledge":110,"idDomain":15,"idCluster":15,"slug":111,"title":112,"description":113,"bodyMarkdown":114,"bodyHtml":115,"author":39,"date":116,"createdAt":117,"topics":118,"image":120,"hasDownload":28,"fileName":15,"youtubeId":27},"107","2B270772-3BC7-0841-96E3-5C747332B707","een-mobiele-app-op-filemaker-bouwen-voor-uw-team","Building a mobile app on FileMaker for your team","Building a mobile app on FileMaker for your processes? Read which approach fits, how to connect data securely, and when a separate app is the better choice.","An employee standing at a client's site, processing an order in a warehouse, or carrying out an inspection on location has little use for a database that only works well behind a desk. **Building a mobile app on FileMaker** can bridge that gap, provided the app aligns with the work people actually perform. The goal is not to copy all the screens of your existing system to a phone. The goal is to make the right information and actions available at the moment they are needed.\n\nFor organisations with an existing FileMaker solution, this is often a [logical modernisation path](https:\u002F\u002Floggix.com\u002Fblog\u002Ffilemaker-systeem-moderniseren-zonder-risico\u002F). You retain processes, data, and accumulated knowledge, while field service staff, planners, technicians, or account managers can work more efficiently. The choice of technical form then determines how much you invest, how well the app works offline, and how far you can go with features such as camera, location, push notifications, and integrations with other systems.\n\n## Start with the mobile work moment\n\nThe best mobile applications do not begin with a screen design, but with a concrete action. A technician wants to open a work order, add photos, register materials used, and obtain a signature. A warehouse employee wants to scan a barcode, confirm a stock location, and record a discrepancy. A salesperson wants to consult customer information and enter a visit report immediately.\n\nFor each user group, therefore, map out what they need to be able to view, modify, and confirm while on the move. Also look at what they do not need. A mobile interface quickly becomes cluttered when all the capabilities of a desktop solution are crammed into it. Fewer fields, clear buttons, and a fixed sequence within a task usually deliver more value than a complete copy of the existing FileMaker file.\n\nIt helps to test the process against real-world conditions. Is there always an internet connection? Does someone need to be able to capture data while wearing gloves? Is a tablet used in a vehicle, or a phone at a client's premises? Those answers determine not only the design, but also the chosen technology.\n\n## Which route suits your FileMaker app?\n\nFileMaker offers several ways to make a mobile working environment available. There is no universally best option. The right choice depends on the device, the desired user experience, the degree of offline working, and the integrations required.\n\n### FileMaker Go for iPhone and iPad\n\nFileMaker Go is the most direct route for organisations working on iPhone or iPad. Your existing FileMaker solution can be adapted with mobile layouts, scripts, and navigation. Employees then use the FileMaker Go app to work with the database.\n\nThis is often a cost-efficient choice when processes are already well established in FileMaker and the target group works with managed Apple devices. Camera, barcode functions, location, and signatures can all be used effectively within such a solution. A file can also be used locally on a device when employees need to work temporarily without a connection, although synchronisation then requires careful design.\n\nThe downside is clear: FileMaker Go focuses on Apple devices. In addition, the experience remains recognisable as a FileMaker app, even when the layouts are excellently configured for mobile use. For many internal applications, that is not a problem. For an app you offer to customers, partners, or a broad Android audience, a different approach may be more suitable.\n\n### FileMaker WebDirect in the browser\n\nWith WebDirect, you make a FileMaker solution accessible via a browser. That is practical when users work on different devices and you do not want to distribute a separate app. For simple lookup screens, forms, portals, and internal processes, this can be a fitting solution.\n\nWebDirect does require discipline in design. Not every desktop layout works comfortably on a smaller screen, and complex scripts or heavy screens can slow down the experience. Test with realistic numbers of users and on the devices your employees actually use. A browser-based solution is particularly strong when accessibility is more important than in-depth mobile features or offline use.\n\n### A separate mobile app with FileMaker as the core system\n\nSometimes a dedicated iOS, Android, or cross-platform app is the better route. In that case, FileMaker remains the system where processes and data management come together, while the mobile app [communicates via APIs](https:\u002F\u002Floggix.com\u002Fapis\u002F) with the underlying data and services.\n\nThis approach offers more freedom in user experience, offline storage, push notifications, device features, and distribution via app stores or enterprise management. It is also often the logical choice when external customers gain access, when Android is essential, or when the app becomes part of a broader digital service offering.\n\nThis comes with a greater investment. You are not only building screens, but also an API layer, security, error handling, version management, and a synchronisation strategy. That is not a reason to avoid the route, but it is a reason to choose it for processes where reach, ease of use, and scalability justify that investment.\n\n## Building a mobile app on FileMaker requires a clear architecture\n\nThe user interface often receives attention first, but the architecture determines whether the solution remains reliable as usage grows. Especially with an existing FileMaker environment, it is wise to assess early on where the data comes from, which data may be stored on mobile devices, and which systems need to be connected.\n\nA field service app might, for example, use customer and work order data from FileMaker, retrieve stock from an ERP system, and store documents in cloud storage. When employees enter changes on the go, it must be clear which system is the leading source of truth. Without that agreement, duplicate data, conflicts, and manual corrections arise — precisely the kind of work the app should reduce.\n\nSecurity belongs here too. Users should only see the customers, orders, and documents required for their role. Think about authentication, roles and permissions, encrypted communication, and a policy for devices that are lost or replaced by employees. For personal data, financial data, or service history, this is a prerequisite, not an extra feature for later.\n\nOffline working also deserves an explicit decision. An app that always needs to be online is simpler to build and manage. But in basements, production halls, rural areas, or on construction sites, that assumption is often unrealistic. Offline support means specifying which data is pre-loaded, how changes are saved locally, and what happens when two users modify the same record. That requires more preparation, but prevents frustration in the field.\n\n## Build in short, usable steps\n\nA mobile extension does not have to be a multi-year replacement project. Especially with FileMaker, it is often possible to get a defined process working first and then expand it in a targeted way. Choose, for example, one workflow with a clear benefit: digital work orders, mobile stock registration, or inspection rounds.\n\nThen create a first version for a small group of users. Measure not only whether the app works technically, but also whether the action is faster, whether data is filled in more completely, and whether the back office needs to correct less. A form that is theoretically complete but requires too many steps on location does not deliver an improvement.\n\nOnly after that should you expand with features that demonstrably add value. These could be photos, barcodes, digital signatures, route data, document generation, or links with planning and invoicing. This sequence keeps the investment manageable and gives users space to grow into the new way of working.\n\n## Common mistakes in mobile FileMaker projects\n\nThe most common mistake is literally shrinking a desktop app. Small text, long portals, and dozens of fields make a mobile process slow and error-prone. It is better to design per task: open, check, record, confirm, and complete.\n\nA second mistake is thinking about integrations too late. When a mobile app [needs data from Exact](https:\u002F\u002Floggix.com\u002Fblog\u002Ffilemaker-koppelen-met-exact-zo-werkt-het\u002F), an ERP system, a planning package, or a customer portal, the data exchange must be part of the design from the outset. Manual exporting and importing may work temporarily, but is rarely a good foundation for a process used daily.\n\nThird, offline use is sometimes promised without working out the consequences. Storing a few records locally is different from reliably synchronising a full working day. Make this choice deliberately and limit offline functionality to what employees genuinely need.\n\nFinally, do not underestimate management. Mobile applications require support, monitoring, updates, and clear ownership. Who manages users? Who monitors error messages? Who decides which change gets priority? With those agreements in place, an app remains usable long after the initial delivery.\n\n## When is this a worthwhile investment?\n\nA mobile extension of FileMaker is particularly interesting when employees currently process information on paper, in separate apps, or only at the end of the day. The benefit then lies in less duplicate work, more up-to-date data, faster follow-up, and fewer input errors. For a small team with occasional mobile use, a well-configured FileMaker Go solution may already be sufficient. For a growing network of external users, a separate app with API integrations may be the wiser choice.\n\nLoggix helps organisations make that assessment in a practical way: not by unnecessarily replacing an existing system, but by determining which extension meaningfully improves the day-to-day process. Start with the work that gets stuck outside the office. Once that work becomes faster, simpler, and easier to record, your FileMaker investment regains value where it matters most: in execution.","\u003Cp>An employee standing at a client's site, processing an order in a warehouse, or carrying out an inspection on location has little use for a database that only works well behind a desk. \u003Cstrong>Building a mobile app on FileMaker\u003C\u002Fstrong> can bridge that gap, provided the app aligns with the work people actually perform. The goal is not to copy all the screens of your existing system to a phone. The goal is to make the right information and actions available at the moment they are needed.\u003C\u002Fp>\n\u003Cp>For organisations with an existing FileMaker solution, this is often a \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Ffilemaker-systeem-moderniseren-zonder-risico\u002F\">logical modernisation path\u003C\u002Fa>. You retain processes, data, and accumulated knowledge, while field service staff, planners, technicians, or account managers can work more efficiently. The choice of technical form then determines how much you invest, how well the app works offline, and how far you can go with features such as camera, location, push notifications, and integrations with other systems.\u003C\u002Fp>\n\u003Ch2>Start with the mobile work moment\u003C\u002Fh2>\n\u003Cp>The best mobile applications do not begin with a screen design, but with a concrete action. A technician wants to open a work order, add photos, register materials used, and obtain a signature. A warehouse employee wants to scan a barcode, confirm a stock location, and record a discrepancy. A salesperson wants to consult customer information and enter a visit report immediately.\u003C\u002Fp>\n\u003Cp>For each user group, therefore, map out what they need to be able to view, modify, and confirm while on the move. Also look at what they do not need. A mobile interface quickly becomes cluttered when all the capabilities of a desktop solution are crammed into it. Fewer fields, clear buttons, and a fixed sequence within a task usually deliver more value than a complete copy of the existing FileMaker file.\u003C\u002Fp>\n\u003Cp>It helps to test the process against real-world conditions. Is there always an internet connection? Does someone need to be able to capture data while wearing gloves? Is a tablet used in a vehicle, or a phone at a client's premises? Those answers determine not only the design, but also the chosen technology.\u003C\u002Fp>\n\u003Ch2>Which route suits your FileMaker app?\u003C\u002Fh2>\n\u003Cp>FileMaker offers several ways to make a mobile working environment available. There is no universally best option. The right choice depends on the device, the desired user experience, the degree of offline working, and the integrations required.\u003C\u002Fp>\n\u003Ch3>FileMaker Go for iPhone and iPad\u003C\u002Fh3>\n\u003Cp>FileMaker Go is the most direct route for organisations working on iPhone or iPad. Your existing FileMaker solution can be adapted with mobile layouts, scripts, and navigation. Employees then use the FileMaker Go app to work with the database.\u003C\u002Fp>\n\u003Cp>This is often a cost-efficient choice when processes are already well established in FileMaker and the target group works with managed Apple devices. Camera, barcode functions, location, and signatures can all be used effectively within such a solution. A file can also be used locally on a device when employees need to work temporarily without a connection, although synchronisation then requires careful design.\u003C\u002Fp>\n\u003Cp>The downside is clear: FileMaker Go focuses on Apple devices. In addition, the experience remains recognisable as a FileMaker app, even when the layouts are excellently configured for mobile use. For many internal applications, that is not a problem. For an app you offer to customers, partners, or a broad Android audience, a different approach may be more suitable.\u003C\u002Fp>\n\u003Ch3>FileMaker WebDirect in the browser\u003C\u002Fh3>\n\u003Cp>With WebDirect, you make a FileMaker solution accessible via a browser. That is practical when users work on different devices and you do not want to distribute a separate app. For simple lookup screens, forms, portals, and internal processes, this can be a fitting solution.\u003C\u002Fp>\n\u003Cp>WebDirect does require discipline in design. Not every desktop layout works comfortably on a smaller screen, and complex scripts or heavy screens can slow down the experience. Test with realistic numbers of users and on the devices your employees actually use. A browser-based solution is particularly strong when accessibility is more important than in-depth mobile features or offline use.\u003C\u002Fp>\n\u003Ch3>A separate mobile app with FileMaker as the core system\u003C\u002Fh3>\n\u003Cp>Sometimes a dedicated iOS, Android, or cross-platform app is the better route. In that case, FileMaker remains the system where processes and data management come together, while the mobile app \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fapis\u002F\">communicates via APIs\u003C\u002Fa> with the underlying data and services.\u003C\u002Fp>\n\u003Cp>This approach offers more freedom in user experience, offline storage, push notifications, device features, and distribution via app stores or enterprise management. It is also often the logical choice when external customers gain access, when Android is essential, or when the app becomes part of a broader digital service offering.\u003C\u002Fp>\n\u003Cp>This comes with a greater investment. You are not only building screens, but also an API layer, security, error handling, version management, and a synchronisation strategy. That is not a reason to avoid the route, but it is a reason to choose it for processes where reach, ease of use, and scalability justify that investment.\u003C\u002Fp>\n\u003Ch2>Building a mobile app on FileMaker requires a clear architecture\u003C\u002Fh2>\n\u003Cp>The user interface often receives attention first, but the architecture determines whether the solution remains reliable as usage grows. Especially with an existing FileMaker environment, it is wise to assess early on where the data comes from, which data may be stored on mobile devices, and which systems need to be connected.\u003C\u002Fp>\n\u003Cp>A field service app might, for example, use customer and work order data from FileMaker, retrieve stock from an ERP system, and store documents in cloud storage. When employees enter changes on the go, it must be clear which system is the leading source of truth. Without that agreement, duplicate data, conflicts, and manual corrections arise — precisely the kind of work the app should reduce.\u003C\u002Fp>\n\u003Cp>Security belongs here too. Users should only see the customers, orders, and documents required for their role. Think about authentication, roles and permissions, encrypted communication, and a policy for devices that are lost or replaced by employees. For personal data, financial data, or service history, this is a prerequisite, not an extra feature for later.\u003C\u002Fp>\n\u003Cp>Offline working also deserves an explicit decision. An app that always needs to be online is simpler to build and manage. But in basements, production halls, rural areas, or on construction sites, that assumption is often unrealistic. Offline support means specifying which data is pre-loaded, how changes are saved locally, and what happens when two users modify the same record. That requires more preparation, but prevents frustration in the field.\u003C\u002Fp>\n\u003Ch2>Build in short, usable steps\u003C\u002Fh2>\n\u003Cp>A mobile extension does not have to be a multi-year replacement project. Especially with FileMaker, it is often possible to get a defined process working first and then expand it in a targeted way. Choose, for example, one workflow with a clear benefit: digital work orders, mobile stock registration, or inspection rounds.\u003C\u002Fp>\n\u003Cp>Then create a first version for a small group of users. Measure not only whether the app works technically, but also whether the action is faster, whether data is filled in more completely, and whether the back office needs to correct less. A form that is theoretically complete but requires too many steps on location does not deliver an improvement.\u003C\u002Fp>\n\u003Cp>Only after that should you expand with features that demonstrably add value. These could be photos, barcodes, digital signatures, route data, document generation, or links with planning and invoicing. This sequence keeps the investment manageable and gives users space to grow into the new way of working.\u003C\u002Fp>\n\u003Ch2>Common mistakes in mobile FileMaker projects\u003C\u002Fh2>\n\u003Cp>The most common mistake is literally shrinking a desktop app. Small text, long portals, and dozens of fields make a mobile process slow and error-prone. It is better to design per task: open, check, record, confirm, and complete.\u003C\u002Fp>\n\u003Cp>A second mistake is thinking about integrations too late. When a mobile app \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Ffilemaker-koppelen-met-exact-zo-werkt-het\u002F\">needs data from Exact\u003C\u002Fa>, an ERP system, a planning package, or a customer portal, the data exchange must be part of the design from the outset. Manual exporting and importing may work temporarily, but is rarely a good foundation for a process used daily.\u003C\u002Fp>\n\u003Cp>Third, offline use is sometimes promised without working out the consequences. Storing a few records locally is different from reliably synchronising a full working day. Make this choice deliberately and limit offline functionality to what employees genuinely need.\u003C\u002Fp>\n\u003Cp>Finally, do not underestimate management. Mobile applications require support, monitoring, updates, and clear ownership. Who manages users? Who monitors error messages? Who decides which change gets priority? With those agreements in place, an app remains usable long after the initial delivery.\u003C\u002Fp>\n\u003Ch2>When is this a worthwhile investment?\u003C\u002Fh2>\n\u003Cp>A mobile extension of FileMaker is particularly interesting when employees currently process information on paper, in separate apps, or only at the end of the day. The benefit then lies in less duplicate work, more up-to-date data, faster follow-up, and fewer input errors. For a small team with occasional mobile use, a well-configured FileMaker Go solution may already be sufficient. For a growing network of external users, a separate app with API integrations may be the wiser choice.\u003C\u002Fp>\n\u003Cp>Loggix helps organisations make that assessment in a practical way: not by unnecessarily replacing an existing system, but by determining which extension meaningfully improves the day-to-day process. Start with the work that gets stuck outside the office. Once that work becomes faster, simpler, and easier to record, your FileMaker investment regains value where it matters most: in execution.\u003C\u002Fp>\n","2026-07-16",1784189109000,[23,119],"Mobiele App","\u002Fapi\u002Fknowledge\u002Fimage\u002F107\u002F?v=81363eebc29c",{"id":122,"idKnowledge":123,"idDomain":15,"idCluster":15,"slug":124,"title":125,"description":126,"bodyMarkdown":127,"bodyHtml":128,"author":39,"date":129,"createdAt":130,"topics":131,"image":133,"hasDownload":28,"fileName":15,"youtubeId":27},"106","68D8CAFA-C67B-2346-8C65-59F8544C43B7","gids-voor-legacy-software-modernisering","Guide to legacy software modernization","This guide to legacy software modernization helps you preserve, connect, and incrementally improve processes without disrupting daily operations.","A warehouse employee who enters data into a FileMaker database, then copies it into Excel, and then drafts an invoice email is not dealing with an outdated screen problem. He is dealing with a process risk. Every manual transfer costs time, makes errors more likely, and keeps valuable business information locked away. This guide to legacy software modernization is therefore not about replacing technology because it is old. It is about targeted improvements that make your operation faster, more reliable, and easier to manage.\n\nMany organizations have been running on custom software for years — software that knows their way of working better than any standard package ever could. Especially with FileMaker solutions, a great deal of accumulated knowledge is often embedded: non-standard pricing agreements, production controls, customer files, scheduling rules, and exceptions that are perfectly normal for the business. You want to preserve that value. At the same time, a system should not become a brake on growth, integrations, or secure working.\n\n## When is legacy software modernization necessary?\n\nLegacy software is not automatically software that is old. A FileMaker system from 2012 that runs stably, is well maintained, and delivers the right information does not need to be replaced immediately. The trigger usually lies in the gap between what the system can do and what the organization now needs.\n\nThat gap becomes visible when employees enter the same data in multiple places, when reports can only be produced with a great deal of manual effort, or when critical knowledge rests with a single administrator. A lack of integrations with accounting, e-commerce, CRM, logistics software, or Microsoft 365 is also often a concrete signal. The database still works, but the process surrounding it has become unnecessarily cumbersome.\n\nTechnical signals count as well. Think of outdated plug-ins, slow screens with growing data files, weak user rights management, dependency on local files, or a solution that does not work comfortably on an iPad, phone, or via a browser. The right question is not: do we need to rebuild everything? The better question is: which limitation is currently causing the most delay, errors, or risk?\n\n## Start with business processes, not a new platform\n\nA modernization effort often stalls when the choice of technology is the starting point. A new platform may sound appealing, but it does not resolve an unclear workflow. First map out where information is created, who uses it, what decision is made with it, and where data leaves the system.\n\nTake order processing as an example. An order can come in via email, a web form, an account manager, or an EDI connection. Then stock must be checked, a price determined, a pick instruction created, and an invoice sent. If three of those steps happen outside the central application, there is not only a loss of time. It also becomes harder to see where an order is getting stuck or why the margin deviates.\n\nA useful inventory distinguishes between three types of components. The first are processes that work well and primarily need to remain stable. The second are processes that are valuable but would benefit from automation or integration. The third are temporary workarounds, duplicate registrations, and manual checks that are better eliminated. This prevents you from carrying old inefficiencies one-to-one into a newer environment.\n\n### Determine what must not change\n\nAlongside bottlenecks, also record what absolutely must be preserved. This could include complex calculation rules, familiar input screens for production, historical data, or a specific authorization method. This gives a modernization project boundaries and prevents users from missing functionality after delivery that only became apparent once it was gone.\n\nInvolve employees from operations in this process, not just IT or management. The person who corrects orders every day usually knows exactly which exceptions a standard process does not handle. That knowledge is essential for a solution that works in practice.\n\n## Choose the modernization route that matches the risk\n\nThere are roughly four routes, which can also coexist. Which route fits depends on the technical condition of the system, the desired pace, and the business impact.\n\n**Targeted improvement** is appropriate when the core application is healthy. You optimize scripts, restore data quality, refresh screens, tighten permissions, or improve reporting. This is often the fastest way to eliminate frustration without major change for users.\n\n**Extending with integrations** makes sense when data continues to move between systems. Via [API connections](https:\u002F\u002Floggix.com\u002Fapis\u002F), a FileMaker solution can, for example, synchronize customer data with a CRM, pass orders to an accounting package, read stock from a webshop, or retrieve shipping information from a carrier. The skill lies not only in the connection itself, but in error handling, logging, and clear agreements about which system is the source of truth.\n\n**Renewing the user layer** works well when the database and business logic are still usable, but employees need to work more mobile or remotely. A web portal, mobile app, or modern user interface can then be built on top of existing processes. This improves the experience without requiring all core logic to migrate immediately.\n\n**Phased rebuilding** is necessary when the solution is structurally difficult to maintain — for example, due to heavily intertwined scripts, old dependencies, or unclear data models. Even then, a big bang is rarely wise. First rebuild a well-defined process, let old and new run alongside each other temporarily, and only then move the next domain.\n\nA full replacement can be sensible, but is not always the cheapest or safest option. The more specific your processes, the greater the chance that you will still need customization, spreadsheets, and workarounds within a standard package. Modernization must deliver a demonstrable improvement, not merely a new name on the invoice.\n\n## Make integrations reliable, not just possible\n\nAn API connection is sometimes treated as a technical detail. In reality, it changes the way your processes function. If a webshop sends an order to your internal system, it must be clear what happens in the event of a temporary outage, a duplicate submission, or a changed article number. Without those agreements, a new manual control process emerges alongside the automation.\n\nTherefore, determine per integration which data is exchanged, how frequently that occurs, and which system is leading. Also record how errors are made visible. A notification in a technical log file helps a developer, but an operations manager primarily needs an overview of orders that require attention. Good integrations make exceptions manageable rather than invisible.\n\nSecurity belongs in this design from the start. Work with minimal access rights, protect API keys, log important actions, and assess which personal data is truly necessary. A modern system does not need to be more complex for users, but it must be better auditable for the organization.\n\n## Use AI only where it demonstrably improves work\n\nAI can be a [meaningful addition](https:\u002F\u002Floggix.com\u002Fai\u002F) to legacy software modernization, provided the application connects to a concrete process. Think of classifying incoming documents, suggesting responses to recurring customer questions, summarizing long notes, or detecting anomalies in data. These are tasks where employees lose time sorting, searching, or repeatedly reading.\n\nAI is less suitable as a replacement for rules that must be exact and auditable, such as price calculations, financial postings, or safety-critical decisions. There, fixed business logic remains leading. It must also be clear what data an AI service receives, where it is processed, and how employees can verify outcomes.\n\nThe most practical approach is to start small. Choose one recurring action, measure the current time spent, and evaluate after a trial whether quality and speed genuinely improve. This keeps AI a practical tool within your application, rather than a standalone experiment without an owner.\n\n## Plan in phases and measure the result\n\nA modernization does not need to halt daily operations. In fact, systems that are critical for planning, sales, or production are better approached in manageable steps. Start with a process that has a clear return and limited dependencies, such as the automatic transfer of customer data or an improved input screen for field service employees.\n\nAgree in advance on what success looks like. That could mean less duplicate entry, shorter lead time per order, fewer corrections on invoices, or fewer requests to the internal administrator. Also measure the less visible return: better insight into the work backlog, faster onboarding of new employees, and less dependency on individual knowledge.\n\nDo not test exclusively on the ideal path. It is precisely exceptions, missing data, duplicate transactions, and users with different rights that reveal whether a solution is ready for real-world use. A short pilot with real users typically yields more than an extensive demonstration with perfect test data.\n\n## Modernizing without losing business knowledge\n\nThe best modernization does not feel to employees like a technical migration, but like work that flows more logically. Orders no longer need to be re-entered. Information is available where it is needed. Errors come to light sooner and exceptions have a clear place.\n\nThis requires a partner who understands both the existing FileMaker environment and modern APIs, web, and mobile applications. Loggix therefore does not automatically opt for replacement, but for an approach that preserves the valuable core and renews in a targeted way where the business gain lies.\n\nStart with one honest process question: where are good people currently spending time on something software could take over? The answer to that is often a much stronger starting point than a plan to rebuild everything from scratch.","\u003Cp>A warehouse employee who enters data into a FileMaker database, then copies it into Excel, and then drafts an invoice email is not dealing with an outdated screen problem. He is dealing with a process risk. Every manual transfer costs time, makes errors more likely, and keeps valuable business information locked away. This guide to legacy software modernization is therefore not about replacing technology because it is old. It is about targeted improvements that make your operation faster, more reliable, and easier to manage.\u003C\u002Fp>\n\u003Cp>Many organizations have been running on custom software for years — software that knows their way of working better than any standard package ever could. Especially with FileMaker solutions, a great deal of accumulated knowledge is often embedded: non-standard pricing agreements, production controls, customer files, scheduling rules, and exceptions that are perfectly normal for the business. You want to preserve that value. At the same time, a system should not become a brake on growth, integrations, or secure working.\u003C\u002Fp>\n\u003Ch2>When is legacy software modernization necessary?\u003C\u002Fh2>\n\u003Cp>Legacy software is not automatically software that is old. A FileMaker system from 2012 that runs stably, is well maintained, and delivers the right information does not need to be replaced immediately. The trigger usually lies in the gap between what the system can do and what the organization now needs.\u003C\u002Fp>\n\u003Cp>That gap becomes visible when employees enter the same data in multiple places, when reports can only be produced with a great deal of manual effort, or when critical knowledge rests with a single administrator. A lack of integrations with accounting, e-commerce, CRM, logistics software, or Microsoft 365 is also often a concrete signal. The database still works, but the process surrounding it has become unnecessarily cumbersome.\u003C\u002Fp>\n\u003Cp>Technical signals count as well. Think of outdated plug-ins, slow screens with growing data files, weak user rights management, dependency on local files, or a solution that does not work comfortably on an iPad, phone, or via a browser. The right question is not: do we need to rebuild everything? The better question is: which limitation is currently causing the most delay, errors, or risk?\u003C\u002Fp>\n\u003Ch2>Start with business processes, not a new platform\u003C\u002Fh2>\n\u003Cp>A modernization effort often stalls when the choice of technology is the starting point. A new platform may sound appealing, but it does not resolve an unclear workflow. First map out where information is created, who uses it, what decision is made with it, and where data leaves the system.\u003C\u002Fp>\n\u003Cp>Take order processing as an example. An order can come in via email, a web form, an account manager, or an EDI connection. Then stock must be checked, a price determined, a pick instruction created, and an invoice sent. If three of those steps happen outside the central application, there is not only a loss of time. It also becomes harder to see where an order is getting stuck or why the margin deviates.\u003C\u002Fp>\n\u003Cp>A useful inventory distinguishes between three types of components. The first are processes that work well and primarily need to remain stable. The second are processes that are valuable but would benefit from automation or integration. The third are temporary workarounds, duplicate registrations, and manual checks that are better eliminated. This prevents you from carrying old inefficiencies one-to-one into a newer environment.\u003C\u002Fp>\n\u003Ch3>Determine what must not change\u003C\u002Fh3>\n\u003Cp>Alongside bottlenecks, also record what absolutely must be preserved. This could include complex calculation rules, familiar input screens for production, historical data, or a specific authorization method. This gives a modernization project boundaries and prevents users from missing functionality after delivery that only became apparent once it was gone.\u003C\u002Fp>\n\u003Cp>Involve employees from operations in this process, not just IT or management. The person who corrects orders every day usually knows exactly which exceptions a standard process does not handle. That knowledge is essential for a solution that works in practice.\u003C\u002Fp>\n\u003Ch2>Choose the modernization route that matches the risk\u003C\u002Fh2>\n\u003Cp>There are roughly four routes, which can also coexist. Which route fits depends on the technical condition of the system, the desired pace, and the business impact.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Targeted improvement\u003C\u002Fstrong> is appropriate when the core application is healthy. You optimize scripts, restore data quality, refresh screens, tighten permissions, or improve reporting. This is often the fastest way to eliminate frustration without major change for users.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Extending with integrations\u003C\u002Fstrong> makes sense when data continues to move between systems. Via \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fapis\u002F\">API connections\u003C\u002Fa>, a FileMaker solution can, for example, synchronize customer data with a CRM, pass orders to an accounting package, read stock from a webshop, or retrieve shipping information from a carrier. The skill lies not only in the connection itself, but in error handling, logging, and clear agreements about which system is the source of truth.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Renewing the user layer\u003C\u002Fstrong> works well when the database and business logic are still usable, but employees need to work more mobile or remotely. A web portal, mobile app, or modern user interface can then be built on top of existing processes. This improves the experience without requiring all core logic to migrate immediately.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Phased rebuilding\u003C\u002Fstrong> is necessary when the solution is structurally difficult to maintain — for example, due to heavily intertwined scripts, old dependencies, or unclear data models. Even then, a big bang is rarely wise. First rebuild a well-defined process, let old and new run alongside each other temporarily, and only then move the next domain.\u003C\u002Fp>\n\u003Cp>A full replacement can be sensible, but is not always the cheapest or safest option. The more specific your processes, the greater the chance that you will still need customization, spreadsheets, and workarounds within a standard package. Modernization must deliver a demonstrable improvement, not merely a new name on the invoice.\u003C\u002Fp>\n\u003Ch2>Make integrations reliable, not just possible\u003C\u002Fh2>\n\u003Cp>An API connection is sometimes treated as a technical detail. In reality, it changes the way your processes function. If a webshop sends an order to your internal system, it must be clear what happens in the event of a temporary outage, a duplicate submission, or a changed article number. Without those agreements, a new manual control process emerges alongside the automation.\u003C\u002Fp>\n\u003Cp>Therefore, determine per integration which data is exchanged, how frequently that occurs, and which system is leading. Also record how errors are made visible. A notification in a technical log file helps a developer, but an operations manager primarily needs an overview of orders that require attention. Good integrations make exceptions manageable rather than invisible.\u003C\u002Fp>\n\u003Cp>Security belongs in this design from the start. Work with minimal access rights, protect API keys, log important actions, and assess which personal data is truly necessary. A modern system does not need to be more complex for users, but it must be better auditable for the organization.\u003C\u002Fp>\n\u003Ch2>Use AI only where it demonstrably improves work\u003C\u002Fh2>\n\u003Cp>AI can be a \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fai\u002F\">meaningful addition\u003C\u002Fa> to legacy software modernization, provided the application connects to a concrete process. Think of classifying incoming documents, suggesting responses to recurring customer questions, summarizing long notes, or detecting anomalies in data. These are tasks where employees lose time sorting, searching, or repeatedly reading.\u003C\u002Fp>\n\u003Cp>AI is less suitable as a replacement for rules that must be exact and auditable, such as price calculations, financial postings, or safety-critical decisions. There, fixed business logic remains leading. It must also be clear what data an AI service receives, where it is processed, and how employees can verify outcomes.\u003C\u002Fp>\n\u003Cp>The most practical approach is to start small. Choose one recurring action, measure the current time spent, and evaluate after a trial whether quality and speed genuinely improve. This keeps AI a practical tool within your application, rather than a standalone experiment without an owner.\u003C\u002Fp>\n\u003Ch2>Plan in phases and measure the result\u003C\u002Fh2>\n\u003Cp>A modernization does not need to halt daily operations. In fact, systems that are critical for planning, sales, or production are better approached in manageable steps. Start with a process that has a clear return and limited dependencies, such as the automatic transfer of customer data or an improved input screen for field service employees.\u003C\u002Fp>\n\u003Cp>Agree in advance on what success looks like. That could mean less duplicate entry, shorter lead time per order, fewer corrections on invoices, or fewer requests to the internal administrator. Also measure the less visible return: better insight into the work backlog, faster onboarding of new employees, and less dependency on individual knowledge.\u003C\u002Fp>\n\u003Cp>Do not test exclusively on the ideal path. It is precisely exceptions, missing data, duplicate transactions, and users with different rights that reveal whether a solution is ready for real-world use. A short pilot with real users typically yields more than an extensive demonstration with perfect test data.\u003C\u002Fp>\n\u003Ch2>Modernizing without losing business knowledge\u003C\u002Fh2>\n\u003Cp>The best modernization does not feel to employees like a technical migration, but like work that flows more logically. Orders no longer need to be re-entered. Information is available where it is needed. Errors come to light sooner and exceptions have a clear place.\u003C\u002Fp>\n\u003Cp>This requires a partner who understands both the existing FileMaker environment and modern APIs, web, and mobile applications. Loggix therefore does not automatically opt for replacement, but for an approach that preserves the valuable core and renews in a targeted way where the business gain lies.\u003C\u002Fp>\n\u003Cp>Start with one honest process question: where are good people currently spending time on something software could take over? The answer to that is often a much stronger starting point than a plan to rebuild everything from scratch.\u003C\u002Fp>\n","2026-07-14",1784016333000,[23,132],"Update","\u002Fapi\u002Fknowledge\u002Fimage\u002F106\u002F?v=0855327daa22",{"id":135,"idKnowledge":136,"idDomain":15,"idCluster":15,"slug":137,"title":138,"description":139,"bodyMarkdown":140,"bodyHtml":141,"author":39,"date":142,"createdAt":143,"topics":144,"image":145,"hasDownload":28,"fileName":15,"youtubeId":27},"105","955D1801-D56B-1841-8F50-F3CE46B81B9A","wat-kost-api-integratie-voor-uw-organisatie","What does API integration cost for your organisation?","What does API integration cost? Read which choices determine the price, from connection and security to management, and how to plan targeted budget for growth.","An order that needs to be re-entered, inventory that only balances a day later, or customer data that differs across three locations: such processes cost time and trust every week. The question **'what does API integration cost'** therefore usually only comes up when manual work starts to noticeably create friction. The honest answer is that the price depends on exactly what needs to be connected, but the main cost drivers are highly predictable.\n\nFor many organisations, an API integration is not a standalone technical project. It is an improvement to a business process. Think of a FileMaker solution that retrieves orders from a web shop, an [accounting package that receives invoice data](https:\u002F\u002Floggix.com\u002Fblog\u002Fexact-online-koppelen-aan-filemaker-zo-automatiseer-je-facturen-veilig-en-foutloos\u002F), or a planning system that automatically updates customer information. The investment should therefore not only be weighed against development hours, but also against fewer errors, less duplicate work, and better information for employees.\n\n## What does API integration cost in practice?\n\nA simple, one-directional connection can often be realised from a few thousand euros. For example, when an existing FileMaker database periodically retrieves data from a single well-documented external service. A connection involving multiple systems, bidirectional data flow, validations, and error handling is typically higher. For such projects, a budget of €10,000 to €30,000 or more is common, depending on the desired reliability and complexity.\n\nThese are not fixed packages. An API is merely the technical access point to a system. The real effort lies in translating that into your processes: which data is transferred when, which system is the source of truth, what happens when information is missing, and who needs to resolve a discrepancy? It is precisely those choices that determine whether an integration saves work later or creates new exceptions.\n\nIn a more extensive [modernisation project](https:\u002F\u002Floggix.com\u002Fblog\u002Ffilemaker-systeem-moderniseren-zonder-risico\u002F), the connection may be part of a larger investment. For example, when a FileMaker solution is simultaneously cleaned up, given new screens, and connected to a web portal, ERP system, and shipping service. In that case, it is more useful to assess costs per process step than to attach a price solely to the API.\n\n## The five factors that determine the price\n\nThe costs of a connection are primarily determined by the following components:\n\n-   **Number of systems and data flows.** A single connection between two systems is more straightforward than a chain of CRM, FileMaker, [accounting, web shop, and logistics](https:\u002F\u002Floggix.com\u002Fblog\u002Flogistieke-software-koppelingen-bouwen\u002F). Bidirectional data flow requires additional logic to prevent conflicts.\n-   **Quality of the available API.** A clear, stable API with good documentation and a test environment reduces development time. A limited or frequently changing API requires more research, custom work, and validation.\n-   **Data mapping and data quality.** Fields that appear identical at first glance do not always carry the same meaning. Think of customer numbers, VAT status, product variants, or delivery addresses. Old, duplicate, or incomplete data increases the effort required.\n-   **Process rules and exceptions.** The standard route is rarely the problem. Costs are often found in partial shipments, credit notes, cancelled orders, manual corrections, and exceptional customer agreements.\n-   **Security, logging, and management.** API keys, authorisations, encrypted communication, error messages, and an audit log are not optional extras. They are necessary to keep a connection secure and manageable.\n\nA cheap integration that does not log errors can prove costly the moment data fails to arrive. Conversely, not every small process needs an extensive real-time architecture. If synchronising inventory once an hour is sufficient, that is often simpler and more cost-effective than processing every change in real time.\n\n### One-off build costs versus recurring costs\n\nDistinguish between implementation and operations. The one-off costs consist of analysis, technical design, development, testing, documentation, and go-live. A thorough testing phase is essential here, especially when invoices, inventory, or personal data are being processed.\n\nIn addition, there are recurring costs. Some software vendors charge per API call, user, or transaction level. Hosting, monitoring, maintenance, and support may also form part of the monthly budget. Also factor in periodic adjustments when an external party changes its API or when your own process evolves.\n\nFor a business-critical connection, a maintenance agreement is often advisable. This keeps security settings, certificates, and dependencies under control. For a less critical reporting process, periodic maintenance may be sufficient. The right choice depends on the consequences of downtime: can a synchronisation wait a day, or will order processing come to a halt?\n\n## Where does development time actually go?\n\nA realistic quote contains more than programming a connection. First, it must be clear which source data is reliable and what the desired end state looks like. Fields, rules, and responsibilities are then documented. This analysis prevents a technical connection from being built quickly that does not hold up operationally.\n\nThe build phase follows. The integration must be able to authenticate, retrieve or send data, process responses, and handle errors correctly. In a FileMaker environment, this involves scripts, data structure, user permissions, and potentially a server process that executes tasks at scheduled times. When large volumes are processed, attention to performance and queuing is also required.\n\nTesting takes time but delivers confidence. It is not only a successful order that needs to be tested, but also an order with an unknown item, a temporary outage at the external service, and a duplicate submission. Only once it is clear how the system behaves in such situations can employees rely on it.\n\nFinally, handover and management are relevant. Who sees that a connection has stalled? How is an error resolved? Can an employee resubmit a transaction without calling a developer? A brief management guide and clear notifications make a considerable difference to day-to-day usability.\n\n## How to keep your API integration budget under control\n\nThe best way to control costs is not to skip analysis, but to define the scope of the first version tightly. Choose one process with demonstrable value. For example: automatically sending new web orders to your internal system, including customer and order line data. Do not immediately include returns, discount rules, inventory mutations, and reports if these are not yet a direct bottleneck.\n\nAlso agree upfront on which system is the source of truth for each type of data. Is the CRM the source for customer data, FileMaker for production data, and the accounting system for payment status? Without this baseline, disputes will arise later over overwritten changes and duplicate records.\n\nWhen requesting a quote, ask not only for a total amount but for the underlying assumptions. How many data flows are included? Has the external API already been reviewed? Are test scenarios, logging, documentation, and aftercare included? What happens if the vendor of the connected system changes its API? These questions make quotes far more comparable than the hourly rate alone.\n\nA phased approach often works well. First a technical proof of concept with a limited number of records, then the core integration, and subsequently extensions based on real user experience. This limits risk without locking the organisation into a half-working solution.\n\n## When is custom development worth the investment?\n\nStandard connectors are attractive when your process is standard and the required fields are available. They can deliver results quickly. The limit is reached when you need to incorporate specific controls, custom pricing agreements, unique production processes, or an existing FileMaker database containing business logic. The question then shifts from 'can the systems connect?' to 'does the connection support the way we actually work?'\n\nCustom development costs more upfront, but can be more cost-effective when it structurally eliminates manual steps or prevents errors. Particularly in processes involving high volumes of orders, invoices, inventory lines, or customer mutations, a small time saving per transaction quickly adds up. The calculation remains practical: how many hours are eliminated, how much rework is prevented, and how much growth can the team handle without additional administration?\n\nFor existing FileMaker environments, modernisation does not necessarily mean a replacement project. A well-designed API layer can actually preserve the value of the existing solution, while allowing new systems to connect to it in a controlled way. This lets you improve what already works, step by step, without unnecessarily disrupting daily operations.\n\nA reliable cost estimate therefore starts with one concrete process and real examples from your organisation. Bring a few orders, exceptions, and desired outcomes to the first conversation. This quickly makes clear which connection is needed, which choices affect the budget, and where the investment will deliver returns first.","\u003Cp>An order that needs to be re-entered, inventory that only balances a day later, or customer data that differs across three locations: such processes cost time and trust every week. The question \u003Cstrong>'what does API integration cost'\u003C\u002Fstrong> therefore usually only comes up when manual work starts to noticeably create friction. The honest answer is that the price depends on exactly what needs to be connected, but the main cost drivers are highly predictable.\u003C\u002Fp>\n\u003Cp>For many organisations, an API integration is not a standalone technical project. It is an improvement to a business process. Think of a FileMaker solution that retrieves orders from a web shop, an \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Fexact-online-koppelen-aan-filemaker-zo-automatiseer-je-facturen-veilig-en-foutloos\u002F\">accounting package that receives invoice data\u003C\u002Fa>, or a planning system that automatically updates customer information. The investment should therefore not only be weighed against development hours, but also against fewer errors, less duplicate work, and better information for employees.\u003C\u002Fp>\n\u003Ch2>What does API integration cost in practice?\u003C\u002Fh2>\n\u003Cp>A simple, one-directional connection can often be realised from a few thousand euros. For example, when an existing FileMaker database periodically retrieves data from a single well-documented external service. A connection involving multiple systems, bidirectional data flow, validations, and error handling is typically higher. For such projects, a budget of €10,000 to €30,000 or more is common, depending on the desired reliability and complexity.\u003C\u002Fp>\n\u003Cp>These are not fixed packages. An API is merely the technical access point to a system. The real effort lies in translating that into your processes: which data is transferred when, which system is the source of truth, what happens when information is missing, and who needs to resolve a discrepancy? It is precisely those choices that determine whether an integration saves work later or creates new exceptions.\u003C\u002Fp>\n\u003Cp>In a more extensive \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Ffilemaker-systeem-moderniseren-zonder-risico\u002F\">modernisation project\u003C\u002Fa>, the connection may be part of a larger investment. For example, when a FileMaker solution is simultaneously cleaned up, given new screens, and connected to a web portal, ERP system, and shipping service. In that case, it is more useful to assess costs per process step than to attach a price solely to the API.\u003C\u002Fp>\n\u003Ch2>The five factors that determine the price\u003C\u002Fh2>\n\u003Cp>The costs of a connection are primarily determined by the following components:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Number of systems and data flows.\u003C\u002Fstrong> A single connection between two systems is more straightforward than a chain of CRM, FileMaker, \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Flogistieke-software-koppelingen-bouwen\u002F\">accounting, web shop, and logistics\u003C\u002Fa>. Bidirectional data flow requires additional logic to prevent conflicts.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Quality of the available API.\u003C\u002Fstrong> A clear, stable API with good documentation and a test environment reduces development time. A limited or frequently changing API requires more research, custom work, and validation.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Data mapping and data quality.\u003C\u002Fstrong> Fields that appear identical at first glance do not always carry the same meaning. Think of customer numbers, VAT status, product variants, or delivery addresses. Old, duplicate, or incomplete data increases the effort required.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Process rules and exceptions.\u003C\u002Fstrong> The standard route is rarely the problem. Costs are often found in partial shipments, credit notes, cancelled orders, manual corrections, and exceptional customer agreements.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Security, logging, and management.\u003C\u002Fstrong> API keys, authorisations, encrypted communication, error messages, and an audit log are not optional extras. They are necessary to keep a connection secure and manageable.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>A cheap integration that does not log errors can prove costly the moment data fails to arrive. Conversely, not every small process needs an extensive real-time architecture. If synchronising inventory once an hour is sufficient, that is often simpler and more cost-effective than processing every change in real time.\u003C\u002Fp>\n\u003Ch3>One-off build costs versus recurring costs\u003C\u002Fh3>\n\u003Cp>Distinguish between implementation and operations. The one-off costs consist of analysis, technical design, development, testing, documentation, and go-live. A thorough testing phase is essential here, especially when invoices, inventory, or personal data are being processed.\u003C\u002Fp>\n\u003Cp>In addition, there are recurring costs. Some software vendors charge per API call, user, or transaction level. Hosting, monitoring, maintenance, and support may also form part of the monthly budget. Also factor in periodic adjustments when an external party changes its API or when your own process evolves.\u003C\u002Fp>\n\u003Cp>For a business-critical connection, a maintenance agreement is often advisable. This keeps security settings, certificates, and dependencies under control. For a less critical reporting process, periodic maintenance may be sufficient. The right choice depends on the consequences of downtime: can a synchronisation wait a day, or will order processing come to a halt?\u003C\u002Fp>\n\u003Ch2>Where does development time actually go?\u003C\u002Fh2>\n\u003Cp>A realistic quote contains more than programming a connection. First, it must be clear which source data is reliable and what the desired end state looks like. Fields, rules, and responsibilities are then documented. This analysis prevents a technical connection from being built quickly that does not hold up operationally.\u003C\u002Fp>\n\u003Cp>The build phase follows. The integration must be able to authenticate, retrieve or send data, process responses, and handle errors correctly. In a FileMaker environment, this involves scripts, data structure, user permissions, and potentially a server process that executes tasks at scheduled times. When large volumes are processed, attention to performance and queuing is also required.\u003C\u002Fp>\n\u003Cp>Testing takes time but delivers confidence. It is not only a successful order that needs to be tested, but also an order with an unknown item, a temporary outage at the external service, and a duplicate submission. Only once it is clear how the system behaves in such situations can employees rely on it.\u003C\u002Fp>\n\u003Cp>Finally, handover and management are relevant. Who sees that a connection has stalled? How is an error resolved? Can an employee resubmit a transaction without calling a developer? A brief management guide and clear notifications make a considerable difference to day-to-day usability.\u003C\u002Fp>\n\u003Ch2>How to keep your API integration budget under control\u003C\u002Fh2>\n\u003Cp>The best way to control costs is not to skip analysis, but to define the scope of the first version tightly. Choose one process with demonstrable value. For example: automatically sending new web orders to your internal system, including customer and order line data. Do not immediately include returns, discount rules, inventory mutations, and reports if these are not yet a direct bottleneck.\u003C\u002Fp>\n\u003Cp>Also agree upfront on which system is the source of truth for each type of data. Is the CRM the source for customer data, FileMaker for production data, and the accounting system for payment status? Without this baseline, disputes will arise later over overwritten changes and duplicate records.\u003C\u002Fp>\n\u003Cp>When requesting a quote, ask not only for a total amount but for the underlying assumptions. How many data flows are included? Has the external API already been reviewed? Are test scenarios, logging, documentation, and aftercare included? What happens if the vendor of the connected system changes its API? These questions make quotes far more comparable than the hourly rate alone.\u003C\u002Fp>\n\u003Cp>A phased approach often works well. First a technical proof of concept with a limited number of records, then the core integration, and subsequently extensions based on real user experience. This limits risk without locking the organisation into a half-working solution.\u003C\u002Fp>\n\u003Ch2>When is custom development worth the investment?\u003C\u002Fh2>\n\u003Cp>Standard connectors are attractive when your process is standard and the required fields are available. They can deliver results quickly. The limit is reached when you need to incorporate specific controls, custom pricing agreements, unique production processes, or an existing FileMaker database containing business logic. The question then shifts from 'can the systems connect?' to 'does the connection support the way we actually work?'\u003C\u002Fp>\n\u003Cp>Custom development costs more upfront, but can be more cost-effective when it structurally eliminates manual steps or prevents errors. Particularly in processes involving high volumes of orders, invoices, inventory lines, or customer mutations, a small time saving per transaction quickly adds up. The calculation remains practical: how many hours are eliminated, how much rework is prevented, and how much growth can the team handle without additional administration?\u003C\u002Fp>\n\u003Cp>For existing FileMaker environments, modernisation does not necessarily mean a replacement project. A well-designed API layer can actually preserve the value of the existing solution, while allowing new systems to connect to it in a controlled way. This lets you improve what already works, step by step, without unnecessarily disrupting daily operations.\u003C\u002Fp>\n\u003Cp>A reliable cost estimate therefore starts with one concrete process and real examples from your organisation. Bring a few orders, exceptions, and desired outcomes to the first conversation. This quickly makes clear which connection is needed, which choices affect the budget, and where the investment will deliver returns first.\u003C\u002Fp>\n","2026-07-12",1783843519000,[73,23],"\u002Fapi\u002Fknowledge\u002Fimage\u002F105\u002F?v=95654b68f9ba",{"id":147,"idKnowledge":148,"idDomain":15,"idCluster":15,"slug":149,"title":150,"description":151,"bodyMarkdown":152,"bodyHtml":153,"author":39,"date":154,"createdAt":155,"topics":156,"image":164,"hasDownload":28,"fileName":15,"youtubeId":27},"103","79667307-63A3-6E4B-8F9A-109439A1139C","legacy-database-omzetten-naar-webapp","Legacy database converting to webapp","A legacy database converted to a web app without throwing everything away — how do you approach that? Practical approach, common mistakes, and concrete steps.","Your database has been doing exactly what it needs to do for ten years. Until a technician wants to log in from outside the office, a customer asks for real-time status updates, or a new integration with your ERP becomes necessary. At that point, the question is no longer *whether* you need to change something, but how to do it without bringing daily operations to a halt.\n\nThis article shows how to pragmatically convert a legacy database into a web app — in phases, without discarding valuable business logic, and without having to launch a large IT project just to get started.\n\n\u003Cimg src=\"\u002Fapi\u002Fknowledge\u002Finline-image\u002F11?w=700&f=webp\" alt=\"Legacy database connected to modern webapp layer, arrows showing data flow between old and new\" loading=\"lazy\" class=\"w-full sm:w-1\u002F3 sm:float-right sm:ml-7 mb-5 rounded-2xl border border-[#E8E8ED] bg-[#F5F5F7]\" \u002F>\n\n## Why is 'simply starting over' rarely the smartest choice?\n\nA database built on for fifteen years contains more than tables and fields. It holds authorization structures that emerged after a data breach in 2014. Validation rules added after a customer received incorrect quantities. Exception logic that nobody fully knows by heart anymore, but that quietly runs correctly every single day.\n\nDiscarding all of that and starting fresh means paying not just for new software. You also pay for the loss of implicit process knowledge, for a longer implementation period while the old system runs in parallel, and for the risk that the new version leaves operational gaps that only become visible months later.\n\nFor organizations running an older FileMaker solution, this is especially true. Many of those environments contain years of business logic that was never explicitly documented — but that does its job every day.\n\n## What does 'converting a legacy database to a web app' actually mean?\n\nIt sounds technical, but the business core is simple: you make an existing system more broadly usable. Employees can work via browser, tablet, or phone, without depending on a specific workstation or locally installed software. Customers or partners can log in via a portal. Systems exchange data automatically.\n\nBut a web app is not simply placing a new screen over an old database. Proper modernization touches three layers simultaneously:\n\n1. **Data** — is the data model still logical, or have duplicates, outdated fields, and inconsistencies crept in?\n2. **Process logic** — which rules, checks, and automations are functionally valuable, and which have grown historically without purpose?\n3. **User experience** — how do people actually work, and how can a web interface make that faster and less error-prone?\n\nIf you only address the third layer, you solve only part of the problem.\n\n## How do you get started without disrupting daily work?\n\nThe most effective projects do not unfold as a big bang. A phased approach reduces risk, keeps operations running, and makes investments more manageable. In practice, it looks like this:\n\n**Step 1 — Analyze the existing landscape**\nNot just inventorying tables and fields, but understanding how people actually work. Which processes are business-critical? Where do errors arise? Which parts are used every day, and which haven't been updated in years?\n\n**Step 2 — Identify the highest-impact components**\nWhere does a web app deliver immediately noticeable results? Think of: field service engineers still filling in service forms on paper and retyping them in the evening. An order process where an order is entered in FileMaker and then manually retyped into Exact Online — every order, every day. Or a planning module only accessible from the office while the project manager is working on site.\n\n**Step 3 — Determine the technical route**\nSometimes the smartest approach is to keep the existing database as the primary source temporarily, while a modern web layer is built on top of it. In other cases, the data model is so outdated that partial restructuring yields more value. Which route fits depends on complexity, maintainability, and long-term scalability.\n\n**Step 4 — Deliver something functional quickly**\nUsers don't need to wait for a complete end product. Start with the component that delivers the most gain — a web form for service registration, a customer portal for order statuses, a mobile-friendly planning screen — and build on that in a controlled manner.\n\n\u003Cimg src=\"\u002Fapi\u002Fknowledge\u002Finline-image\u002F12?w=700&f=webp\" alt=\"Step-by-step migration diagram: analysis, prioritize modules, build web layer, expand gradually\" loading=\"lazy\" class=\"w-full sm:w-1\u002F3 sm:float-left sm:mr-7 mb-5 rounded-2xl border border-[#E8E8ED] bg-[#F5F5F7]\" \u002F>\n\n## What do you want to keep, and what is better left behind?\n\nA legacy system always contains two types of logic: logic that is functionally strong, and logic that has simply grown over time.\n\n**Keep:**\n- Authorization structures that were deliberately built\n- Process steps that prevent errors or handle exceptions correctly\n- Validation rules that align with how the business actually operates\n- Integrations with processes that are still current\n\n**Leave behind:**\n- Fields without an owner that haven't been filled in for years\n- Reports nobody opens anymore\n- Temporary workarounds that have become permanent\n- Manual intermediate steps made redundant by automation\n\nA modernization is also an opportunity to clean up. Not every existing screen layout needs to reappear in the web app. Not every manual check is still necessary if automation can take it over. Good modernization means preserving what is functionally strong and letting go of what only exists because it was once put there.\n\n## When is a hybrid model smarter than full replacement?\n\nNot every organization needs to replace its entire legacy environment in one move. A hybrid approach — where parts of the existing system remain active while new features are developed web-based — is often the most realistic route for SME organizations.\n\nThis is a good choice when:\n- The current database is stable, but accessibility falls short\n- The investment needs to be spread across multiple phases\n- Certain parts of the system can remain in use for years without modification\n- The organization needs time to internally adjust to new ways of working\n\nA hybrid model also fits better with how businesses actually change. Processes evolve, teams grow, requirements shift. Software that moves along with that — step by step — is more valuable in the long run than a rigid end vision that is already trailing reality by the time it is delivered.\n\n## Why are integrations so decisive for the end result?\n\nFor many businesses, the greatest gain lies not only in a web interface, but in better connections with other systems. Converting a legacy database to a web app only truly delivers value when data flows automatically.\n\nA concrete example: a installation company processes service visits in FileMaker. The technician fills in the form on paper, the back-office staff rekeys it, and the invoice is manually created in the accounting package. With a proper web app and API integration, the technician reports the service visit directly from his phone, the invoice is automatically created in Exact Online, and the customer sees the status in real time in their portal.\n\nThat is not a future scenario — it is what is already possible when the technical architecture is right.\n\nIntegrations often look simpler on paper than they are in practice. Authentication, data mapping, error handling, synchronization timing, and authorizations all play a significant role. A web app that looks good but integrates poorly solves only part of the problem.\n\n## What mistakes are made most often?\n\n**1. Assuming cheaper always means smarter**\nA quick rebuild without analysis seems attractive. But as soon as exceptions, data quality issues, or existing dependencies become visible, extra work piles up. What starts cheap becomes expensive to fix.\n\n**2. Trying to tackle everything at once**\nWhen every process, report, and screen is in scope at the same time, the project becomes unmanageable. Better: start with a clear core and expand in a controlled manner.\n\n**3. Forgetting that users need to work every day**\nA system can be technically excellent but still meet resistance if daily tasks become more cumbersome. Employees need to work faster and more easily — not just look at a more modern interface.\n\n**4. Underestimating how much knowledge is embedded in the old system**\nEspecially in FileMaker environments, much of the business logic has been built up implicitly over the years. Anyone who does not explicitly account for this in the analysis will quickly build a neat web app that still leaves operational gaps.\n\n## Checklist: are you ready to get started?\n\nBefore starting a project, it helps to answer these questions:\n\n- [ ] Do you know which processes are business-critical and which are optional?\n- [ ] Have the integrations needed with other systems been mapped out?\n- [ ] Are user roles and authorizations clearly defined?\n- [ ] Is there someone internally who can transfer process knowledge to the development team?\n- [ ] Is there a phased plan that delivers something functional quickly?\n- [ ] Has data quality and cleanup been accounted for?\n- [ ] Is the business case also expressed in operational gains, not just in build costs?\n\n## How strong is the business case, really?\n\nMany businesses postpone modernization because they primarily look at development costs. Understandable — but incomplete. The real calculation also includes:\n\n- Time lost through manual data entry and duplicate registrations\n- Error corrections that cost employees hours per week\n- Limited availability of information that slows down decision-making\n- Scalability blocked by technical limitations\n\nWhen a web app eliminates manual steps on a daily basis — and makes information available faster to the people who base decisions on it — that translates directly into operational performance and customer service. You also extend the lifespan of process knowledge that has been proving its value for years. That is what makes converting a legacy database to a web app not an IT project, but an investment in continuity.\n\nThe best first step is rarely the most radical one. Start with what meaningfully improves the business operation, build on that, and ensure that technology supports operations rather than dictating them.\n\n---\n\nLoggix helps organizations facing exactly this trade-off: a legacy environment that still works well, but needs to be more accessible, more scalable, or better connected. Whether it involves an existing FileMaker solution that needs to move to a web environment, a custom application that requires API integrations, or a phased modernization project where existing business logic is the starting point — we prefer to think through the approach together rather than immediately selling a new-build project. Get in touch if you'd like to explore the options for your situation.","\u003Cp>Your database has been doing exactly what it needs to do for ten years. Until a technician wants to log in from outside the office, a customer asks for real-time status updates, or a new integration with your ERP becomes necessary. At that point, the question is no longer \u003Cem>whether\u003C\u002Fem> you need to change something, but how to do it without bringing daily operations to a halt.\u003C\u002Fp>\n\u003Cp>This article shows how to pragmatically convert a legacy database into a web app — in phases, without discarding valuable business logic, and without having to launch a large IT project just to get started.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fapi\u002Fknowledge\u002Finline-image\u002F11?w=700&f=webp\" alt=\"Legacy database connected to modern webapp layer, arrows showing data flow between old and new\" loading=\"lazy\" class=\"w-full sm:w-1\u002F3 sm:float-right sm:ml-7 mb-5 rounded-2xl border border-[#E8E8ED] bg-[#F5F5F7]\" \u002F>\n\n\u003Ch2>Why is 'simply starting over' rarely the smartest choice?\u003C\u002Fh2>\n\u003Cp>A database built on for fifteen years contains more than tables and fields. It holds authorization structures that emerged after a data breach in 2014. Validation rules added after a customer received incorrect quantities. Exception logic that nobody fully knows by heart anymore, but that quietly runs correctly every single day.\u003C\u002Fp>\n\u003Cp>Discarding all of that and starting fresh means paying not just for new software. You also pay for the loss of implicit process knowledge, for a longer implementation period while the old system runs in parallel, and for the risk that the new version leaves operational gaps that only become visible months later.\u003C\u002Fp>\n\u003Cp>For organizations running an older FileMaker solution, this is especially true. Many of those environments contain years of business logic that was never explicitly documented — but that does its job every day.\u003C\u002Fp>\n\u003Ch2>What does 'converting a legacy database to a web app' actually mean?\u003C\u002Fh2>\n\u003Cp>It sounds technical, but the business core is simple: you make an existing system more broadly usable. Employees can work via browser, tablet, or phone, without depending on a specific workstation or locally installed software. Customers or partners can log in via a portal. Systems exchange data automatically.\u003C\u002Fp>\n\u003Cp>But a web app is not simply placing a new screen over an old database. Proper modernization touches three layers simultaneously:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Data\u003C\u002Fstrong> — is the data model still logical, or have duplicates, outdated fields, and inconsistencies crept in?\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Process logic\u003C\u002Fstrong> — which rules, checks, and automations are functionally valuable, and which have grown historically without purpose?\u003C\u002Fli>\n\u003Cli>\u003Cstrong>User experience\u003C\u002Fstrong> — how do people actually work, and how can a web interface make that faster and less error-prone?\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>If you only address the third layer, you solve only part of the problem.\u003C\u002Fp>\n\u003Ch2>How do you get started without disrupting daily work?\u003C\u002Fh2>\n\u003Cp>The most effective projects do not unfold as a big bang. A phased approach reduces risk, keeps operations running, and makes investments more manageable. In practice, it looks like this:\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Step 1 — Analyze the existing landscape\u003C\u002Fstrong>\nNot just inventorying tables and fields, but understanding how people actually work. Which processes are business-critical? Where do errors arise? Which parts are used every day, and which haven't been updated in years?\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Step 2 — Identify the highest-impact components\u003C\u002Fstrong>\nWhere does a web app deliver immediately noticeable results? Think of: field service engineers still filling in service forms on paper and retyping them in the evening. An order process where an order is entered in FileMaker and then manually retyped into Exact Online — every order, every day. Or a planning module only accessible from the office while the project manager is working on site.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Step 3 — Determine the technical route\u003C\u002Fstrong>\nSometimes the smartest approach is to keep the existing database as the primary source temporarily, while a modern web layer is built on top of it. In other cases, the data model is so outdated that partial restructuring yields more value. Which route fits depends on complexity, maintainability, and long-term scalability.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Step 4 — Deliver something functional quickly\u003C\u002Fstrong>\nUsers don't need to wait for a complete end product. Start with the component that delivers the most gain — a web form for service registration, a customer portal for order statuses, a mobile-friendly planning screen — and build on that in a controlled manner.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fapi\u002Fknowledge\u002Finline-image\u002F12?w=700&f=webp\" alt=\"Step-by-step migration diagram: analysis, prioritize modules, build web layer, expand gradually\" loading=\"lazy\" class=\"w-full sm:w-1\u002F3 sm:float-left sm:mr-7 mb-5 rounded-2xl border border-[#E8E8ED] bg-[#F5F5F7]\" \u002F>\n\n\u003Ch2>What do you want to keep, and what is better left behind?\u003C\u002Fh2>\n\u003Cp>A legacy system always contains two types of logic: logic that is functionally strong, and logic that has simply grown over time.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Keep:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Authorization structures that were deliberately built\u003C\u002Fli>\n\u003Cli>Process steps that prevent errors or handle exceptions correctly\u003C\u002Fli>\n\u003Cli>Validation rules that align with how the business actually operates\u003C\u002Fli>\n\u003Cli>Integrations with processes that are still current\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Leave behind:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Fields without an owner that haven't been filled in for years\u003C\u002Fli>\n\u003Cli>Reports nobody opens anymore\u003C\u002Fli>\n\u003Cli>Temporary workarounds that have become permanent\u003C\u002Fli>\n\u003Cli>Manual intermediate steps made redundant by automation\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>A modernization is also an opportunity to clean up. Not every existing screen layout needs to reappear in the web app. Not every manual check is still necessary if automation can take it over. Good modernization means preserving what is functionally strong and letting go of what only exists because it was once put there.\u003C\u002Fp>\n\u003Ch2>When is a hybrid model smarter than full replacement?\u003C\u002Fh2>\n\u003Cp>Not every organization needs to replace its entire legacy environment in one move. A hybrid approach — where parts of the existing system remain active while new features are developed web-based — is often the most realistic route for SME organizations.\u003C\u002Fp>\n\u003Cp>This is a good choice when:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>The current database is stable, but accessibility falls short\u003C\u002Fli>\n\u003Cli>The investment needs to be spread across multiple phases\u003C\u002Fli>\n\u003Cli>Certain parts of the system can remain in use for years without modification\u003C\u002Fli>\n\u003Cli>The organization needs time to internally adjust to new ways of working\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>A hybrid model also fits better with how businesses actually change. Processes evolve, teams grow, requirements shift. Software that moves along with that — step by step — is more valuable in the long run than a rigid end vision that is already trailing reality by the time it is delivered.\u003C\u002Fp>\n\u003Ch2>Why are integrations so decisive for the end result?\u003C\u002Fh2>\n\u003Cp>For many businesses, the greatest gain lies not only in a web interface, but in better connections with other systems. Converting a legacy database to a web app only truly delivers value when data flows automatically.\u003C\u002Fp>\n\u003Cp>A concrete example: a installation company processes service visits in FileMaker. The technician fills in the form on paper, the back-office staff rekeys it, and the invoice is manually created in the accounting package. With a proper web app and API integration, the technician reports the service visit directly from his phone, the invoice is automatically created in Exact Online, and the customer sees the status in real time in their portal.\u003C\u002Fp>\n\u003Cp>That is not a future scenario — it is what is already possible when the technical architecture is right.\u003C\u002Fp>\n\u003Cp>Integrations often look simpler on paper than they are in practice. Authentication, data mapping, error handling, synchronization timing, and authorizations all play a significant role. A web app that looks good but integrates poorly solves only part of the problem.\u003C\u002Fp>\n\u003Ch2>What mistakes are made most often?\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>1. Assuming cheaper always means smarter\u003C\u002Fstrong>\nA quick rebuild without analysis seems attractive. But as soon as exceptions, data quality issues, or existing dependencies become visible, extra work piles up. What starts cheap becomes expensive to fix.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>2. Trying to tackle everything at once\u003C\u002Fstrong>\nWhen every process, report, and screen is in scope at the same time, the project becomes unmanageable. Better: start with a clear core and expand in a controlled manner.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>3. Forgetting that users need to work every day\u003C\u002Fstrong>\nA system can be technically excellent but still meet resistance if daily tasks become more cumbersome. Employees need to work faster and more easily — not just look at a more modern interface.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>4. Underestimating how much knowledge is embedded in the old system\u003C\u002Fstrong>\nEspecially in FileMaker environments, much of the business logic has been built up implicitly over the years. Anyone who does not explicitly account for this in the analysis will quickly build a neat web app that still leaves operational gaps.\u003C\u002Fp>\n\u003Ch2>Checklist: are you ready to get started?\u003C\u002Fh2>\n\u003Cp>Before starting a project, it helps to answer these questions:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> Do you know which processes are business-critical and which are optional?\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> Have the integrations needed with other systems been mapped out?\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> Are user roles and authorizations clearly defined?\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> Is there someone internally who can transfer process knowledge to the development team?\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> Is there a phased plan that delivers something functional quickly?\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> Has data quality and cleanup been accounted for?\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> Is the business case also expressed in operational gains, not just in build costs?\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>How strong is the business case, really?\u003C\u002Fh2>\n\u003Cp>Many businesses postpone modernization because they primarily look at development costs. Understandable — but incomplete. The real calculation also includes:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Time lost through manual data entry and duplicate registrations\u003C\u002Fli>\n\u003Cli>Error corrections that cost employees hours per week\u003C\u002Fli>\n\u003Cli>Limited availability of information that slows down decision-making\u003C\u002Fli>\n\u003Cli>Scalability blocked by technical limitations\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>When a web app eliminates manual steps on a daily basis — and makes information available faster to the people who base decisions on it — that translates directly into operational performance and customer service. You also extend the lifespan of process knowledge that has been proving its value for years. That is what makes converting a legacy database to a web app not an IT project, but an investment in continuity.\u003C\u002Fp>\n\u003Cp>The best first step is rarely the most radical one. Start with what meaningfully improves the business operation, build on that, and ensure that technology supports operations rather than dictating them.\u003C\u002Fp>\n\u003Chr>\n\u003Cp>Loggix helps organizations facing exactly this trade-off: a legacy environment that still works well, but needs to be more accessible, more scalable, or better connected. Whether it involves an existing FileMaker solution that needs to move to a web environment, a custom application that requires API integrations, or a phased modernization project where existing business logic is the starting point — we prefer to think through the approach together rather than immediately selling a new-build project. Get in touch if you'd like to explore the options for your situation.\u003C\u002Fp>\n","2026-07-10",1783670691000,[157,158,159,23,160,161,162,163],"legacy database","webapp","modernisering","API-integraties","maatwerksoftware","systeemmigratie","gefaseerde aanpak","\u002Fapi\u002Fknowledge\u002Fimage\u002F103\u002F?v=c4025f69d64d",{"id":166,"idKnowledge":167,"idDomain":15,"idCluster":15,"slug":168,"title":169,"description":170,"bodyMarkdown":171,"bodyHtml":172,"author":39,"date":173,"createdAt":174,"topics":175,"image":177,"hasDownload":28,"fileName":15,"youtubeId":27},"98","CE93071E-F225-6146-8857-FB4D4776FA75","filemaker-koppelen-met-exact-zo-werkt-het","Connecting FileMaker with Exact: here's how it works","Connecting FileMaker with Exact helps reduce manual work and errors. Read what works, where the pitfalls lie, and how to integrate smartly.","Anyone who manages orders in FileMaker and processes accounting in Exact is usually already familiar with the problem: the same data is entered in multiple places, checks take time, and errors only come to light when invoices or reports show discrepancies. Connecting FileMaker with Exact is therefore not a technical luxury, but a logical step toward making processes calmer, faster, and more manageable.\n\nThe question is not whether you should integrate, but how. Because a good integration does more than shuttle data back and forth. It must fit your way of working, your version of Exact, the quality of your FileMaker solution, and the degree to which you want to automate processes without disrupting daily operations.\n\n## Why connecting FileMaker with Exact often pays off immediately\n\nIn many organizations, FileMaker has grown into the operational heart of the business. It typically holds customer agreements, project data, hours, internal work orders, product configurations, or order logic that standard software does not handle well. Exact is then used for financial processing, article management, accounts receivable, accounts payable, or logistics administration.\n\nThat is not a problem in itself. The problem arises when employees manually copy data from FileMaker into Exact, or vice versa. Every process then becomes dependent on discipline, specific knowledge, and additional checks. As things get busier, discrepancies between systems emerge. An incorrect VAT rate, an outdated pricing agreement, or a missing debtor number may seem minor, but it ripples through into quotes, invoices, and management information.\n\nAn integration addresses exactly that bottleneck. Not by replacing FileMaker or Exact, but by connecting the strengths of both systems. FileMaker remains the system that supports your specific process. Exact remains the system in which financial and administrative processing takes place. That division of roles is often far more effective than a costly migration to a single package that ultimately does not fit your operations anyway.\n\n## What is typically integrated\n\nThe content of the integration varies by organization, but in practice we see a number of recurring scenarios. Customer data is synchronized from a single source so that debtor records are consistent everywhere. Articles, prices, or ledger information are retrieved from Exact to support the correct commercial or operational process in FileMaker. Orders or invoices that originate in FileMaker are then automatically forwarded to Exact for financial processing.\n\nSometimes the direction is primarily one-way. For example, when FileMaker is used for order processing and Exact only for accounting. In other cases, two-way traffic is required — for instance, when payment statuses, outstanding items, or article mutations need to flow back to FileMaker. That distinction matters, because a one-way integration is generally simpler, more stable, and less expensive than full two-way synchronization.\n\n## The technical route depends on your Exact environment\n\nAnyone wanting to connect FileMaker with Exact must first be clear about which Exact product is involved. Exact Online offers different integration options than older on-premise environments or specific Exact variants. That may sound like a detail, but it directly determines what is feasible, how securely the integration can be set up, and how much custom development is required.\n\nWith Exact Online, work is often done [via APIs](https:\u002F\u002Floggix.com\u002Fen\u002Fapis\u002F). This is usually the most future-proof route, as data exchange then takes place through controlled and documented interfaces. FileMaker can retrieve, create, or update data via an intermediate layer or direct API calls. Authentication, rate limits, error handling, and field mapping all play a major role in this.\n\nWith older or non-standard environments, the situation can differ. A connection via import files, middleware, or a hybrid approach may then be more practical. That is not inherently worse. Sometimes it is actually the most reliable solution within an existing IT environment. The right choice depends on your risks, your desired level of automation, and how much flexibility you will need later.\n\n## Connecting FileMaker with Exact requires careful data translation\n\nThe technology is rarely the hardest part. The real challenge usually lies in translating between two different logics. A FileMaker system is often fully tailored to your internal process. Exact, by contrast, is structured more tightly around administrative rules. As a result, fields may appear to match while their meaning in practice is subtly different.\n\nTake a customer record. In FileMaker, a single relationship can have multiple roles within sales, delivery, and service. In Exact, that may need to be split into a debtor, a delivery address, and a contact person. The same applies to articles, cost centers, projects, VAT codes, or payment terms. If that mapping is not designed carefully, you end up with an integration that works technically but still causes friction operationally.\n\nThat is why a good integration project does not start with programming, but with process analysis. Which data is leading? Where does data originate? Which mutations may be passed on automatically? What happens if a record changes in one system while the other has already been updated? These are not theoretical questions. They determine whether the integration brings calm or creates additional exceptions.\n\n## The biggest pitfalls in an integration\n\nA common mistake is trying to automate too much at once. Customers, articles, quotes, orders, invoices, payments, and reports are all included at the same time. That may seem efficient, but it makes a project unnecessarily complex. Especially with older FileMaker solutions, it is wiser to first establish one critical process properly — for example, order to invoice or synchronizing debtor data.\n\nA second pitfall is underestimating the quality of existing data. Duplicate customers, free-text input fields, outdated article codes, and inconsistent naming conventions are very common in custom-built systems. As long as a single team works with them, it is often still manageable. Once you start integrating, those inconsistencies become glaringly visible. That is frustrating, but also valuable: integration often forces much-needed data discipline.\n\nA third pitfall is the absence of error handling. Not every transaction succeeds on the first attempt. An integration must therefore be able to log what happens, signal where something goes wrong, and give employees enough information to make targeted corrections. Without that mechanism, automation quickly turns into invisible accumulation of errors.\n\n## What a pragmatic approach looks like\n\nFor most organizations, a phased approach works best. First, it is determined which process will yield the greatest benefit. This is often a process with a high volume of manual input, a high risk of error, or a direct impact on invoicing and cash flow. The data fields, business rules, and exceptions are then worked out in detail.\n\nNext, a small, controlled integration is built and tested with realistic scenarios. Not just a clean standard order, but also credit rules, exceptional VAT situations, missing values, and existing relationships already present in Exact. That is precisely where an integration proves whether it holds up in practice.\n\nOnly once that first step is running stably does it make sense to expand. Think of return flows from Exact, more extensive synchronization, or additional dashboards in FileMaker. This keeps risk, budget, and lead time under control. It is also the approach that works best in practice for organizations looking to modernize their [existing FileMaker environment](https:\u002F\u002Floggix.com\u002Fblog\u002Flegacy-database-vervangen-of-uitbreiden\u002F) without tearing everything apart.\n\n## When custom development is truly necessary\n\nSometimes it is assumed that a standard connector will suffice. That may be the case, but only if your process closely follows Exact's standard model. In organizations where FileMaker was built precisely because standard software did not fit, that is often unlikely. In those cases, the value of the integration lies in respecting your own workflow and translating it cleanly into the administrative reality of Exact.\n\nCustom development is especially needed when you have complex order logic, manage multiple legal entities, work project-based, or want to preserve historical FileMaker structures while still integrating in a more modern way. It then makes sense not only to look at the integration itself, but also at the quality and future-proofness of your FileMaker solution. Sometimes it is worthwhile to first clean up or restructure certain parts before extending the integration.\n\n## What does it deliver in day-to-day practice?\n\nThe benefit is rarely limited to time savings alone, although those are often immediately noticeable. At least as important is that employees need to check less, that financial data becomes available more quickly, and that processes become less dependent on specific individuals. Your organization becomes more predictable.\n\nFor management and operations, that typically means better steering information, less rework, and a shorter lead time between order, delivery, and invoicing. For IT, it means that an existing FileMaker system no longer needs to be an island, but becomes part of a functional software landscape. And for companies that have worked with a legacy solution for years, this is often the smartest path forward: not replacing everything, but connecting and improving in a targeted way.\n\nAnyone who takes connecting FileMaker with Exact seriously will usually quickly discover that it is not only about integration. It is also an opportunity to clean up processes, clarify responsibilities, and extract more value from systems that are already in place. That makes the investment not only technically justifiable, but above all commercially logical.\n\nA well-built integration ultimately feels not like a project, but like a relief in daily operations.","\u003Cp>Anyone who manages orders in FileMaker and processes accounting in Exact is usually already familiar with the problem: the same data is entered in multiple places, checks take time, and errors only come to light when invoices or reports show discrepancies. Connecting FileMaker with Exact is therefore not a technical luxury, but a logical step toward making processes calmer, faster, and more manageable.\u003C\u002Fp>\n\u003Cp>The question is not whether you should integrate, but how. Because a good integration does more than shuttle data back and forth. It must fit your way of working, your version of Exact, the quality of your FileMaker solution, and the degree to which you want to automate processes without disrupting daily operations.\u003C\u002Fp>\n\u003Ch2>Why connecting FileMaker with Exact often pays off immediately\u003C\u002Fh2>\n\u003Cp>In many organizations, FileMaker has grown into the operational heart of the business. It typically holds customer agreements, project data, hours, internal work orders, product configurations, or order logic that standard software does not handle well. Exact is then used for financial processing, article management, accounts receivable, accounts payable, or logistics administration.\u003C\u002Fp>\n\u003Cp>That is not a problem in itself. The problem arises when employees manually copy data from FileMaker into Exact, or vice versa. Every process then becomes dependent on discipline, specific knowledge, and additional checks. As things get busier, discrepancies between systems emerge. An incorrect VAT rate, an outdated pricing agreement, or a missing debtor number may seem minor, but it ripples through into quotes, invoices, and management information.\u003C\u002Fp>\n\u003Cp>An integration addresses exactly that bottleneck. Not by replacing FileMaker or Exact, but by connecting the strengths of both systems. FileMaker remains the system that supports your specific process. Exact remains the system in which financial and administrative processing takes place. That division of roles is often far more effective than a costly migration to a single package that ultimately does not fit your operations anyway.\u003C\u002Fp>\n\u003Ch2>What is typically integrated\u003C\u002Fh2>\n\u003Cp>The content of the integration varies by organization, but in practice we see a number of recurring scenarios. Customer data is synchronized from a single source so that debtor records are consistent everywhere. Articles, prices, or ledger information are retrieved from Exact to support the correct commercial or operational process in FileMaker. Orders or invoices that originate in FileMaker are then automatically forwarded to Exact for financial processing.\u003C\u002Fp>\n\u003Cp>Sometimes the direction is primarily one-way. For example, when FileMaker is used for order processing and Exact only for accounting. In other cases, two-way traffic is required — for instance, when payment statuses, outstanding items, or article mutations need to flow back to FileMaker. That distinction matters, because a one-way integration is generally simpler, more stable, and less expensive than full two-way synchronization.\u003C\u002Fp>\n\u003Ch2>The technical route depends on your Exact environment\u003C\u002Fh2>\n\u003Cp>Anyone wanting to connect FileMaker with Exact must first be clear about which Exact product is involved. Exact Online offers different integration options than older on-premise environments or specific Exact variants. That may sound like a detail, but it directly determines what is feasible, how securely the integration can be set up, and how much custom development is required.\u003C\u002Fp>\n\u003Cp>With Exact Online, work is often done \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fen\u002Fapis\u002F\">via APIs\u003C\u002Fa>. This is usually the most future-proof route, as data exchange then takes place through controlled and documented interfaces. FileMaker can retrieve, create, or update data via an intermediate layer or direct API calls. Authentication, rate limits, error handling, and field mapping all play a major role in this.\u003C\u002Fp>\n\u003Cp>With older or non-standard environments, the situation can differ. A connection via import files, middleware, or a hybrid approach may then be more practical. That is not inherently worse. Sometimes it is actually the most reliable solution within an existing IT environment. The right choice depends on your risks, your desired level of automation, and how much flexibility you will need later.\u003C\u002Fp>\n\u003Ch2>Connecting FileMaker with Exact requires careful data translation\u003C\u002Fh2>\n\u003Cp>The technology is rarely the hardest part. The real challenge usually lies in translating between two different logics. A FileMaker system is often fully tailored to your internal process. Exact, by contrast, is structured more tightly around administrative rules. As a result, fields may appear to match while their meaning in practice is subtly different.\u003C\u002Fp>\n\u003Cp>Take a customer record. In FileMaker, a single relationship can have multiple roles within sales, delivery, and service. In Exact, that may need to be split into a debtor, a delivery address, and a contact person. The same applies to articles, cost centers, projects, VAT codes, or payment terms. If that mapping is not designed carefully, you end up with an integration that works technically but still causes friction operationally.\u003C\u002Fp>\n\u003Cp>That is why a good integration project does not start with programming, but with process analysis. Which data is leading? Where does data originate? Which mutations may be passed on automatically? What happens if a record changes in one system while the other has already been updated? These are not theoretical questions. They determine whether the integration brings calm or creates additional exceptions.\u003C\u002Fp>\n\u003Ch2>The biggest pitfalls in an integration\u003C\u002Fh2>\n\u003Cp>A common mistake is trying to automate too much at once. Customers, articles, quotes, orders, invoices, payments, and reports are all included at the same time. That may seem efficient, but it makes a project unnecessarily complex. Especially with older FileMaker solutions, it is wiser to first establish one critical process properly — for example, order to invoice or synchronizing debtor data.\u003C\u002Fp>\n\u003Cp>A second pitfall is underestimating the quality of existing data. Duplicate customers, free-text input fields, outdated article codes, and inconsistent naming conventions are very common in custom-built systems. As long as a single team works with them, it is often still manageable. Once you start integrating, those inconsistencies become glaringly visible. That is frustrating, but also valuable: integration often forces much-needed data discipline.\u003C\u002Fp>\n\u003Cp>A third pitfall is the absence of error handling. Not every transaction succeeds on the first attempt. An integration must therefore be able to log what happens, signal where something goes wrong, and give employees enough information to make targeted corrections. Without that mechanism, automation quickly turns into invisible accumulation of errors.\u003C\u002Fp>\n\u003Ch2>What a pragmatic approach looks like\u003C\u002Fh2>\n\u003Cp>For most organizations, a phased approach works best. First, it is determined which process will yield the greatest benefit. This is often a process with a high volume of manual input, a high risk of error, or a direct impact on invoicing and cash flow. The data fields, business rules, and exceptions are then worked out in detail.\u003C\u002Fp>\n\u003Cp>Next, a small, controlled integration is built and tested with realistic scenarios. Not just a clean standard order, but also credit rules, exceptional VAT situations, missing values, and existing relationships already present in Exact. That is precisely where an integration proves whether it holds up in practice.\u003C\u002Fp>\n\u003Cp>Only once that first step is running stably does it make sense to expand. Think of return flows from Exact, more extensive synchronization, or additional dashboards in FileMaker. This keeps risk, budget, and lead time under control. It is also the approach that works best in practice for organizations looking to modernize their \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Flegacy-database-vervangen-of-uitbreiden\u002F\">existing FileMaker environment\u003C\u002Fa> without tearing everything apart.\u003C\u002Fp>\n\u003Ch2>When custom development is truly necessary\u003C\u002Fh2>\n\u003Cp>Sometimes it is assumed that a standard connector will suffice. That may be the case, but only if your process closely follows Exact's standard model. In organizations where FileMaker was built precisely because standard software did not fit, that is often unlikely. In those cases, the value of the integration lies in respecting your own workflow and translating it cleanly into the administrative reality of Exact.\u003C\u002Fp>\n\u003Cp>Custom development is especially needed when you have complex order logic, manage multiple legal entities, work project-based, or want to preserve historical FileMaker structures while still integrating in a more modern way. It then makes sense not only to look at the integration itself, but also at the quality and future-proofness of your FileMaker solution. Sometimes it is worthwhile to first clean up or restructure certain parts before extending the integration.\u003C\u002Fp>\n\u003Ch2>What does it deliver in day-to-day practice?\u003C\u002Fh2>\n\u003Cp>The benefit is rarely limited to time savings alone, although those are often immediately noticeable. At least as important is that employees need to check less, that financial data becomes available more quickly, and that processes become less dependent on specific individuals. Your organization becomes more predictable.\u003C\u002Fp>\n\u003Cp>For management and operations, that typically means better steering information, less rework, and a shorter lead time between order, delivery, and invoicing. For IT, it means that an existing FileMaker system no longer needs to be an island, but becomes part of a functional software landscape. And for companies that have worked with a legacy solution for years, this is often the smartest path forward: not replacing everything, but connecting and improving in a targeted way.\u003C\u002Fp>\n\u003Cp>Anyone who takes connecting FileMaker with Exact seriously will usually quickly discover that it is not only about integration. It is also an opportunity to clean up processes, clarify responsibilities, and extract more value from systems that are already in place. That makes the investment not only technically justifiable, but above all commercially logical.\u003C\u002Fp>\n\u003Cp>A well-built integration ultimately feels not like a project, but like a relief in daily operations.\u003C\u002Fp>\n","2026-07-05",1783264394000,[176],"Exact","\u002Fapi\u002Fknowledge\u002Fimage\u002F98\u002F?v=ba2d901c71bf",{"id":179,"idKnowledge":180,"idDomain":15,"idCluster":15,"slug":181,"title":182,"description":183,"bodyMarkdown":184,"bodyHtml":185,"author":39,"date":186,"createdAt":187,"topics":188,"image":190,"hasDownload":28,"fileName":15,"youtubeId":27},"97","0FC902B8-F505-C74F-8D67-891A0917DEEB","voice-agent-voor-leadopvolging-zin-of-niet","Voice agent for lead follow-up: worth it or not?","When does a voice agent for lead follow-up really work? Practical explanation of speed, integration, data, risks and return on investment.","A lead comes in, the sales team is in a meeting, and by the time someone calls back the attention is already gone. That is exactly where a voice agent for lead follow-up can add value - not as a gimmick, but as a practical tool to respond faster, qualify leads and immediately set follow-up actions in motion.\n\nMany companies, when thinking about this type of AI application, immediately picture a complete replacement of human contact. That is usually the wrong approach. In practice, it works better to view a voice agent as an operational layer between marketing, sales and back office. The agent handles the first point of contact, collects the right information, registers everything in the correct system and then prepares the next step for a team member.\n\n## What a voice agent for lead follow-up does and does not solve\n\nThe biggest gain almost always lies in speed and consistency. New leads are contacted immediately, even outside office hours or during peak moments. This prevents warm enquiries from going cold because a mailbox or task list is not checked until hours later.\n\nIn addition, a voice agent ensures a consistent approach. Every lead receives the same initial questions, the same logical routing and the same registration. That sounds simple, but this is precisely where many organisations go wrong. Information arrives via forms, email, phone calls and loose notes. Someone then has to figure out what is serious, what is urgent and what needs more context first.\n\nWhat a voice agent does not solve is a flawed process. If it is unclear when a lead is sales-ready, what data is minimally required or which system holds the source of truth, you are mostly automating confusion. Complex commercial conversations, exceptional situations and relationship-driven sales also often remain better handled by people.\n\n## When voice lead follow-up becomes truly interesting\n\nNot every company immediately benefits from this. The added value depends strongly on volume, response time and process discipline.\n\nA voice agent is particularly interesting when leads need to be followed up quickly, when opportunities are regularly missed due to capacity shortages, or when the initial intake is fairly structured. Think of companies dealing with demo requests, quote requests, intake conversations, service requests or inbound campaigns where basic information needs to be collected first.\n\nOrganisations with existing custom systems or a [FileMaker environment](https:\u002F\u002Floggix.com\u002Fblog\u002Fmaatwerk-database-software-laten-maken\u002F) can also benefit considerably. The gain there lies not only in the conversation itself, but in the connection with existing workflows. A lead who calls or is called should not end up as a loose transcript in a separate dashboard. The information must end up where employees actually work with it - in CRM, planning, ticketing or an [internal follow-up system](https:\u002F\u002Floggix.com\u002Fblog\u002Ffilemaker-api-koppeling-zonder-gedoe\u002F).\n\n## How a good voice agent for lead follow-up works\n\nA usable solution does not start with the voice, but with the process. Which leads come in? What questions are needed to qualify? When should a team member immediately take over? And which action should follow automatically?\n\nSuppose a prospect fills in a form for a product demo. Instead of waiting for manual follow-up, the voice agent can call right away. The agent confirms the request, asks about company size, use case, urgency and desired planning, and checks whether the lead meets predefined criteria. A task is then automatically created, an appointment scheduled or an account manager assigned.\n\nThis only works well if the underlying logic is tightly configured. The agent must know which answers are relevant, how variations in language should be interpreted and when a conversation needs to be transferred. A too open-ended conversation quickly leads to noise. A too rigid script feels unnatural. The right balance is usually a conversation with clear objectives, but with enough room for normal human phrasing.\n\n### The role of systems and integrations\n\nThis is often where the difference lies between a nice demo and a solution that actually delivers results. Lead follow-up is rarely a standalone process. Data often needs to be combined with forms, historical customer data, calendars, ERP, marketing automation or an existing CRM.\n\nIf those connections are missing, additional manual work arises. Someone still has to retype data, correct labels or manually assess exactly what the agent has recorded. A large part of the gain then disappears.\n\nFor organisations with legacy software or custom systems, this applies even more strongly. A voice agent must fit the reality of the business, not the other way around. That is precisely why a pragmatic implementation is important: connecting to existing data models, only automating what is sufficiently stable, and explicitly routing exceptions to people.\n\n## The business benefits - when the foundation is right\n\nThe most direct return is a shorter response time. In many sectors this has a direct effect on conversion. Whoever responds adequately first simply has a better chance of keeping the conversation going.\n\nIn addition, the administrative burden decreases. Data from the first contact is immediately recorded, summarised and linked to the correct lead or relation. This not only saves time, but also reduces interpretation errors and missing information.\n\nAnother advantage is scalability. During campaign peaks or seasonal pressure, additional capacity does not immediately need to be hired for repetitive intake conversations. The voice agent handles that first layer, while employees focus on conversations where genuine commercial or substantive judgement is required.\n\nYet return on investment is not solely a matter of more automation. Sometimes the gain lies in better selection. If a voice agent can establish early on that a request falls outside scope, is not urgent or is still insufficiently concrete, you prevent sales from losing time on low-probability leads.\n\n## Where things often go wrong\n\nThe biggest mistake is purchasing technology without process design. A voice agent is then set up as a kind of universal receptionist, while no one has clearly defined what a good end result looks like. The consequence is predictable: conversations feel strange, data is incomplete and employees do not trust the outcome.\n\nA second mistake is wanting to automate too much. Not every conversation needs to be handled by AI. Especially with larger deals, sensitive sectors or complex services, it is wise to have the voice agent primarily handle initial qualification and routing.\n\nLanguage and context are also frequently underestimated. Dutch conversations contain nuance, interruptions, accents and incomplete sentences. Your design must account for this. A solution that works neatly in a standard demo can perform very differently in real operational conditions.\n\n### Privacy, consent and reputation\n\nLead follow-up directly touches on trust. Companies must therefore be transparent about how conversations are conducted, what data is recorded and what happens with that information. This is not only a legal matter, but also a commercial one.\n\nIf a prospect gets the feeling of ending up in an unclear or forced flow, it damages that first contact. A good voice agent does not need to pretend to be human. Clarity often works better. Simply state that it is an automated assistant helping with quick follow-up and scheduling.\n\n## How to start small without doing a half-hearted job\n\nThe best approach is usually to start limited with a clear scenario. For example, only inbound lead follow-up after a web form, or only calling back new demo requests within a defined service or region.\n\nThen measure not only how many conversations have taken place, but especially what the business outcome is. How quickly is the first response? How many leads are correctly qualified? How much manual work disappears? And how many of the automatically followed-up leads actually enter a sales process?\n\nThis is precisely where custom work is often smarter than blindly rolling out a generic tool. Companies with existing internal processes, their own customer fields, specific qualification rules or a FileMaker environment benefit more from a solution that connects to those. Loggix sees in practice that the real value often lies not in the AI component alone, but in the combination of AI, workflow logic and solid system integrations.\n\n## Is a voice agent for lead follow-up the right step?\n\nThat depends on one straightforward question: are you currently demonstrably losing revenue or time due to slow, inconsistent or manual follow-up? If the answer is yes, then a voice agent can be a very worthwhile step. Not because it is new, but because it solves a concrete bottleneck.\n\nIf your processes are still unclear, your data is fragmented or your team does not use fixed qualification steps themselves, then cleaning that up first is smarter. A voice agent primarily amplifies what is already there - for better or worse.\n\nThe companies that benefit most from this take a level-headed approach. They start with the process, choose one clear use case, integrate with existing systems and let employees only do the work where human judgement truly makes a difference. Lead follow-up then becomes not only faster, but also more reliable and more scalable.\n\nThe best next step is therefore not to immediately choose a voice, but to get a clear picture of which first point of contact in your organisation is currently costing money, time or oversight. That is where a solution begins that also holds up in practice.\n\nIf you have ideas or want to know what is possible, feel free to contact us!","\u003Cp>A lead comes in, the sales team is in a meeting, and by the time someone calls back the attention is already gone. That is exactly where a voice agent for lead follow-up can add value - not as a gimmick, but as a practical tool to respond faster, qualify leads and immediately set follow-up actions in motion.\u003C\u002Fp>\n\u003Cp>Many companies, when thinking about this type of AI application, immediately picture a complete replacement of human contact. That is usually the wrong approach. In practice, it works better to view a voice agent as an operational layer between marketing, sales and back office. The agent handles the first point of contact, collects the right information, registers everything in the correct system and then prepares the next step for a team member.\u003C\u002Fp>\n\u003Ch2>What a voice agent for lead follow-up does and does not solve\u003C\u002Fh2>\n\u003Cp>The biggest gain almost always lies in speed and consistency. New leads are contacted immediately, even outside office hours or during peak moments. This prevents warm enquiries from going cold because a mailbox or task list is not checked until hours later.\u003C\u002Fp>\n\u003Cp>In addition, a voice agent ensures a consistent approach. Every lead receives the same initial questions, the same logical routing and the same registration. That sounds simple, but this is precisely where many organisations go wrong. Information arrives via forms, email, phone calls and loose notes. Someone then has to figure out what is serious, what is urgent and what needs more context first.\u003C\u002Fp>\n\u003Cp>What a voice agent does not solve is a flawed process. If it is unclear when a lead is sales-ready, what data is minimally required or which system holds the source of truth, you are mostly automating confusion. Complex commercial conversations, exceptional situations and relationship-driven sales also often remain better handled by people.\u003C\u002Fp>\n\u003Ch2>When voice lead follow-up becomes truly interesting\u003C\u002Fh2>\n\u003Cp>Not every company immediately benefits from this. The added value depends strongly on volume, response time and process discipline.\u003C\u002Fp>\n\u003Cp>A voice agent is particularly interesting when leads need to be followed up quickly, when opportunities are regularly missed due to capacity shortages, or when the initial intake is fairly structured. Think of companies dealing with demo requests, quote requests, intake conversations, service requests or inbound campaigns where basic information needs to be collected first.\u003C\u002Fp>\n\u003Cp>Organisations with existing custom systems or a \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Fmaatwerk-database-software-laten-maken\u002F\">FileMaker environment\u003C\u002Fa> can also benefit considerably. The gain there lies not only in the conversation itself, but in the connection with existing workflows. A lead who calls or is called should not end up as a loose transcript in a separate dashboard. The information must end up where employees actually work with it - in CRM, planning, ticketing or an \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Ffilemaker-api-koppeling-zonder-gedoe\u002F\">internal follow-up system\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2>How a good voice agent for lead follow-up works\u003C\u002Fh2>\n\u003Cp>A usable solution does not start with the voice, but with the process. Which leads come in? What questions are needed to qualify? When should a team member immediately take over? And which action should follow automatically?\u003C\u002Fp>\n\u003Cp>Suppose a prospect fills in a form for a product demo. Instead of waiting for manual follow-up, the voice agent can call right away. The agent confirms the request, asks about company size, use case, urgency and desired planning, and checks whether the lead meets predefined criteria. A task is then automatically created, an appointment scheduled or an account manager assigned.\u003C\u002Fp>\n\u003Cp>This only works well if the underlying logic is tightly configured. The agent must know which answers are relevant, how variations in language should be interpreted and when a conversation needs to be transferred. A too open-ended conversation quickly leads to noise. A too rigid script feels unnatural. The right balance is usually a conversation with clear objectives, but with enough room for normal human phrasing.\u003C\u002Fp>\n\u003Ch3>The role of systems and integrations\u003C\u002Fh3>\n\u003Cp>This is often where the difference lies between a nice demo and a solution that actually delivers results. Lead follow-up is rarely a standalone process. Data often needs to be combined with forms, historical customer data, calendars, ERP, marketing automation or an existing CRM.\u003C\u002Fp>\n\u003Cp>If those connections are missing, additional manual work arises. Someone still has to retype data, correct labels or manually assess exactly what the agent has recorded. A large part of the gain then disappears.\u003C\u002Fp>\n\u003Cp>For organisations with legacy software or custom systems, this applies even more strongly. A voice agent must fit the reality of the business, not the other way around. That is precisely why a pragmatic implementation is important: connecting to existing data models, only automating what is sufficiently stable, and explicitly routing exceptions to people.\u003C\u002Fp>\n\u003Ch2>The business benefits - when the foundation is right\u003C\u002Fh2>\n\u003Cp>The most direct return is a shorter response time. In many sectors this has a direct effect on conversion. Whoever responds adequately first simply has a better chance of keeping the conversation going.\u003C\u002Fp>\n\u003Cp>In addition, the administrative burden decreases. Data from the first contact is immediately recorded, summarised and linked to the correct lead or relation. This not only saves time, but also reduces interpretation errors and missing information.\u003C\u002Fp>\n\u003Cp>Another advantage is scalability. During campaign peaks or seasonal pressure, additional capacity does not immediately need to be hired for repetitive intake conversations. The voice agent handles that first layer, while employees focus on conversations where genuine commercial or substantive judgement is required.\u003C\u002Fp>\n\u003Cp>Yet return on investment is not solely a matter of more automation. Sometimes the gain lies in better selection. If a voice agent can establish early on that a request falls outside scope, is not urgent or is still insufficiently concrete, you prevent sales from losing time on low-probability leads.\u003C\u002Fp>\n\u003Ch2>Where things often go wrong\u003C\u002Fh2>\n\u003Cp>The biggest mistake is purchasing technology without process design. A voice agent is then set up as a kind of universal receptionist, while no one has clearly defined what a good end result looks like. The consequence is predictable: conversations feel strange, data is incomplete and employees do not trust the outcome.\u003C\u002Fp>\n\u003Cp>A second mistake is wanting to automate too much. Not every conversation needs to be handled by AI. Especially with larger deals, sensitive sectors or complex services, it is wise to have the voice agent primarily handle initial qualification and routing.\u003C\u002Fp>\n\u003Cp>Language and context are also frequently underestimated. Dutch conversations contain nuance, interruptions, accents and incomplete sentences. Your design must account for this. A solution that works neatly in a standard demo can perform very differently in real operational conditions.\u003C\u002Fp>\n\u003Ch3>Privacy, consent and reputation\u003C\u002Fh3>\n\u003Cp>Lead follow-up directly touches on trust. Companies must therefore be transparent about how conversations are conducted, what data is recorded and what happens with that information. This is not only a legal matter, but also a commercial one.\u003C\u002Fp>\n\u003Cp>If a prospect gets the feeling of ending up in an unclear or forced flow, it damages that first contact. A good voice agent does not need to pretend to be human. Clarity often works better. Simply state that it is an automated assistant helping with quick follow-up and scheduling.\u003C\u002Fp>\n\u003Ch2>How to start small without doing a half-hearted job\u003C\u002Fh2>\n\u003Cp>The best approach is usually to start limited with a clear scenario. For example, only inbound lead follow-up after a web form, or only calling back new demo requests within a defined service or region.\u003C\u002Fp>\n\u003Cp>Then measure not only how many conversations have taken place, but especially what the business outcome is. How quickly is the first response? How many leads are correctly qualified? How much manual work disappears? And how many of the automatically followed-up leads actually enter a sales process?\u003C\u002Fp>\n\u003Cp>This is precisely where custom work is often smarter than blindly rolling out a generic tool. Companies with existing internal processes, their own customer fields, specific qualification rules or a FileMaker environment benefit more from a solution that connects to those. Loggix sees in practice that the real value often lies not in the AI component alone, but in the combination of AI, workflow logic and solid system integrations.\u003C\u002Fp>\n\u003Ch2>Is a voice agent for lead follow-up the right step?\u003C\u002Fh2>\n\u003Cp>That depends on one straightforward question: are you currently demonstrably losing revenue or time due to slow, inconsistent or manual follow-up? If the answer is yes, then a voice agent can be a very worthwhile step. Not because it is new, but because it solves a concrete bottleneck.\u003C\u002Fp>\n\u003Cp>If your processes are still unclear, your data is fragmented or your team does not use fixed qualification steps themselves, then cleaning that up first is smarter. A voice agent primarily amplifies what is already there - for better or worse.\u003C\u002Fp>\n\u003Cp>The companies that benefit most from this take a level-headed approach. They start with the process, choose one clear use case, integrate with existing systems and let employees only do the work where human judgement truly makes a difference. Lead follow-up then becomes not only faster, but also more reliable and more scalable.\u003C\u002Fp>\n\u003Cp>The best next step is therefore not to immediately choose a voice, but to get a clear picture of which first point of contact in your organisation is currently costing money, time or oversight. That is where a solution begins that also holds up in practice.\u003C\u002Fp>\n\u003Cp>If you have ideas or want to know what is possible, feel free to contact us!\u003C\u002Fp>\n","2026-07-04",1783154314000,[189,86],"Voice Agent","\u002Fapi\u002Fknowledge\u002Fimage\u002F97\u002F?v=9e3e477df062",{"id":192,"idKnowledge":193,"idDomain":15,"idCluster":15,"slug":194,"title":195,"description":196,"bodyMarkdown":197,"bodyHtml":198,"author":39,"date":199,"createdAt":200,"topics":201,"image":204,"hasDownload":28,"fileName":15,"youtubeId":27},"95","4E7DD4EF-4E7D-8648-ACBF-21D11A71E1F4","ai-chatbot-voor-interne-kennisbank-werkt-het","AI chatbot for internal knowledge base: does it work?","An AI chatbot for an internal knowledge base provides faster answers, but only with good data, permissions, and management. Here's how to approach it practically.","An employee looks up a work instruction, finds three versions in SharePoint, an old PDF in Teams, and then just asks a colleague anyway. That costs time, interrupts work, and often produces different answers to the same question. This is precisely where an AI chatbot for an internal knowledge base can add a lot of value — provided you approach it correctly.\n\nFor many organisations, the problem is not a lack of information, but a lack of usable access to that information. Knowledge is spread across manuals, tickets, notes, emails, databases, and applications like FileMaker. Employees don't want to search through an archive. They want a direct, reliable answer that fits their role, process, and context.\n\n## When an AI chatbot for an internal knowledge base truly makes sense\n\nA chatbot is not a goal in itself. It is most interesting when knowledge frequently recurs in questions, information exists in multiple places, or processes depend on internal agreements. Think of HR questions about leave and expense claims, support questions about standard procedures, operational instructions on the shop floor, or product-specific knowledge for sales and service.\n\nIn such situations, a good knowledge base chatbot delivers more than just speed. You reduce the pressure on key users and administrators, lower the risk of incorrect interpretations, and make knowledge less dependent on a handful of experienced colleagues. The latter is especially relevant during team growth, turnover, or an ageing workforce.\n\nAt the same time: not every knowledge problem calls for AI. If information is heavily outdated, processes vary significantly per location, or source data is insufficiently managed, a chatbot will not solve those weaknesses. It will make them more visible. That is useful, but only if you are prepared to address the underlying knowledge structure.\n\n## What sets a good internal knowledge base chatbot apart\n\nMost people know chatbots from customer service or public websites. An internal variant sets higher requirements. Employees expect not just a friendly answer, but a correct answer based on internal rules, current documents, and access rights.\n\nThat is why an internal chatbot works best as a layer on top of existing knowledge sources and systems, not as a standalone island. The chatbot must be able to retrieve relevant information from the places where it already lives. That could be a document environment, but also a CRM, ticketing system, intranet, or a custom system in which operational knowledge is recorded.\n\nFor organisations with an [existing FileMaker environment](https:\u002F\u002Floggix.com\u002Fdatabases\u002F), this is an important point. Much critical business knowledge is not in neat manuals, but in screen texts, tables, notes, procedures, and process fields within the system itself. A chatbot only has real value if it can also work with that environment, rather than just searching PDF files.\n\n### Not just searching, but answering in context\n\nA classic search function returns documents. An AI chatbot ideally provides an answer, plus its source. That difference seems small but is operationally significant. A warehouse employee wants to know which procedure applies to a return without a packing slip. A project manager wants to know which step comes first in an internal approval process. An HR employee wants to know which exception applies to temporary contracts.\n\nIn all these cases, context matters. The best answer depends on department, location, product type, or customer agreement. A chatbot that only summarises general text falls short. A chatbot that can incorporate context from systems comes much closer to providing useful support in daily work.\n\n## The biggest misconception: more documents automatically means better\n\nMany companies believe a chatbot becomes smarter the moment you add enough documents. In practice, the opposite is true. If you supply large quantities of duplicate, outdated, or contradictory information, the likelihood of questionable answers increases.\n\nThe quality of an AI chatbot for an internal knowledge base therefore stands or falls with source management. Which documents are authoritative? Who owns the content? How are updates processed? Which information may or may not be visible per role? These are not minor details. They are the foundation.\n\nA pragmatic approach usually works better than a large knowledge base project. Start with a well-defined domain that generates many questions and where the source information is reasonably in order. For example, HR policy, service procedures, or internal IT support. There you quickly learn where users really run into problems, which answers are reliable, and which sources need additional cleanup.\n\n## What to watch for technically and organisationally\n\nAnyone who wants to deploy a chatbot internally must look beyond the language model. The real value lies in the entire chain around it. Source selection, permission structure, logging, feedback, and maintenance together determine whether the solution remains usable.\n\n### Permissions and confidentiality\n\nInternal knowledge is rarely fully public within an organisation. Financial procedures, contract information, personnel documents, or project-specific agreements may often only be viewed by certain roles. A chatbot must respect those permissions. Otherwise use becomes unsafe, or employees simply won't trust the tool.\n\n### Currency of the source\n\nIf your procedures change monthly but documents have to be uploaded manually, a backlog quickly develops. In that case, a connection to existing systems or document sources is usually better than a standalone knowledge collection. Less duplicate management means less chance of errors.\n\n### Traceability of answers\n\nAn employee must be able to see where an answer comes from. Not because everyone always wants to read the source, but because verification is essential in important processes. A chatbot without source references feels smart until a wrong answer appears. After that, trust disappears quickly.\n\n### Feedback and management\n\nThe first version is rarely perfect. Employees must be able to indicate whether an answer was useful, was missing, or was incorrect. Those signals are valuable for content management as well as technical refinement. Without a feedback loop, a chatbot quickly becomes a one-off experiment.\n\n## The best use cases are often less spectacular than expected\n\nThe most profitable applications are usually not the most striking ones. An internal chatbot does not need to be a general digital colleague. It often delivers the most value in very targeted scenarios.\n\nThink of first-line questions from employees, onboarding of new colleagues, recurring process questions in operations, support for helpdesk staff, or quick access to product specifications and exception rules. That is precisely where there is a lot of repetitive work, dependence on experienced colleagues, and delays in daily processes.\n\nThis makes the business case often surprisingly straightforward. Fewer interruptions. Less time spent searching. Less incorrect interpretation of procedures. Fewer escalations to scarce specialists. Those are concrete improvements that are easy to measure, especially if you are already handling many internal questions via email, chat, or telephone.\n\n## Does this also work with legacy systems?\n\nYes, often especially so. Companies with older custom systems regularly assume AI only becomes relevant later, after a full overhaul. That is far from always necessary. If core knowledge and process logic are already present in existing systems, a chatbot can actually help make that knowledge more accessible without immediately replacing everything.\n\nThere is also an important distinction here between hype and practical implementation. An organisation does not first need to build an entirely new platform to benefit from AI. Often, smarter access to existing data is more valuable than yet another new system alongside the current environment.\n\nFor companies with FileMaker, [linked databases](https:\u002F\u002Floggix.com\u002Fblog\u002Fgemini-embedding-2-geef-je-filemaker-oplossing-een-ai-geheugen\u002F), or their own internal tools, this is relevant. With the right architecture, you can [unlock existing information sources](https:\u002F\u002Floggix.com\u002Fblog\u002Ffilemaker-mcp-server-ai-and-hosted-fm-files\u002F), combine them, and offer them in a controlled manner via a chatbot interface. That requires technical knowledge of both the AI component and the underlying systems. But it also avoids a costly rip-and-replace approach that places unnecessary strain on operations.\n\n## How to start small without thinking small\n\nA good starting point is not: we want a company-wide AI assistant. A good starting point is: which questions cost us the most time today, where does the information for those questions reside, and who needs to be able to rely on it?\n\nThen choose one well-defined knowledge domain, set up source management rigorously, and measure usage from day one. Look not only at the number of chats, but especially at intercepted questions, time saved, quality of answers, and a reduction in internal disruptions. That gives a more realistic picture of returns.\n\nAt Loggix, we see that this approach works best in organisations where processes are already digitally supported, but knowledge still lives in fragmented form across multiple systems and documents. In that case, the chatbot is not a standalone experiment, but a practical extension of the software environment that is already in place.\n\nThe real gain ultimately lies not in the fact that employees can chat with AI. That novelty passes quickly. The gain lies in working faster and more consistently, less dependence on individual knowledge holders, and better use of the systems and information you already have.\n\nIf you are considering making an internal knowledge base more intelligently accessible, do not start with the technology, but with the questions your organisation answers anew every week. That is usually where the clearest starting point lies — and often where the fastest results are found as well.","\u003Cp>An employee looks up a work instruction, finds three versions in SharePoint, an old PDF in Teams, and then just asks a colleague anyway. That costs time, interrupts work, and often produces different answers to the same question. This is precisely where an AI chatbot for an internal knowledge base can add a lot of value — provided you approach it correctly.\u003C\u002Fp>\n\u003Cp>For many organisations, the problem is not a lack of information, but a lack of usable access to that information. Knowledge is spread across manuals, tickets, notes, emails, databases, and applications like FileMaker. Employees don't want to search through an archive. They want a direct, reliable answer that fits their role, process, and context.\u003C\u002Fp>\n\u003Ch2>When an AI chatbot for an internal knowledge base truly makes sense\u003C\u002Fh2>\n\u003Cp>A chatbot is not a goal in itself. It is most interesting when knowledge frequently recurs in questions, information exists in multiple places, or processes depend on internal agreements. Think of HR questions about leave and expense claims, support questions about standard procedures, operational instructions on the shop floor, or product-specific knowledge for sales and service.\u003C\u002Fp>\n\u003Cp>In such situations, a good knowledge base chatbot delivers more than just speed. You reduce the pressure on key users and administrators, lower the risk of incorrect interpretations, and make knowledge less dependent on a handful of experienced colleagues. The latter is especially relevant during team growth, turnover, or an ageing workforce.\u003C\u002Fp>\n\u003Cp>At the same time: not every knowledge problem calls for AI. If information is heavily outdated, processes vary significantly per location, or source data is insufficiently managed, a chatbot will not solve those weaknesses. It will make them more visible. That is useful, but only if you are prepared to address the underlying knowledge structure.\u003C\u002Fp>\n\u003Ch2>What sets a good internal knowledge base chatbot apart\u003C\u002Fh2>\n\u003Cp>Most people know chatbots from customer service or public websites. An internal variant sets higher requirements. Employees expect not just a friendly answer, but a correct answer based on internal rules, current documents, and access rights.\u003C\u002Fp>\n\u003Cp>That is why an internal chatbot works best as a layer on top of existing knowledge sources and systems, not as a standalone island. The chatbot must be able to retrieve relevant information from the places where it already lives. That could be a document environment, but also a CRM, ticketing system, intranet, or a custom system in which operational knowledge is recorded.\u003C\u002Fp>\n\u003Cp>For organisations with an \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fdatabases\u002F\">existing FileMaker environment\u003C\u002Fa>, this is an important point. Much critical business knowledge is not in neat manuals, but in screen texts, tables, notes, procedures, and process fields within the system itself. A chatbot only has real value if it can also work with that environment, rather than just searching PDF files.\u003C\u002Fp>\n\u003Ch3>Not just searching, but answering in context\u003C\u002Fh3>\n\u003Cp>A classic search function returns documents. An AI chatbot ideally provides an answer, plus its source. That difference seems small but is operationally significant. A warehouse employee wants to know which procedure applies to a return without a packing slip. A project manager wants to know which step comes first in an internal approval process. An HR employee wants to know which exception applies to temporary contracts.\u003C\u002Fp>\n\u003Cp>In all these cases, context matters. The best answer depends on department, location, product type, or customer agreement. A chatbot that only summarises general text falls short. A chatbot that can incorporate context from systems comes much closer to providing useful support in daily work.\u003C\u002Fp>\n\u003Ch2>The biggest misconception: more documents automatically means better\u003C\u002Fh2>\n\u003Cp>Many companies believe a chatbot becomes smarter the moment you add enough documents. In practice, the opposite is true. If you supply large quantities of duplicate, outdated, or contradictory information, the likelihood of questionable answers increases.\u003C\u002Fp>\n\u003Cp>The quality of an AI chatbot for an internal knowledge base therefore stands or falls with source management. Which documents are authoritative? Who owns the content? How are updates processed? Which information may or may not be visible per role? These are not minor details. They are the foundation.\u003C\u002Fp>\n\u003Cp>A pragmatic approach usually works better than a large knowledge base project. Start with a well-defined domain that generates many questions and where the source information is reasonably in order. For example, HR policy, service procedures, or internal IT support. There you quickly learn where users really run into problems, which answers are reliable, and which sources need additional cleanup.\u003C\u002Fp>\n\u003Ch2>What to watch for technically and organisationally\u003C\u002Fh2>\n\u003Cp>Anyone who wants to deploy a chatbot internally must look beyond the language model. The real value lies in the entire chain around it. Source selection, permission structure, logging, feedback, and maintenance together determine whether the solution remains usable.\u003C\u002Fp>\n\u003Ch3>Permissions and confidentiality\u003C\u002Fh3>\n\u003Cp>Internal knowledge is rarely fully public within an organisation. Financial procedures, contract information, personnel documents, or project-specific agreements may often only be viewed by certain roles. A chatbot must respect those permissions. Otherwise use becomes unsafe, or employees simply won't trust the tool.\u003C\u002Fp>\n\u003Ch3>Currency of the source\u003C\u002Fh3>\n\u003Cp>If your procedures change monthly but documents have to be uploaded manually, a backlog quickly develops. In that case, a connection to existing systems or document sources is usually better than a standalone knowledge collection. Less duplicate management means less chance of errors.\u003C\u002Fp>\n\u003Ch3>Traceability of answers\u003C\u002Fh3>\n\u003Cp>An employee must be able to see where an answer comes from. Not because everyone always wants to read the source, but because verification is essential in important processes. A chatbot without source references feels smart until a wrong answer appears. After that, trust disappears quickly.\u003C\u002Fp>\n\u003Ch3>Feedback and management\u003C\u002Fh3>\n\u003Cp>The first version is rarely perfect. Employees must be able to indicate whether an answer was useful, was missing, or was incorrect. Those signals are valuable for content management as well as technical refinement. Without a feedback loop, a chatbot quickly becomes a one-off experiment.\u003C\u002Fp>\n\u003Ch2>The best use cases are often less spectacular than expected\u003C\u002Fh2>\n\u003Cp>The most profitable applications are usually not the most striking ones. An internal chatbot does not need to be a general digital colleague. It often delivers the most value in very targeted scenarios.\u003C\u002Fp>\n\u003Cp>Think of first-line questions from employees, onboarding of new colleagues, recurring process questions in operations, support for helpdesk staff, or quick access to product specifications and exception rules. That is precisely where there is a lot of repetitive work, dependence on experienced colleagues, and delays in daily processes.\u003C\u002Fp>\n\u003Cp>This makes the business case often surprisingly straightforward. Fewer interruptions. Less time spent searching. Less incorrect interpretation of procedures. Fewer escalations to scarce specialists. Those are concrete improvements that are easy to measure, especially if you are already handling many internal questions via email, chat, or telephone.\u003C\u002Fp>\n\u003Ch2>Does this also work with legacy systems?\u003C\u002Fh2>\n\u003Cp>Yes, often especially so. Companies with older custom systems regularly assume AI only becomes relevant later, after a full overhaul. That is far from always necessary. If core knowledge and process logic are already present in existing systems, a chatbot can actually help make that knowledge more accessible without immediately replacing everything.\u003C\u002Fp>\n\u003Cp>There is also an important distinction here between hype and practical implementation. An organisation does not first need to build an entirely new platform to benefit from AI. Often, smarter access to existing data is more valuable than yet another new system alongside the current environment.\u003C\u002Fp>\n\u003Cp>For companies with FileMaker, \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Fgemini-embedding-2-geef-je-filemaker-oplossing-een-ai-geheugen\u002F\">linked databases\u003C\u002Fa>, or their own internal tools, this is relevant. With the right architecture, you can \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Ffilemaker-mcp-server-ai-and-hosted-fm-files\u002F\">unlock existing information sources\u003C\u002Fa>, combine them, and offer them in a controlled manner via a chatbot interface. That requires technical knowledge of both the AI component and the underlying systems. But it also avoids a costly rip-and-replace approach that places unnecessary strain on operations.\u003C\u002Fp>\n\u003Ch2>How to start small without thinking small\u003C\u002Fh2>\n\u003Cp>A good starting point is not: we want a company-wide AI assistant. A good starting point is: which questions cost us the most time today, where does the information for those questions reside, and who needs to be able to rely on it?\u003C\u002Fp>\n\u003Cp>Then choose one well-defined knowledge domain, set up source management rigorously, and measure usage from day one. Look not only at the number of chats, but especially at intercepted questions, time saved, quality of answers, and a reduction in internal disruptions. That gives a more realistic picture of returns.\u003C\u002Fp>\n\u003Cp>At Loggix, we see that this approach works best in organisations where processes are already digitally supported, but knowledge still lives in fragmented form across multiple systems and documents. In that case, the chatbot is not a standalone experiment, but a practical extension of the software environment that is already in place.\u003C\u002Fp>\n\u003Cp>The real gain ultimately lies not in the fact that employees can chat with AI. That novelty passes quickly. The gain lies in working faster and more consistently, less dependence on individual knowledge holders, and better use of the systems and information you already have.\u003C\u002Fp>\n\u003Cp>If you are considering making an internal knowledge base more intelligently accessible, do not start with the technology, but with the questions your organisation answers anew every week. That is usually where the clearest starting point lies — and often where the fastest results are found as well.\u003C\u002Fp>\n","2026-07-03",1783091777000,[23,86,202,203],"Kennisdeling","Chatbot","\u002Fapi\u002Fknowledge\u002Fimage\u002F95\u002F?v=a0c5c953ebaf",{"id":206,"idKnowledge":207,"idDomain":15,"idCluster":15,"slug":208,"title":209,"description":210,"bodyMarkdown":211,"bodyHtml":212,"author":39,"date":213,"createdAt":214,"topics":215,"image":216,"hasDownload":28,"fileName":15,"youtubeId":27},"94","19D21E4E-153A-734B-A49B-76E4A673EAB3","rag-systeem-voor-bedrijven-slim-of-te-vroeg","RAG system for businesses: smart or too soon?","When does a RAG system for businesses make sense? Read where RAG truly delivers value, what preconditions apply, and where the pitfalls lie.","A chatbot that politely answers questions based on internet knowledge is not very interesting for most organisations. A system that provides answers based on your own manuals, quotes, service procedures, contracts, and project documentation is. That is where a RAG system for businesses comes into view: not as a toy, but as a practical way to make existing knowledge usable in day-to-day processes.\n\nThe question is not simply whether RAG is technically possible. The real question is whether it fits your organisation, where the return lies, and which preconditions need to be in order first. For many SMEs, the value lies not in a large AI rollout, but in a targeted application that saves time, reduces errors, and gets employees to the right information faster.\n\n## What is a RAG system for businesses?\n\nRAG stands for Retrieval-Augmented Generation. In plain language, this means: an AI model does not generate its answer solely on the basis of general training, but first retrieves relevant information from your own sources. Think of internal knowledge bases, FileMaker data, SharePoint documents, PDF manuals, ticketing systems, or product information.\n\nThat distinction matters. A standard language model can formulate fluently, but does not automatically know which version of your pricing agreements applies, what your return process exactly entails, or which technical exceptions your service team uses. A RAG solution adds that business context at the moment a question is asked.\n\nFor businesses, that is usually the only form of AI that gains real working value. Not because it is more spectacular, but because it is closer to the operation.\n\n## Where a RAG system for businesses truly makes a difference\n\nThe most meaningful applications are often found in departments where a great deal of knowledge is spread across systems, documents, and people. Customer service is an obvious example. Employees there frequently look up the same information across different sources. A well-configured RAG system can bring together procedures, product specifications, and previous cases into a usable answer, including a reference to the internal documentation.\n\nIn sales and project work it can also make a significant difference. Suppose account managers want to quickly find out which solution was previously offered to similar customers, what conditions applied, and which technical requirements were specified at the time. It is then more useful to make existing project data and documentation accessible than to add yet another CRM screen.\n\nIn operations and back-office work there is often even more to gain. Much of the work there revolves around exceptions, internal agreements, and process variants that do not fit neatly into one standard package. Organisations with [custom processes](https:\u002F\u002Floggix.com\u002Fblog\u002Ffilemaker-systeem-moderniseren-zonder-risico\u002F) often have a great deal of knowledge but little structure in access to it. A RAG approach can then help make existing systems smarter without rebuilding everything from scratch.\n\n## RAG only works if the source information is usable\n\nThis is where things often go wrong in practice. Companies hear that RAG reduces hallucinations and then assume that the quality of their documentation becomes less important. The opposite is true. If outdated manuals, duplicate versions, and loose notes form the source, you will get faster answers, but not necessarily better ones.\n\nA RAG system is therefore not a silver bullet for a messy information landscape. It tends to make that mess more visible rather than less. That is not purely a disadvantage. It can actually help clarify which knowledge is crucial, which sources should be authoritative, and where processes in practice deviate from what is on paper.\n\nFor many organisations, that is a healthier starting point than immediately formulating a broad AI strategy. First determine which information needs to be reliable, who owns that knowledge, and how updates are managed. Only then does a RAG solution have a real chance of success.\n\n## The technology is not the hardest part\n\nFrom the outside, a RAG project looks primarily like an AI question. In reality, the complexity usually lies in the layers around it. Which systems supply the source data? How often is that data refreshed? Should certain documents only be visible to specific roles? And how do you prevent an employee from receiving a convincing answer based on draft information or an outdated work instruction?\n\nThese are not theoretical details. They determine whether a solution is safe and usable in daily practice. Especially in companies where information is spread across FileMaker solutions, ERP software, cloud storage, email archives, and standalone documents, the biggest gain is often not the model itself but the way [data flows](https:\u002F\u002Floggix.com\u002Fapis\u002F) are set up.\n\nThat is why a pragmatic approach is usually better than rolling out a large AI platform all at once. Start with one clearly defined use case, one set of reliable sources, and one well-defined user group. If that works, you can expand.\n\n## When RAG works better than a classic search function\n\nThis question is valid, because many organisations already have search capabilities in their document management system or intranet. Not every information request requires AI. If employees know exactly which document they are looking for and know the name or location, a standard search function is often faster and cheaper.\n\nRAG becomes more interesting once questions are less precise. For example, when someone wants to know how an exceptional situation is normally handled, which product variant suits a specific customer, or which steps should be followed given a combination of conditions. It then helps that a system collects relevant sections and returns them in natural language.\n\nNuance remains necessary, however. If a process is legally sensitive, financially critical, or heavily regulated, you may sometimes prefer not to receive a generated answer but a direct reference to the correct source document. In such cases, a hybrid approach is often wiser: AI for context and summarisation, with a clear reference to the original source for verification.\n\n## Integration determines the real business value\n\nA standalone AI screen is rarely enough. Most value is created when a RAG solution is placed where people already work. That could be in a customer portal, in an internal service app, in a FileMaker environment, or as part of a workflow in which questions are directly linked to customers, orders, files, or projects.\n\nThat is when RAG changes from an interesting demo into a usable working tool. A service employee does not have to search separately for documentation but receives context within the ticket. A project manager sees relevant knowledge alongside a specific file. An internal application can base answers on both data and documents, rather than on free text sources alone.\n\nFor businesses with [existing FileMaker systems](https:\u002F\u002Floggix.com\u002Fblog\u002Fwhy-use-filemaker-features-importance-and-ai-integration\u002F) or other custom applications, this is especially relevant. Years of operational knowledge and logic are often already embedded in the system. You do not want to throw that value away. By modernising and integrating, a RAG layer can strengthen that existing environment rather than replace it. That is usually cheaper, faster, and organisationally more realistic than a complete rebuild.\n\n## What does it cost — and when does it pay for itself?\n\nThe costs of a RAG system for businesses depend less on the AI model than many people think. The largest items are often preparation, data connections, access rights, testing, and management. Anyone who only calculates model costs is being overly optimistic.\n\nThe return, on the other hand, is often easy to substantiate when the use case is well chosen. Look at time lost through searching, the number of internal queries, error-prone actions, onboarding time for new employees, or delays in customer responses. If a solution brings measurable improvement there, the business case is usually stronger than with broad, vague AI objectives.\n\nNot every company therefore needs to immediately build a comprehensive knowledge assistant for the entire organisation. Sometimes a compact solution for support, quality management, or internal operations is enough to prove the value. From that foundation you can scale up with less risk.\n\n## Where you need to be honest with yourself upfront\n\nRAG is not a substitute for process discipline. If your organisation has no clear source ownership, barely maintains knowledge, and exceptions exist only in employees' heads, AI will not fix that neatly. It can, however, help make those weak spots visible.\n\nIn addition, you need to decide how much autonomy you give the system. Only showing answers based on approved sources is different from also allowing summaries, recommendations, or draft texts to be generated. The greater the freedom, the more governance is required.\n\nThe best implementations are therefore usually boring in the right way. They do one thing well, connect to real work processes, and are set up with technical rigour. That is less fashionable than promising an all-in-one solution, but far more valuable for the operation.\n\nFor organisations that have worked for years with their own databases, custom processes, and connected applications, that is a familiar principle. Technology only delivers results when it fits the way work actually runs. That is precisely where the strength of a well-configured RAG approach also lies — not as a standalone experiment, but as a practical extension of the systems that already carry your business.\n\nIf you are considering getting started, do not begin with the question of which AI tool is the most popular. Begin with the question of where employees are currently losing time due to fragmented knowledge, and which reliable information you already have in-house. That is usually where the fastest and most sensible first step lies.\n\nGet in touch if you would like to know more about how we can start small and targeted with RAG in your organisation.","\u003Cp>A chatbot that politely answers questions based on internet knowledge is not very interesting for most organisations. A system that provides answers based on your own manuals, quotes, service procedures, contracts, and project documentation is. That is where a RAG system for businesses comes into view: not as a toy, but as a practical way to make existing knowledge usable in day-to-day processes.\u003C\u002Fp>\n\u003Cp>The question is not simply whether RAG is technically possible. The real question is whether it fits your organisation, where the return lies, and which preconditions need to be in order first. For many SMEs, the value lies not in a large AI rollout, but in a targeted application that saves time, reduces errors, and gets employees to the right information faster.\u003C\u002Fp>\n\u003Ch2>What is a RAG system for businesses?\u003C\u002Fh2>\n\u003Cp>RAG stands for Retrieval-Augmented Generation. In plain language, this means: an AI model does not generate its answer solely on the basis of general training, but first retrieves relevant information from your own sources. Think of internal knowledge bases, FileMaker data, SharePoint documents, PDF manuals, ticketing systems, or product information.\u003C\u002Fp>\n\u003Cp>That distinction matters. A standard language model can formulate fluently, but does not automatically know which version of your pricing agreements applies, what your return process exactly entails, or which technical exceptions your service team uses. A RAG solution adds that business context at the moment a question is asked.\u003C\u002Fp>\n\u003Cp>For businesses, that is usually the only form of AI that gains real working value. Not because it is more spectacular, but because it is closer to the operation.\u003C\u002Fp>\n\u003Ch2>Where a RAG system for businesses truly makes a difference\u003C\u002Fh2>\n\u003Cp>The most meaningful applications are often found in departments where a great deal of knowledge is spread across systems, documents, and people. Customer service is an obvious example. Employees there frequently look up the same information across different sources. A well-configured RAG system can bring together procedures, product specifications, and previous cases into a usable answer, including a reference to the internal documentation.\u003C\u002Fp>\n\u003Cp>In sales and project work it can also make a significant difference. Suppose account managers want to quickly find out which solution was previously offered to similar customers, what conditions applied, and which technical requirements were specified at the time. It is then more useful to make existing project data and documentation accessible than to add yet another CRM screen.\u003C\u002Fp>\n\u003Cp>In operations and back-office work there is often even more to gain. Much of the work there revolves around exceptions, internal agreements, and process variants that do not fit neatly into one standard package. Organisations with \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Ffilemaker-systeem-moderniseren-zonder-risico\u002F\">custom processes\u003C\u002Fa> often have a great deal of knowledge but little structure in access to it. A RAG approach can then help make existing systems smarter without rebuilding everything from scratch.\u003C\u002Fp>\n\u003Ch2>RAG only works if the source information is usable\u003C\u002Fh2>\n\u003Cp>This is where things often go wrong in practice. Companies hear that RAG reduces hallucinations and then assume that the quality of their documentation becomes less important. The opposite is true. If outdated manuals, duplicate versions, and loose notes form the source, you will get faster answers, but not necessarily better ones.\u003C\u002Fp>\n\u003Cp>A RAG system is therefore not a silver bullet for a messy information landscape. It tends to make that mess more visible rather than less. That is not purely a disadvantage. It can actually help clarify which knowledge is crucial, which sources should be authoritative, and where processes in practice deviate from what is on paper.\u003C\u002Fp>\n\u003Cp>For many organisations, that is a healthier starting point than immediately formulating a broad AI strategy. First determine which information needs to be reliable, who owns that knowledge, and how updates are managed. Only then does a RAG solution have a real chance of success.\u003C\u002Fp>\n\u003Ch2>The technology is not the hardest part\u003C\u002Fh2>\n\u003Cp>From the outside, a RAG project looks primarily like an AI question. In reality, the complexity usually lies in the layers around it. Which systems supply the source data? How often is that data refreshed? Should certain documents only be visible to specific roles? And how do you prevent an employee from receiving a convincing answer based on draft information or an outdated work instruction?\u003C\u002Fp>\n\u003Cp>These are not theoretical details. They determine whether a solution is safe and usable in daily practice. Especially in companies where information is spread across FileMaker solutions, ERP software, cloud storage, email archives, and standalone documents, the biggest gain is often not the model itself but the way \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fapis\u002F\">data flows\u003C\u002Fa> are set up.\u003C\u002Fp>\n\u003Cp>That is why a pragmatic approach is usually better than rolling out a large AI platform all at once. Start with one clearly defined use case, one set of reliable sources, and one well-defined user group. If that works, you can expand.\u003C\u002Fp>\n\u003Ch2>When RAG works better than a classic search function\u003C\u002Fh2>\n\u003Cp>This question is valid, because many organisations already have search capabilities in their document management system or intranet. Not every information request requires AI. If employees know exactly which document they are looking for and know the name or location, a standard search function is often faster and cheaper.\u003C\u002Fp>\n\u003Cp>RAG becomes more interesting once questions are less precise. For example, when someone wants to know how an exceptional situation is normally handled, which product variant suits a specific customer, or which steps should be followed given a combination of conditions. It then helps that a system collects relevant sections and returns them in natural language.\u003C\u002Fp>\n\u003Cp>Nuance remains necessary, however. If a process is legally sensitive, financially critical, or heavily regulated, you may sometimes prefer not to receive a generated answer but a direct reference to the correct source document. In such cases, a hybrid approach is often wiser: AI for context and summarisation, with a clear reference to the original source for verification.\u003C\u002Fp>\n\u003Ch2>Integration determines the real business value\u003C\u002Fh2>\n\u003Cp>A standalone AI screen is rarely enough. Most value is created when a RAG solution is placed where people already work. That could be in a customer portal, in an internal service app, in a FileMaker environment, or as part of a workflow in which questions are directly linked to customers, orders, files, or projects.\u003C\u002Fp>\n\u003Cp>That is when RAG changes from an interesting demo into a usable working tool. A service employee does not have to search separately for documentation but receives context within the ticket. A project manager sees relevant knowledge alongside a specific file. An internal application can base answers on both data and documents, rather than on free text sources alone.\u003C\u002Fp>\n\u003Cp>For businesses with \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Fwhy-use-filemaker-features-importance-and-ai-integration\u002F\">existing FileMaker systems\u003C\u002Fa> or other custom applications, this is especially relevant. Years of operational knowledge and logic are often already embedded in the system. You do not want to throw that value away. By modernising and integrating, a RAG layer can strengthen that existing environment rather than replace it. That is usually cheaper, faster, and organisationally more realistic than a complete rebuild.\u003C\u002Fp>\n\u003Ch2>What does it cost — and when does it pay for itself?\u003C\u002Fh2>\n\u003Cp>The costs of a RAG system for businesses depend less on the AI model than many people think. The largest items are often preparation, data connections, access rights, testing, and management. Anyone who only calculates model costs is being overly optimistic.\u003C\u002Fp>\n\u003Cp>The return, on the other hand, is often easy to substantiate when the use case is well chosen. Look at time lost through searching, the number of internal queries, error-prone actions, onboarding time for new employees, or delays in customer responses. If a solution brings measurable improvement there, the business case is usually stronger than with broad, vague AI objectives.\u003C\u002Fp>\n\u003Cp>Not every company therefore needs to immediately build a comprehensive knowledge assistant for the entire organisation. Sometimes a compact solution for support, quality management, or internal operations is enough to prove the value. From that foundation you can scale up with less risk.\u003C\u002Fp>\n\u003Ch2>Where you need to be honest with yourself upfront\u003C\u002Fh2>\n\u003Cp>RAG is not a substitute for process discipline. If your organisation has no clear source ownership, barely maintains knowledge, and exceptions exist only in employees' heads, AI will not fix that neatly. It can, however, help make those weak spots visible.\u003C\u002Fp>\n\u003Cp>In addition, you need to decide how much autonomy you give the system. Only showing answers based on approved sources is different from also allowing summaries, recommendations, or draft texts to be generated. The greater the freedom, the more governance is required.\u003C\u002Fp>\n\u003Cp>The best implementations are therefore usually boring in the right way. They do one thing well, connect to real work processes, and are set up with technical rigour. That is less fashionable than promising an all-in-one solution, but far more valuable for the operation.\u003C\u002Fp>\n\u003Cp>For organisations that have worked for years with their own databases, custom processes, and connected applications, that is a familiar principle. Technology only delivers results when it fits the way work actually runs. That is precisely where the strength of a well-configured RAG approach also lies — not as a standalone experiment, but as a practical extension of the systems that already carry your business.\u003C\u002Fp>\n\u003Cp>If you are considering getting started, do not begin with the question of which AI tool is the most popular. Begin with the question of where employees are currently losing time due to fragmented knowledge, and which reliable information you already have in-house. That is usually where the fastest and most sensible first step lies.\u003C\u002Fp>\n\u003Cp>Get in touch if you would like to know more about how we can start small and targeted with RAG in your organisation.\u003C\u002Fp>\n","2026-07-02",1782989814000,[87,23],"\u002Fapi\u002Fknowledge\u002Fimage\u002F94\u002F?v=ad1d1f177305",{"id":218,"idKnowledge":219,"idDomain":15,"idCluster":15,"slug":220,"title":221,"description":222,"bodyMarkdown":223,"bodyHtml":224,"author":39,"date":225,"createdAt":226,"topics":227,"image":229,"hasDownload":28,"fileName":15,"youtubeId":27},"92","207DE47D-60E7-5342-A44A-CF50C3383CAE","bedrijfsprocessen-automatiseren-met-ai","Automating Business Processes with AI","Automating business processes with AI reduces errors, saves time, and improves data control — provided you choose the right processes.","An order stuck in a mailbox, an employee retyping the same data three times, a schedule that only comes together after someone has manually compared multiple systems side by side — this is where time and margin leak away daily in many organisations. Automating business processes with AI is therefore not a futuristic project, but often a logical next step for companies that have been working for years with custom solutions, spreadsheets, standalone apps, or an existing [FileMaker system](https:\u002F\u002Floggix.com\u002Fblog\u002Fwhy-your-filemaker-crm-needs-a-data-upgrade-and-how-to-start-today\u002F).\n\nThe question is not whether AI can automate something. The real question is where AI is genuinely useful, where ordinary software logic is already sufficient, and how to improve existing processes without disrupting operations. This is precisely where things often go wrong in practice. Not due to a lack of technology, but due to the wrong choice of approach.\n\n## When automating business processes with AI truly delivers value\n\nAI is most interesting for processes with variation, exceptions, and a large amount of manual assessment work. Think of classifying incoming emails, reading documents, summarising customer queries, preparing quotes, or flagging anomalies in orders, inventory, or service requests. In these types of processes, the step from human effort to full automation with fixed rules is often too large, whereas AI can assist precisely with interpretation and pre-selection.\n\nFor strictly predictable steps, AI is usually not the first answer. If an order always needs to move from system A to system B, or if a form must automatically generate an invoice after approval, classical workflow automation is often faster, cheaper, and more reliable. AI only adds value when the software also needs to understand what is written, what has priority, or which action is most likely correct.\n\nThat distinction matters. Organisations that lump everything under the label AI quickly buy complexity where it isn't needed. Those that deploy AI only where interpretation is required get more return from existing systems.\n\n## Don't start with the technology — start with the friction in the process\n\nIn many organisations, the biggest bottlenecks have been known for years. The sales department is waiting for up-to-date data from an internal system. The back office manually checks whether customer data is complete. Planning combines information from email, Excel, and a database. These are not isolated irritations, but signals that processes work in principle yet no longer fit together technically.\n\nThat is why a good automation trajectory does not start with a model choice or an AI tool, but with three practical questions. Where is work currently being duplicated? Where do errors arise from manual input? And where must an employee assess or structure information before the process can continue?\n\nVery concrete opportunities often emerge from this. An AI component can, for example, recognise emails and assign them to the correct file, read attachments, and populate relevant fields in an existing system. Or it can help a service team by automatically summarising incoming notifications and linking them to previous cases. These kinds of applications shorten lead times without employees losing control.\n\n## Which processes are suitable for AI automation?\n\nNot every process is equally suitable, but a number of patterns recur consistently. Administrative processes involving many documents are often a good starting point. Invoices, packing slips, request forms, contracts, and service messages contain valuable information, but that information is rarely immediately in the right structure for your software. AI can then help convert unstructured input into usable data.\n\nProcesses around communication are also well suited to AI. Think of automatically classifying customer queries, suggesting standard responses, or flagging urgency. This does not mean AI should fully take over customer service. A hybrid approach often works better: AI performs the initial analysis, an employee reviews and sends.\n\nA third category is process monitoring. If you work with multiple systems, manual handovers, and many exceptions, AI can help recognise patterns in delays, errors, or anomalies — not as a silver bullet, but as an additional layer on top of your existing software environment.\n\n### Good initial use cases\n\nThe most successful trajectories rarely begin with a fully autonomous workflow. Better starting points are applications with a clearly defined task, a measurable result, and limited risk. For example: accelerating order processing, automatically capturing document data, routing service tickets more intelligently, or summarising management information from various sources.\n\nFor companies with an existing [FileMaker landscape](https:\u002F\u002Floggix.com\u002Fblog\u002Fgemini-embedding-2-geef-je-filemaker-oplossing-een-ai-geheugen\u002F) or other legacy environment, this is especially relevant. You do not need to replace everything first. In many cases, you can retain an existing process, enrich it with AI, and connect it to other systems via [APIs or middleware](https:\u002F\u002Floggix.com\u002Fai\u002F). This preserves the operational knowledge in your current environment while making the process more modern and less error-prone.\n\n## Automating business processes with AI in existing systems\n\nA commonly heard concern is that AI only works in entirely new software environments. In practice, that is rarely necessary. Precisely companies with existing databases, internal tools, or custom applications can achieve significant gains, because those environments often still contain manual steps between systems.\n\nSuppose an organisation uses FileMaker for relationship management and order registration, also has an accounting package, and additionally works with email and spreadsheets for exceptions. The inefficiency usually lies not within one system, but in the transitions between them. AI can make those transitions smarter — for example, by interpreting documents, structuring text, or suggesting next steps. API connections and targeted software adjustments then ensure that the outcome actually ends up in the right place.\n\nThis is a pragmatic approach. No costly rip-and-replace, but targeted modernisation where the greatest operational gains are found. For many SMEs, this is the most financially and organisationally sensible route.\n\n### Where things often go wrong\n\nThe biggest mistake is wanting to do too much at once. An organisation sees ten possible AI applications and tries to fit everything into a single project. This creates a technically complex trajectory with unclear priorities. The alternative is simpler: choose one process with a clear pain point, measure the outcome, and only then scale.\n\nA second mistake is insufficient attention to data quality. AI can do a great deal, but poor source data remains a problem. If customer information is scattered, product codes are inconsistent, or documents are delivered differently by each department, some structure needs to be established first. Otherwise, you are mainly automating confusion.\n\nA third mistake is letting AI decide where control must be retained. Not every process lends itself to full autonomy. In pricing agreements, compliance, contracts, or exceptional customer cases, a human control layer is often the wiser choice. That is not a weakness of AI, but good process design.\n\n## How do you approach this sensibly?\n\nStart small, but with commitment. Choose a process that occurs regularly, currently involves noticeable manual effort, and where improvement is directly visible in time, error reduction, or lead time. Then describe the current situation as concretely as possible: what input arrives, what steps follow, what exceptions exist, and where do delays occur?\n\nNext, determine which components require fixed logic and which require interpretation. That distinction determines the solution. Some steps only need a connection or workflow adjustment. Others lend themselves to AI — for example, text recognition, classification, summarisation, or decision support.\n\nYou then build a controlled pilot. Not as a standalone experiment without a process owner, but in a real working environment with clear measurement points. How much time does this save? How often does an employee correct the output? What exceptions remain? Only once that is clear does scaling up make sense.\n\nThis is also why a technical partner must look not only at the AI component, but at the whole picture: database, integrations, user process, and management. At Loggix, that is the core: AI only works well when it connects to the reality of your operations and to the systems you already use.\n\n## What does it deliver — and what doesn't it?\n\nWhen the application is well chosen, AI automation typically delivers three things: less manual work, fewer data entry errors, and greater speed in recurring processes. Better insight often emerges as well, because data is recorded more consistently and remains less scattered across mailboxes and files.\n\nWhat it usually does not deliver is an organisation that can suddenly operate without process discipline. AI does not replace ownership, clear working agreements, or good system design. It makes a good process faster, and sometimes makes a messy process visibly messier. That is valuable, but it does require realistic expectations.\n\nFor operational teams, that may be the most important message. Automating business processes with AI does not have to be a major transformation programme. It often starts with one persistent manual step that is finally solved intelligently. If you choose that step based on impact rather than hype, the rest usually follows naturally.\n\nThe best first step is therefore rarely the most spectacular one. It is the step that gives your people less duplicated work tomorrow and gives your organisation noticeably more control over processes and data six months from now.\n\nLoggix is a database specialist and has therefore been active at the forefront of the AI wave for years. We now know very well what works and what doesn't. Feel free to get in touch if you'd like to talk it through! (www.loggix.com)","\u003Cp>An order stuck in a mailbox, an employee retyping the same data three times, a schedule that only comes together after someone has manually compared multiple systems side by side — this is where time and margin leak away daily in many organisations. Automating business processes with AI is therefore not a futuristic project, but often a logical next step for companies that have been working for years with custom solutions, spreadsheets, standalone apps, or an existing \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Fwhy-your-filemaker-crm-needs-a-data-upgrade-and-how-to-start-today\u002F\">FileMaker system\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>The question is not whether AI can automate something. The real question is where AI is genuinely useful, where ordinary software logic is already sufficient, and how to improve existing processes without disrupting operations. This is precisely where things often go wrong in practice. Not due to a lack of technology, but due to the wrong choice of approach.\u003C\u002Fp>\n\u003Ch2>When automating business processes with AI truly delivers value\u003C\u002Fh2>\n\u003Cp>AI is most interesting for processes with variation, exceptions, and a large amount of manual assessment work. Think of classifying incoming emails, reading documents, summarising customer queries, preparing quotes, or flagging anomalies in orders, inventory, or service requests. In these types of processes, the step from human effort to full automation with fixed rules is often too large, whereas AI can assist precisely with interpretation and pre-selection.\u003C\u002Fp>\n\u003Cp>For strictly predictable steps, AI is usually not the first answer. If an order always needs to move from system A to system B, or if a form must automatically generate an invoice after approval, classical workflow automation is often faster, cheaper, and more reliable. AI only adds value when the software also needs to understand what is written, what has priority, or which action is most likely correct.\u003C\u002Fp>\n\u003Cp>That distinction matters. Organisations that lump everything under the label AI quickly buy complexity where it isn't needed. Those that deploy AI only where interpretation is required get more return from existing systems.\u003C\u002Fp>\n\u003Ch2>Don't start with the technology — start with the friction in the process\u003C\u002Fh2>\n\u003Cp>In many organisations, the biggest bottlenecks have been known for years. The sales department is waiting for up-to-date data from an internal system. The back office manually checks whether customer data is complete. Planning combines information from email, Excel, and a database. These are not isolated irritations, but signals that processes work in principle yet no longer fit together technically.\u003C\u002Fp>\n\u003Cp>That is why a good automation trajectory does not start with a model choice or an AI tool, but with three practical questions. Where is work currently being duplicated? Where do errors arise from manual input? And where must an employee assess or structure information before the process can continue?\u003C\u002Fp>\n\u003Cp>Very concrete opportunities often emerge from this. An AI component can, for example, recognise emails and assign them to the correct file, read attachments, and populate relevant fields in an existing system. Or it can help a service team by automatically summarising incoming notifications and linking them to previous cases. These kinds of applications shorten lead times without employees losing control.\u003C\u002Fp>\n\u003Ch2>Which processes are suitable for AI automation?\u003C\u002Fh2>\n\u003Cp>Not every process is equally suitable, but a number of patterns recur consistently. Administrative processes involving many documents are often a good starting point. Invoices, packing slips, request forms, contracts, and service messages contain valuable information, but that information is rarely immediately in the right structure for your software. AI can then help convert unstructured input into usable data.\u003C\u002Fp>\n\u003Cp>Processes around communication are also well suited to AI. Think of automatically classifying customer queries, suggesting standard responses, or flagging urgency. This does not mean AI should fully take over customer service. A hybrid approach often works better: AI performs the initial analysis, an employee reviews and sends.\u003C\u002Fp>\n\u003Cp>A third category is process monitoring. If you work with multiple systems, manual handovers, and many exceptions, AI can help recognise patterns in delays, errors, or anomalies — not as a silver bullet, but as an additional layer on top of your existing software environment.\u003C\u002Fp>\n\u003Ch3>Good initial use cases\u003C\u002Fh3>\n\u003Cp>The most successful trajectories rarely begin with a fully autonomous workflow. Better starting points are applications with a clearly defined task, a measurable result, and limited risk. For example: accelerating order processing, automatically capturing document data, routing service tickets more intelligently, or summarising management information from various sources.\u003C\u002Fp>\n\u003Cp>For companies with an existing \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Fgemini-embedding-2-geef-je-filemaker-oplossing-een-ai-geheugen\u002F\">FileMaker landscape\u003C\u002Fa> or other legacy environment, this is especially relevant. You do not need to replace everything first. In many cases, you can retain an existing process, enrich it with AI, and connect it to other systems via \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fai\u002F\">APIs or middleware\u003C\u002Fa>. This preserves the operational knowledge in your current environment while making the process more modern and less error-prone.\u003C\u002Fp>\n\u003Ch2>Automating business processes with AI in existing systems\u003C\u002Fh2>\n\u003Cp>A commonly heard concern is that AI only works in entirely new software environments. In practice, that is rarely necessary. Precisely companies with existing databases, internal tools, or custom applications can achieve significant gains, because those environments often still contain manual steps between systems.\u003C\u002Fp>\n\u003Cp>Suppose an organisation uses FileMaker for relationship management and order registration, also has an accounting package, and additionally works with email and spreadsheets for exceptions. The inefficiency usually lies not within one system, but in the transitions between them. AI can make those transitions smarter — for example, by interpreting documents, structuring text, or suggesting next steps. API connections and targeted software adjustments then ensure that the outcome actually ends up in the right place.\u003C\u002Fp>\n\u003Cp>This is a pragmatic approach. No costly rip-and-replace, but targeted modernisation where the greatest operational gains are found. For many SMEs, this is the most financially and organisationally sensible route.\u003C\u002Fp>\n\u003Ch3>Where things often go wrong\u003C\u002Fh3>\n\u003Cp>The biggest mistake is wanting to do too much at once. An organisation sees ten possible AI applications and tries to fit everything into a single project. This creates a technically complex trajectory with unclear priorities. The alternative is simpler: choose one process with a clear pain point, measure the outcome, and only then scale.\u003C\u002Fp>\n\u003Cp>A second mistake is insufficient attention to data quality. AI can do a great deal, but poor source data remains a problem. If customer information is scattered, product codes are inconsistent, or documents are delivered differently by each department, some structure needs to be established first. Otherwise, you are mainly automating confusion.\u003C\u002Fp>\n\u003Cp>A third mistake is letting AI decide where control must be retained. Not every process lends itself to full autonomy. In pricing agreements, compliance, contracts, or exceptional customer cases, a human control layer is often the wiser choice. That is not a weakness of AI, but good process design.\u003C\u002Fp>\n\u003Ch2>How do you approach this sensibly?\u003C\u002Fh2>\n\u003Cp>Start small, but with commitment. Choose a process that occurs regularly, currently involves noticeable manual effort, and where improvement is directly visible in time, error reduction, or lead time. Then describe the current situation as concretely as possible: what input arrives, what steps follow, what exceptions exist, and where do delays occur?\u003C\u002Fp>\n\u003Cp>Next, determine which components require fixed logic and which require interpretation. That distinction determines the solution. Some steps only need a connection or workflow adjustment. Others lend themselves to AI — for example, text recognition, classification, summarisation, or decision support.\u003C\u002Fp>\n\u003Cp>You then build a controlled pilot. Not as a standalone experiment without a process owner, but in a real working environment with clear measurement points. How much time does this save? How often does an employee correct the output? What exceptions remain? Only once that is clear does scaling up make sense.\u003C\u002Fp>\n\u003Cp>This is also why a technical partner must look not only at the AI component, but at the whole picture: database, integrations, user process, and management. At Loggix, that is the core: AI only works well when it connects to the reality of your operations and to the systems you already use.\u003C\u002Fp>\n\u003Ch2>What does it deliver — and what doesn't it?\u003C\u002Fh2>\n\u003Cp>When the application is well chosen, AI automation typically delivers three things: less manual work, fewer data entry errors, and greater speed in recurring processes. Better insight often emerges as well, because data is recorded more consistently and remains less scattered across mailboxes and files.\u003C\u002Fp>\n\u003Cp>What it usually does not deliver is an organisation that can suddenly operate without process discipline. AI does not replace ownership, clear working agreements, or good system design. It makes a good process faster, and sometimes makes a messy process visibly messier. That is valuable, but it does require realistic expectations.\u003C\u002Fp>\n\u003Cp>For operational teams, that may be the most important message. Automating business processes with AI does not have to be a major transformation programme. It often starts with one persistent manual step that is finally solved intelligently. If you choose that step based on impact rather than hype, the rest usually follows naturally.\u003C\u002Fp>\n\u003Cp>The best first step is therefore rarely the most spectacular one. It is the step that gives your people less duplicated work tomorrow and gives your organisation noticeably more control over processes and data six months from now.\u003C\u002Fp>\n\u003Cp>Loggix is a database specialist and has therefore been active at the forefront of the AI wave for years. We now know very well what works and what doesn't. Feel free to get in touch if you'd like to talk it through! (\u003Ca href=\"http:\u002F\u002Fwww.loggix.com\">www.loggix.com\u003C\u002Fa>)\u003C\u002Fp>\n","2026-07-01",1782922412000,[86,228],"Consult","\u002Fapi\u002Fknowledge\u002Fimage\u002F92\u002F?v=b46156bd24b3",{"id":231,"idKnowledge":232,"idDomain":15,"idCluster":15,"slug":233,"title":234,"description":235,"bodyMarkdown":236,"bodyHtml":237,"author":39,"date":238,"createdAt":239,"topics":240,"image":242,"hasDownload":28,"fileName":15,"youtubeId":27},"91","42111723-0B11-1E4F-BD6C-38FD4579D3B7","legacy-database-vervangen-of-uitbreiden","Replace or extend your legacy database?","Replace or extend your legacy database? Discover when modernising is smarter than migrating, with less risk, lower costs and more control.","A legacy database is rarely replaced because someone feels like it. It usually only happens when processes slow down, become error-prone or rely too heavily on a handful of people who \"still know how it works\". That's when the question lands on the table: replace or extend the legacy database? For many organisations, this is not a purely technical choice, but an operational and financial one.\n\n## When legacy truly becomes a problem\n\nAn older system is not automatically a bad system. Many legacy databases have been supporting exactly the processes a business runs on for years: quotes, planning, order processing, project registration, inventory or service. Problems usually arise not from age alone, but because the surrounding environment changes.\n\nThink of teams working from multiple locations, customers expecting real-time information, or management wanting to combine data from different systems. Integrations with accounting software, CRM, webshops, scanners or mobile apps are also becoming increasingly common. A database that once worked perfectly as a standalone internal system can then get stuck on reach, integration or maintenance.\n\nThere is something else to consider. Many legacy environments, especially custom-built systems, contain years of business logic. Discounts, exceptions, approval steps, calculations and customer agreements are often deeply embedded in the system. Anyone who underestimates this faces a high risk of delays, extra costs and loss of crucial knowledge when replacing the system.\n\n## Replace or extend the legacy database: the real trade-off\n\nThe question of whether to replace or extend a legacy database is often framed too black-and-white. As if a company must choose between doing nothing or starting completely from scratch. In practice, the best route usually lies somewhere in between.\n\nFull replacement can make sense when the technical foundation has genuinely run its course, manageability is lacking, security falls structurally short, or the system has become so fragmented that changes cost more than they deliver. When an organisation is about to adopt radically different processes, a new platform may also be the better choice.\n\nExtending is often the wiser option when the core of the system still aligns well with operations. Especially when staff use it efficiently every day and the database contains valuable data and business rules. In that case, it is often smarter to retain that foundation and modernise in a targeted way with new interfaces, API integrations, mobile functionality, dashboards or automated tasks.\n\nThe difference therefore lies not only in technology, but in business fit. Replacing a system simply because it is old is rarely a strong argument. Adapting a system because it cannot support the next phase of growth is.\n\n## Why rip-and-replace often costs more than expected\n\nOn paper, a fresh start looks attractive. Old limitations disappear, the technology looks more modern and the project feels manageable. But in practice, a complete rebuild often turns out to be more complex than anticipated.\n\nThis is because organisations are usually not just replacing software, but implicitly redesigning processes at the same time. What seemed like a migration becomes a change programme simultaneously. Users have to relearn how to work, exceptions surface late and integrations with other systems prove more critical than expected.\n\nMoreover, the real value of a legacy database rarely lies in the screens. It lies in the logic behind the screens. If that knowledge is not properly documented, it has to be rediscovered. That costs time and creates risk. Companies then find that a new system may look modern, but functionally is still far from the level of the old custom solution.\n\nThat does not mean replacement is never the right call. It does mean the business case must be honest. Not just licences and development hours count, but also testing, adoption, process disruption and a temporary drop in productivity.\n\n## When extending is the stronger choice\n\nFor many SMEs, extending is the most pragmatic route. Not because change is being postponed, but because value is preserved. An existing database can often continue to serve perfectly well as the transaction layer or process engine, while new components are built around it.\n\nThink of a customer portal that draws data from the existing database. Or a mobile app for field staff, while the back office continues to operate in the familiar system. [API integrations](https:\u002F\u002Floggix.com\u002Fblog\u002Fseamless-payment-integration-between-filemaker-and-mollie-payment-provider\u002F) with accounting software, ERP, webshops or shipping platforms are also typical extensions that deliver immediate operational benefit.\n\nThe same applies to reporting and automation. Many organisations do not need to replace their database to reduce manual work. A well-designed extension can reduce data entry, prevent errors and shorten lead times without overhauling the entire foundation.\n\nThis is especially relevant for legacy FileMaker systems. Those environments often contain precisely the processes where standard software falls short. By extending them in a controlled way with [modern techniques](https:\u002F\u002Floggix.com\u002Fblog\u002Fwhy-use-filemaker-features-importance-and-ai-integration\u002F), a solution emerges that is both familiar and future-proof.\n\n## What to assess before you decide\n\nA sound decision starts with a business analysis, not a technology preference. The first question is simple: which processes must keep running without fail? If downtime directly affects revenue, service or planning, every approach must be designed around that.\n\nThen look at four areas. First, functional value: does the current system still support the core processes well? Second, technical condition: is the database manageable, secure and reasonably extendable? Third, integration needs: does the system primarily need to work better together with other applications? And fourth, pressure to change: how quickly must the organisation be able to support new ways of working?\n\nIf functional value is high but technology and integration are lagging, extending is the obvious choice. If both functionality and technology fall structurally short, replacement comes more into view. Many situations fall somewhere in the middle, however. A phased approach then works best.\n\n## A phased modernisation is usually the safest approach\n\nThe biggest mistake in modernisation is trying to solve too much at once. That may sound ambitious, but it increases risk and slows down results. A phased approach is usually wiser.\n\nStart with the areas causing the most pressure. That could be a manual process, a missing integration, an outdated user interface or a reporting problem. By improving those first, space is created for the next step. This keeps operations running and makes the project manageable.\n\nA good trajectory might look like this, for example: first clean up the existing database technically, then realise integrations with other systems, subsequently add a [web portal or app](https:\u002F\u002Floggix.com\u002Fblog\u002Fwebapps-based-on-filemaker\u002F), and only later decide whether parts of the core need to be replaced. In this way, modernisation becomes a series of business improvements rather than an all-or-nothing project.\n\nThis is also more financially attractive. Investments can be spread across phases with demonstrable results. That gives management more control and prevents a large project from having to promise value for months before anything visibly improves.\n\n## Watch for these signals that replacement is still necessary\n\nSometimes extending is no longer sensible. For example, when every change causes new instability, documentation is absent and nobody really understands how the solution is technically structured. Serious security issues, structural performance problems or dependence on outdated infrastructure can also indicate that the system has reached its limits.\n\nAnother signal is when the organisation has fundamentally changed the way it works compared to what the system was originally designed for. If an internal desktop database now also has to serve customers, suppliers, mobile teams and external platforms, the original architecture may be too limited.\n\nIn that case, replacing or rebuilding parts is indeed logical. But even then, it does not have to mean a hard break. A controlled transition is often better, carrying valuable data, logic and process knowledge into a new setup.\n\n## The role of specialisation makes a big difference here\n\nLegacy modernisation is not just about building software. It is about understanding existing processes, historical decisions and dependencies that are essential to the business. That is why domain knowledge makes a significant difference.\n\nExperience is especially important with FileMaker environments. Someone who only looks at modern technology quickly misses why an existing system was built the way it was. Someone who only knows the old system misses opportunities around APIs, apps, AI support and platform expansion. The best approach combines both perspectives.\n\nThat is where the practical added value of a specialist partner like Loggix lies: not steering towards replacement for replacement's sake, but assessing what should be retained, what can be integrated more intelligently and what genuinely needs to be rebuilt.\n\n## Don't choose new, choose fitting\n\nThe question is therefore not whether old systems must inevitably disappear. The real question is which scenario makes operations stronger at acceptable cost and with manageable risk. Sometimes that means replacing. Very often it means extending, connecting and modernising step by step.\n\nMaking that choice carefully prevents two costly mistakes at once: staying stuck in limitations for too long, or parting ways too quickly with software that still holds a great deal of value. So start not with the technology, but with the work that needs to keep running well every day. That usually makes it clear on its own whether your legacy database needs to be replaced, extended or first put to smarter use.\n\nGet in touch for an open conversation and let's explore together what is possible for you!","\u003Cp>A legacy database is rarely replaced because someone feels like it. It usually only happens when processes slow down, become error-prone or rely too heavily on a handful of people who "still know how it works". That's when the question lands on the table: replace or extend the legacy database? For many organisations, this is not a purely technical choice, but an operational and financial one.\u003C\u002Fp>\n\u003Ch2>When legacy truly becomes a problem\u003C\u002Fh2>\n\u003Cp>An older system is not automatically a bad system. Many legacy databases have been supporting exactly the processes a business runs on for years: quotes, planning, order processing, project registration, inventory or service. Problems usually arise not from age alone, but because the surrounding environment changes.\u003C\u002Fp>\n\u003Cp>Think of teams working from multiple locations, customers expecting real-time information, or management wanting to combine data from different systems. Integrations with accounting software, CRM, webshops, scanners or mobile apps are also becoming increasingly common. A database that once worked perfectly as a standalone internal system can then get stuck on reach, integration or maintenance.\u003C\u002Fp>\n\u003Cp>There is something else to consider. Many legacy environments, especially custom-built systems, contain years of business logic. Discounts, exceptions, approval steps, calculations and customer agreements are often deeply embedded in the system. Anyone who underestimates this faces a high risk of delays, extra costs and loss of crucial knowledge when replacing the system.\u003C\u002Fp>\n\u003Ch2>Replace or extend the legacy database: the real trade-off\u003C\u002Fh2>\n\u003Cp>The question of whether to replace or extend a legacy database is often framed too black-and-white. As if a company must choose between doing nothing or starting completely from scratch. In practice, the best route usually lies somewhere in between.\u003C\u002Fp>\n\u003Cp>Full replacement can make sense when the technical foundation has genuinely run its course, manageability is lacking, security falls structurally short, or the system has become so fragmented that changes cost more than they deliver. When an organisation is about to adopt radically different processes, a new platform may also be the better choice.\u003C\u002Fp>\n\u003Cp>Extending is often the wiser option when the core of the system still aligns well with operations. Especially when staff use it efficiently every day and the database contains valuable data and business rules. In that case, it is often smarter to retain that foundation and modernise in a targeted way with new interfaces, API integrations, mobile functionality, dashboards or automated tasks.\u003C\u002Fp>\n\u003Cp>The difference therefore lies not only in technology, but in business fit. Replacing a system simply because it is old is rarely a strong argument. Adapting a system because it cannot support the next phase of growth is.\u003C\u002Fp>\n\u003Ch2>Why rip-and-replace often costs more than expected\u003C\u002Fh2>\n\u003Cp>On paper, a fresh start looks attractive. Old limitations disappear, the technology looks more modern and the project feels manageable. But in practice, a complete rebuild often turns out to be more complex than anticipated.\u003C\u002Fp>\n\u003Cp>This is because organisations are usually not just replacing software, but implicitly redesigning processes at the same time. What seemed like a migration becomes a change programme simultaneously. Users have to relearn how to work, exceptions surface late and integrations with other systems prove more critical than expected.\u003C\u002Fp>\n\u003Cp>Moreover, the real value of a legacy database rarely lies in the screens. It lies in the logic behind the screens. If that knowledge is not properly documented, it has to be rediscovered. That costs time and creates risk. Companies then find that a new system may look modern, but functionally is still far from the level of the old custom solution.\u003C\u002Fp>\n\u003Cp>That does not mean replacement is never the right call. It does mean the business case must be honest. Not just licences and development hours count, but also testing, adoption, process disruption and a temporary drop in productivity.\u003C\u002Fp>\n\u003Ch2>When extending is the stronger choice\u003C\u002Fh2>\n\u003Cp>For many SMEs, extending is the most pragmatic route. Not because change is being postponed, but because value is preserved. An existing database can often continue to serve perfectly well as the transaction layer or process engine, while new components are built around it.\u003C\u002Fp>\n\u003Cp>Think of a customer portal that draws data from the existing database. Or a mobile app for field staff, while the back office continues to operate in the familiar system. \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Fseamless-payment-integration-between-filemaker-and-mollie-payment-provider\u002F\">API integrations\u003C\u002Fa> with accounting software, ERP, webshops or shipping platforms are also typical extensions that deliver immediate operational benefit.\u003C\u002Fp>\n\u003Cp>The same applies to reporting and automation. Many organisations do not need to replace their database to reduce manual work. A well-designed extension can reduce data entry, prevent errors and shorten lead times without overhauling the entire foundation.\u003C\u002Fp>\n\u003Cp>This is especially relevant for legacy FileMaker systems. Those environments often contain precisely the processes where standard software falls short. By extending them in a controlled way with \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Fwhy-use-filemaker-features-importance-and-ai-integration\u002F\">modern techniques\u003C\u002Fa>, a solution emerges that is both familiar and future-proof.\u003C\u002Fp>\n\u003Ch2>What to assess before you decide\u003C\u002Fh2>\n\u003Cp>A sound decision starts with a business analysis, not a technology preference. The first question is simple: which processes must keep running without fail? If downtime directly affects revenue, service or planning, every approach must be designed around that.\u003C\u002Fp>\n\u003Cp>Then look at four areas. First, functional value: does the current system still support the core processes well? Second, technical condition: is the database manageable, secure and reasonably extendable? Third, integration needs: does the system primarily need to work better together with other applications? And fourth, pressure to change: how quickly must the organisation be able to support new ways of working?\u003C\u002Fp>\n\u003Cp>If functional value is high but technology and integration are lagging, extending is the obvious choice. If both functionality and technology fall structurally short, replacement comes more into view. Many situations fall somewhere in the middle, however. A phased approach then works best.\u003C\u002Fp>\n\u003Ch2>A phased modernisation is usually the safest approach\u003C\u002Fh2>\n\u003Cp>The biggest mistake in modernisation is trying to solve too much at once. That may sound ambitious, but it increases risk and slows down results. A phased approach is usually wiser.\u003C\u002Fp>\n\u003Cp>Start with the areas causing the most pressure. That could be a manual process, a missing integration, an outdated user interface or a reporting problem. By improving those first, space is created for the next step. This keeps operations running and makes the project manageable.\u003C\u002Fp>\n\u003Cp>A good trajectory might look like this, for example: first clean up the existing database technically, then realise integrations with other systems, subsequently add a \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Fwebapps-based-on-filemaker\u002F\">web portal or app\u003C\u002Fa>, and only later decide whether parts of the core need to be replaced. In this way, modernisation becomes a series of business improvements rather than an all-or-nothing project.\u003C\u002Fp>\n\u003Cp>This is also more financially attractive. Investments can be spread across phases with demonstrable results. That gives management more control and prevents a large project from having to promise value for months before anything visibly improves.\u003C\u002Fp>\n\u003Ch2>Watch for these signals that replacement is still necessary\u003C\u002Fh2>\n\u003Cp>Sometimes extending is no longer sensible. For example, when every change causes new instability, documentation is absent and nobody really understands how the solution is technically structured. Serious security issues, structural performance problems or dependence on outdated infrastructure can also indicate that the system has reached its limits.\u003C\u002Fp>\n\u003Cp>Another signal is when the organisation has fundamentally changed the way it works compared to what the system was originally designed for. If an internal desktop database now also has to serve customers, suppliers, mobile teams and external platforms, the original architecture may be too limited.\u003C\u002Fp>\n\u003Cp>In that case, replacing or rebuilding parts is indeed logical. But even then, it does not have to mean a hard break. A controlled transition is often better, carrying valuable data, logic and process knowledge into a new setup.\u003C\u002Fp>\n\u003Ch2>The role of specialisation makes a big difference here\u003C\u002Fh2>\n\u003Cp>Legacy modernisation is not just about building software. It is about understanding existing processes, historical decisions and dependencies that are essential to the business. That is why domain knowledge makes a significant difference.\u003C\u002Fp>\n\u003Cp>Experience is especially important with FileMaker environments. Someone who only looks at modern technology quickly misses why an existing system was built the way it was. Someone who only knows the old system misses opportunities around APIs, apps, AI support and platform expansion. The best approach combines both perspectives.\u003C\u002Fp>\n\u003Cp>That is where the practical added value of a specialist partner like Loggix lies: not steering towards replacement for replacement's sake, but assessing what should be retained, what can be integrated more intelligently and what genuinely needs to be rebuilt.\u003C\u002Fp>\n\u003Ch2>Don't choose new, choose fitting\u003C\u002Fh2>\n\u003Cp>The question is therefore not whether old systems must inevitably disappear. The real question is which scenario makes operations stronger at acceptable cost and with manageable risk. Sometimes that means replacing. Very often it means extending, connecting and modernising step by step.\u003C\u002Fp>\n\u003Cp>Making that choice carefully prevents two costly mistakes at once: staying stuck in limitations for too long, or parting ways too quickly with software that still holds a great deal of value. So start not with the technology, but with the work that needs to keep running well every day. That usually makes it clear on its own whether your legacy database needs to be replaced, extended or first put to smarter use.\u003C\u002Fp>\n\u003Cp>Get in touch for an open conversation and let's explore together what is possible for you!\u003C\u002Fp>\n","2026-06-30",1782835313000,[241,23,228],"Database","\u002Fapi\u002Fknowledge\u002Fimage\u002F91\u002F?v=13feda9004c7",{"id":244,"idKnowledge":245,"idDomain":15,"idCluster":15,"slug":246,"title":247,"description":248,"bodyMarkdown":249,"bodyHtml":250,"author":39,"date":238,"createdAt":251,"topics":252,"image":254,"hasDownload":28,"fileName":15,"youtubeId":27},"90","4BAA36F2-93EE-2244-948C-8619C423500A","exact-online-koppelen-aan-filemaker-zo-automatiseer-je-facturen-veilig-en-foutloos","Connecting Exact Online to FileMaker: how to automate invoices securely and without errors","Learn how an API integration between FileMaker and Exact Online makes invoice processing faster, safer, and more accurate — without manual retyping.","An API integration between FileMaker and Exact Online eliminates manual retyping, reduces the risk of errors, and ensures financial data is always up to date. This article explains how such an integration works, what the benefits are for IT and finance managers, and what to watch out for.\n\n## Why an integration between FileMaker and Exact Online?\n\nMany organisations manage their operational data (orders, projects, clients) in FileMaker, but enter financial transactions manually in Exact Online. This creates three problems:\n\n- **Duplicate work** — the same data is entered in two places.\n- **Errors** — manual retyping introduces mistakes in amounts, VAT codes, or relation numbers.\n- **Delays** — invoices become available later, slowing down cash flow and reporting.\n\nAn API integration solves this by allowing FileMaker and Exact Online to communicate directly with each other.\n\n## How does the Exact Online API integration work technically?\n\nExact Online offers a REST API that allows external systems — such as FileMaker — to read and write data. The integration works broadly as follows:\n\n1. **Authentication via OAuth 2.0** — FileMaker obtains a secured access token through the Exact Online OAuth flow. Tokens are refreshed automatically, without users needing to share login credentials.\n2. **Retrieving data** — FileMaker sends a GET request to the Exact API to retrieve, for example, relations, general ledger accounts, or outstanding items.\n3. **Writing data** — When creating an invoice, FileMaker sends a POST request with the invoice lines, VAT codes, relation ID, and due date to Exact Online.\n4. **Status feedback** — Exact Online returns a transaction ID and status, which FileMaker stores. This makes it always traceable which records have already been processed.\n5. **Error handling** — If a request fails, FileMaker logs the error code and notifies the user, so nothing gets silently stuck.\n\n## Which processes can you automate?\n\n- **Creating sales invoices** — post an invoice directly in Exact Online from a FileMaker order or project.\n- **Synchronising customer and supplier data** — new relations in FileMaker are automatically created in Exact, and vice versa.\n- **Retrieving payment status** — FileMaker periodically retrieves the payment status, so account managers always see whether an invoice is open or paid.\n- **Processing bank statements** — payments received in Exact are fed back to the correct project or order in FileMaker.\n\n## What about security?\n\nSecurity is a top priority for financial integrations. The Loggix integration applies the following measures:\n\n- **OAuth 2.0 with short-lived tokens** — no passwords are stored or transmitted.\n- **HTTPS for all communication** — data is encrypted in transit.\n- **Role-based access** — only authorised FileMaker accounts may call the API scripts.\n- **Audit log in FileMaker** — every API request (including timestamp, user, and result) is logged for auditing and compliance.\n- **No sensitive data in scripts** — client secrets are stored in secured FileMaker value lists or external vaults, not in readable script steps.\n\n## What does it deliver in practice?\n\n| Situation | Before integration | After integration |\n|---|---|---|\n| Creating an invoice | 5–10 min. manually | \u003C 5 seconds automatically |\n| Error rate | 2–5% (manual entry) | Near 0% |\n| Viewing payment status | Manual check daily | Real-time in FileMaker |\n| Audit trail | Fragmented | Centrally logged |\n\n## What should you watch out for during implementation?\n\n1. **Exact Online subscription** — check whether your subscription includes API access (Standard or higher).\n2. **Division ID** — Exact Online works with divisions; ensure FileMaker always includes the correct division in every API request.\n3. **Mapping VAT codes** — FileMaker VAT codes must correspond exactly to the Exact Online general ledger structure. Set up a translation table.\n4. **Rate limiting** — Exact Online enforces a limit of 60 requests per minute per token. Build a queue in FileMaker for bulk processing.\n5. **Use a test environment** — Exact Online provides a sandbox. Always test with dummy data first before going live.\n\n## Ready to integrate?\n\nA well-implemented API integration between FileMaker and Exact Online saves hours per week, reduces errors, and gives finance managers real-time insight. Loggix builds these integrations on a custom basis, tailored to your processes and security requirements. Get in touch for a no-obligation conversation.","\u003Cp>An API integration between FileMaker and Exact Online eliminates manual retyping, reduces the risk of errors, and ensures financial data is always up to date. This article explains how such an integration works, what the benefits are for IT and finance managers, and what to watch out for.\u003C\u002Fp>\n\u003Ch2>Why an integration between FileMaker and Exact Online?\u003C\u002Fh2>\n\u003Cp>Many organisations manage their operational data (orders, projects, clients) in FileMaker, but enter financial transactions manually in Exact Online. This creates three problems:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Duplicate work\u003C\u002Fstrong> — the same data is entered in two places.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Errors\u003C\u002Fstrong> — manual retyping introduces mistakes in amounts, VAT codes, or relation numbers.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Delays\u003C\u002Fstrong> — invoices become available later, slowing down cash flow and reporting.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>An API integration solves this by allowing FileMaker and Exact Online to communicate directly with each other.\u003C\u002Fp>\n\u003Ch2>How does the Exact Online API integration work technically?\u003C\u002Fh2>\n\u003Cp>Exact Online offers a REST API that allows external systems — such as FileMaker — to read and write data. The integration works broadly as follows:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Authentication via OAuth 2.0\u003C\u002Fstrong> — FileMaker obtains a secured access token through the Exact Online OAuth flow. Tokens are refreshed automatically, without users needing to share login credentials.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Retrieving data\u003C\u002Fstrong> — FileMaker sends a GET request to the Exact API to retrieve, for example, relations, general ledger accounts, or outstanding items.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Writing data\u003C\u002Fstrong> — When creating an invoice, FileMaker sends a POST request with the invoice lines, VAT codes, relation ID, and due date to Exact Online.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Status feedback\u003C\u002Fstrong> — Exact Online returns a transaction ID and status, which FileMaker stores. This makes it always traceable which records have already been processed.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Error handling\u003C\u002Fstrong> — If a request fails, FileMaker logs the error code and notifies the user, so nothing gets silently stuck.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2>Which processes can you automate?\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Creating sales invoices\u003C\u002Fstrong> — post an invoice directly in Exact Online from a FileMaker order or project.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Synchronising customer and supplier data\u003C\u002Fstrong> — new relations in FileMaker are automatically created in Exact, and vice versa.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Retrieving payment status\u003C\u002Fstrong> — FileMaker periodically retrieves the payment status, so account managers always see whether an invoice is open or paid.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Processing bank statements\u003C\u002Fstrong> — payments received in Exact are fed back to the correct project or order in FileMaker.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>What about security?\u003C\u002Fh2>\n\u003Cp>Security is a top priority for financial integrations. The Loggix integration applies the following measures:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>OAuth 2.0 with short-lived tokens\u003C\u002Fstrong> — no passwords are stored or transmitted.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>HTTPS for all communication\u003C\u002Fstrong> — data is encrypted in transit.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Role-based access\u003C\u002Fstrong> — only authorised FileMaker accounts may call the API scripts.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Audit log in FileMaker\u003C\u002Fstrong> — every API request (including timestamp, user, and result) is logged for auditing and compliance.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>No sensitive data in scripts\u003C\u002Fstrong> — client secrets are stored in secured FileMaker value lists or external vaults, not in readable script steps.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>What does it deliver in practice?\u003C\u002Fh2>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Situation\u003C\u002Fth>\n\u003Cth>Before integration\u003C\u002Fth>\n\u003Cth>After integration\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Creating an invoice\u003C\u002Ftd>\n\u003Ctd>5–10 min. manually\u003C\u002Ftd>\n\u003Ctd>< 5 seconds automatically\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Error rate\u003C\u002Ftd>\n\u003Ctd>2–5% (manual entry)\u003C\u002Ftd>\n\u003Ctd>Near 0%\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Viewing payment status\u003C\u002Ftd>\n\u003Ctd>Manual check daily\u003C\u002Ftd>\n\u003Ctd>Real-time in FileMaker\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Audit trail\u003C\u002Ftd>\n\u003Ctd>Fragmented\u003C\u002Ftd>\n\u003Ctd>Centrally logged\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\n\u003Ch2>What should you watch out for during implementation?\u003C\u002Fh2>\n\u003Col>\n\u003Cli>\u003Cstrong>Exact Online subscription\u003C\u002Fstrong> — check whether your subscription includes API access (Standard or higher).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Division ID\u003C\u002Fstrong> — Exact Online works with divisions; ensure FileMaker always includes the correct division in every API request.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Mapping VAT codes\u003C\u002Fstrong> — FileMaker VAT codes must correspond exactly to the Exact Online general ledger structure. Set up a translation table.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Rate limiting\u003C\u002Fstrong> — Exact Online enforces a limit of 60 requests per minute per token. Build a queue in FileMaker for bulk processing.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Use a test environment\u003C\u002Fstrong> — Exact Online provides a sandbox. Always test with dummy data first before going live.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2>Ready to integrate?\u003C\u002Fh2>\n\u003Cp>A well-implemented API integration between FileMaker and Exact Online saves hours per week, reduces errors, and gives finance managers real-time insight. Loggix builds these integrations on a custom basis, tailored to your processes and security requirements. Get in touch for a no-obligation conversation.\u003C\u002Fp>\n",1782825233000,[23,253,73,44],"Exact Online","\u002Fapi\u002Fknowledge\u002Fimage\u002F90\u002F?v=08dd008c9df1",{"id":256,"idKnowledge":257,"idDomain":15,"idCluster":15,"slug":258,"title":259,"description":260,"bodyMarkdown":261,"bodyHtml":262,"author":39,"date":263,"createdAt":264,"topics":265,"image":268,"hasDownload":28,"fileName":15,"youtubeId":27},"88","85F29E6F-A1DC-3249-8377-49ECCA36356A","filemaker-mobiele-app-bouwen-wat-werkt","Building a FileMaker mobile app: what works","Building a FileMaker mobile app for inventory, service, or sales? Read what works, where the pitfalls are, and how to modernize smartly.","Building a FileMaker mobile app sounds like a logical next step for many organizations. The reality, however, is that mobile working only delivers real value when the app aligns with existing processes, data sources, and exceptions on the shop floor. That is precisely where things often go wrong: too much attention is paid to screens, while adoption usually depends on workflow, performance, and data quality.\n\nFor companies with an existing FileMaker environment, this is not a theoretical point. Often, years of business logic are already embedded in the system — from pricing agreements and order checks to scheduling rules and service reports. In that case, you don't want to start over, but you also don't want to be stuck with a solution that just doesn't work comfortably outside the office or warehouse. A mobile approach therefore needs to do two things simultaneously: preserve existing value and make usage simpler.\n\n## When building a FileMaker mobile app makes sense\n\nA mobile app is especially interesting when employees don't sit at a desk all day. Think of field service, warehouse, production, field service technicians, quality control, or on-site sales. In such situations, working with paper, Excel, or separate apps costs time every day and causes errors through double entry.\n\nYet mobile is not always the best first step. Sometimes the real problem lies in outdated scripts, a messy data model, or missing connections to other systems. If that foundation is not in order, you simply move the problem to a smaller screen. That is why a good mobile project usually doesn't start with design, but with the question: which tasks need to be faster, simpler, and more reliable?\n\nThis often yields a clear selection of processes that lend themselves well to mobile use. Inventory counts, work orders, inspections, time tracking, delivery confirmation, and CRM updates are good examples. Complex back-office tasks with many exceptions, extensive reports, or intensive data management often continue to work better on desktop or web.\n\n## Building a FileMaker mobile app from existing processes\n\nFor organizations with an existing FileMaker system, it is tempting to make current layouts available on mobile one-to-one. Technically that is sometimes possible, but functionally it is rarely the best choice. A desktop screen with many fields, tabs, and buttons simply works differently on a phone or tablet.\n\nThe better approach is to look per role at which actions someone actually performs on the go. A service technician wants to view customer data, complete a checklist, add photos, register parts, and collect a signature. That user has little use for administrative functions or extensive analyses. By designing the mobile app around those core tasks, usage becomes faster and the chance of errors decreases.\n\nThis also means making choices. Not everything needs to be mobile. In many projects, a combination of desktop, web, and mobile is actually most effective. FileMaker then remains the central platform, while the mobile layer is focused on execution in the field. This is often faster to realize and less expensive to maintain than a completely standalone app with a separate backend.\n\n## The technical choice: FileMaker Go, web, or native\n\nAnyone considering building a FileMaker mobile app will quickly encounter four options: FileMaker Go, WebDirect, a progressive web app, or a native mobile app. Which route fits depends on the use case, budget, maintenance preferences, and growth plans.\n\nFileMaker Go seems like the fastest route but has a major limitation — it is iOS only and therefore does not work on Android. If you happen to need an iOS-only solution, FileMaker Go lets you reuse existing logic, test relatively quickly with users, and keep the step toward mobile small. For internal apps, tablets in operations, or controlled user groups, this is often a very workable choice. Do keep in mind the limitations of the FileMaker ecosystem on mobile, including interface behavior, distribution, and device management.\n\nWebDirect is FileMaker's 'plug-and-play' environment for transforming FileMaker's client interface directly into a browser. Although Claris (https:\u002F\u002Fwww.claris.com) appears to be placing greater emphasis on WebDirect, it is still a functionally limited environment. In addition, offline use is not possible.\n\nA progressive web app is more interesting when accessibility, distribution, and platform-independent use are important. Users then do not always need to work through the FileMaker client, and the user experience can be more specifically tailored to mobile use. The trade-off is that development often requires more customization, especially if existing FileMaker logic is not neatly structured or if a lot of interaction with external services is needed. 'Progressive' means, by the way, that your solution can simply be installed via a browser without going through an app store.\n\nA (hybrid) native app is usually only logical when device features, performance, offline behavior, or distribution requirements carry more weight. Think of intensive camera use, barcode scanning, push notifications, or complex interaction without a stable connection. That can deliver a lot, but it is also a heavier undertaking. The business value must then be clear.\n\n## Where mobile projects fail in practice\n\nThe biggest pitfall is not technology, but underestimating the shop floor. An app that seems logical in the office can turn out to be completely impractical in the field. Gloves, poor connectivity, time pressure, dirty environments, and various exceptional situations all determine how well a mobile solution actually works.\n\nThat is why details matter. How many taps are needed to complete a work order? Can you quickly search by customer, order, or serial number? What happens when a technician is temporarily offline? Can you easily capture photos and attachments without slowing down the process? These kinds of questions often determine adoption more than what technology is under the hood.\n\nA second problem is that mobile apps are often seen as a standalone project. In reality, they almost always touch integrations, permission structures, synchronization, and data standards. As soon as a field service employee enters data, it needs to be accurate in scheduling, invoicing, inventory, and reporting. If that chain is not involved, manual correction work will still arise.\n\n## Integrations make the difference\n\nA mobile FileMaker solution becomes much more valuable as soon as it does not stand alone. In practice, that means [connections with ERP](https:\u002F\u002Floggix.com\u002Fapis\u002F), accounting, CRM, e-commerce, scheduling software, identity management, or document services. Mobile then changes from a convenient input layer into a genuine part of the business process.\n\nExample: a service team works on-site in a mobile app, sees the correct customer agreements directly, registers parts used, collects a digital signature, and automatically forwards the work order to invoicing. Or a warehouse employee scans goods, after which inventory is immediately updated in both FileMaker and an external platform. That kind of chain usually delivers more than just a nicer mobile screen.\n\nThis is precisely where a [pragmatic approach](https:\u002F\u002Floggix.com\u002Fblog\u002Fnecessity-driven-development-bouw-alleen-software-die-echt-nodig-is\u002F) is important. Not every integration needs to go live in phase one. It is often smarter to first stabilize the core of the mobile process and then expand integrations in phases. This keeps lead time and risk manageable.\n\n## How to approach building a FileMaker mobile app wisely\n\nA good project starts with a limited, concrete scope. Not \"we want everything mobile\", but for example \"technicians must be able to complete work orders within three minutes\". Such a definition makes choices easier and prevents a project from getting bogged down in wish lists.\n\nThis is usually followed by a brief analysis of process, user roles, and existing FileMaker structure. Which tables, scripts, and validations are usable? Where is there technical debt? Which parts are suitable for reuse and where is renewal needed? This step is less visible than design, but it determines whether you can move forward quickly.\n\nSubsequently, a working prototype is often more effective than extensive documentation. Real users can then indicate early on what does and does not work. This saves debate and prevents the team from spending months building a solution that turns out to be slightly wrong in practice.\n\nSecurity and maintenance also deserve early attention. Mobile access means thinking about authentication, role-based permissions, encryption, device loss, logging, and updates. Especially when customer data, service history, or commercial information becomes available outside the office, you don't want to arrange that after the fact.\n\n## What it costs and when it pays off\n\nThe costs of a mobile FileMaker solution vary widely. A targeted extension for an internal team can remain relatively compact. A broader platform with a custom interface, offline logic, API connections, and multiple user roles naturally requires more investment.\n\nWith the advent of AI and the many vibe coding solutions, the cost of developing an 'app' has dropped dramatically. Where we might previously have spent months on a development, today we can sometimes deliver an MVP within two weeks.\n\nThe business case usually lies not only in time savings per user. Fewer errors, faster invoicing, better data quality, less paperwork, and shorter lead times count just as much. Especially for organizations that perform many actions daily, returns often materialize faster than expected.\n\nAt the same time: not every process deserves an app. Sometimes it is smarter to first [clean up the core of the FileMaker system](https:\u002F\u002Floggix.com\u002Fblog\u002Fwhy-use-filemaker-features-importance-and-ai-integration\u002F), improve integrations, or modernize web access. An experienced partner will simply say so. At Loggix, that is often exactly the starting point: not adding more technology than necessary, but choosing the right combination for how people actually work.\n\nThe best mobile solution is ultimately not the most impressive one. It is the solution that allows employees to think less, ensures data is immediately correct, and finally makes the existing system move along with the reality on the shop floor.\n\nWant to know more or have questions? Feel free to contact us: kantoor@loggix.com","\u003Cp>Building a FileMaker mobile app sounds like a logical next step for many organizations. The reality, however, is that mobile working only delivers real value when the app aligns with existing processes, data sources, and exceptions on the shop floor. That is precisely where things often go wrong: too much attention is paid to screens, while adoption usually depends on workflow, performance, and data quality.\u003C\u002Fp>\n\u003Cp>For companies with an existing FileMaker environment, this is not a theoretical point. Often, years of business logic are already embedded in the system — from pricing agreements and order checks to scheduling rules and service reports. In that case, you don't want to start over, but you also don't want to be stuck with a solution that just doesn't work comfortably outside the office or warehouse. A mobile approach therefore needs to do two things simultaneously: preserve existing value and make usage simpler.\u003C\u002Fp>\n\u003Ch2>When building a FileMaker mobile app makes sense\u003C\u002Fh2>\n\u003Cp>A mobile app is especially interesting when employees don't sit at a desk all day. Think of field service, warehouse, production, field service technicians, quality control, or on-site sales. In such situations, working with paper, Excel, or separate apps costs time every day and causes errors through double entry.\u003C\u002Fp>\n\u003Cp>Yet mobile is not always the best first step. Sometimes the real problem lies in outdated scripts, a messy data model, or missing connections to other systems. If that foundation is not in order, you simply move the problem to a smaller screen. That is why a good mobile project usually doesn't start with design, but with the question: which tasks need to be faster, simpler, and more reliable?\u003C\u002Fp>\n\u003Cp>This often yields a clear selection of processes that lend themselves well to mobile use. Inventory counts, work orders, inspections, time tracking, delivery confirmation, and CRM updates are good examples. Complex back-office tasks with many exceptions, extensive reports, or intensive data management often continue to work better on desktop or web.\u003C\u002Fp>\n\u003Ch2>Building a FileMaker mobile app from existing processes\u003C\u002Fh2>\n\u003Cp>For organizations with an existing FileMaker system, it is tempting to make current layouts available on mobile one-to-one. Technically that is sometimes possible, but functionally it is rarely the best choice. A desktop screen with many fields, tabs, and buttons simply works differently on a phone or tablet.\u003C\u002Fp>\n\u003Cp>The better approach is to look per role at which actions someone actually performs on the go. A service technician wants to view customer data, complete a checklist, add photos, register parts, and collect a signature. That user has little use for administrative functions or extensive analyses. By designing the mobile app around those core tasks, usage becomes faster and the chance of errors decreases.\u003C\u002Fp>\n\u003Cp>This also means making choices. Not everything needs to be mobile. In many projects, a combination of desktop, web, and mobile is actually most effective. FileMaker then remains the central platform, while the mobile layer is focused on execution in the field. This is often faster to realize and less expensive to maintain than a completely standalone app with a separate backend.\u003C\u002Fp>\n\u003Ch2>The technical choice: FileMaker Go, web, or native\u003C\u002Fh2>\n\u003Cp>Anyone considering building a FileMaker mobile app will quickly encounter four options: FileMaker Go, WebDirect, a progressive web app, or a native mobile app. Which route fits depends on the use case, budget, maintenance preferences, and growth plans.\u003C\u002Fp>\n\u003Cp>FileMaker Go seems like the fastest route but has a major limitation — it is iOS only and therefore does not work on Android. If you happen to need an iOS-only solution, FileMaker Go lets you reuse existing logic, test relatively quickly with users, and keep the step toward mobile small. For internal apps, tablets in operations, or controlled user groups, this is often a very workable choice. Do keep in mind the limitations of the FileMaker ecosystem on mobile, including interface behavior, distribution, and device management.\u003C\u002Fp>\n\u003Cp>WebDirect is FileMaker's 'plug-and-play' environment for transforming FileMaker's client interface directly into a browser. Although Claris (\u003Ca href=\"https:\u002F\u002Fwww.claris.com\">https:\u002F\u002Fwww.claris.com\u003C\u002Fa>) appears to be placing greater emphasis on WebDirect, it is still a functionally limited environment. In addition, offline use is not possible.\u003C\u002Fp>\n\u003Cp>A progressive web app is more interesting when accessibility, distribution, and platform-independent use are important. Users then do not always need to work through the FileMaker client, and the user experience can be more specifically tailored to mobile use. The trade-off is that development often requires more customization, especially if existing FileMaker logic is not neatly structured or if a lot of interaction with external services is needed. 'Progressive' means, by the way, that your solution can simply be installed via a browser without going through an app store.\u003C\u002Fp>\n\u003Cp>A (hybrid) native app is usually only logical when device features, performance, offline behavior, or distribution requirements carry more weight. Think of intensive camera use, barcode scanning, push notifications, or complex interaction without a stable connection. That can deliver a lot, but it is also a heavier undertaking. The business value must then be clear.\u003C\u002Fp>\n\u003Ch2>Where mobile projects fail in practice\u003C\u002Fh2>\n\u003Cp>The biggest pitfall is not technology, but underestimating the shop floor. An app that seems logical in the office can turn out to be completely impractical in the field. Gloves, poor connectivity, time pressure, dirty environments, and various exceptional situations all determine how well a mobile solution actually works.\u003C\u002Fp>\n\u003Cp>That is why details matter. How many taps are needed to complete a work order? Can you quickly search by customer, order, or serial number? What happens when a technician is temporarily offline? Can you easily capture photos and attachments without slowing down the process? These kinds of questions often determine adoption more than what technology is under the hood.\u003C\u002Fp>\n\u003Cp>A second problem is that mobile apps are often seen as a standalone project. In reality, they almost always touch integrations, permission structures, synchronization, and data standards. As soon as a field service employee enters data, it needs to be accurate in scheduling, invoicing, inventory, and reporting. If that chain is not involved, manual correction work will still arise.\u003C\u002Fp>\n\u003Ch2>Integrations make the difference\u003C\u002Fh2>\n\u003Cp>A mobile FileMaker solution becomes much more valuable as soon as it does not stand alone. In practice, that means \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fapis\u002F\">connections with ERP\u003C\u002Fa>, accounting, CRM, e-commerce, scheduling software, identity management, or document services. Mobile then changes from a convenient input layer into a genuine part of the business process.\u003C\u002Fp>\n\u003Cp>Example: a service team works on-site in a mobile app, sees the correct customer agreements directly, registers parts used, collects a digital signature, and automatically forwards the work order to invoicing. Or a warehouse employee scans goods, after which inventory is immediately updated in both FileMaker and an external platform. That kind of chain usually delivers more than just a nicer mobile screen.\u003C\u002Fp>\n\u003Cp>This is precisely where a \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Fnecessity-driven-development-bouw-alleen-software-die-echt-nodig-is\u002F\">pragmatic approach\u003C\u002Fa> is important. Not every integration needs to go live in phase one. It is often smarter to first stabilize the core of the mobile process and then expand integrations in phases. This keeps lead time and risk manageable.\u003C\u002Fp>\n\u003Ch2>How to approach building a FileMaker mobile app wisely\u003C\u002Fh2>\n\u003Cp>A good project starts with a limited, concrete scope. Not "we want everything mobile", but for example "technicians must be able to complete work orders within three minutes". Such a definition makes choices easier and prevents a project from getting bogged down in wish lists.\u003C\u002Fp>\n\u003Cp>This is usually followed by a brief analysis of process, user roles, and existing FileMaker structure. Which tables, scripts, and validations are usable? Where is there technical debt? Which parts are suitable for reuse and where is renewal needed? This step is less visible than design, but it determines whether you can move forward quickly.\u003C\u002Fp>\n\u003Cp>Subsequently, a working prototype is often more effective than extensive documentation. Real users can then indicate early on what does and does not work. This saves debate and prevents the team from spending months building a solution that turns out to be slightly wrong in practice.\u003C\u002Fp>\n\u003Cp>Security and maintenance also deserve early attention. Mobile access means thinking about authentication, role-based permissions, encryption, device loss, logging, and updates. Especially when customer data, service history, or commercial information becomes available outside the office, you don't want to arrange that after the fact.\u003C\u002Fp>\n\u003Ch2>What it costs and when it pays off\u003C\u002Fh2>\n\u003Cp>The costs of a mobile FileMaker solution vary widely. A targeted extension for an internal team can remain relatively compact. A broader platform with a custom interface, offline logic, API connections, and multiple user roles naturally requires more investment.\u003C\u002Fp>\n\u003Cp>With the advent of AI and the many vibe coding solutions, the cost of developing an 'app' has dropped dramatically. Where we might previously have spent months on a development, today we can sometimes deliver an MVP within two weeks.\u003C\u002Fp>\n\u003Cp>The business case usually lies not only in time savings per user. Fewer errors, faster invoicing, better data quality, less paperwork, and shorter lead times count just as much. Especially for organizations that perform many actions daily, returns often materialize faster than expected.\u003C\u002Fp>\n\u003Cp>At the same time: not every process deserves an app. Sometimes it is smarter to first \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Fwhy-use-filemaker-features-importance-and-ai-integration\u002F\">clean up the core of the FileMaker system\u003C\u002Fa>, improve integrations, or modernize web access. An experienced partner will simply say so. At Loggix, that is often exactly the starting point: not adding more technology than necessary, but choosing the right combination for how people actually work.\u003C\u002Fp>\n\u003Cp>The best mobile solution is ultimately not the most impressive one. It is the solution that allows employees to think less, ensures data is immediately correct, and finally makes the existing system move along with the reality on the shop floor.\u003C\u002Fp>\n\u003Cp>Want to know more or have questions? Feel free to contact us: \u003Ca href=\"mailto:kantoor@loggix.com\">kantoor@loggix.com\u003C\u002Fa>\u003C\u002Fp>\n","2026-06-29",1782754422000,[266,267],"Mobile","App","\u002Fapi\u002Fknowledge\u002Fimage\u002F88\u002F?v=93b0917ddb10",{"id":270,"idKnowledge":271,"idDomain":15,"idCluster":15,"slug":272,"title":273,"description":274,"bodyMarkdown":275,"bodyHtml":276,"author":39,"date":277,"createdAt":278,"topics":279,"image":281,"hasDownload":28,"fileName":15,"youtubeId":27},"87","09B6C2C7-79A0-9049-A4DA-1DFE6B3D4B07","webapp-op-filemaker-data-slim-aanpakken","Webapp on FileMaker data: the smart approach","A webapp on FileMaker data gives existing systems a modern layer. Read what works, where the pitfalls are, and how to modernise smartly.","A team that has been working with FileMaker for years knows the pattern: the database does exactly what is needed, the processes are well established, but access via browser or mobile falls short. Then the question comes up: can we build a webapp on FileMaker data without rebuilding everything from scratch? The short answer is yes. The longer answer is that the quality of that solution depends entirely on architecture, integrations, and the choices you make at the start.\n\n## When a webapp on FileMaker data makes sense\n\nFor many organisations, FileMaker is not the problem — it is precisely the reason processes have remained workable for years. The database often contains exactly the business logic that standard software lacks: quotes, order flows, work orders, schedules, quality registrations, or customer files that have grown through practical use. The problem only arises when users outside the office, external parties, or larger teams need access in a modern way.\n\nA webapp on FileMaker data is then often a logical step. You retain the value of existing data and process logic, while adding a user experience that suits browser use, mobile screens, and external access. That is different from a full migration. You are not immediately replacing the foundation, but making it more usable for the next phase of your organisation.\n\nThis is especially relevant if your FileMaker environment is business-critical, if a replacement project is too expensive or too risky, or if you want quick results without disrupting daily operations.\n\n## What a webapp does and does not solve\n\nA webapp solves accessibility, ease of use, and integration possibilities. Employees can work in a browser, customers or partners can view or enter data via a secured portal, and processes can be more easily connected to other systems such as accounting, e-commerce, planning, or BI.\n\nBut a webapp is not a cosmetic layer that automatically removes all technical debt. If the underlying FileMaker structure is messy, scripts are outdated, or data models have not been built consistently, that problem simply moves along with it. The front end becomes more modern, but the vulnerability remains.\n\nThat is why a good trajectory does not start with design, but with analysis. Which data needs to be available? What user roles exist? Which actions need to be fast and error-free? And which logic should remain in FileMaker, and which logic is better moved to a separate application layer or API?\n\n## Architecture choices determine longevity\n\nAnyone wanting to build a webapp on FileMaker data has roughly three routes. The first is working directly on existing FileMaker functionality. That can be quick in some cases, but is usually limited if you want a modern, scalable web experience. The second route is using FileMaker as the primary data source and business logic, with a separate webapp that communicates via [APIs](https:\u002F\u002Floggix.com\u002Fapis\u002F). The third route is a hybrid model, where part of the logic remains in FileMaker and part is separated out into services or middleware.\n\nFor most organisations, the second or third route is the wisest choice. This prevents the webapp from being too tightly coupled to the internal workings of FileMaker. It creates room for better performance, tighter security, and future-proof maintenance.\n\nThis is also the point where pragmatism matters more than theory. Not every environment needs to be set up in a fully service-oriented way right away. Sometimes it is smarter to first build a [customer portal](https:\u002F\u002Floggix.com\u002Fblog\u002Fwebapps-based-on-filemaker\u002F), scheduling module, or input screen on the existing FileMaker data, and only then further separate parts of the architecture. Modernisation often works better in steps than in one big all-or-nothing project.\n\n## Which processes are most suitable\n\nNot every part of a FileMaker solution needs to go to the web. Processes with clear input, many users, or external access in particular often deliver quick returns. Think of service notifications, work orders, time tracking, inventory mutations, CRM data, customer portals, and approval flows.\n\nInternal screens with many exceptions, complex layouts, or specialised administrative tasks are sometimes less suitable as a first step. There the business value of a webapp is often lower, while the development effort is higher. A sensible approach therefore first selects the processes where ease of use, speed, and error reduction are directly measurable.\n\nFor operations and IT, this is a relevant distinction. A webapp project rarely succeeds because all functions are migrated at once. It succeeds because the right functions are chosen first.\n\n## Integrations make the difference\n\nThe real value of a webapp on FileMaker data often lies not only in the interface, but in what becomes possible around it. Once data becomes available through a clean application layer, connecting systems becomes easier. You can then, for example, combine orders from a web shop with internal order processing in FileMaker, or have customer data flow through to invoicing, support, or dashboards.\n\nThis transforms FileMaker from a standalone system into part of a broader software chain. For many organisations, that is the step that finally makes manual retyping, double entry, and error-prone export files redundant.\n\nA clear caveat applies here, however: integrations require discipline. APIs, authentication, error handling, and logging must be properly set up. Otherwise you end up with a modern-looking solution that proves difficult and fragile to maintain. Especially when multiple systems are involved, technical design is not an afterthought but a prerequisite.\n\n## Security and permissions require extra attention\n\nOnce FileMaker data becomes available via a webapp, the risk profile changes. Internal users behind a trusted network are different from field staff, customers, or suppliers working via the internet. You therefore need to think more carefully about session management, authorisations, data selection, and audit trails.\n\nA common mistake is that existing FileMaker permissions are taken over one-to-one without reconsidering roles and context. A user may be allowed to see a lot internally because it was practical, but in a webapp that broad access is often undesirable. Good security therefore does not start with technology alone, but with redesigning who is allowed to see and change what.\n\nFor companies in sectors with sensitive data, this is even more important. Then it is not only a matter of whether the webapp works, but also whether management, logging, and compliance are defensible.\n\n## Performance is more than page speed\n\nUsers quickly judge a webapp by response time, but performance is broader than that. It also concerns how efficiently data is retrieved, how many records are processed simultaneously, how search functions are set up, and what happens under peak load. A screen that works fine in a test environment can grind to a halt in practice when dozens of users are simultaneously searching, filtering, and editing.\n\nA webapp on FileMaker data therefore needs to be designed differently from a traditional desktop-oriented FileMaker solution. Not every data request needs to be complete. Not every layout logic needs to come along. And not every user needs to receive the same amount of data.\n\nBy working smartly with APIs, caching where appropriate, targeted queries, and clear user flows, a solution becomes not only faster but also more stable. You notice this especially at moments when the pressure is high and systems must not cause delays.\n\n## When migrating is better than extending\n\nThere are also situations where a webapp on FileMaker data is not the best route. If the data model is severely corrupted, the solution is barely maintainable, critical knowledge has disappeared, or scalability requirements are growing significantly, a partial or full rebuild may be the wiser choice.\n\nThis does not mean that earlier investments are lost. On the contrary. FileMaker environments in particular often contain valuable process knowledge that can serve as the basis for a new architecture. The question is therefore not only whether you want to retain the existing database, but which part of that environment is strategically valuable.\n\nAn experienced development partner therefore looks not only at what is technically possible, but at what makes business sense. Sometimes extending is the right choice. Sometimes phased replacement is smarter. And sometimes the best solution is a combination of both.\n\n## What a practical trajectory looks like\n\nA good trajectory begins with a technical and functional inventory. Not as a heavy preliminary study taking months, but as a sharp analysis of processes, data, dependencies, and risks. This is usually followed by scoping one concrete use case that makes value visible quickly.\n\nThink of a customer portal, a mobile input app for field staff, or an internal web module for order status and approval. If that first step is set up well, a pattern emerges on which further expansion can build. This prevents standalone solutions that have to be reworked later.\n\nThat is precisely where the practical added value of a partner like Loggix lies: not just making something work, but ensuring the chosen solution fits the existing FileMaker environment, future integrations, and daily use by employees.\n\nA webapp on FileMaker data is rarely a goal in itself. It is a way to make a system that already delivers value deployable again for the way your organisation works today. Those who approach this [step by step](https:\u002F\u002Floggix.com\u002Fblog\u002Ffilemaker-systeem-moderniseren-zonder-risico\u002F) and with technical rigour often get more value from existing software than from a hasty replacement.","\u003Cp>A team that has been working with FileMaker for years knows the pattern: the database does exactly what is needed, the processes are well established, but access via browser or mobile falls short. Then the question comes up: can we build a webapp on FileMaker data without rebuilding everything from scratch? The short answer is yes. The longer answer is that the quality of that solution depends entirely on architecture, integrations, and the choices you make at the start.\u003C\u002Fp>\n\u003Ch2>When a webapp on FileMaker data makes sense\u003C\u002Fh2>\n\u003Cp>For many organisations, FileMaker is not the problem — it is precisely the reason processes have remained workable for years. The database often contains exactly the business logic that standard software lacks: quotes, order flows, work orders, schedules, quality registrations, or customer files that have grown through practical use. The problem only arises when users outside the office, external parties, or larger teams need access in a modern way.\u003C\u002Fp>\n\u003Cp>A webapp on FileMaker data is then often a logical step. You retain the value of existing data and process logic, while adding a user experience that suits browser use, mobile screens, and external access. That is different from a full migration. You are not immediately replacing the foundation, but making it more usable for the next phase of your organisation.\u003C\u002Fp>\n\u003Cp>This is especially relevant if your FileMaker environment is business-critical, if a replacement project is too expensive or too risky, or if you want quick results without disrupting daily operations.\u003C\u002Fp>\n\u003Ch2>What a webapp does and does not solve\u003C\u002Fh2>\n\u003Cp>A webapp solves accessibility, ease of use, and integration possibilities. Employees can work in a browser, customers or partners can view or enter data via a secured portal, and processes can be more easily connected to other systems such as accounting, e-commerce, planning, or BI.\u003C\u002Fp>\n\u003Cp>But a webapp is not a cosmetic layer that automatically removes all technical debt. If the underlying FileMaker structure is messy, scripts are outdated, or data models have not been built consistently, that problem simply moves along with it. The front end becomes more modern, but the vulnerability remains.\u003C\u002Fp>\n\u003Cp>That is why a good trajectory does not start with design, but with analysis. Which data needs to be available? What user roles exist? Which actions need to be fast and error-free? And which logic should remain in FileMaker, and which logic is better moved to a separate application layer or API?\u003C\u002Fp>\n\u003Ch2>Architecture choices determine longevity\u003C\u002Fh2>\n\u003Cp>Anyone wanting to build a webapp on FileMaker data has roughly three routes. The first is working directly on existing FileMaker functionality. That can be quick in some cases, but is usually limited if you want a modern, scalable web experience. The second route is using FileMaker as the primary data source and business logic, with a separate webapp that communicates via \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fapis\u002F\">APIs\u003C\u002Fa>. The third route is a hybrid model, where part of the logic remains in FileMaker and part is separated out into services or middleware.\u003C\u002Fp>\n\u003Cp>For most organisations, the second or third route is the wisest choice. This prevents the webapp from being too tightly coupled to the internal workings of FileMaker. It creates room for better performance, tighter security, and future-proof maintenance.\u003C\u002Fp>\n\u003Cp>This is also the point where pragmatism matters more than theory. Not every environment needs to be set up in a fully service-oriented way right away. Sometimes it is smarter to first build a \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Fwebapps-based-on-filemaker\u002F\">customer portal\u003C\u002Fa>, scheduling module, or input screen on the existing FileMaker data, and only then further separate parts of the architecture. Modernisation often works better in steps than in one big all-or-nothing project.\u003C\u002Fp>\n\u003Ch2>Which processes are most suitable\u003C\u002Fh2>\n\u003Cp>Not every part of a FileMaker solution needs to go to the web. Processes with clear input, many users, or external access in particular often deliver quick returns. Think of service notifications, work orders, time tracking, inventory mutations, CRM data, customer portals, and approval flows.\u003C\u002Fp>\n\u003Cp>Internal screens with many exceptions, complex layouts, or specialised administrative tasks are sometimes less suitable as a first step. There the business value of a webapp is often lower, while the development effort is higher. A sensible approach therefore first selects the processes where ease of use, speed, and error reduction are directly measurable.\u003C\u002Fp>\n\u003Cp>For operations and IT, this is a relevant distinction. A webapp project rarely succeeds because all functions are migrated at once. It succeeds because the right functions are chosen first.\u003C\u002Fp>\n\u003Ch2>Integrations make the difference\u003C\u002Fh2>\n\u003Cp>The real value of a webapp on FileMaker data often lies not only in the interface, but in what becomes possible around it. Once data becomes available through a clean application layer, connecting systems becomes easier. You can then, for example, combine orders from a web shop with internal order processing in FileMaker, or have customer data flow through to invoicing, support, or dashboards.\u003C\u002Fp>\n\u003Cp>This transforms FileMaker from a standalone system into part of a broader software chain. For many organisations, that is the step that finally makes manual retyping, double entry, and error-prone export files redundant.\u003C\u002Fp>\n\u003Cp>A clear caveat applies here, however: integrations require discipline. APIs, authentication, error handling, and logging must be properly set up. Otherwise you end up with a modern-looking solution that proves difficult and fragile to maintain. Especially when multiple systems are involved, technical design is not an afterthought but a prerequisite.\u003C\u002Fp>\n\u003Ch2>Security and permissions require extra attention\u003C\u002Fh2>\n\u003Cp>Once FileMaker data becomes available via a webapp, the risk profile changes. Internal users behind a trusted network are different from field staff, customers, or suppliers working via the internet. You therefore need to think more carefully about session management, authorisations, data selection, and audit trails.\u003C\u002Fp>\n\u003Cp>A common mistake is that existing FileMaker permissions are taken over one-to-one without reconsidering roles and context. A user may be allowed to see a lot internally because it was practical, but in a webapp that broad access is often undesirable. Good security therefore does not start with technology alone, but with redesigning who is allowed to see and change what.\u003C\u002Fp>\n\u003Cp>For companies in sectors with sensitive data, this is even more important. Then it is not only a matter of whether the webapp works, but also whether management, logging, and compliance are defensible.\u003C\u002Fp>\n\u003Ch2>Performance is more than page speed\u003C\u002Fh2>\n\u003Cp>Users quickly judge a webapp by response time, but performance is broader than that. It also concerns how efficiently data is retrieved, how many records are processed simultaneously, how search functions are set up, and what happens under peak load. A screen that works fine in a test environment can grind to a halt in practice when dozens of users are simultaneously searching, filtering, and editing.\u003C\u002Fp>\n\u003Cp>A webapp on FileMaker data therefore needs to be designed differently from a traditional desktop-oriented FileMaker solution. Not every data request needs to be complete. Not every layout logic needs to come along. And not every user needs to receive the same amount of data.\u003C\u002Fp>\n\u003Cp>By working smartly with APIs, caching where appropriate, targeted queries, and clear user flows, a solution becomes not only faster but also more stable. You notice this especially at moments when the pressure is high and systems must not cause delays.\u003C\u002Fp>\n\u003Ch2>When migrating is better than extending\u003C\u002Fh2>\n\u003Cp>There are also situations where a webapp on FileMaker data is not the best route. If the data model is severely corrupted, the solution is barely maintainable, critical knowledge has disappeared, or scalability requirements are growing significantly, a partial or full rebuild may be the wiser choice.\u003C\u002Fp>\n\u003Cp>This does not mean that earlier investments are lost. On the contrary. FileMaker environments in particular often contain valuable process knowledge that can serve as the basis for a new architecture. The question is therefore not only whether you want to retain the existing database, but which part of that environment is strategically valuable.\u003C\u002Fp>\n\u003Cp>An experienced development partner therefore looks not only at what is technically possible, but at what makes business sense. Sometimes extending is the right choice. Sometimes phased replacement is smarter. And sometimes the best solution is a combination of both.\u003C\u002Fp>\n\u003Ch2>What a practical trajectory looks like\u003C\u002Fh2>\n\u003Cp>A good trajectory begins with a technical and functional inventory. Not as a heavy preliminary study taking months, but as a sharp analysis of processes, data, dependencies, and risks. This is usually followed by scoping one concrete use case that makes value visible quickly.\u003C\u002Fp>\n\u003Cp>Think of a customer portal, a mobile input app for field staff, or an internal web module for order status and approval. If that first step is set up well, a pattern emerges on which further expansion can build. This prevents standalone solutions that have to be reworked later.\u003C\u002Fp>\n\u003Cp>That is precisely where the practical added value of a partner like Loggix lies: not just making something work, but ensuring the chosen solution fits the existing FileMaker environment, future integrations, and daily use by employees.\u003C\u002Fp>\n\u003Cp>A webapp on FileMaker data is rarely a goal in itself. It is a way to make a system that already delivers value deployable again for the way your organisation works today. Those who approach this \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Ffilemaker-systeem-moderniseren-zonder-risico\u002F\">step by step\u003C\u002Fa> and with technical rigour often get more value from existing software than from a hasty replacement.\u003C\u002Fp>\n","2026-06-28",1782660057000,[23,280,73],"WebApp","\u002Fapi\u002Fknowledge\u002Fimage\u002F87\u002F?v=aa279ad5a00d",{"id":283,"idKnowledge":284,"idDomain":15,"idCluster":15,"slug":285,"title":286,"description":287,"bodyMarkdown":288,"bodyHtml":289,"author":39,"date":277,"createdAt":290,"topics":291,"image":293,"hasDownload":28,"fileName":15,"youtubeId":27},"86","C7382B86-2A6E-724A-A086-16980CD52883","how-to-speed-up-data-input-in-filemaker-with-handy-free-speech-to-text-tool","How to Speed Up Data Input in FileMaker with Handy (Free Speech-to-Text Tool)","Handy is a free tool that lets you dictate text into any FileMaker field using a single hotkey — powered by a local AI model, no cloud needed.","Assign a single keyboard key, speak, and Handy instantly transcribes your words into any FileMaker field. No copy-pasting, no switching apps — just faster data input.\n\n## What is Handy?\n\nHandy is a free, lightweight desktop app that brings speech-to-text to any input field on your computer — including every field in your FileMaker solution. What makes it stand out: it runs a **local AI model**, meaning your data never leaves your machine. That is a big deal for businesses handling sensitive or confidential information.\n\n## Why FileMaker Users Will Love It\n\nFileMaker is powerful, but entering large amounts of text — notes, descriptions, client feedback — can slow you down. Handy removes that friction:\n\n- Works in **any** FileMaker field (text, notes, portals — you name it)\n- No internet connection required\n- No subscription or licensing cost — it's completely **free**\n- Privacy-friendly: all processing happens locally on your device\n\n## How to Get Started with Handy\n\n1. **Download Handy** — grab the free app and install it on your Windows or Mac machine.\n2. **Assign a hotkey** — open the settings and pick any keyboard key or key combination you want to use as your push-to-talk trigger.\n3. **Open your FileMaker solution** — navigate to any field where you want to enter text.\n4. **Click into the field** — place your cursor in the FileMaker field as you normally would.\n5. **Hold your hotkey and speak** — Handy listens while you hold the key and transcribes your speech directly into the field when you release it.\n6. **Done** — your spoken words appear as text, ready to save.\n\nThat's the entire workflow. No extra steps, no copy-pasting.\n\n## Local Model: Why It Matters\n\nMany speech-to-text tools send your audio to a cloud server for processing. Handy skips that entirely by running the AI model locally. For FileMaker users working with customer data, financial records, or internal business information, this means:\n\n- **No data leaves your network**\n- **Works offline** — no Wi-Fi, no problem\n- **Faster response times** — no round-trip to a server\n\n## Who Benefits Most?\n\nHandy is especially useful for FileMaker users who:\n\n- Enter long notes or descriptions regularly\n- Work in healthcare, legal, or finance where data privacy is critical\n- Want to reduce repetitive strain from typing\n- Are looking for a zero-cost productivity boost\n\n## Start Dictating Today\n\nHandy is free, takes minutes to set up, and works across your entire FileMaker solution without any custom development. If you type a lot into FileMaker fields, this is one of the easiest wins you can make right now.\n\n> **Tip:** At Loggix, we are always on the lookout for tools and integrations that make FileMaker solutions faster and smarter. Want to know how we can take your FileMaker environment to the next level? [Get in touch with us.](#)","\u003Cp>Assign a single keyboard key, speak, and Handy instantly transcribes your words into any FileMaker field. No copy-pasting, no switching apps — just faster data input.\u003C\u002Fp>\n\u003Ch2>What is Handy?\u003C\u002Fh2>\n\u003Cp>Handy is a free, lightweight desktop app that brings speech-to-text to any input field on your computer — including every field in your FileMaker solution. What makes it stand out: it runs a \u003Cstrong>local AI model\u003C\u002Fstrong>, meaning your data never leaves your machine. That is a big deal for businesses handling sensitive or confidential information.\u003C\u002Fp>\n\u003Ch2>Why FileMaker Users Will Love It\u003C\u002Fh2>\n\u003Cp>FileMaker is powerful, but entering large amounts of text — notes, descriptions, client feedback — can slow you down. Handy removes that friction:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Works in \u003Cstrong>any\u003C\u002Fstrong> FileMaker field (text, notes, portals — you name it)\u003C\u002Fli>\n\u003Cli>No internet connection required\u003C\u002Fli>\n\u003Cli>No subscription or licensing cost — it's completely \u003Cstrong>free\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Privacy-friendly: all processing happens locally on your device\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>How to Get Started with Handy\u003C\u002Fh2>\n\u003Col>\n\u003Cli>\u003Cstrong>Download Handy\u003C\u002Fstrong> — grab the free app and install it on your Windows or Mac machine.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Assign a hotkey\u003C\u002Fstrong> — open the settings and pick any keyboard key or key combination you want to use as your push-to-talk trigger.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Open your FileMaker solution\u003C\u002Fstrong> — navigate to any field where you want to enter text.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Click into the field\u003C\u002Fstrong> — place your cursor in the FileMaker field as you normally would.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Hold your hotkey and speak\u003C\u002Fstrong> — Handy listens while you hold the key and transcribes your speech directly into the field when you release it.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Done\u003C\u002Fstrong> — your spoken words appear as text, ready to save.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>That's the entire workflow. No extra steps, no copy-pasting.\u003C\u002Fp>\n\u003Ch2>Local Model: Why It Matters\u003C\u002Fh2>\n\u003Cp>Many speech-to-text tools send your audio to a cloud server for processing. Handy skips that entirely by running the AI model locally. For FileMaker users working with customer data, financial records, or internal business information, this means:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>No data leaves your network\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Works offline\u003C\u002Fstrong> — no Wi-Fi, no problem\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Faster response times\u003C\u002Fstrong> — no round-trip to a server\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Who Benefits Most?\u003C\u002Fh2>\n\u003Cp>Handy is especially useful for FileMaker users who:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Enter long notes or descriptions regularly\u003C\u002Fli>\n\u003Cli>Work in healthcare, legal, or finance where data privacy is critical\u003C\u002Fli>\n\u003Cli>Want to reduce repetitive strain from typing\u003C\u002Fli>\n\u003Cli>Are looking for a zero-cost productivity boost\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Start Dictating Today\u003C\u002Fh2>\n\u003Cp>Handy is free, takes minutes to set up, and works across your entire FileMaker solution without any custom development. If you type a lot into FileMaker fields, this is one of the easiest wins you can make right now.\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>\u003Cstrong>Tip:\u003C\u002Fstrong> At Loggix, we are always on the lookout for tools and integrations that make FileMaker solutions faster and smarter. Want to know how we can take your FileMaker environment to the next level? \u003Ca href=\"#\">Get in touch with us.\u003C\u002Fa>\u003C\u002Fp>\n\u003C\u002Fblockquote>\n",1782637838000,[23,292,86],"speech-to-text","\u002Fapi\u002Fknowledge\u002Fimage\u002F86\u002F?v=086f050baab4",{"id":295,"idKnowledge":296,"idDomain":15,"idCluster":15,"slug":297,"title":298,"description":299,"bodyMarkdown":300,"bodyHtml":301,"author":39,"date":302,"createdAt":303,"topics":304,"image":305,"hasDownload":28,"fileName":15,"youtubeId":27},"85","E446A0B6-B3D8-A24C-8F3A-C97EE1C180D7","filemaker-api-koppeling-zonder-gedoe","FileMaker API integration without the hassle","A FileMaker API integration connects your database to other systems, automates work and prevents errors - without costly replacement.","A FileMaker API integration is often not a technical luxury project, but a direct solution to something that costs time every day. Think of employees entering customer data twice, manually transferring orders to an accounting package, or checking stock levels across multiple systems. As long as that work remains just about manageable, it stays that way. Until errors accumulate, processes slow down, and nobody knows exactly which system is leading.\n\n## What a FileMaker API integration solves in practice\n\nMany companies have been using FileMaker for years for processes that are too specific for standard software. Quotes, planning, order processing, service administration, project registration — these are often exactly the operational processes where FileMaker excels. The problem usually doesn't arise in FileMaker itself, but around it.\n\nAs soon as an organisation also works with a webshop, CRM, ERP, accounting software, shipping platform, or BI tool, islands emerge. Data is then copied manually or exchanged via workarounds using exports and imports. That works for a while, but it is error-prone and difficult to scale.\n\nA good API integration ensures that FileMaker is no longer a standalone system, but becomes part of a functioning software landscape. Customer data can be retrieved or updated automatically, orders can be pushed through directly, statuses can flow back into FileMaker, and employees need to switch between screens less often. That saves time, but above all coordination.\n\n## When an integration makes sense — and when it doesn't\n\nNot every integration is automatically a good idea. Sometimes a manual step is perfectly fine, especially if a process occurs infrequently or if human oversight is intentionally required. An API integration is particularly worthwhile when data changes frequently, must be error-free, or is needed in multiple places simultaneously.\n\nThere are roughly three signals that an integration pays for itself quickly. The first is duplicate entry. If the same data is maintained in FileMaker and another system, discrepancies almost always arise. The second is delay. When employees are waiting for exports, emails, or manual updates, it slows down operations. The third is lack of insight. If reports are unreliable because information is scattered, steering the business becomes difficult.\n\nThe reverse also applies: if the source system is unstable, processes are still changing weekly, or there is no internal ownership, it is wiser to get the basics in order first. Automating a messy process usually just makes it messier, faster.\n\n## How a FileMaker API integration works technically\n\nAt its core, an API exchanges data between FileMaker and another system via agreed requests and responses. That sounds abstract, but in practice it comes down to a number of clear questions. Which data needs to go from A to B? When should that happen? Which system is leading when data differs? And what should happen if a message fails?\n\nFileMaker can both retrieve and send data. That can happen in real time — for example, immediately when an order is created — or at fixed intervals via scheduled tasks. Which approach is best depends on the process. For a [stock check](https:\u002F\u002Floggix.com\u002Fblog\u002Fvoorraad-beheer-systeem\u002F) or order status, direct synchronisation is often logical. For larger datasets or less time-critical information, batch processing is often more efficient and stable.\n\nAuthentication also plays a role. Modern APIs typically work with tokens, keys, or OAuth. That requires a solid setup for security, logging, and error handling. This is precisely where many do-it-yourself integrations go wrong. The first demo works, but as soon as a token expires, a field name changes, or a rate limit is hit, the process stops without anyone noticing immediately.\n\n## Common integrations with FileMaker\n\nThe most requested integrations are rarely exotic. In practice, it usually involves connecting FileMaker to accounting software, CRM systems, webshops, shipping services, payment platforms, and internal portals. Integrations with Power BI, Microsoft 365, Google Workspace, or custom web applications also occur regularly.\n\nAn order flow is a good example. A sales order comes in via a webshop or field sales app, is processed in FileMaker for planning or production, and then forwarded to invoicing and shipping. If those steps are manual, each one costs time and errors arise in prices, quantities, or addresses. With an API integration, each system can do what it does best, without employees having to handle the translation.\n\nSomething similar applies to service organisations. Technicians log work orders on mobile devices, FileMaker processes the operational data, and customer or contract information is synchronised with a CRM or financial system. This creates a chain that doesn't necessarily need to be entirely new, but works together much better.\n\n## The pitfall: integrating without process agreements\n\nBuilding a technical integration is often not the hardest part. The real challenge lies in decisions that need to be made beforehand. Who manages the customer record? What happens with duplicate data? Which fields are mandatory? What may be overwritten and what may not?\n\nWithout those agreements, disputes arise afterwards. It turns out, for example, that sales uses a different status in the CRM than operations uses in FileMaker, or that item codes in the webshop differ from the codes in the back office. An API does not resolve such differences. It only makes them visible faster.\n\nThat is why a meaningful integration usually starts not with technology, but with process analysis. Not endless documentation, but getting a clear picture of where the gains are and where risks arise. For operational teams, that is often a relief: not a large IT project, but a targeted improvement of work that already happens every day.\n\n## Modernising FileMaker without starting over\n\nFor many organisations, this is the most important point. An existing FileMaker environment often contains years of business logic, exceptions, screens, and working agreements. You don't simply replace that with standard software without losing functionality, flexibility, or history.\n\nA FileMaker API integration makes it possible to retain that existing environment while modernising it at the same time. You don't have to choose between leaving everything as it is or replacing everything. It is precisely in that middle ground that the most value often emerges. The current system remains usable for core processes, while new components such as [customer portals, mobile apps](https:\u002F\u002Floggix.com\u002Fblog\u002Fwebapps-based-on-filemaker\u002F), or external platforms connect via APIs.\n\nThat is usually cheaper, faster, and less disruptive than a full migration. Not because old is always good, but because business processes are often more valuable than the technology in which they were originally built. Those who understand that make better decisions about where to invest.\n\n## What to look out for in your approach\n\nA successful integration is rarely the result of writing code alone. Reliability requires choices in architecture, monitoring, and maintenance. If an external system is temporarily unavailable, it must be clear what happens. Is a message retried? Does someone receive a notification? Does the data remain in a queue?\n\nVersion management is also important. APIs change. Vendors add fields, adjust authentication, or remove old endpoints. An integration that works today must therefore remain manageable six or twelve months from now. That requires documentation, logging, and ideally a setup where changes do not immediately block the entire process.\n\nIt is also wise to start small. Rather than designing a complete integration landscape upfront, start with the process where there is the most gain or frustration — for example, order transfer, customer updates, or invoicing status. Once that runs well, expanding is much easier to achieve and justify.\n\n## Who this is relevant for\n\nCompanies with an existing FileMaker solution often have more options than they realise. Especially when the system still functionally aligns well with operations, but the surrounding environment has changed. New sales channels, external software, reporting needs, and mobile work processes then call for connection, not necessarily replacement.\n\nFor operations managers, that means less manual work and more control over execution. For [IT managers](https:\u002F\u002Floggix.com\u002Ffor-who\u002F), it means fewer shadow processes and better manageability. For directors or owners, it means that earlier investments retain their value longer, while the organisation can still continue to grow.\n\nThat is also why a partner with both FileMaker and integration expertise often makes the difference. You need someone who not only understands how an API works, but also what an existing FileMaker solution means operationally. Loggix works precisely at that intersection: modernising without unnecessary disruption, and building integrations that hold up in practice.\n\n## A good integration feels boring\n\nThat may sound strange, but it is usually a good sign. The best FileMaker API integration attracts no attention because employees no longer need to think about transfer, corrections, or intermediate steps. Data is where it needs to be, processes continue to run, and exceptions are visible before they cause damage.\n\nThat is where the real value lies. Not in technology as an end in itself, but in an operation that becomes calmer, faster, and more reliable. If your current FileMaker system is still important to your business, the question is often not whether to continue with it — but how to connect it intelligently with everything around it.\n\nWant to know more about whether API integrations can accelerate your processes? Feel free to contact us with no obligation.","\u003Cp>A FileMaker API integration is often not a technical luxury project, but a direct solution to something that costs time every day. Think of employees entering customer data twice, manually transferring orders to an accounting package, or checking stock levels across multiple systems. As long as that work remains just about manageable, it stays that way. Until errors accumulate, processes slow down, and nobody knows exactly which system is leading.\u003C\u002Fp>\n\u003Ch2>What a FileMaker API integration solves in practice\u003C\u002Fh2>\n\u003Cp>Many companies have been using FileMaker for years for processes that are too specific for standard software. Quotes, planning, order processing, service administration, project registration — these are often exactly the operational processes where FileMaker excels. The problem usually doesn't arise in FileMaker itself, but around it.\u003C\u002Fp>\n\u003Cp>As soon as an organisation also works with a webshop, CRM, ERP, accounting software, shipping platform, or BI tool, islands emerge. Data is then copied manually or exchanged via workarounds using exports and imports. That works for a while, but it is error-prone and difficult to scale.\u003C\u002Fp>\n\u003Cp>A good API integration ensures that FileMaker is no longer a standalone system, but becomes part of a functioning software landscape. Customer data can be retrieved or updated automatically, orders can be pushed through directly, statuses can flow back into FileMaker, and employees need to switch between screens less often. That saves time, but above all coordination.\u003C\u002Fp>\n\u003Ch2>When an integration makes sense — and when it doesn't\u003C\u002Fh2>\n\u003Cp>Not every integration is automatically a good idea. Sometimes a manual step is perfectly fine, especially if a process occurs infrequently or if human oversight is intentionally required. An API integration is particularly worthwhile when data changes frequently, must be error-free, or is needed in multiple places simultaneously.\u003C\u002Fp>\n\u003Cp>There are roughly three signals that an integration pays for itself quickly. The first is duplicate entry. If the same data is maintained in FileMaker and another system, discrepancies almost always arise. The second is delay. When employees are waiting for exports, emails, or manual updates, it slows down operations. The third is lack of insight. If reports are unreliable because information is scattered, steering the business becomes difficult.\u003C\u002Fp>\n\u003Cp>The reverse also applies: if the source system is unstable, processes are still changing weekly, or there is no internal ownership, it is wiser to get the basics in order first. Automating a messy process usually just makes it messier, faster.\u003C\u002Fp>\n\u003Ch2>How a FileMaker API integration works technically\u003C\u002Fh2>\n\u003Cp>At its core, an API exchanges data between FileMaker and another system via agreed requests and responses. That sounds abstract, but in practice it comes down to a number of clear questions. Which data needs to go from A to B? When should that happen? Which system is leading when data differs? And what should happen if a message fails?\u003C\u002Fp>\n\u003Cp>FileMaker can both retrieve and send data. That can happen in real time — for example, immediately when an order is created — or at fixed intervals via scheduled tasks. Which approach is best depends on the process. For a \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Fvoorraad-beheer-systeem\u002F\">stock check\u003C\u002Fa> or order status, direct synchronisation is often logical. For larger datasets or less time-critical information, batch processing is often more efficient and stable.\u003C\u002Fp>\n\u003Cp>Authentication also plays a role. Modern APIs typically work with tokens, keys, or OAuth. That requires a solid setup for security, logging, and error handling. This is precisely where many do-it-yourself integrations go wrong. The first demo works, but as soon as a token expires, a field name changes, or a rate limit is hit, the process stops without anyone noticing immediately.\u003C\u002Fp>\n\u003Ch2>Common integrations with FileMaker\u003C\u002Fh2>\n\u003Cp>The most requested integrations are rarely exotic. In practice, it usually involves connecting FileMaker to accounting software, CRM systems, webshops, shipping services, payment platforms, and internal portals. Integrations with Power BI, Microsoft 365, Google Workspace, or custom web applications also occur regularly.\u003C\u002Fp>\n\u003Cp>An order flow is a good example. A sales order comes in via a webshop or field sales app, is processed in FileMaker for planning or production, and then forwarded to invoicing and shipping. If those steps are manual, each one costs time and errors arise in prices, quantities, or addresses. With an API integration, each system can do what it does best, without employees having to handle the translation.\u003C\u002Fp>\n\u003Cp>Something similar applies to service organisations. Technicians log work orders on mobile devices, FileMaker processes the operational data, and customer or contract information is synchronised with a CRM or financial system. This creates a chain that doesn't necessarily need to be entirely new, but works together much better.\u003C\u002Fp>\n\u003Ch2>The pitfall: integrating without process agreements\u003C\u002Fh2>\n\u003Cp>Building a technical integration is often not the hardest part. The real challenge lies in decisions that need to be made beforehand. Who manages the customer record? What happens with duplicate data? Which fields are mandatory? What may be overwritten and what may not?\u003C\u002Fp>\n\u003Cp>Without those agreements, disputes arise afterwards. It turns out, for example, that sales uses a different status in the CRM than operations uses in FileMaker, or that item codes in the webshop differ from the codes in the back office. An API does not resolve such differences. It only makes them visible faster.\u003C\u002Fp>\n\u003Cp>That is why a meaningful integration usually starts not with technology, but with process analysis. Not endless documentation, but getting a clear picture of where the gains are and where risks arise. For operational teams, that is often a relief: not a large IT project, but a targeted improvement of work that already happens every day.\u003C\u002Fp>\n\u003Ch2>Modernising FileMaker without starting over\u003C\u002Fh2>\n\u003Cp>For many organisations, this is the most important point. An existing FileMaker environment often contains years of business logic, exceptions, screens, and working agreements. You don't simply replace that with standard software without losing functionality, flexibility, or history.\u003C\u002Fp>\n\u003Cp>A FileMaker API integration makes it possible to retain that existing environment while modernising it at the same time. You don't have to choose between leaving everything as it is or replacing everything. It is precisely in that middle ground that the most value often emerges. The current system remains usable for core processes, while new components such as \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Fwebapps-based-on-filemaker\u002F\">customer portals, mobile apps\u003C\u002Fa>, or external platforms connect via APIs.\u003C\u002Fp>\n\u003Cp>That is usually cheaper, faster, and less disruptive than a full migration. Not because old is always good, but because business processes are often more valuable than the technology in which they were originally built. Those who understand that make better decisions about where to invest.\u003C\u002Fp>\n\u003Ch2>What to look out for in your approach\u003C\u002Fh2>\n\u003Cp>A successful integration is rarely the result of writing code alone. Reliability requires choices in architecture, monitoring, and maintenance. If an external system is temporarily unavailable, it must be clear what happens. Is a message retried? Does someone receive a notification? Does the data remain in a queue?\u003C\u002Fp>\n\u003Cp>Version management is also important. APIs change. Vendors add fields, adjust authentication, or remove old endpoints. An integration that works today must therefore remain manageable six or twelve months from now. That requires documentation, logging, and ideally a setup where changes do not immediately block the entire process.\u003C\u002Fp>\n\u003Cp>It is also wise to start small. Rather than designing a complete integration landscape upfront, start with the process where there is the most gain or frustration — for example, order transfer, customer updates, or invoicing status. Once that runs well, expanding is much easier to achieve and justify.\u003C\u002Fp>\n\u003Ch2>Who this is relevant for\u003C\u002Fh2>\n\u003Cp>Companies with an existing FileMaker solution often have more options than they realise. Especially when the system still functionally aligns well with operations, but the surrounding environment has changed. New sales channels, external software, reporting needs, and mobile work processes then call for connection, not necessarily replacement.\u003C\u002Fp>\n\u003Cp>For operations managers, that means less manual work and more control over execution. For \u003Ca href=\"https:\u002F\u002Floggix.com\u002Ffor-who\u002F\">IT managers\u003C\u002Fa>, it means fewer shadow processes and better manageability. For directors or owners, it means that earlier investments retain their value longer, while the organisation can still continue to grow.\u003C\u002Fp>\n\u003Cp>That is also why a partner with both FileMaker and integration expertise often makes the difference. You need someone who not only understands how an API works, but also what an existing FileMaker solution means operationally. Loggix works precisely at that intersection: modernising without unnecessary disruption, and building integrations that hold up in practice.\u003C\u002Fp>\n\u003Ch2>A good integration feels boring\u003C\u002Fh2>\n\u003Cp>That may sound strange, but it is usually a good sign. The best FileMaker API integration attracts no attention because employees no longer need to think about transfer, corrections, or intermediate steps. Data is where it needs to be, processes continue to run, and exceptions are visible before they cause damage.\u003C\u002Fp>\n\u003Cp>That is where the real value lies. Not in technology as an end in itself, but in an operation that becomes calmer, faster, and more reliable. If your current FileMaker system is still important to your business, the question is often not whether to continue with it — but how to connect it intelligently with everything around it.\u003C\u002Fp>\n\u003Cp>Want to know more about whether API integrations can accelerate your processes? Feel free to contact us with no obligation.\u003C\u002Fp>\n","2026-06-27",1782573353000,[73,23],"\u002Fapi\u002Fknowledge\u002Fimage\u002F85\u002F?v=9faadc80168e",{"id":307,"idKnowledge":308,"idDomain":15,"idCluster":15,"slug":309,"title":310,"description":311,"bodyMarkdown":312,"bodyHtml":313,"author":39,"date":314,"createdAt":315,"topics":316,"image":318,"hasDownload":28,"fileName":15,"youtubeId":27},"84","C73EB985-581E-E940-9B96-D96B473D2710","maatwerk-database-software-laten-maken","Having custom database software built?","Having custom database software built? Read when it pays off, what to look out for, and how to modernise legacy systems intelligently.","A database that once worked perfectly can quietly become a drag on operations. Reports require too much manual effort, information is scattered, integrations are missing, and small changes suddenly feel large and risky. That is precisely when the question arises: is having custom database software built the right step, or is that heavier and more expensive than necessary?\n\nFor many organisations, the honest answer is: it depends. Not every need calls for an entirely new system. But once processes genuinely deviate from the standard, multiple departments work with the same data, or an existing environment no longer connects properly with apps, web portals, or external systems, custom software often becomes the most logical choice. Not because custom-built is inherently superior, but because it fits better with how your business actually works.\n\n## When having custom database software built makes sense\n\nOff-the-shelf software works well as long as your processes broadly resemble those of thousands of other companies. That is often fine for accounting, basic CRM functionality, or HR administration. The boundary becomes visible the moment your organisation has built its own ways of working around planning, service, project administration, production, registration, or customer communication.\n\nThe same signals usually appear at that point. Teams use Excel alongside the main process. Staff enter the same data multiple times. There is disagreement about which version of a record is correct. Management information arrives too late or has to be compiled manually. And whenever a customer, supplier, or internal user asks for something new, the software turns out to be barely flexible enough.\n\nAt that stage, having custom database software built is not a technical luxury but a business consideration. You are then investing in a system that supports processes as they actually run, rather than the other way around. This typically results in fewer errors, shorter throughput times, and less dependence on ad-hoc workarounds.\n\n## Not rebuilding everything is often smarter\n\nA common misconception is that custom automatically means everything must be built from scratch. In practice, that is far from always wise. Especially not when an existing database environment already contains a great deal of knowledge, history, and business logic — such as older FileMaker solutions or internally grown registration systems.\n\nOften the value lies not only in the data but also in years of accumulated process knowledge. A full replacement may sound modern, but it also carries risk. You have to redesign processes, retrain users, and accept that details refined over many years need to be reinvented.\n\nA pragmatic approach therefore looks first at what is usable. Sometimes a thorough modernisation of the existing environment is sufficient, supplemented with new screens, better structure, API integrations, or mobile access. Sometimes a phased rebuild is smarter, where critical parts keep running while others are renewed. That is often faster, more affordable, and safer than a hard cutover.\n\n## What good custom software solves in practice\n\nThe essence of a good database solution is not the technology itself, but control over the process. A well-designed custom system ensures that data only needs to be entered once and is then available wherever it is needed. Quotes, orders, schedules, service data, stock, or files no longer become isolated islands but parts of one working chain.\n\nThis has a direct impact on the shop floor. Staff spend less time searching. Errors from double entry decrease. Checks can be partially automated. And management gains faster insight into the current state of affairs. The difference rarely lies in one spectacular feature, but in dozens of small improvements that together save a great deal of time.\n\nThere is something else to consider. Modern custom software does not need to stand alone. It is precisely the combination with external systems that makes the difference. Think of integrations with accounting software, ERP, webshops, customer portals, email services, scanners, planning systems, or BI tools. This transforms a standalone database into a central link within your operation.\n\n## What to look out for when choosing a development partner\n\nWhen you have custom software developed, you are not buying a standard product but a collaboration. Technical knowledge alone is therefore not enough. The right partner must also be able to understand processes, dare to think critically alongside you, and make choices that fit your organisation, budget, and pace.\n\nSo do not only ask how something will be built, but also why. A good development partner will not blindly execute every request. Sometimes a wish is a symptom of an underlying process problem. In that case, it is wiser to simplify the workflow than to add extra screens or exceptions.\n\nExperience with existing environments is important here. Organisations with FileMaker or other legacy databases in particular benefit from a partner who understands modernisation without immediately steering towards tearing down and [starting over](https:\u002F\u002Floggix.com\u002Fblog\u002Ffilemaker-systeem-moderniseren-zonder-risico). That combination of respect for what already exists and knowledge of modern integrations, apps, and AI applications makes a significant difference in practice.\n\nPay attention to manageability as well. A custom system must not only work today but also remain adaptable in two or five years. That requires clear structure, documentation, [consistent choices](https:\u002F\u002Floggix.com\u002Fblog\u002Fnecessity-driven-development-bouw-alleen-software-die-echt-nodig-is), and a development style that other specialists can build on later. Good custom software is not a closed black box.\n\n## The biggest cost item is often not development\n\nWhen making investment decisions, the focus is often primarily on build costs. Understandable, but incomplete. The real costs of poor software usually lie in daily inefficiency: lost time, errors, manual checks, delays in invoicing, dependence on key employees, and missing management information.\n\nThis does not mean custom software is always cheap. It does mean the business case needs to be viewed more broadly. If five employees lose half an hour every day to retyping, correcting, or searching, the costs accumulate faster than many organisations realise. The same applies to errors in planning, [stock management](https:\u002F\u002Floggix.com\u002Fblog\u002Fvoorraad-beheer-systeem), service handling, or customer communication.\n\nA good development partner therefore helps to set priorities. Not everything needs to be in phase one. It is often wiser to first tackle the areas where the greatest operational gain lies, and from there build forward in a controlled manner. This keeps the project manageable and allows the organisation to see results sooner.\n\n## Modernising without disrupting operations\n\nOne of the biggest concerns with software renewal is disruption to daily work. Rightly so. A system can be well conceived in terms of content, but still fail if the transition is too abrupt or if users are not sufficiently brought along.\n\nThat is why a phased approach often works best. First, it is made clear which processes are critical, which data needs to migrate reliably, and which integrations are indispensable. After that, you can renew step by step — for example, first order processing, then reporting, then mobile data entry for field staff or the warehouse.\n\nThis also makes adoption easier. Users do not have to suddenly understand an entirely new landscape. They mainly notice that irritating bottlenecks disappear. That practical gain matters more than a grand technical promise.\n\nFor organisations with existing FileMaker environments, modernisation does not have to mean that the familiar foundation disappears. By extending such an environment with API integrations, web components, mobile applications, or AI-supported features, a trusted system can serve the organisation for years to come. That is often a more realistic route than a costly replacement project full of uncertainties. In such projects, the strength of a specialist like Loggix lies primarily in keeping technology subordinate to business fit.\n\n## How to determine whether your organisation is ready\n\nYou do not need a fully elaborated functional design before starting the conversation. What you do need is clarity on your biggest pain points. Where is time being lost? Which errors keep recurring? What information do you want but cannot get on time? And which systems should actually be talking to each other?\n\nOnce those questions are clear, a workable initial scope usually emerges naturally. It also becomes clear whether you need a limited optimisation, a modernisation of an existing database, or a broader custom solution with apps and integrations.\n\nIt helps to remain pragmatic throughout. Not every process needs to stay unique simply because it evolved that way historically. Sometimes standardising is actually the smart move. But if a process is distinctive to your service delivery, compliance, planning, or internal efficiency, then it is worth having software align with it.\n\nCustom software is at its best when it removes complexity rather than adding it. That is what the entire consideration should revolve around. Not whether custom sounds modern, but whether your people can work better with it, your data becomes more reliable, and your organisation can respond more quickly.\n\nAnyone wanting to have custom database software built would therefore do well to start not from technology, but from operations. Look at the places where your current system costs money, time, or oversight. That is usually also where the most valuable improvement begins — small enough to remain manageable, large enough to make a real difference.","\u003Cp>A database that once worked perfectly can quietly become a drag on operations. Reports require too much manual effort, information is scattered, integrations are missing, and small changes suddenly feel large and risky. That is precisely when the question arises: is having custom database software built the right step, or is that heavier and more expensive than necessary?\u003C\u002Fp>\n\u003Cp>For many organisations, the honest answer is: it depends. Not every need calls for an entirely new system. But once processes genuinely deviate from the standard, multiple departments work with the same data, or an existing environment no longer connects properly with apps, web portals, or external systems, custom software often becomes the most logical choice. Not because custom-built is inherently superior, but because it fits better with how your business actually works.\u003C\u002Fp>\n\u003Ch2>When having custom database software built makes sense\u003C\u002Fh2>\n\u003Cp>Off-the-shelf software works well as long as your processes broadly resemble those of thousands of other companies. That is often fine for accounting, basic CRM functionality, or HR administration. The boundary becomes visible the moment your organisation has built its own ways of working around planning, service, project administration, production, registration, or customer communication.\u003C\u002Fp>\n\u003Cp>The same signals usually appear at that point. Teams use Excel alongside the main process. Staff enter the same data multiple times. There is disagreement about which version of a record is correct. Management information arrives too late or has to be compiled manually. And whenever a customer, supplier, or internal user asks for something new, the software turns out to be barely flexible enough.\u003C\u002Fp>\n\u003Cp>At that stage, having custom database software built is not a technical luxury but a business consideration. You are then investing in a system that supports processes as they actually run, rather than the other way around. This typically results in fewer errors, shorter throughput times, and less dependence on ad-hoc workarounds.\u003C\u002Fp>\n\u003Ch2>Not rebuilding everything is often smarter\u003C\u002Fh2>\n\u003Cp>A common misconception is that custom automatically means everything must be built from scratch. In practice, that is far from always wise. Especially not when an existing database environment already contains a great deal of knowledge, history, and business logic — such as older FileMaker solutions or internally grown registration systems.\u003C\u002Fp>\n\u003Cp>Often the value lies not only in the data but also in years of accumulated process knowledge. A full replacement may sound modern, but it also carries risk. You have to redesign processes, retrain users, and accept that details refined over many years need to be reinvented.\u003C\u002Fp>\n\u003Cp>A pragmatic approach therefore looks first at what is usable. Sometimes a thorough modernisation of the existing environment is sufficient, supplemented with new screens, better structure, API integrations, or mobile access. Sometimes a phased rebuild is smarter, where critical parts keep running while others are renewed. That is often faster, more affordable, and safer than a hard cutover.\u003C\u002Fp>\n\u003Ch2>What good custom software solves in practice\u003C\u002Fh2>\n\u003Cp>The essence of a good database solution is not the technology itself, but control over the process. A well-designed custom system ensures that data only needs to be entered once and is then available wherever it is needed. Quotes, orders, schedules, service data, stock, or files no longer become isolated islands but parts of one working chain.\u003C\u002Fp>\n\u003Cp>This has a direct impact on the shop floor. Staff spend less time searching. Errors from double entry decrease. Checks can be partially automated. And management gains faster insight into the current state of affairs. The difference rarely lies in one spectacular feature, but in dozens of small improvements that together save a great deal of time.\u003C\u002Fp>\n\u003Cp>There is something else to consider. Modern custom software does not need to stand alone. It is precisely the combination with external systems that makes the difference. Think of integrations with accounting software, ERP, webshops, customer portals, email services, scanners, planning systems, or BI tools. This transforms a standalone database into a central link within your operation.\u003C\u002Fp>\n\u003Ch2>What to look out for when choosing a development partner\u003C\u002Fh2>\n\u003Cp>When you have custom software developed, you are not buying a standard product but a collaboration. Technical knowledge alone is therefore not enough. The right partner must also be able to understand processes, dare to think critically alongside you, and make choices that fit your organisation, budget, and pace.\u003C\u002Fp>\n\u003Cp>So do not only ask how something will be built, but also why. A good development partner will not blindly execute every request. Sometimes a wish is a symptom of an underlying process problem. In that case, it is wiser to simplify the workflow than to add extra screens or exceptions.\u003C\u002Fp>\n\u003Cp>Experience with existing environments is important here. Organisations with FileMaker or other legacy databases in particular benefit from a partner who understands modernisation without immediately steering towards tearing down and \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Ffilemaker-systeem-moderniseren-zonder-risico\">starting over\u003C\u002Fa>. That combination of respect for what already exists and knowledge of modern integrations, apps, and AI applications makes a significant difference in practice.\u003C\u002Fp>\n\u003Cp>Pay attention to manageability as well. A custom system must not only work today but also remain adaptable in two or five years. That requires clear structure, documentation, \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Fnecessity-driven-development-bouw-alleen-software-die-echt-nodig-is\">consistent choices\u003C\u002Fa>, and a development style that other specialists can build on later. Good custom software is not a closed black box.\u003C\u002Fp>\n\u003Ch2>The biggest cost item is often not development\u003C\u002Fh2>\n\u003Cp>When making investment decisions, the focus is often primarily on build costs. Understandable, but incomplete. The real costs of poor software usually lie in daily inefficiency: lost time, errors, manual checks, delays in invoicing, dependence on key employees, and missing management information.\u003C\u002Fp>\n\u003Cp>This does not mean custom software is always cheap. It does mean the business case needs to be viewed more broadly. If five employees lose half an hour every day to retyping, correcting, or searching, the costs accumulate faster than many organisations realise. The same applies to errors in planning, \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Fvoorraad-beheer-systeem\">stock management\u003C\u002Fa>, service handling, or customer communication.\u003C\u002Fp>\n\u003Cp>A good development partner therefore helps to set priorities. Not everything needs to be in phase one. It is often wiser to first tackle the areas where the greatest operational gain lies, and from there build forward in a controlled manner. This keeps the project manageable and allows the organisation to see results sooner.\u003C\u002Fp>\n\u003Ch2>Modernising without disrupting operations\u003C\u002Fh2>\n\u003Cp>One of the biggest concerns with software renewal is disruption to daily work. Rightly so. A system can be well conceived in terms of content, but still fail if the transition is too abrupt or if users are not sufficiently brought along.\u003C\u002Fp>\n\u003Cp>That is why a phased approach often works best. First, it is made clear which processes are critical, which data needs to migrate reliably, and which integrations are indispensable. After that, you can renew step by step — for example, first order processing, then reporting, then mobile data entry for field staff or the warehouse.\u003C\u002Fp>\n\u003Cp>This also makes adoption easier. Users do not have to suddenly understand an entirely new landscape. They mainly notice that irritating bottlenecks disappear. That practical gain matters more than a grand technical promise.\u003C\u002Fp>\n\u003Cp>For organisations with existing FileMaker environments, modernisation does not have to mean that the familiar foundation disappears. By extending such an environment with API integrations, web components, mobile applications, or AI-supported features, a trusted system can serve the organisation for years to come. That is often a more realistic route than a costly replacement project full of uncertainties. In such projects, the strength of a specialist like Loggix lies primarily in keeping technology subordinate to business fit.\u003C\u002Fp>\n\u003Ch2>How to determine whether your organisation is ready\u003C\u002Fh2>\n\u003Cp>You do not need a fully elaborated functional design before starting the conversation. What you do need is clarity on your biggest pain points. Where is time being lost? Which errors keep recurring? What information do you want but cannot get on time? And which systems should actually be talking to each other?\u003C\u002Fp>\n\u003Cp>Once those questions are clear, a workable initial scope usually emerges naturally. It also becomes clear whether you need a limited optimisation, a modernisation of an existing database, or a broader custom solution with apps and integrations.\u003C\u002Fp>\n\u003Cp>It helps to remain pragmatic throughout. Not every process needs to stay unique simply because it evolved that way historically. Sometimes standardising is actually the smart move. But if a process is distinctive to your service delivery, compliance, planning, or internal efficiency, then it is worth having software align with it.\u003C\u002Fp>\n\u003Cp>Custom software is at its best when it removes complexity rather than adding it. That is what the entire consideration should revolve around. Not whether custom sounds modern, but whether your people can work better with it, your data becomes more reliable, and your organisation can respond more quickly.\u003C\u002Fp>\n\u003Cp>Anyone wanting to have custom database software built would therefore do well to start not from technology, but from operations. Look at the places where your current system costs money, time, or oversight. That is usually also where the most valuable improvement begins — small enough to remain manageable, large enough to make a real difference.\u003C\u002Fp>\n","2026-06-26",1782508852000,[317],"Socials","\u002Fapi\u002Fknowledge\u002Fimage\u002F84\u002F?v=b177ae588489",{"id":320,"idKnowledge":321,"idDomain":15,"idCluster":15,"slug":322,"title":323,"description":324,"bodyMarkdown":325,"bodyHtml":326,"author":327,"date":314,"createdAt":328,"topics":329,"image":332,"hasDownload":28,"fileName":15,"youtubeId":27},"83","C84F087B-3308-4B45-A3B9-4EC9AD1DB001","remotion-a-tool-that-builds-videos-using-code-instead-of-a-timeline","Remotion — A Tool That Builds Videos Using Code Instead of a Timeline","Remotion is a framework that lets people create real video files by writing code rather than using a traditional drag-and-drop video editor. It's especially useful for creating many similar videos automatically, such as personalized clips or data-driven animations.","What this is about\nRemotion is a tool for creating videos using React, a popular web programming framework normally used to build websites and apps. Instead of dragging clips around on a timeline like in a traditional video editor (such as Adobe After Effects or Premiere Pro), a person writes code that describes what should appear on screen at each moment, and Remotion turns that code into a real video file (like an MP4).\nHow it's different from a normal video editor\nIn a typical editor, each frame of an animation is usually placed and adjusted by hand. With Remotion:\n\nA video is built the same way a website is built — using reusable components, variables, and logic.\nThe same \"template\" can automatically generate many different versions of a video just by changing the data fed into it — for example, generating hundreds of personalized videos with different names, numbers, or images from a single design.\nBecause it's based on code, video projects can be tracked and managed using the same version-control tools developers already use for software (like Git), which is not normally possible with traditional video editing files.\n\nWhat it's good at\n\nData visualizations — charts, graphs, and dashboards that animate as the underlying numbers change.\nPersonalized videos at scale — things like a \"yearly recap\" video, where the layout stays the same but the content is different for each person.\nTemplated marketing or product videos — generating many versions of the same style of video automatically from a spreadsheet or database, instead of editing each one by hand.\n\nIt is generally not the right tool for vlog-style content, reaction videos, or anything that relies heavily on real filmed footage — it works best for animated, structured, or data-driven content.\nA notable recent development: AI can now write the code for you\nAs of January 2026, Remotion introduced a way for AI coding assistants (such as Claude Code) to write the necessary code automatically, based on a plain-English description of the video someone wants. Instead of writing the React code by hand, a person can describe what they want — for example, \"create a 10-second title animation that says Welcome\" — and the AI writes the corresponding code, which Remotion then renders into a video. This has made the tool meaningfully more approachable, though it still works through code under the hood rather than a visual drag-and-drop interface.\nThings to know before using it\n\nIt does require at least some comfort with code, or an AI coding assistant to help write that code — it is not a simple drag-and-drop tool for non-technical users.\nRemotion is free to use for individuals and for small companies (commonly cited as 3 or fewer employees); larger companies are required to purchase a commercial license.\nIt currently has some technical limitations, such as not supporting high dynamic range (HDR) video output.\n\nWhy it matters\nRemotion represents a different way of thinking about video production: instead of treating each video as a one-off manual editing job, it treats video as something that can be automated, templated, and produced at scale — similar to how software is built. For any business that needs to produce many similar videos (such as personalized customer videos, recurring data reports turned into video, or templated social media content), this approach can save a large amount of repetitive manual work, especially now that AI can help write the underlying code.","\u003Cp>What this is about\nRemotion is a tool for creating videos using React, a popular web programming framework normally used to build websites and apps. Instead of dragging clips around on a timeline like in a traditional video editor (such as Adobe After Effects or Premiere Pro), a person writes code that describes what should appear on screen at each moment, and Remotion turns that code into a real video file (like an MP4).\nHow it's different from a normal video editor\nIn a typical editor, each frame of an animation is usually placed and adjusted by hand. With Remotion:\u003C\u002Fp>\n\u003Cp>A video is built the same way a website is built — using reusable components, variables, and logic.\nThe same "template" can automatically generate many different versions of a video just by changing the data fed into it — for example, generating hundreds of personalized videos with different names, numbers, or images from a single design.\nBecause it's based on code, video projects can be tracked and managed using the same version-control tools developers already use for software (like Git), which is not normally possible with traditional video editing files.\u003C\u002Fp>\n\u003Cp>What it's good at\u003C\u002Fp>\n\u003Cp>Data visualizations — charts, graphs, and dashboards that animate as the underlying numbers change.\nPersonalized videos at scale — things like a "yearly recap" video, where the layout stays the same but the content is different for each person.\nTemplated marketing or product videos — generating many versions of the same style of video automatically from a spreadsheet or database, instead of editing each one by hand.\u003C\u002Fp>\n\u003Cp>It is generally not the right tool for vlog-style content, reaction videos, or anything that relies heavily on real filmed footage — it works best for animated, structured, or data-driven content.\nA notable recent development: AI can now write the code for you\nAs of January 2026, Remotion introduced a way for AI coding assistants (such as Claude Code) to write the necessary code automatically, based on a plain-English description of the video someone wants. Instead of writing the React code by hand, a person can describe what they want — for example, "create a 10-second title animation that says Welcome" — and the AI writes the corresponding code, which Remotion then renders into a video. This has made the tool meaningfully more approachable, though it still works through code under the hood rather than a visual drag-and-drop interface.\nThings to know before using it\u003C\u002Fp>\n\u003Cp>It does require at least some comfort with code, or an AI coding assistant to help write that code — it is not a simple drag-and-drop tool for non-technical users.\nRemotion is free to use for individuals and for small companies (commonly cited as 3 or fewer employees); larger companies are required to purchase a commercial license.\nIt currently has some technical limitations, such as not supporting high dynamic range (HDR) video output.\u003C\u002Fp>\n\u003Cp>Why it matters\nRemotion represents a different way of thinking about video production: instead of treating each video as a one-off manual editing job, it treats video as something that can be automated, templated, and produced at scale — similar to how software is built. For any business that needs to produce many similar videos (such as personalized customer videos, recurring data reports turned into video, or templated social media content), this approach can save a large amount of repetitive manual work, especially now that AI can help write the underlying code.\u003C\u002Fp>\n","Pratiksha",1782461057000,[86,330,331],"Motion Graphics","Video","\u002Fapi\u002Fknowledge\u002Fimage\u002F83\u002F?v=47d90af7b465",{"id":334,"idKnowledge":335,"idDomain":15,"idCluster":15,"slug":336,"title":337,"description":338,"bodyMarkdown":339,"bodyHtml":340,"author":341,"date":314,"createdAt":342,"topics":343,"image":345,"hasDownload":28,"fileName":15,"youtubeId":27},"82","BCB80984-E20B-C64C-BCFD-9C015D027875","how-to-use-agentic-fm-to-generate-paste-filemaker-scripts-with-ai","How to Use agentic-fm to Generate & Paste FileMaker Scripts with AI","Learn how agentic-fm lets FileMaker developers generate, refine, and paste scripts directly into Claris FileMaker using AI — saving hours of manual work.","**agentic-fm lets you describe what you want in plain English and get working FileMaker scripts pasted directly into your solution — no copy-paste gymnastics required.** Here is everything you need to know to get started and why this tool is changing how FileMaker developers work.\n\n## What Is agentic-fm?\n\nagentic-fm is an open-source AI agent built specifically for Claris FileMaker developers. It connects a large language model (LLM) — such as OpenAI's GPT-4o — to your FileMaker environment via the Data API and MCP (Model Context Protocol). The result: an AI assistant that does not just *suggest* code, it can **read your schema, write scripts, and inject them directly into your FileMaker file**.\n\nIt is not a generic coding assistant. It understands FileMaker-specific concepts: script steps, calculations, ExecuteSQL, relationships, and layouts. That specificity is what makes it genuinely useful.\n\n## Why Does It Matter for FileMaker Developers?\n\n- **Speed:** Generating a looping script, a complex Let() calculation, or an API integration routine that used to take 30–60 minutes can now take under 5 minutes.\n- **Lower barrier for junior developers:** Less experienced team members can describe what they need and get a working starting point immediately.\n- **Schema-aware output:** Because the agent can read your actual table and field names via the Data API, the generated code references *your* real structure — not generic placeholders.\n- **Iterative refinement:** You can tell the agent \"now add error handling\" or \"make this work for portal rows\" and it adjusts in context.\n- **Open source:** No vendor lock-in. You control the model, the data, and the workflow.\n\n## How AI Is Changing FileMaker Custom Development\n\nFileMaker has always been a rapid-development platform, but the scripting and calculation layer still required deep expertise. AI changes that equation in three ways:\n\n1. **Natural language → working logic.** Developers can prototype logic verbally before writing a single script step.\n2. **Documentation on demand.** AI can explain what an existing script does, making onboarding and code review faster.\n3. **Bridging FileMaker and modern APIs.** Tools like agentic-fm make it easier to connect FileMaker solutions to REST APIs, webhooks, and AI services — closing the gap between legacy data and modern infrastructure.\n\nagentic-fm is the clearest example yet of this shift: it is not just AI *alongside* FileMaker, it is AI *inside* the development loop.\n\n## What You Need Before You Start\n\n- Claris FileMaker Pro 19+ (or FileMaker Server with Data API enabled)\n- An OpenAI API key (GPT-4o recommended) or a compatible LLM\n- Node.js installed on your machine\n- Basic familiarity with running terminal\u002Fcommand-line commands\n- A FileMaker file with the Data API privilege set enabled for your account\n\n## How to Set Up agentic-fm: Step by Step\n\n### 1. Clone the Repository\n\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002Fagentic-fm\u002Fagentic-fm.git\ncd agentic-fm\nnpm install\n```\n\n### 2. Configure Your Environment\n\nCreate a `.env` file in the project root and fill in your credentials:\n\n```\nFILEMAKER_HOST=https:\u002F\u002Fyour-filemaker-server.com\nFILEMAKER_DATABASE=YourFileName\nFILEMAKER_USERNAME=your_account\nFILEMAKER_PASSWORD=your_password\nOPENAI_API_KEY=sk-...\n```\n\n> **Tip:** Use a dedicated FileMaker account with only the permissions the agent needs. Principle of least privilege applies here too.\n\n### 3. Start the Agent\n\n```bash\nnpm start\n```\n\nThe agent will connect to your FileMaker Data API, read your schema (tables, fields, layouts), and present a chat interface.\n\n### 4. Describe What You Want\n\nType your request in plain English. Examples:\n\n- *\"Write a script that loops through all records in the Orders table and sets Status to 'Overdue' where DueDate is more than 7 days in the past.\"*\n- *\"Create a Let() calculation that returns the full name from FirstName and LastName fields, handling empty values gracefully.\"*\n- *\"Build a script that calls the Stripe API to create a customer and stores the returned customer ID in the ContactID field.\"*\n\n### 5. Review the Generated Script\n\nThe agent returns the script in FileMaker Script Workspace-compatible format. Review it — check the logic, field references, and any hardcoded values — before proceeding.\n\n### 6. Paste Directly into FileMaker\n\nagentic-fm can push scripts directly into your FileMaker file via the Data API and MCP integration, depending on your setup. Alternatively, copy the output and paste it into Script Workspace manually. Either way, the heavy lifting is already done.\n\n### 7. Test and Iterate\n\nRun the script in a test environment first. If the output needs adjustment, ask the agent to refine it:\n\n- *\"Add error handling for when the API call fails.\"*\n- *\"Make this script work when triggered from a portal row instead of the main layout.\"*\n\nThe agent maintains context within the session, so follow-up instructions are understood correctly.\n\n## Practical Tips for Better Results\n\n- **Be specific about field names.** The more precise your prompt, the closer the output will be to production-ready.\n- **Mention your FileMaker version.** Some script steps behave differently across versions.\n- **Ask for comments in the script.** Prompt with *\"add inline comments explaining each step\"* — great for documentation and team handoffs.\n- **Break complex workflows into smaller scripts.** Ask the agent to build modular sub-scripts rather than one giant script. Easier to test and maintain.\n- **Always review before deploying to production.** AI output is a strong starting point, not a rubber stamp.\n\n## What agentic-fm Does Not Replace\n\nagentic-fm accelerates scripting — it does not replace architectural thinking. You still need a FileMaker developer to:\n\n- Design the data model and relationships\n- Make decisions about UX and layout structure\n- Handle complex business logic that requires deep domain knowledge\n- Perform QA and performance testing\n\nThink of it as a very fast, very knowledgeable junior developer who writes first drafts extremely well.\n\n## The Bigger Picture: AI Inside FileMaker Development\n\nTools like agentic-fm signal a broader shift. The question is no longer *\"can AI help with FileMaker?\"* — it clearly can. The question is *how to integrate AI into a FileMaker workflow without sacrificing reliability or data integrity*.\n\nAt Loggix, we build custom FileMaker solutions and ERP integrations where accuracy and stability are non-negotiable. We see agentic-fm — and the MCP + AI approach it represents — as a meaningful accelerator for development velocity, especially for repetitive scripting tasks and API connector work.\n\nIf you are a FileMaker developer, try agentic-fm on a non-production file today. The setup takes under 15 minutes and the productivity impact is immediate.\n\n---\n\n*Building a FileMaker solution or looking to connect your FileMaker data with modern APIs and AI? [Talk to the Loggix team.](https:\u002F\u002Floggix.nl)*","\u003Cp>\u003Cstrong>agentic-fm lets you describe what you want in plain English and get working FileMaker scripts pasted directly into your solution — no copy-paste gymnastics required.\u003C\u002Fstrong> Here is everything you need to know to get started and why this tool is changing how FileMaker developers work.\u003C\u002Fp>\n\u003Ch2>What Is agentic-fm?\u003C\u002Fh2>\n\u003Cp>agentic-fm is an open-source AI agent built specifically for Claris FileMaker developers. It connects a large language model (LLM) — such as OpenAI's GPT-4o — to your FileMaker environment via the Data API and MCP (Model Context Protocol). The result: an AI assistant that does not just \u003Cem>suggest\u003C\u002Fem> code, it can \u003Cstrong>read your schema, write scripts, and inject them directly into your FileMaker file\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>It is not a generic coding assistant. It understands FileMaker-specific concepts: script steps, calculations, ExecuteSQL, relationships, and layouts. That specificity is what makes it genuinely useful.\u003C\u002Fp>\n\u003Ch2>Why Does It Matter for FileMaker Developers?\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Speed:\u003C\u002Fstrong> Generating a looping script, a complex Let() calculation, or an API integration routine that used to take 30–60 minutes can now take under 5 minutes.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Lower barrier for junior developers:\u003C\u002Fstrong> Less experienced team members can describe what they need and get a working starting point immediately.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Schema-aware output:\u003C\u002Fstrong> Because the agent can read your actual table and field names via the Data API, the generated code references \u003Cem>your\u003C\u002Fem> real structure — not generic placeholders.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Iterative refinement:\u003C\u002Fstrong> You can tell the agent "now add error handling" or "make this work for portal rows" and it adjusts in context.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Open source:\u003C\u002Fstrong> No vendor lock-in. You control the model, the data, and the workflow.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>How AI Is Changing FileMaker Custom Development\u003C\u002Fh2>\n\u003Cp>FileMaker has always been a rapid-development platform, but the scripting and calculation layer still required deep expertise. AI changes that equation in three ways:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Natural language → working logic.\u003C\u002Fstrong> Developers can prototype logic verbally before writing a single script step.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Documentation on demand.\u003C\u002Fstrong> AI can explain what an existing script does, making onboarding and code review faster.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Bridging FileMaker and modern APIs.\u003C\u002Fstrong> Tools like agentic-fm make it easier to connect FileMaker solutions to REST APIs, webhooks, and AI services — closing the gap between legacy data and modern infrastructure.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>agentic-fm is the clearest example yet of this shift: it is not just AI \u003Cem>alongside\u003C\u002Fem> FileMaker, it is AI \u003Cem>inside\u003C\u002Fem> the development loop.\u003C\u002Fp>\n\u003Ch2>What You Need Before You Start\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Claris FileMaker Pro 19+ (or FileMaker Server with Data API enabled)\u003C\u002Fli>\n\u003Cli>An OpenAI API key (GPT-4o recommended) or a compatible LLM\u003C\u002Fli>\n\u003Cli>Node.js installed on your machine\u003C\u002Fli>\n\u003Cli>Basic familiarity with running terminal\u002Fcommand-line commands\u003C\u002Fli>\n\u003Cli>A FileMaker file with the Data API privilege set enabled for your account\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>How to Set Up agentic-fm: Step by Step\u003C\u002Fh2>\n\u003Ch3>1. Clone the Repository\u003C\u002Fh3>\n\u003Cpre>\u003Ccode class=\"language-bash\">git clone https:\u002F\u002Fgithub.com\u002Fagentic-fm\u002Fagentic-fm.git\ncd agentic-fm\nnpm install\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>2. Configure Your Environment\u003C\u002Fh3>\n\u003Cp>Create a \u003Ccode>.env\u003C\u002Fcode> file in the project root and fill in your credentials:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>FILEMAKER_HOST=https:\u002F\u002Fyour-filemaker-server.com\nFILEMAKER_DATABASE=YourFileName\nFILEMAKER_USERNAME=your_account\nFILEMAKER_PASSWORD=your_password\nOPENAI_API_KEY=sk-...\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cblockquote>\n\u003Cp>\u003Cstrong>Tip:\u003C\u002Fstrong> Use a dedicated FileMaker account with only the permissions the agent needs. Principle of least privilege applies here too.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch3>3. Start the Agent\u003C\u002Fh3>\n\u003Cpre>\u003Ccode class=\"language-bash\">npm start\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The agent will connect to your FileMaker Data API, read your schema (tables, fields, layouts), and present a chat interface.\u003C\u002Fp>\n\u003Ch3>4. Describe What You Want\u003C\u002Fh3>\n\u003Cp>Type your request in plain English. Examples:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cem>"Write a script that loops through all records in the Orders table and sets Status to 'Overdue' where DueDate is more than 7 days in the past."\u003C\u002Fem>\u003C\u002Fli>\n\u003Cli>\u003Cem>"Create a Let() calculation that returns the full name from FirstName and LastName fields, handling empty values gracefully."\u003C\u002Fem>\u003C\u002Fli>\n\u003Cli>\u003Cem>"Build a script that calls the Stripe API to create a customer and stores the returned customer ID in the ContactID field."\u003C\u002Fem>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>5. Review the Generated Script\u003C\u002Fh3>\n\u003Cp>The agent returns the script in FileMaker Script Workspace-compatible format. Review it — check the logic, field references, and any hardcoded values — before proceeding.\u003C\u002Fp>\n\u003Ch3>6. Paste Directly into FileMaker\u003C\u002Fh3>\n\u003Cp>agentic-fm can push scripts directly into your FileMaker file via the Data API and MCP integration, depending on your setup. Alternatively, copy the output and paste it into Script Workspace manually. Either way, the heavy lifting is already done.\u003C\u002Fp>\n\u003Ch3>7. Test and Iterate\u003C\u002Fh3>\n\u003Cp>Run the script in a test environment first. If the output needs adjustment, ask the agent to refine it:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cem>"Add error handling for when the API call fails."\u003C\u002Fem>\u003C\u002Fli>\n\u003Cli>\u003Cem>"Make this script work when triggered from a portal row instead of the main layout."\u003C\u002Fem>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The agent maintains context within the session, so follow-up instructions are understood correctly.\u003C\u002Fp>\n\u003Ch2>Practical Tips for Better Results\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Be specific about field names.\u003C\u002Fstrong> The more precise your prompt, the closer the output will be to production-ready.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Mention your FileMaker version.\u003C\u002Fstrong> Some script steps behave differently across versions.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Ask for comments in the script.\u003C\u002Fstrong> Prompt with \u003Cem>"add inline comments explaining each step"\u003C\u002Fem> — great for documentation and team handoffs.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Break complex workflows into smaller scripts.\u003C\u002Fstrong> Ask the agent to build modular sub-scripts rather than one giant script. Easier to test and maintain.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Always review before deploying to production.\u003C\u002Fstrong> AI output is a strong starting point, not a rubber stamp.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>What agentic-fm Does Not Replace\u003C\u002Fh2>\n\u003Cp>agentic-fm accelerates scripting — it does not replace architectural thinking. You still need a FileMaker developer to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Design the data model and relationships\u003C\u002Fli>\n\u003Cli>Make decisions about UX and layout structure\u003C\u002Fli>\n\u003Cli>Handle complex business logic that requires deep domain knowledge\u003C\u002Fli>\n\u003Cli>Perform QA and performance testing\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Think of it as a very fast, very knowledgeable junior developer who writes first drafts extremely well.\u003C\u002Fp>\n\u003Ch2>The Bigger Picture: AI Inside FileMaker Development\u003C\u002Fh2>\n\u003Cp>Tools like agentic-fm signal a broader shift. The question is no longer \u003Cem>"can AI help with FileMaker?"\u003C\u002Fem> — it clearly can. The question is \u003Cem>how to integrate AI into a FileMaker workflow without sacrificing reliability or data integrity\u003C\u002Fem>.\u003C\u002Fp>\n\u003Cp>At Loggix, we build custom FileMaker solutions and ERP integrations where accuracy and stability are non-negotiable. We see agentic-fm — and the MCP + AI approach it represents — as a meaningful accelerator for development velocity, especially for repetitive scripting tasks and API connector work.\u003C\u002Fp>\n\u003Cp>If you are a FileMaker developer, try agentic-fm on a non-production file today. The setup takes under 15 minutes and the productivity impact is immediate.\u003C\u002Fp>\n\u003Chr>\n\u003Cp>\u003Cem>Building a FileMaker solution or looking to connect your FileMaker data with modern APIs and AI? \u003Ca href=\"https:\u002F\u002Floggix.nl\">Talk to the Loggix team.\u003C\u002Fa>\u003C\u002Fem>\u003C\u002Fp>\n","Shantanu",1782457366000,[86,23,44,73,344],"MCP","\u002Fapi\u002Fknowledge\u002Fimage\u002F82\u002F?v=d10e0d9c6e1a",{"id":347,"idKnowledge":348,"idDomain":15,"idCluster":15,"slug":349,"title":350,"description":351,"bodyMarkdown":352,"bodyHtml":353,"author":354,"date":314,"createdAt":355,"topics":356,"image":357,"hasDownload":28,"fileName":15,"youtubeId":27},"81","35D1B267-BD8E-B545-850A-1A0A35CB8050","filemaker-2026-ai-gets-serious-llms-gemini-support-and-agentic-development-on-the-horizon","FileMaker 2026: AI Gets Serious – LLMs, Gemini Support, and Agentic Development on the Horizon","Claris FileMaker 2026 (v26) brings major AI upgrades including Google Gemini support, smarter schema annotations for LLMs, and a roadmap toward fully agentic FileMaker development.","## FileMaker 2026: AI Gets Serious\n\nClaris officially released **FileMaker 2026** (internal version 26) in June 2026, \nand it's the most AI-forward release in the platform's 40-year history.\n\n### What's New for AI & LLMs\n\n**Google Gemini support**  \nFileMaker now supports Google Gemini alongside existing providers — OpenAI, Anthropic (Claude), \nand Cohere. Gemini also allows developers to pass container-field images directly into prompts \nfor visual analysis workflows.\n\n**Field & Table Annotations**  \nA long-standing frustration has been solved: you can now add a dedicated **field annotation** \nvia the Database Manager's Advanced options. This gives LLMs proper context about what a field \n*means* — not just what it's named. The new `FieldAnnotation()` and `BaseTableComment()` \ncalculation functions make this metadata accessible at runtime too.\n\n**Faster JSON & API calls**  \nWhen `Insert from URL` retrieves a JSON response, it is now automatically parsed and cached — \nmaking all subsequent JSON operations dramatically faster. A major win for solutions that \nmake heavy use of REST APIs and AI calls.\n\n**AI Model Server improvements**  \nThe AI Model Server now has its own version number and can be upgraded independently of \nFileMaker Server. Multiple Python processes mean embedding and text-generation workloads \nrun concurrently rather than queuing.\n\n**Timeout control**  \nText generation steps now accept a `CURLOPT_TIMEOUT` parameter in seconds — so if a \nlocal\u002Fopen-source model server stalls, your scripts no longer hang indefinitely.\n\n---\n\n### What's Coming: Agentic FileMaker Development\n\nThe bigger news may be what's *next*. Claris CEO Ryan McCann has outlined a vision for \n**agentic coding capabilities** — where tools like Claude Code, Cursor, and Codex can read \nyour FileMaker schema and automatically generate native scripts, tables, fields, layouts, \nand calculations.\n\nDeveloper previews are expected **later this summer (2026)**.\n\n---\n\n### Why This Matters for Your FileMaker Solutions\n\n- You can now connect FileMaker to **multiple AI providers** and choose based on cost, \n  capability, or data residency requirements.\n- **Schema annotations** make natural language queries and semantic search significantly \n  more accurate — without restructuring your database.\n- **Local LLM support** remains fully intact: run models like Llama 3 on-premise, \n  keeping sensitive data entirely within your own infrastructure.\n\nFileMaker 2026 treats AI as a **foundational platform layer**, not an add-on — \nand the agentic capabilities coming this summer could fundamentally change how \nFileMaker solutions are built.","\u003Ch2>FileMaker 2026: AI Gets Serious\u003C\u002Fh2>\n\u003Cp>Claris officially released \u003Cstrong>FileMaker 2026\u003C\u002Fstrong> (internal version 26) in June 2026, \nand it's the most AI-forward release in the platform's 40-year history.\u003C\u002Fp>\n\u003Ch3>What's New for AI & LLMs\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Google Gemini support\u003C\u002Fstrong>\u003Cbr>FileMaker now supports Google Gemini alongside existing providers — OpenAI, Anthropic (Claude), \nand Cohere. Gemini also allows developers to pass container-field images directly into prompts \nfor visual analysis workflows.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Field & Table Annotations\u003C\u002Fstrong>\u003Cbr>A long-standing frustration has been solved: you can now add a dedicated \u003Cstrong>field annotation\u003C\u002Fstrong> \nvia the Database Manager's Advanced options. This gives LLMs proper context about what a field \n\u003Cem>means\u003C\u002Fem> — not just what it's named. The new \u003Ccode>FieldAnnotation()\u003C\u002Fcode> and \u003Ccode>BaseTableComment()\u003C\u002Fcode> \ncalculation functions make this metadata accessible at runtime too.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Faster JSON & API calls\u003C\u002Fstrong>\u003Cbr>When \u003Ccode>Insert from URL\u003C\u002Fcode> retrieves a JSON response, it is now automatically parsed and cached — \nmaking all subsequent JSON operations dramatically faster. A major win for solutions that \nmake heavy use of REST APIs and AI calls.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>AI Model Server improvements\u003C\u002Fstrong>\u003Cbr>The AI Model Server now has its own version number and can be upgraded independently of \nFileMaker Server. Multiple Python processes mean embedding and text-generation workloads \nrun concurrently rather than queuing.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Timeout control\u003C\u002Fstrong>\u003Cbr>Text generation steps now accept a \u003Ccode>CURLOPT_TIMEOUT\u003C\u002Fcode> parameter in seconds — so if a \nlocal\u002Fopen-source model server stalls, your scripts no longer hang indefinitely.\u003C\u002Fp>\n\u003Chr>\n\u003Ch3>What's Coming: Agentic FileMaker Development\u003C\u002Fh3>\n\u003Cp>The bigger news may be what's \u003Cem>next\u003C\u002Fem>. Claris CEO Ryan McCann has outlined a vision for \n\u003Cstrong>agentic coding capabilities\u003C\u002Fstrong> — where tools like Claude Code, Cursor, and Codex can read \nyour FileMaker schema and automatically generate native scripts, tables, fields, layouts, \nand calculations.\u003C\u002Fp>\n\u003Cp>Developer previews are expected \u003Cstrong>later this summer (2026)\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Chr>\n\u003Ch3>Why This Matters for Your FileMaker Solutions\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>You can now connect FileMaker to \u003Cstrong>multiple AI providers\u003C\u002Fstrong> and choose based on cost, \ncapability, or data residency requirements.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Schema annotations\u003C\u002Fstrong> make natural language queries and semantic search significantly \nmore accurate — without restructuring your database.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Local LLM support\u003C\u002Fstrong> remains fully intact: run models like Llama 3 on-premise, \nkeeping sensitive data entirely within your own infrastructure.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>FileMaker 2026 treats AI as a \u003Cstrong>foundational platform layer\u003C\u002Fstrong>, not an add-on — \nand the agentic capabilities coming this summer could fundamentally change how \nFileMaker solutions are built.\u003C\u002Fp>\n","Shubham",1782453679000,[86,23],"\u002Fapi\u002Fknowledge\u002Fimage\u002F81\u002F?v=7a51f6e7d9bf",{"id":359,"idKnowledge":360,"idDomain":15,"idCluster":15,"slug":361,"title":362,"description":363,"bodyMarkdown":364,"bodyHtml":365,"author":39,"date":366,"createdAt":367,"topics":368,"image":369,"hasDownload":28,"fileName":15,"youtubeId":27},"80","59244153-68D5-EC4D-B0B2-F8C20F53F614","filemaker-systeem-moderniseren-zonder-risico","Modernizing a FileMaker system without risk","Modernizing a FileMaker system doesn't have to be a risky undertaking. Here's how to practically address outdated processes, integrations, and growth.","Modernizing a FileMaker system rarely starts with technology. It usually starts with frustration on the work floor. Orders being entered twice, reports updated manually, employees working with exports because integrations are missing, or a solution that once worked fine but now has too many exceptions. That's when the question arises: do we rebuild from scratch, or can we develop more intelligently?\n\nFor many organizations, this isn't a theoretical choice. The system has been running in operations for years. It holds knowledge, business rules, and often processes that haven't been properly documented anywhere else. That's precisely why modernizing is usually wiser than replacing. Not because old is inherently good, but because the value of an existing FileMaker system is often greater than it appears at first glance.\n\n## When modernizing a FileMaker system makes sense\n\nAn outdated system is not automatically a bad system. The real question is whether the current landscape is still helping your organization or holding it back. That difference typically becomes visible on three points: maintenance, usage, and alignment with other software.\n\nIn terms of maintenance, you see it in small adjustments that suddenly take a lot of time. Nobody quite knows how certain scripts work anymore, documentation is missing, and every change feels like a risk. In terms of usage, you notice that employees start working around the system. They enter data later, use Excel as an intermediate layer, or no longer fully trust reports. And when it comes to integrations, the pain often surfaces fastest. The FileMaker system still works, but doesn't connect well with accounting, e-commerce, planning, CRM, or mobile applications.\n\nThose are signals that modernizing a FileMaker system is worthwhile. Not to have something new, but to regain control over processes, data quality, and scalability.\n\n## Modernizing is not an all-or-nothing decision\n\nA common mistake is that organizations think in extremes. Either everything stays as it is, or a completely new platform must come. In practice, the best route usually lies somewhere in between.\n\nSometimes the core of the system is still fine, but the user interface is outdated and scripts have become too complex. Sometimes the database works well, but modern API integrations are missing. And sometimes the structure under the hood has become messy, while the functional logic remains valuable. A good modernization process therefore doesn't start with rebuilding, but with assessing what needs to be preserved, cleaned up, replaced, or extended.\n\nThis is also financially relevant. A full migration sometimes sounds attractive on paper, but often brings more risk, more project time, and more organizational burden than anticipated. Especially when there are many custom processes in the current system.\n\n### What you typically want to preserve\n\nExisting FileMaker environments often contain years of practical knowledge. Think of calculation rules, exceptions in workflows, permission structures, statuses, validations, and reporting logic. Throwing all of that away means you first have to rediscover it before it can be rebuilt.\n\nThat's why preserving business logic is often a strong starting point. Not everything needs to remain technically the same, but the functional value deserves to be taken seriously.\n\n### What often needs to be addressed\n\nThere are also components that lend themselves well to renewal. Outdated layouts, inefficient scripts, manual import and export steps, local workarounds, and missing integrations are often the first candidates. Performance issues, limited mobile usability, and a lack of logging or manageability also demand attention.\n\nModernizing then means: leaving the strong parts in place, and selectively improving the weak parts.\n\n## The biggest gains are often found outside the database itself\n\nWhen modernizing, many organizations focus primarily on screens and functionality. That's understandable, but the real gains are often in the connection to the rest of the landscape.\n\nA FileMaker solution that is linked to [accounting software](https:\u002F\u002Floggix.com\u002Fblog\u002Fseamless-payment-integration-between-filemaker-and-mollie-payment-provider), webshops, portals, planning systems, or document services becomes immediately more valuable. Data needs to be manually transferred less often, errors decrease, and process lead times drop. That effect is usually greater than a prettier screen alone.\n\nThink of automatic synchronization of customer and order data, invoice creation, inventory updates, digital document flows, or notifications to mobile apps. That's precisely where an internal system transforms from a standalone database into a working part of the business operation.\n\nFor organizations with multiple tools, that is often the difference between improvising daily and working structurally efficiently.\n\n## Modernizing a FileMaker system in phases usually works better\n\nA pragmatic approach is almost always more effective than one big leap. Especially when the current system is business-critical. You want to improve without bringing operations to a standstill.\n\nThe first phase is usually a technical and functional analysis. Not just what the system does, but also how it is used, where the dependencies lie, and which bottlenecks have real impact. This is followed by prioritization. Which improvement delivers quick results? What reduces risk? And which components need to be in order before further expansion is possible?\n\nOften a phasing emerges such as: clean up, structure, connect, and expand. Stability first, then renewal. That sounds less spectacular than a complete rebuild, but it works better in practice. The organization stays in control, users can get used to changes, and investments remain more predictable.\n\n### Stabilize first, then accelerate\n\nIf the foundation is technically messy, there is little point in immediately adding new features. You'd be building on uncertainty. Stabilizing means, for example, restructuring scripts, making naming consistent, reviewing data models, improving permissions, and making dependencies transparent.\n\nOnly then does room open up for acceleration. That's when you can think about API integrations, web portals, mobile data entry, or [automated workflows](https:\u002F\u002Floggix.com\u002Fblog\u002Fusing-n8n-as-an-automation-agent-for-filemaker-solutions).\n\n## When rebuilding is still the better choice\n\nModernizing is often wise, but not always. Sometimes an existing system has become so fragmented that further development becomes more expensive and riskier than a controlled rebuild. For example, when years of unstructured modifications have been made, when performance remains structurally poor, or when the architecture blocks new requirements.\n\nEven then, you don't have to throw everything away. A rebuild can still be based on existing processes, existing data, and proven functional logic. The difference is that you then choose a new technical foundation while preserving what is valuable from a business perspective.\n\nThis is exactly where experience counts. You want someone who doesn't say out of habit that everything must stay, but also doesn't advise rebuilding everything from scratch out of convenience.\n\n## The role of AI and automation in modernization\n\nAI is not a mandatory step in every project, but in the right place it can certainly be practical. Not as a marketing layer on top of an old system, but as a targeted addition to existing processes.\n\nThink of automatically classifying incoming data, [summarizing notes](https:\u002F\u002Floggix.com\u002Fblog\u002Fwhy-use-filemaker-features-importance-and-ai-integration), recognizing patterns in support requests, or preparing draft responses and documentation. In combination with FileMaker and good integrations, this can noticeably reduce manual work.\n\nThe same applies to process automation without AI. A lot of value already lies in automatically triggering follow-up actions, checks, and synchronizations. For most organizations, that is more valuable first than experimenting with complex applications.\n\n## Where decision-making often goes wrong\n\nThe biggest pitfall is not technology, but underestimation. Organizations sometimes think modernizing is a purely IT project, when in reality it is an operations project with technical components. As soon as daily working methods, responsibilities, and exceptions are not properly taken into account, discussions, delays, and disappointment arise.\n\nA second pitfall is wanting too much at once. New interface, new integrations, new reporting concept, new permissions model, and mobile expansion in one project sounds efficient, but often makes dependencies unnecessarily large. Then every component becomes a blocker for the rest.\n\nA third pitfall is steering by tool choice rather than business outcome. The relevant questions are usually simpler: where do people lose time, where do errors occur, which data needs to be reliably available, and which processes need to be scalable?\n\n## What a good modernization project delivers\n\nWhen done right, a modernized FileMaker system delivers more than just a cleaner application. Above all, you gain more calm in operations. Less duplicate entry, fewer manual intermediate steps, better data quality, and a system that can once again keep up with new requirements.\n\nIn addition, manageability improves. Changes become more predictable, integrations are set up more explicitly, and dependence on improvisation decreases. For management and IT, that is at least as important as ease of use on the work floor.\n\nFor organizations that want to build on their existing solution without starting over, that is often the best scenario. Business knowledge is retained, while technical and functional limitations are removed step by step. That is also why parties like Loggix approach modernization as a practical growth path, not as a buzzword.\n\nAnyone who wants to make their FileMaker environment future-proof therefore doesn't have to choose between standing still and a risky reset. Often the wisest route is much simpler: sharply assess what has value, selectively improve what hinders, and only renew where it truly makes a difference. That's usually where sustainable software simply begins.","\u003Cp>Modernizing a FileMaker system rarely starts with technology. It usually starts with frustration on the work floor. Orders being entered twice, reports updated manually, employees working with exports because integrations are missing, or a solution that once worked fine but now has too many exceptions. That's when the question arises: do we rebuild from scratch, or can we develop more intelligently?\u003C\u002Fp>\n\u003Cp>For many organizations, this isn't a theoretical choice. The system has been running in operations for years. It holds knowledge, business rules, and often processes that haven't been properly documented anywhere else. That's precisely why modernizing is usually wiser than replacing. Not because old is inherently good, but because the value of an existing FileMaker system is often greater than it appears at first glance.\u003C\u002Fp>\n\u003Ch2>When modernizing a FileMaker system makes sense\u003C\u002Fh2>\n\u003Cp>An outdated system is not automatically a bad system. The real question is whether the current landscape is still helping your organization or holding it back. That difference typically becomes visible on three points: maintenance, usage, and alignment with other software.\u003C\u002Fp>\n\u003Cp>In terms of maintenance, you see it in small adjustments that suddenly take a lot of time. Nobody quite knows how certain scripts work anymore, documentation is missing, and every change feels like a risk. In terms of usage, you notice that employees start working around the system. They enter data later, use Excel as an intermediate layer, or no longer fully trust reports. And when it comes to integrations, the pain often surfaces fastest. The FileMaker system still works, but doesn't connect well with accounting, e-commerce, planning, CRM, or mobile applications.\u003C\u002Fp>\n\u003Cp>Those are signals that modernizing a FileMaker system is worthwhile. Not to have something new, but to regain control over processes, data quality, and scalability.\u003C\u002Fp>\n\u003Ch2>Modernizing is not an all-or-nothing decision\u003C\u002Fh2>\n\u003Cp>A common mistake is that organizations think in extremes. Either everything stays as it is, or a completely new platform must come. In practice, the best route usually lies somewhere in between.\u003C\u002Fp>\n\u003Cp>Sometimes the core of the system is still fine, but the user interface is outdated and scripts have become too complex. Sometimes the database works well, but modern API integrations are missing. And sometimes the structure under the hood has become messy, while the functional logic remains valuable. A good modernization process therefore doesn't start with rebuilding, but with assessing what needs to be preserved, cleaned up, replaced, or extended.\u003C\u002Fp>\n\u003Cp>This is also financially relevant. A full migration sometimes sounds attractive on paper, but often brings more risk, more project time, and more organizational burden than anticipated. Especially when there are many custom processes in the current system.\u003C\u002Fp>\n\u003Ch3>What you typically want to preserve\u003C\u002Fh3>\n\u003Cp>Existing FileMaker environments often contain years of practical knowledge. Think of calculation rules, exceptions in workflows, permission structures, statuses, validations, and reporting logic. Throwing all of that away means you first have to rediscover it before it can be rebuilt.\u003C\u002Fp>\n\u003Cp>That's why preserving business logic is often a strong starting point. Not everything needs to remain technically the same, but the functional value deserves to be taken seriously.\u003C\u002Fp>\n\u003Ch3>What often needs to be addressed\u003C\u002Fh3>\n\u003Cp>There are also components that lend themselves well to renewal. Outdated layouts, inefficient scripts, manual import and export steps, local workarounds, and missing integrations are often the first candidates. Performance issues, limited mobile usability, and a lack of logging or manageability also demand attention.\u003C\u002Fp>\n\u003Cp>Modernizing then means: leaving the strong parts in place, and selectively improving the weak parts.\u003C\u002Fp>\n\u003Ch2>The biggest gains are often found outside the database itself\u003C\u002Fh2>\n\u003Cp>When modernizing, many organizations focus primarily on screens and functionality. That's understandable, but the real gains are often in the connection to the rest of the landscape.\u003C\u002Fp>\n\u003Cp>A FileMaker solution that is linked to \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Fseamless-payment-integration-between-filemaker-and-mollie-payment-provider\">accounting software\u003C\u002Fa>, webshops, portals, planning systems, or document services becomes immediately more valuable. Data needs to be manually transferred less often, errors decrease, and process lead times drop. That effect is usually greater than a prettier screen alone.\u003C\u002Fp>\n\u003Cp>Think of automatic synchronization of customer and order data, invoice creation, inventory updates, digital document flows, or notifications to mobile apps. That's precisely where an internal system transforms from a standalone database into a working part of the business operation.\u003C\u002Fp>\n\u003Cp>For organizations with multiple tools, that is often the difference between improvising daily and working structurally efficiently.\u003C\u002Fp>\n\u003Ch2>Modernizing a FileMaker system in phases usually works better\u003C\u002Fh2>\n\u003Cp>A pragmatic approach is almost always more effective than one big leap. Especially when the current system is business-critical. You want to improve without bringing operations to a standstill.\u003C\u002Fp>\n\u003Cp>The first phase is usually a technical and functional analysis. Not just what the system does, but also how it is used, where the dependencies lie, and which bottlenecks have real impact. This is followed by prioritization. Which improvement delivers quick results? What reduces risk? And which components need to be in order before further expansion is possible?\u003C\u002Fp>\n\u003Cp>Often a phasing emerges such as: clean up, structure, connect, and expand. Stability first, then renewal. That sounds less spectacular than a complete rebuild, but it works better in practice. The organization stays in control, users can get used to changes, and investments remain more predictable.\u003C\u002Fp>\n\u003Ch3>Stabilize first, then accelerate\u003C\u002Fh3>\n\u003Cp>If the foundation is technically messy, there is little point in immediately adding new features. You'd be building on uncertainty. Stabilizing means, for example, restructuring scripts, making naming consistent, reviewing data models, improving permissions, and making dependencies transparent.\u003C\u002Fp>\n\u003Cp>Only then does room open up for acceleration. That's when you can think about API integrations, web portals, mobile data entry, or \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Fusing-n8n-as-an-automation-agent-for-filemaker-solutions\">automated workflows\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2>When rebuilding is still the better choice\u003C\u002Fh2>\n\u003Cp>Modernizing is often wise, but not always. Sometimes an existing system has become so fragmented that further development becomes more expensive and riskier than a controlled rebuild. For example, when years of unstructured modifications have been made, when performance remains structurally poor, or when the architecture blocks new requirements.\u003C\u002Fp>\n\u003Cp>Even then, you don't have to throw everything away. A rebuild can still be based on existing processes, existing data, and proven functional logic. The difference is that you then choose a new technical foundation while preserving what is valuable from a business perspective.\u003C\u002Fp>\n\u003Cp>This is exactly where experience counts. You want someone who doesn't say out of habit that everything must stay, but also doesn't advise rebuilding everything from scratch out of convenience.\u003C\u002Fp>\n\u003Ch2>The role of AI and automation in modernization\u003C\u002Fh2>\n\u003Cp>AI is not a mandatory step in every project, but in the right place it can certainly be practical. Not as a marketing layer on top of an old system, but as a targeted addition to existing processes.\u003C\u002Fp>\n\u003Cp>Think of automatically classifying incoming data, \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Fwhy-use-filemaker-features-importance-and-ai-integration\">summarizing notes\u003C\u002Fa>, recognizing patterns in support requests, or preparing draft responses and documentation. In combination with FileMaker and good integrations, this can noticeably reduce manual work.\u003C\u002Fp>\n\u003Cp>The same applies to process automation without AI. A lot of value already lies in automatically triggering follow-up actions, checks, and synchronizations. For most organizations, that is more valuable first than experimenting with complex applications.\u003C\u002Fp>\n\u003Ch2>Where decision-making often goes wrong\u003C\u002Fh2>\n\u003Cp>The biggest pitfall is not technology, but underestimation. Organizations sometimes think modernizing is a purely IT project, when in reality it is an operations project with technical components. As soon as daily working methods, responsibilities, and exceptions are not properly taken into account, discussions, delays, and disappointment arise.\u003C\u002Fp>\n\u003Cp>A second pitfall is wanting too much at once. New interface, new integrations, new reporting concept, new permissions model, and mobile expansion in one project sounds efficient, but often makes dependencies unnecessarily large. Then every component becomes a blocker for the rest.\u003C\u002Fp>\n\u003Cp>A third pitfall is steering by tool choice rather than business outcome. The relevant questions are usually simpler: where do people lose time, where do errors occur, which data needs to be reliably available, and which processes need to be scalable?\u003C\u002Fp>\n\u003Ch2>What a good modernization project delivers\u003C\u002Fh2>\n\u003Cp>When done right, a modernized FileMaker system delivers more than just a cleaner application. Above all, you gain more calm in operations. Less duplicate entry, fewer manual intermediate steps, better data quality, and a system that can once again keep up with new requirements.\u003C\u002Fp>\n\u003Cp>In addition, manageability improves. Changes become more predictable, integrations are set up more explicitly, and dependence on improvisation decreases. For management and IT, that is at least as important as ease of use on the work floor.\u003C\u002Fp>\n\u003Cp>For organizations that want to build on their existing solution without starting over, that is often the best scenario. Business knowledge is retained, while technical and functional limitations are removed step by step. That is also why parties like Loggix approach modernization as a practical growth path, not as a buzzword.\u003C\u002Fp>\n\u003Cp>Anyone who wants to make their FileMaker environment future-proof therefore doesn't have to choose between standing still and a risky reset. Often the wisest route is much simpler: sharply assess what has value, selectively improve what hinders, and only renew where it truly makes a difference. That's usually where sustainable software simply begins.\u003C\u002Fp>\n","2026-06-25",1782406394000,[23],"\u002Fapi\u002Fknowledge\u002Fimage\u002F80\u002F?v=84237b8302ef",{"id":371,"idKnowledge":372,"idDomain":15,"idCluster":15,"slug":373,"title":374,"description":375,"bodyMarkdown":376,"bodyHtml":377,"author":378,"date":379,"createdAt":380,"topics":381,"image":382,"hasDownload":28,"fileName":15,"youtubeId":27},"79","62D99CF1-1C84-F146-80B3-AA680A5FAE8B","how-to-supercharge-your-ai-coding-agent-workflow-with-ecc","How to Supercharge Your AI Coding Agent Workflow with ECC","ECC is a production-ready operator system for AI coding agents. Learn how to set it up and use its skills, memory, and security features to ship faster.","**The short answer:** ECC (Engineer Command Center) is a battle-tested, harness-native operator system that gives your AI coding agent real skills, persistent memory, security scanning, and continuous learning — all in one drop-in setup. If you're using Claude, Cursor, or any agentic coding harness, ECC turns a bare agent into a production-grade engineering teammate.\n\n---\n\n## What is ECC and Why Should You Care?\n\nMost AI coding agents work out of the box — but only barely. They forget context, hallucinate commands, and have no consistent behavior across sessions. ECC solves this by providing:\n\n- **Skills & instincts** — pre-built behavioral rules that guide the agent like a senior engineer would\n- **Memory optimization** — keeps the context window lean so the agent stays sharp over long sessions\n- **Security scanning** — hooks that flag vulnerabilities before code is committed\n- **Continuous learning** — the system evolves based on real engineering feedback\n- **MCP configurations** — ready-made Model Context Protocol setups for multi-harness environments\n- **Legacy command shims** — backward compatibility so older workflows don't break\n\nThis isn't just a config file. It's an operator system built over 10+ months of daily real-world use building actual products.\n\n---\n\n## Who Is ECC For?\n\nECC is built for:\n\n- **Tech leads** who want consistent, governed AI agent behavior across a dev team\n- **AI-curious developers** who want to go beyond basic Copilot\u002FChat use and run true agentic workflows\n- **Engineering teams** adopting multi-agent or multi-harness setups (e.g. Claude + Cursor + custom tooling)\n\n---\n\n## How to Set Up ECC in Your Workflow\n\n### Step 1: Clone the ECC Repository\n\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002Faffaan-m\u002FECC.git\ncd ECC\n```\n\nThis gives you the full operator system: agents, skills, hooks, rules, and MCP configs.\n\n### Step 2: Review the Directory Structure\n\nBefore touching anything, understand what you're working with:\n\n- `\u002Fagents` — pre-configured agent definitions\n- `\u002Fskills` — reusable task modules (e.g. refactor, document, test)\n- `\u002Fhooks` — event-driven triggers (e.g. pre-commit security scan)\n- `\u002Frules` — behavioral constraints and coding instincts\n- `\u002Fmcp` — Model Context Protocol configurations for your harness\n\n### Step 3: Configure Your Harness\n\nCopy the relevant MCP configuration to your harness setup (e.g. Claude Projects, Cursor rules, or a custom harness config):\n\n```bash\ncp mcp\u002Fyour-harness-config.json ~\u002F.your-harness\u002Fconfig.json\n```\n\nAdapt paths and model names to match your local environment.\n\n### Step 4: Activate Skills and Rules\n\nLoad the skills and rules that match your project type. ECC comes with profiles evolved from real engineering workflows — pick the closest match and extend from there:\n\n1. Open the `\u002Frules` folder and review the instinct files\n2. Enable the rules relevant to your stack (e.g. Python, TypeScript, SQL)\n3. Add custom rules for your team's conventions\n\n### Step 5: Enable Security Hooks\n\nECC includes pre-commit and pre-push hooks for security scanning. Install them with:\n\n```bash\ncp hooks\u002Fpre-commit .git\u002Fhooks\u002Fpre-commit\nchmod +x .git\u002Fhooks\u002Fpre-commit\n```\n\nThe hook will scan staged code for common vulnerabilities before every commit — no separate tool needed.\n\n### Step 6: Tune Memory Optimization\n\nMemory bloat is the #1 reason AI agents degrade over a long session. ECC's memory optimization settings control:\n\n- **Context pruning** — drops low-value history automatically\n- **Summarization triggers** — compresses older context into summaries\n- **Priority pinning** — keeps critical instructions always in scope\n\nReview `\u002Fagents\u002Fmemory-config.yaml` and adjust thresholds to your typical session length and model context window.\n\n### Step 7: Run Your First Agentic Task\n\nWith everything configured, trigger a task through your harness. ECC will:\n\n1. Load the relevant skills for the task type\n2. Apply behavioral rules automatically\n3. Run security checks on any generated code\n4. Log the session for continuous learning\n\n---\n\n## Key Tips for Production Use\n\n- **Start with one skill set** — don't activate everything at once. Add skills incrementally as your team validates them.\n- **Version-control your ECC config** — treat your operator setup like code. Use branches for experimentation.\n- **Review the learning logs** — ECC captures what worked and what didn't. Use these logs to refine your rules over time.\n- **Share across the team** — the real power of ECC is consistency. One shared operator config means every developer's agent behaves the same way.\n\n---\n\n## Bottom Line\n\nECC closes the gap between \"AI assistant\" and \"engineering teammate.\" By giving your agent a structured set of skills, memory controls, and guardrails, you stop babysitting it and start shipping faster. Clone it, configure it to your stack, and let 10+ months of real-world engineering distill directly into your workflow.","\u003Cp>\u003Cstrong>The short answer:\u003C\u002Fstrong> ECC (Engineer Command Center) is a battle-tested, harness-native operator system that gives your AI coding agent real skills, persistent memory, security scanning, and continuous learning — all in one drop-in setup. If you're using Claude, Cursor, or any agentic coding harness, ECC turns a bare agent into a production-grade engineering teammate.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>What is ECC and Why Should You Care?\u003C\u002Fh2>\n\u003Cp>Most AI coding agents work out of the box — but only barely. They forget context, hallucinate commands, and have no consistent behavior across sessions. ECC solves this by providing:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Skills & instincts\u003C\u002Fstrong> — pre-built behavioral rules that guide the agent like a senior engineer would\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Memory optimization\u003C\u002Fstrong> — keeps the context window lean so the agent stays sharp over long sessions\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Security scanning\u003C\u002Fstrong> — hooks that flag vulnerabilities before code is committed\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Continuous learning\u003C\u002Fstrong> — the system evolves based on real engineering feedback\u003C\u002Fli>\n\u003Cli>\u003Cstrong>MCP configurations\u003C\u002Fstrong> — ready-made Model Context Protocol setups for multi-harness environments\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Legacy command shims\u003C\u002Fstrong> — backward compatibility so older workflows don't break\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This isn't just a config file. It's an operator system built over 10+ months of daily real-world use building actual products.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Who Is ECC For?\u003C\u002Fh2>\n\u003Cp>ECC is built for:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Tech leads\u003C\u002Fstrong> who want consistent, governed AI agent behavior across a dev team\u003C\u002Fli>\n\u003Cli>\u003Cstrong>AI-curious developers\u003C\u002Fstrong> who want to go beyond basic Copilot\u002FChat use and run true agentic workflows\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Engineering teams\u003C\u002Fstrong> adopting multi-agent or multi-harness setups (e.g. Claude + Cursor + custom tooling)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Chr>\n\u003Ch2>How to Set Up ECC in Your Workflow\u003C\u002Fh2>\n\u003Ch3>Step 1: Clone the ECC Repository\u003C\u002Fh3>\n\u003Cpre>\u003Ccode class=\"language-bash\">git clone https:\u002F\u002Fgithub.com\u002Faffaan-m\u002FECC.git\ncd ECC\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>This gives you the full operator system: agents, skills, hooks, rules, and MCP configs.\u003C\u002Fp>\n\u003Ch3>Step 2: Review the Directory Structure\u003C\u002Fh3>\n\u003Cp>Before touching anything, understand what you're working with:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>\u002Fagents\u003C\u002Fcode> — pre-configured agent definitions\u003C\u002Fli>\n\u003Cli>\u003Ccode>\u002Fskills\u003C\u002Fcode> — reusable task modules (e.g. refactor, document, test)\u003C\u002Fli>\n\u003Cli>\u003Ccode>\u002Fhooks\u003C\u002Fcode> — event-driven triggers (e.g. pre-commit security scan)\u003C\u002Fli>\n\u003Cli>\u003Ccode>\u002Frules\u003C\u002Fcode> — behavioral constraints and coding instincts\u003C\u002Fli>\n\u003Cli>\u003Ccode>\u002Fmcp\u003C\u002Fcode> — Model Context Protocol configurations for your harness\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Step 3: Configure Your Harness\u003C\u002Fh3>\n\u003Cp>Copy the relevant MCP configuration to your harness setup (e.g. Claude Projects, Cursor rules, or a custom harness config):\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">cp mcp\u002Fyour-harness-config.json ~\u002F.your-harness\u002Fconfig.json\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Adapt paths and model names to match your local environment.\u003C\u002Fp>\n\u003Ch3>Step 4: Activate Skills and Rules\u003C\u002Fh3>\n\u003Cp>Load the skills and rules that match your project type. ECC comes with profiles evolved from real engineering workflows — pick the closest match and extend from there:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Open the \u003Ccode>\u002Frules\u003C\u002Fcode> folder and review the instinct files\u003C\u002Fli>\n\u003Cli>Enable the rules relevant to your stack (e.g. Python, TypeScript, SQL)\u003C\u002Fli>\n\u003Cli>Add custom rules for your team's conventions\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Step 5: Enable Security Hooks\u003C\u002Fh3>\n\u003Cp>ECC includes pre-commit and pre-push hooks for security scanning. Install them with:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">cp hooks\u002Fpre-commit .git\u002Fhooks\u002Fpre-commit\nchmod +x .git\u002Fhooks\u002Fpre-commit\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The hook will scan staged code for common vulnerabilities before every commit — no separate tool needed.\u003C\u002Fp>\n\u003Ch3>Step 6: Tune Memory Optimization\u003C\u002Fh3>\n\u003Cp>Memory bloat is the #1 reason AI agents degrade over a long session. ECC's memory optimization settings control:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Context pruning\u003C\u002Fstrong> — drops low-value history automatically\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Summarization triggers\u003C\u002Fstrong> — compresses older context into summaries\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Priority pinning\u003C\u002Fstrong> — keeps critical instructions always in scope\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Review \u003Ccode>\u002Fagents\u002Fmemory-config.yaml\u003C\u002Fcode> and adjust thresholds to your typical session length and model context window.\u003C\u002Fp>\n\u003Ch3>Step 7: Run Your First Agentic Task\u003C\u002Fh3>\n\u003Cp>With everything configured, trigger a task through your harness. ECC will:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Load the relevant skills for the task type\u003C\u002Fli>\n\u003Cli>Apply behavioral rules automatically\u003C\u002Fli>\n\u003Cli>Run security checks on any generated code\u003C\u002Fli>\n\u003Cli>Log the session for continuous learning\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Chr>\n\u003Ch2>Key Tips for Production Use\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Start with one skill set\u003C\u002Fstrong> — don't activate everything at once. Add skills incrementally as your team validates them.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Version-control your ECC config\u003C\u002Fstrong> — treat your operator setup like code. Use branches for experimentation.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Review the learning logs\u003C\u002Fstrong> — ECC captures what worked and what didn't. Use these logs to refine your rules over time.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Share across the team\u003C\u002Fstrong> — the real power of ECC is consistency. One shared operator config means every developer's agent behaves the same way.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Chr>\n\u003Ch2>Bottom Line\u003C\u002Fh2>\n\u003Cp>ECC closes the gap between "AI assistant" and "engineering teammate." By giving your agent a structured set of skills, memory controls, and guardrails, you stop babysitting it and start shipping faster. Clone it, configure it to your stack, and let 10+ months of real-world engineering distill directly into your workflow.\u003C\u002Fp>\n","Bhushan","2026-06-19",1781859564000,[344,86],"\u002Fapi\u002Fknowledge\u002Fimage\u002F79\u002F?v=c411830a264d",{"id":384,"idKnowledge":385,"idDomain":15,"idCluster":15,"slug":386,"title":387,"description":388,"bodyMarkdown":389,"bodyHtml":390,"author":39,"date":391,"createdAt":392,"topics":393,"image":394,"hasDownload":28,"fileName":15,"youtubeId":27},"26","52DA7FCF-BD2B-6A4D-B739-0B7A21814A2F","necessity-driven-development-bouw-alleen-software-die-echt-nodig-is","Necessity-Driven Development: build only the software that's truly needed","Discover how the Loggix manifesto 'Necessity-Driven Development' helps entrepreneurs and FileMaker developers make better software decisions in the AI era.","**Stop building what's possible. Build what's necessary.** That is the essence of Necessity-Driven Development (NDD) — the philosophy that Loggix founder Jeroen Lutmers describes in the [Loggix Manifest](https:\u002F\u002Floggix-manifesto.vercel.app\u002F). In a world where AI makes everything *possible*, the real challenge is: knowing what you *don't* build.\n\n## What is Necessity-Driven Development?\n\nNDD is an approach in which every software decision starts with one central question: **is this truly necessary?** Not: can it be done? Not: does someone want it? But: does it solve a concrete, proven problem?\n\nThis sounds simple, but it is a direct response to a growing issue: as AI tools make building software faster and cheaper, the temptation grows to stack features, integrations, and automations — even when the business case is razor-thin.\n\n## Why is this relevant for entrepreneurs?\n\nMany companies invest in custom software or ERP extensions based on enthusiasm rather than necessity. The result:\n\n- Systems that are too complex for daily use\n- Maintenance that costs more than the solution delivers\n- Teams that work around the system instead of within it\n\nNDD forces you to first clearly define the *problem* before thinking about a solution.\n\n## Why is this relevant for FileMaker developers?\n\nFileMaker makes it tempting to build something quickly. But speed is no excuse for unnecessary complexity. NDD helps developers to:\n\n1. **Recognise scope creep** before it sneaks into the database\n2. **Have better conversations** with clients about what they *need* vs. what they *want*\n3. **Deliver more sustainable solutions** that are still maintainable 3 years from now\n\n## How do you apply NDD in practice?\n\nThe approach is concrete and applicable to any software project:\n\n1. **Formulate the problem without a solution** — write down what is going wrong without naming a system yet.\n2. **Quantify the pain** — how much time, money, or errors does the problem currently cost?\n3. **Test the necessity** — does the proposed software directly solve this, or does it address a symptom?\n4. **Determine the minimal solution** — what is the smallest system that eliminates the problem?\n5. **Build, measure, decide** — deliver something small, measure the impact, and then decide whether expansion makes sense.\n\n## The role of AI in NDD\n\nAI accelerates building, but changes nothing about the question of *what* you build. On the contrary: precisely because AI makes it easier to generate features, the discipline to say *no* becomes more valuable. NDD gives that discipline a name and a framework.\n\nAt Loggix we apply this in FileMaker custom work, ERP projects, API integrations, and AI integrations: always starting from the question of whether the investment covers a proven necessity.\n\n## Want to know whether your software idea is truly necessary?\n\nLoggix is happy to think along with you. Whether you are an entrepreneur with a concrete challenge or a FileMaker developer looking for a sharper approach — [get in touch](https:\u002F\u002Fwww.loggix.nl\u002Fcontact) and we will look together at what is truly needed.","\u003Cp>\u003Cstrong>Stop building what's possible. Build what's necessary.\u003C\u002Fstrong> That is the essence of Necessity-Driven Development (NDD) — the philosophy that Loggix founder Jeroen Lutmers describes in the \u003Ca href=\"https:\u002F\u002Floggix-manifesto.vercel.app\u002F\">Loggix Manifest\u003C\u002Fa>. In a world where AI makes everything \u003Cem>possible\u003C\u002Fem>, the real challenge is: knowing what you \u003Cem>don't\u003C\u002Fem> build.\u003C\u002Fp>\n\u003Ch2>What is Necessity-Driven Development?\u003C\u002Fh2>\n\u003Cp>NDD is an approach in which every software decision starts with one central question: \u003Cstrong>is this truly necessary?\u003C\u002Fstrong> Not: can it be done? Not: does someone want it? But: does it solve a concrete, proven problem?\u003C\u002Fp>\n\u003Cp>This sounds simple, but it is a direct response to a growing issue: as AI tools make building software faster and cheaper, the temptation grows to stack features, integrations, and automations — even when the business case is razor-thin.\u003C\u002Fp>\n\u003Ch2>Why is this relevant for entrepreneurs?\u003C\u002Fh2>\n\u003Cp>Many companies invest in custom software or ERP extensions based on enthusiasm rather than necessity. The result:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Systems that are too complex for daily use\u003C\u002Fli>\n\u003Cli>Maintenance that costs more than the solution delivers\u003C\u002Fli>\n\u003Cli>Teams that work around the system instead of within it\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>NDD forces you to first clearly define the \u003Cem>problem\u003C\u002Fem> before thinking about a solution.\u003C\u002Fp>\n\u003Ch2>Why is this relevant for FileMaker developers?\u003C\u002Fh2>\n\u003Cp>FileMaker makes it tempting to build something quickly. But speed is no excuse for unnecessary complexity. NDD helps developers to:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Recognise scope creep\u003C\u002Fstrong> before it sneaks into the database\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Have better conversations\u003C\u002Fstrong> with clients about what they \u003Cem>need\u003C\u002Fem> vs. what they \u003Cem>want\u003C\u002Fem>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Deliver more sustainable solutions\u003C\u002Fstrong> that are still maintainable 3 years from now\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2>How do you apply NDD in practice?\u003C\u002Fh2>\n\u003Cp>The approach is concrete and applicable to any software project:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Formulate the problem without a solution\u003C\u002Fstrong> — write down what is going wrong without naming a system yet.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Quantify the pain\u003C\u002Fstrong> — how much time, money, or errors does the problem currently cost?\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Test the necessity\u003C\u002Fstrong> — does the proposed software directly solve this, or does it address a symptom?\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Determine the minimal solution\u003C\u002Fstrong> — what is the smallest system that eliminates the problem?\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Build, measure, decide\u003C\u002Fstrong> — deliver something small, measure the impact, and then decide whether expansion makes sense.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2>The role of AI in NDD\u003C\u002Fh2>\n\u003Cp>AI accelerates building, but changes nothing about the question of \u003Cem>what\u003C\u002Fem> you build. On the contrary: precisely because AI makes it easier to generate features, the discipline to say \u003Cem>no\u003C\u002Fem> becomes more valuable. NDD gives that discipline a name and a framework.\u003C\u002Fp>\n\u003Cp>At Loggix we apply this in FileMaker custom work, ERP projects, API integrations, and AI integrations: always starting from the question of whether the investment covers a proven necessity.\u003C\u002Fp>\n\u003Ch2>Want to know whether your software idea is truly necessary?\u003C\u002Fh2>\n\u003Cp>Loggix is happy to think along with you. Whether you are an entrepreneur with a concrete challenge or a FileMaker developer looking for a sharper approach — \u003Ca href=\"https:\u002F\u002Fwww.loggix.nl\u002Fcontact\">get in touch\u003C\u002Fa> and we will look together at what is truly needed.\u003C\u002Fp>\n","2026-06-11",1781191272000,[23,86],"\u002Fapi\u002Fknowledge\u002Fimage\u002F26\u002F?v=357c49d8d079",{"id":396,"idKnowledge":397,"idDomain":15,"idCluster":15,"slug":398,"title":399,"description":400,"bodyMarkdown":401,"bodyHtml":402,"author":39,"date":403,"createdAt":404,"topics":405,"image":406,"hasDownload":28,"fileName":15,"youtubeId":27},"25","80C66151-0CF0-DA49-8DEB-F8B3CC34B060","de-10-belangrijkste-nieuwe-functies-van-filemaker-2026-voor-eindgebruikers","The 10 Most Important New Features of FileMaker 2026 for End Users","FileMaker 2026 brings major improvements in the areas of AI, performance, and reliability. These are the 10 features you'll notice directly as an end user.","FileMaker 2026 is here — and it's a substantial update. Whether you work with a custom solution on a daily basis or are a manager responsible for business software: these 10 improvements are worth knowing about...\n\n## 1. New PDF Script Steps: More Control Over Documents\n\nFileMaker 2026 introduces new script steps specifically for PDF processing. This means your custom solution will be able to handle PDF files intelligently — think automatic merging, splitting, or reading — without external tools.\n\n**Benefit for you:** Less manual work around documents and invoices.\n\n## 2. Easier Remote Backup\n\nSetting up backups to an external location was cumbersome in the past. In 2026, this has been significantly simplified, allowing administrators to configure backups faster and more reliably.\n\n**Benefit for you:** Lower risk of data loss, easier to manage.\n\n## 3. Image Captioning with AI\n\nFileMaker 2026 can automatically generate descriptions for images — also known as *image captioning*. This works through built-in AI functionality.\n\n**Benefit for you:** Images in your database become searchable and easier to find, without having to label them manually.\n\n## 4. Better Data Embedding and RAG\n\nRAG stands for *Retrieval-Augmented Generation*: a technique in which AI bases its answers on *your* company data rather than solely on general training data. FileMaker 2026 significantly improves support for this.\n\n**Benefit for you:** AI features in your custom solution become more relevant and accurate — based on your own data.\n\n## 5. Faster Thanks to Improved JSON Parsing\n\nMany modern integrations (APIs) communicate via JSON. FileMaker 2026 now processes this format considerably faster.\n\n**Benefit for you:** Integrations with external systems — such as webshops, accounting packages, or CRMs — respond more quickly.\n\n## 6. GetRecordIDsFromFoundSet Is Now Relationship-Aware\n\nThis function can now also retrieve records via related tables. A technical detail, but with a significant impact on the speed of complex queries.\n\n**Benefit for you:** Reports and overviews that combine multiple tables load noticeably faster.\n\n## 7. Using Relationships in SQL Queries\n\nDevelopers can now use relationships between tables directly in SQL queries within FileMaker. This makes advanced data querying significantly simpler and more powerful.\n\n**Benefit for you:** Complex reports and analyses become possible without workarounds or additional scripting.\n\n## 8. WebP Support for Images\n\nWebP is a modern image format that produces smaller files at the same quality. FileMaker 2026 now supports this format natively.\n\n**Benefit for you:** Less storage space, faster loading of screens with many images.\n\n## 9. Standby Server Available\n\nA standby server is a backup server that automatically takes over if the primary server goes down. FileMaker 2026 now makes this possible within the standard server environment.\n\n**Benefit for you:** Higher availability of your software — less downtime during outages.\n\n## 10. Export Field Content Server-Side\n\nExporting field content (such as files or attachments) can now take place directly on the server, rather than on the user's device.\n\n**Benefit for you:** Faster exports, less load on your computer, and better possibilities for automated processes.\n\n---\n\n## What Does This Mean for Your Custom Solution?\n\nNot every feature is immediately visible to end users, but together they create a faster, smarter, and more reliable environment. Want to know which of these improvements are relevant to your specific situation? Get in touch with Loggix — we'll help you determine what an upgrade to FileMaker 2026 can deliver for your organisation.","\u003Cp>FileMaker 2026 is here — and it's a substantial update. Whether you work with a custom solution on a daily basis or are a manager responsible for business software: these 10 improvements are worth knowing about...\u003C\u002Fp>\n\u003Ch2>1. New PDF Script Steps: More Control Over Documents\u003C\u002Fh2>\n\u003Cp>FileMaker 2026 introduces new script steps specifically for PDF processing. This means your custom solution will be able to handle PDF files intelligently — think automatic merging, splitting, or reading — without external tools.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Benefit for you:\u003C\u002Fstrong> Less manual work around documents and invoices.\u003C\u002Fp>\n\u003Ch2>2. Easier Remote Backup\u003C\u002Fh2>\n\u003Cp>Setting up backups to an external location was cumbersome in the past. In 2026, this has been significantly simplified, allowing administrators to configure backups faster and more reliably.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Benefit for you:\u003C\u002Fstrong> Lower risk of data loss, easier to manage.\u003C\u002Fp>\n\u003Ch2>3. Image Captioning with AI\u003C\u002Fh2>\n\u003Cp>FileMaker 2026 can automatically generate descriptions for images — also known as \u003Cem>image captioning\u003C\u002Fem>. This works through built-in AI functionality.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Benefit for you:\u003C\u002Fstrong> Images in your database become searchable and easier to find, without having to label them manually.\u003C\u002Fp>\n\u003Ch2>4. Better Data Embedding and RAG\u003C\u002Fh2>\n\u003Cp>RAG stands for \u003Cem>Retrieval-Augmented Generation\u003C\u002Fem>: a technique in which AI bases its answers on \u003Cem>your\u003C\u002Fem> company data rather than solely on general training data. FileMaker 2026 significantly improves support for this.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Benefit for you:\u003C\u002Fstrong> AI features in your custom solution become more relevant and accurate — based on your own data.\u003C\u002Fp>\n\u003Ch2>5. Faster Thanks to Improved JSON Parsing\u003C\u002Fh2>\n\u003Cp>Many modern integrations (APIs) communicate via JSON. FileMaker 2026 now processes this format considerably faster.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Benefit for you:\u003C\u002Fstrong> Integrations with external systems — such as webshops, accounting packages, or CRMs — respond more quickly.\u003C\u002Fp>\n\u003Ch2>6. GetRecordIDsFromFoundSet Is Now Relationship-Aware\u003C\u002Fh2>\n\u003Cp>This function can now also retrieve records via related tables. A technical detail, but with a significant impact on the speed of complex queries.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Benefit for you:\u003C\u002Fstrong> Reports and overviews that combine multiple tables load noticeably faster.\u003C\u002Fp>\n\u003Ch2>7. Using Relationships in SQL Queries\u003C\u002Fh2>\n\u003Cp>Developers can now use relationships between tables directly in SQL queries within FileMaker. This makes advanced data querying significantly simpler and more powerful.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Benefit for you:\u003C\u002Fstrong> Complex reports and analyses become possible without workarounds or additional scripting.\u003C\u002Fp>\n\u003Ch2>8. WebP Support for Images\u003C\u002Fh2>\n\u003Cp>WebP is a modern image format that produces smaller files at the same quality. FileMaker 2026 now supports this format natively.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Benefit for you:\u003C\u002Fstrong> Less storage space, faster loading of screens with many images.\u003C\u002Fp>\n\u003Ch2>9. Standby Server Available\u003C\u002Fh2>\n\u003Cp>A standby server is a backup server that automatically takes over if the primary server goes down. FileMaker 2026 now makes this possible within the standard server environment.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Benefit for you:\u003C\u002Fstrong> Higher availability of your software — less downtime during outages.\u003C\u002Fp>\n\u003Ch2>10. Export Field Content Server-Side\u003C\u002Fh2>\n\u003Cp>Exporting field content (such as files or attachments) can now take place directly on the server, rather than on the user's device.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Benefit for you:\u003C\u002Fstrong> Faster exports, less load on your computer, and better possibilities for automated processes.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>What Does This Mean for Your Custom Solution?\u003C\u002Fh2>\n\u003Cp>Not every feature is immediately visible to end users, but together they create a faster, smarter, and more reliable environment. Want to know which of these improvements are relevant to your specific situation? Get in touch with Loggix — we'll help you determine what an upgrade to FileMaker 2026 can deliver for your organisation.\u003C\u002Fp>\n","2026-06-10",1781094401000,[23,86],"\u002Fapi\u002Fknowledge\u002Fimage\u002F25\u002F?v=3a0718aa2b8b",{"id":408,"idKnowledge":409,"idDomain":15,"idCluster":15,"slug":410,"title":411,"description":412,"bodyMarkdown":413,"bodyHtml":414,"author":378,"date":415,"createdAt":416,"topics":417,"image":419,"hasDownload":28,"fileName":15,"youtubeId":27},"24","4D10C135-B594-E946-9AA7-4F7B5204AEA8","what-if-you-could-generate-an-entire-ai-podcast-with-multiple-speakers-from-a-single-text-prompt","What if you could generate an entire AI podcast with multiple speakers from a single text prompt?","Did you know Microsoft has open-sourced a voice AI model that can generate up to 90 minutes of multi-speaker audio from text?\nVibeVoice is Microsoft's open-source voice AI framework designed for long-form speech generation, real-time text-to-speech, speech recognition, and multi-speaker conversational audio.\nUnlike traditional text-to-speech systems that struggle with long conversations, speaker consistency, and natural turn-taking, VibeVoice is designed to generate podcast-quality conversations, voice agents, audiobooks, and long-form spoken content with remarkable coherence.\nWhether you're building AI voice agents, podcast generators, customer support systems, or conversational applications, VibeVoice provides a powerful open-source foundation.","## Key Features\n\n* Completely open source\n* Long-form speech generation\n* Multi-speaker conversations\n* Real-time streaming TTS\n* Voice agent support\n* Podcast generation\n* Audiobook generation\n* Speech-to-Text (ASR)\n* Speaker diarization\n* Multilingual support\n* Voice cloning support\n* Local deployment support\n\n---\n\n## What is VibeVoice?\n\nVibeVoice is a family of speech AI models developed by Microsoft Research.\n\nThe project currently includes:\n\n### VibeVoice-TTS\n\nLong-form text-to-speech generation.\n\n### VibeVoice-Realtime\n\nUltra-low latency streaming text-to-speech.\n\n### VibeVoice-ASR\n\nSpeech-to-text transcription for long audio recordings.\n\nTogether, these models cover the complete voice AI stack from speech generation to speech understanding.\n\n---\n\n## What Can You Build?\n\nVibeVoice can be used to create:\n\n* AI Podcasts\n* AI Voice Agents\n* Audiobooks\n* Customer Support Agents\n* AI Receptionists\n* Voice Assistants\n* Call Center Automation\n* Educational Narration\n* Content Creation Tools\n* Voice-Enabled SaaS Products\n* Meeting Transcription Systems\n* Multilingual Voice Applications\n\n---\n\n## How VibeVoice Works\n\n### Text-to-Speech Pipeline\n\n```text\nText Script\n      ↓\nVibeVoice Model\n      ↓\nSpeaker Generation\n      ↓\nVoice Synthesis\n      ↓\nNatural Audio Output\n```\n\nFor conversational content:\n\n```text\nScript\n      ↓\nSpeaker 1\nSpeaker 2\nSpeaker 3\nSpeaker 4\n      ↓\nNatural Turn Taking\n      ↓\nPodcast \u002F Conversation\n```\n\nUnlike many TTS systems that support only one or two speakers, VibeVoice can generate conversations with up to four speakers while maintaining speaker consistency across long sessions.\n\n---\n\n## Why VibeVoice Is Different\n\nTraditional TTS systems often struggle with:\n\n* Long conversations\n* Speaker consistency\n* Context retention\n* Natural turn-taking\n\nVibeVoice was specifically designed to solve these challenges.\n\nKey capabilities include:\n\n### Up to 90 Minutes of Audio\n\nGenerate long-form speech in a single generation session.\n\n### Up to 4 Speakers\n\nCreate realistic conversations and podcasts.\n\n### Real-Time Streaming\n\nGenerate audio while text is still being produced.\n\n### Long Context Understanding\n\nMaintain consistency throughout extended conversations.\n\n---\n\n## Available Models\n\n### VibeVoice-1.5B\n\nSmaller model optimized for efficiency and local deployment.\n\nBest for:\n\n* Personal projects\n* AI applications\n* Local inference\n\n### VibeVoice-7B\n\nLargest model with higher quality output.\n\nBest for:\n\n* Professional podcasts\n* Production workloads\n* High-quality narration\n\n### VibeVoice-Realtime-0.5B\n\nOptimized for streaming voice generation.\n\nFeatures:\n\n* Streaming text input\n* Approximately 200–300 ms latency\n* Real-time voice agents\n* Live AI assistants\n\nPerfect for conversational AI applications.\n\n---\n\n## Prerequisites\n\nBefore running VibeVoice locally, install:\n\n### Python\n\n```bash\npython --version\n```\n\nPython 3.10+ is recommended.\n\n### Git\n\n```bash\ngit --version\n```\n\n### GPU (Recommended)\n\nFor best performance:\n\n* NVIDIA GPU\n* CUDA support\n* 10GB+ VRAM for smaller models\n* 18GB+ VRAM for larger models\n\nThe 1.5B model can run on consumer GPUs while larger models require more resources.\n\n---\n\n## Step 1 – Clone the Repository\n\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FVibeVoice.git\n```\n\nMove into the project:\n\n```bash\ncd VibeVoice\n```\n\n---\n\n## Step 2 – Create a Virtual Environment\n\n```bash\npython -m venv venv\n```\n\nActivate:\n\n### Windows\n\n```bash\nvenv\\Scripts\\activate\n```\n\n### Mac\u002FLinux\n\n```bash\nsource venv\u002Fbin\u002Factivate\n```\n\n---\n\n## Step 3 – Install Dependencies\n\nInstall required packages:\n\n```bash\npip install -r requirements.txt\n```\n\nOr install using the project's recommended setup instructions.\n\n---\n\n## Step 4 – Download a Model\n\nAvailable models include:\n\n* VibeVoice-1.5B\n* VibeVoice-7B\n* VibeVoice-Realtime-0.5B\n* VibeVoice-ASR\n\nModels are hosted on Hugging Face and Microsoft repositories.\n\n---\n\n## Step 5 – Generate Your First Audio\n\nCreate a text file:\n\n```text\nSpeaker 1:\nWelcome to today's AI podcast.\n\nSpeaker 2:\nToday we are discussing voice agents and generative AI.\n```\n\nRun inference using the provided examples.\n\nVibeVoice generates natural multi-speaker audio automatically.\n\n---\n\n## Real-Time Voice Agents with VibeVoice\n\nOne of the most exciting additions is:\n\n### VibeVoice-Realtime\n\nDesigned specifically for:\n\n* AI Voice Agents\n* Customer Support Bots\n* Real-Time Assistants\n* Interactive Applications\n\nFeatures include:\n\n* Streaming text input\n* Low latency speech generation\n* Continuous speech output\n* Long-form audio support\n\nThis makes VibeVoice a strong alternative to proprietary voice systems.\n\n---\n\n## Speech Recognition with VibeVoice-ASR\n\nMicrosoft also released:\n\n### VibeVoice-ASR\n\nCapabilities include:\n\n* 60-minute transcription\n* Single-pass processing\n* Speaker diarization\n* Timestamp generation\n* 50+ languages\n* Code-switching support\n\nThis allows developers to transcribe long meetings, podcasts, interviews, and recordings without splitting audio into small chunks.\n\n---\n\n## Example Business Use Cases\n\n### AI Podcast Generator\n\nConvert written scripts into fully voiced podcasts.\n\n### AI Receptionist\n\nAnswer phone calls using natural AI voices.\n\n### Audiobook Platform\n\nGenerate long-form audiobook narration.\n\n### Customer Support Agent\n\nProvide voice-based support automatically.\n\n### Meeting Transcription\n\nConvert meetings into searchable text.\n\n### Educational Content Creation\n\nCreate narrated training materials.\n\n### Voice-Enabled SaaS Products\n\nAdd voice generation to existing applications.\n\n---\n\n## Supported Languages\n\nVibeVoice supports multilingual speech generation and transcription.\n\nCapabilities include:\n\n* English\n* Mandarin\n* Multilingual Voices\n* Code-Switching Support\n\nMicrosoft continues expanding language coverage across the model family.\n\n---\n\n## Deployment Options\n\nYou can deploy VibeVoice on:\n\n* Local Machines\n* Workstations\n* Dedicated GPU Servers\n* Docker Containers\n* Railway\n* RunPod\n* Modal\n* AWS\n* Azure\n* Google Cloud\n\nThis makes it suitable for both hobby projects and production-scale voice applications.\n\n---\n\n## Why Use VibeVoice?\n\nMost voice AI platforms:\n\n* Charge monthly fees\n* Restrict customization\n* Limit model access\n\nVibeVoice gives developers:\n\n* Open-source freedom\n* Local deployment\n* Long-form speech generation\n* Multi-speaker conversations\n* Real-time voice synthesis\n* Speech recognition capabilities\n* Full control over infrastructure\n\nBecause it is open source, developers can build highly customized voice applications without vendor lock-in.","\u003Ch2>Key Features\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Completely open source\u003C\u002Fli>\n\u003Cli>Long-form speech generation\u003C\u002Fli>\n\u003Cli>Multi-speaker conversations\u003C\u002Fli>\n\u003Cli>Real-time streaming TTS\u003C\u002Fli>\n\u003Cli>Voice agent support\u003C\u002Fli>\n\u003Cli>Podcast generation\u003C\u002Fli>\n\u003Cli>Audiobook generation\u003C\u002Fli>\n\u003Cli>Speech-to-Text (ASR)\u003C\u002Fli>\n\u003Cli>Speaker diarization\u003C\u002Fli>\n\u003Cli>Multilingual support\u003C\u002Fli>\n\u003Cli>Voice cloning support\u003C\u002Fli>\n\u003Cli>Local deployment support\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Chr>\n\u003Ch2>What is VibeVoice?\u003C\u002Fh2>\n\u003Cp>VibeVoice is a family of speech AI models developed by Microsoft Research.\u003C\u002Fp>\n\u003Cp>The project currently includes:\u003C\u002Fp>\n\u003Ch3>VibeVoice-TTS\u003C\u002Fh3>\n\u003Cp>Long-form text-to-speech generation.\u003C\u002Fp>\n\u003Ch3>VibeVoice-Realtime\u003C\u002Fh3>\n\u003Cp>Ultra-low latency streaming text-to-speech.\u003C\u002Fp>\n\u003Ch3>VibeVoice-ASR\u003C\u002Fh3>\n\u003Cp>Speech-to-text transcription for long audio recordings.\u003C\u002Fp>\n\u003Cp>Together, these models cover the complete voice AI stack from speech generation to speech understanding.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>What Can You Build?\u003C\u002Fh2>\n\u003Cp>VibeVoice can be used to create:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>AI Podcasts\u003C\u002Fli>\n\u003Cli>AI Voice Agents\u003C\u002Fli>\n\u003Cli>Audiobooks\u003C\u002Fli>\n\u003Cli>Customer Support Agents\u003C\u002Fli>\n\u003Cli>AI Receptionists\u003C\u002Fli>\n\u003Cli>Voice Assistants\u003C\u002Fli>\n\u003Cli>Call Center Automation\u003C\u002Fli>\n\u003Cli>Educational Narration\u003C\u002Fli>\n\u003Cli>Content Creation Tools\u003C\u002Fli>\n\u003Cli>Voice-Enabled SaaS Products\u003C\u002Fli>\n\u003Cli>Meeting Transcription Systems\u003C\u002Fli>\n\u003Cli>Multilingual Voice Applications\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Chr>\n\u003Ch2>How VibeVoice Works\u003C\u002Fh2>\n\u003Ch3>Text-to-Speech Pipeline\u003C\u002Fh3>\n\u003Cpre>\u003Ccode class=\"language-text\">Text Script\n      ↓\nVibeVoice Model\n      ↓\nSpeaker Generation\n      ↓\nVoice Synthesis\n      ↓\nNatural Audio Output\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>For conversational content:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-text\">Script\n      ↓\nSpeaker 1\nSpeaker 2\nSpeaker 3\nSpeaker 4\n      ↓\nNatural Turn Taking\n      ↓\nPodcast \u002F Conversation\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Unlike many TTS systems that support only one or two speakers, VibeVoice can generate conversations with up to four speakers while maintaining speaker consistency across long sessions.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Why VibeVoice Is Different\u003C\u002Fh2>\n\u003Cp>Traditional TTS systems often struggle with:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Long conversations\u003C\u002Fli>\n\u003Cli>Speaker consistency\u003C\u002Fli>\n\u003Cli>Context retention\u003C\u002Fli>\n\u003Cli>Natural turn-taking\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>VibeVoice was specifically designed to solve these challenges.\u003C\u002Fp>\n\u003Cp>Key capabilities include:\u003C\u002Fp>\n\u003Ch3>Up to 90 Minutes of Audio\u003C\u002Fh3>\n\u003Cp>Generate long-form speech in a single generation session.\u003C\u002Fp>\n\u003Ch3>Up to 4 Speakers\u003C\u002Fh3>\n\u003Cp>Create realistic conversations and podcasts.\u003C\u002Fp>\n\u003Ch3>Real-Time Streaming\u003C\u002Fh3>\n\u003Cp>Generate audio while text is still being produced.\u003C\u002Fp>\n\u003Ch3>Long Context Understanding\u003C\u002Fh3>\n\u003Cp>Maintain consistency throughout extended conversations.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Available Models\u003C\u002Fh2>\n\u003Ch3>VibeVoice-1.5B\u003C\u002Fh3>\n\u003Cp>Smaller model optimized for efficiency and local deployment.\u003C\u002Fp>\n\u003Cp>Best for:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Personal projects\u003C\u002Fli>\n\u003Cli>AI applications\u003C\u002Fli>\n\u003Cli>Local inference\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>VibeVoice-7B\u003C\u002Fh3>\n\u003Cp>Largest model with higher quality output.\u003C\u002Fp>\n\u003Cp>Best for:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Professional podcasts\u003C\u002Fli>\n\u003Cli>Production workloads\u003C\u002Fli>\n\u003Cli>High-quality narration\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>VibeVoice-Realtime-0.5B\u003C\u002Fh3>\n\u003Cp>Optimized for streaming voice generation.\u003C\u002Fp>\n\u003Cp>Features:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Streaming text input\u003C\u002Fli>\n\u003Cli>Approximately 200–300 ms latency\u003C\u002Fli>\n\u003Cli>Real-time voice agents\u003C\u002Fli>\n\u003Cli>Live AI assistants\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Perfect for conversational AI applications.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Prerequisites\u003C\u002Fh2>\n\u003Cp>Before running VibeVoice locally, install:\u003C\u002Fp>\n\u003Ch3>Python\u003C\u002Fh3>\n\u003Cpre>\u003Ccode class=\"language-bash\">python --version\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Python 3.10+ is recommended.\u003C\u002Fp>\n\u003Ch3>Git\u003C\u002Fh3>\n\u003Cpre>\u003Ccode class=\"language-bash\">git --version\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>GPU (Recommended)\u003C\u002Fh3>\n\u003Cp>For best performance:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>NVIDIA GPU\u003C\u002Fli>\n\u003Cli>CUDA support\u003C\u002Fli>\n\u003Cli>10GB+ VRAM for smaller models\u003C\u002Fli>\n\u003Cli>18GB+ VRAM for larger models\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The 1.5B model can run on consumer GPUs while larger models require more resources.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Step 1 – Clone the Repository\u003C\u002Fh2>\n\u003Cpre>\u003Ccode class=\"language-bash\">git clone https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FVibeVoice.git\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Move into the project:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">cd VibeVoice\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Chr>\n\u003Ch2>Step 2 – Create a Virtual Environment\u003C\u002Fh2>\n\u003Cpre>\u003Ccode class=\"language-bash\">python -m venv venv\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Activate:\u003C\u002Fp>\n\u003Ch3>Windows\u003C\u002Fh3>\n\u003Cpre>\u003Ccode class=\"language-bash\">venv\\Scripts\\activate\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>Mac\u002FLinux\u003C\u002Fh3>\n\u003Cpre>\u003Ccode class=\"language-bash\">source venv\u002Fbin\u002Factivate\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Chr>\n\u003Ch2>Step 3 – Install Dependencies\u003C\u002Fh2>\n\u003Cp>Install required packages:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">pip install -r requirements.txt\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Or install using the project's recommended setup instructions.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Step 4 – Download a Model\u003C\u002Fh2>\n\u003Cp>Available models include:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>VibeVoice-1.5B\u003C\u002Fli>\n\u003Cli>VibeVoice-7B\u003C\u002Fli>\n\u003Cli>VibeVoice-Realtime-0.5B\u003C\u002Fli>\n\u003Cli>VibeVoice-ASR\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Models are hosted on Hugging Face and Microsoft repositories.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Step 5 – Generate Your First Audio\u003C\u002Fh2>\n\u003Cp>Create a text file:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-text\">Speaker 1:\nWelcome to today's AI podcast.\n\nSpeaker 2:\nToday we are discussing voice agents and generative AI.\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Run inference using the provided examples.\u003C\u002Fp>\n\u003Cp>VibeVoice generates natural multi-speaker audio automatically.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Real-Time Voice Agents with VibeVoice\u003C\u002Fh2>\n\u003Cp>One of the most exciting additions is:\u003C\u002Fp>\n\u003Ch3>VibeVoice-Realtime\u003C\u002Fh3>\n\u003Cp>Designed specifically for:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>AI Voice Agents\u003C\u002Fli>\n\u003Cli>Customer Support Bots\u003C\u002Fli>\n\u003Cli>Real-Time Assistants\u003C\u002Fli>\n\u003Cli>Interactive Applications\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Features include:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Streaming text input\u003C\u002Fli>\n\u003Cli>Low latency speech generation\u003C\u002Fli>\n\u003Cli>Continuous speech output\u003C\u002Fli>\n\u003Cli>Long-form audio support\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This makes VibeVoice a strong alternative to proprietary voice systems.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Speech Recognition with VibeVoice-ASR\u003C\u002Fh2>\n\u003Cp>Microsoft also released:\u003C\u002Fp>\n\u003Ch3>VibeVoice-ASR\u003C\u002Fh3>\n\u003Cp>Capabilities include:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>60-minute transcription\u003C\u002Fli>\n\u003Cli>Single-pass processing\u003C\u002Fli>\n\u003Cli>Speaker diarization\u003C\u002Fli>\n\u003Cli>Timestamp generation\u003C\u002Fli>\n\u003Cli>50+ languages\u003C\u002Fli>\n\u003Cli>Code-switching support\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This allows developers to transcribe long meetings, podcasts, interviews, and recordings without splitting audio into small chunks.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Example Business Use Cases\u003C\u002Fh2>\n\u003Ch3>AI Podcast Generator\u003C\u002Fh3>\n\u003Cp>Convert written scripts into fully voiced podcasts.\u003C\u002Fp>\n\u003Ch3>AI Receptionist\u003C\u002Fh3>\n\u003Cp>Answer phone calls using natural AI voices.\u003C\u002Fp>\n\u003Ch3>Audiobook Platform\u003C\u002Fh3>\n\u003Cp>Generate long-form audiobook narration.\u003C\u002Fp>\n\u003Ch3>Customer Support Agent\u003C\u002Fh3>\n\u003Cp>Provide voice-based support automatically.\u003C\u002Fp>\n\u003Ch3>Meeting Transcription\u003C\u002Fh3>\n\u003Cp>Convert meetings into searchable text.\u003C\u002Fp>\n\u003Ch3>Educational Content Creation\u003C\u002Fh3>\n\u003Cp>Create narrated training materials.\u003C\u002Fp>\n\u003Ch3>Voice-Enabled SaaS Products\u003C\u002Fh3>\n\u003Cp>Add voice generation to existing applications.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Supported Languages\u003C\u002Fh2>\n\u003Cp>VibeVoice supports multilingual speech generation and transcription.\u003C\u002Fp>\n\u003Cp>Capabilities include:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>English\u003C\u002Fli>\n\u003Cli>Mandarin\u003C\u002Fli>\n\u003Cli>Multilingual Voices\u003C\u002Fli>\n\u003Cli>Code-Switching Support\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Microsoft continues expanding language coverage across the model family.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Deployment Options\u003C\u002Fh2>\n\u003Cp>You can deploy VibeVoice on:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Local Machines\u003C\u002Fli>\n\u003Cli>Workstations\u003C\u002Fli>\n\u003Cli>Dedicated GPU Servers\u003C\u002Fli>\n\u003Cli>Docker Containers\u003C\u002Fli>\n\u003Cli>Railway\u003C\u002Fli>\n\u003Cli>RunPod\u003C\u002Fli>\n\u003Cli>Modal\u003C\u002Fli>\n\u003Cli>AWS\u003C\u002Fli>\n\u003Cli>Azure\u003C\u002Fli>\n\u003Cli>Google Cloud\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This makes it suitable for both hobby projects and production-scale voice applications.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Why Use VibeVoice?\u003C\u002Fh2>\n\u003Cp>Most voice AI platforms:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Charge monthly fees\u003C\u002Fli>\n\u003Cli>Restrict customization\u003C\u002Fli>\n\u003Cli>Limit model access\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>VibeVoice gives developers:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Open-source freedom\u003C\u002Fli>\n\u003Cli>Local deployment\u003C\u002Fli>\n\u003Cli>Long-form speech generation\u003C\u002Fli>\n\u003Cli>Multi-speaker conversations\u003C\u002Fli>\n\u003Cli>Real-time voice synthesis\u003C\u002Fli>\n\u003Cli>Speech recognition capabilities\u003C\u002Fli>\n\u003Cli>Full control over infrastructure\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Because it is open source, developers can build highly customized voice applications without vendor lock-in.\u003C\u002Fp>\n","2026-06-09",1781009874000,[418],"text-to-speech","\u002Fapi\u002Fknowledge\u002Fimage\u002F24\u002F?v=2dc7aad4cafe",{"id":421,"idKnowledge":422,"idDomain":15,"idCluster":15,"slug":423,"title":424,"description":425,"bodyMarkdown":426,"bodyHtml":427,"author":39,"date":415,"createdAt":428,"topics":429,"image":431,"hasDownload":28,"fileName":15,"youtubeId":27},"23","9049C8F8-76AB-234D-9528-B67BE198E1AD","gemini-embedding-2-geef-je-filemaker-oplossing-een-ai-geheugen","Gemini Embedding 2: Give Your FileMaker Solution an AI Memory","AI has long since stopped being just about chatting. The real power emerges when an AI model understands and can retrieve your own knowledge, documents, manuals, emails, or project information. That's where embeddings come in.","# Gemini Embedding 2: Give Your FileMaker Solution an AI Memory\n\nAI has long since stopped being just about chatting. The real power emerges when an AI model understands and can retrieve your own knowledge, documents, manuals, emails, or project information. That's where embeddings come in.\n\nWith the introduction of Gemini Embedding 2, Google has made one of the most powerful embedding models available today. But what exactly are embeddings, why do they matter, and how can you use them within a FileMaker solution?\n\n---\n\n## What are embeddings?\n\nAn embedding can be seen as a numerical representation of text.\n\nWhen you pass a document, manual, or email through an embedding model, it is converted into a long list of numbers (a vector). Those numbers do not represent the exact words, but rather the meaning of the text.\n\nAs a result, two texts that share the same meaning can lie close together in what is called the vector space, even if entirely different words are used.\n\n### Example\n\nDocument\n\n> How do I create an invoice in FileMaker?\n\nUser question\n\n> What is the way to generate a new bill?\n\nTo a traditional search engine, these look like two different texts. To an embedding model, they are virtually identical.\n\nThis is what makes semantic search possible.\n\n---\n\n## Why Gemini Embedding 2?\n\nGoogle developed Gemini Embedding 2 as the successor to earlier embedding models.\n\nKey advantages include:\n\n- Higher accuracy in semantic search\n- Strong performance on business documents\n- Support for multiple languages\n- Suitable for large knowledge bases\n- Lower cost than repeatedly sending complete documents to a Large Language Model\n- Fast processing of large volumes of data\n\nFor organisations that want to combine AI with their own knowledge, this is an essential building block.\n\n---\n\n## How does it work?\n\nThe process consists of four steps.\n\n### Step 1: Gather your knowledge\n\nThink of:\n\n- Manuals\n- Procedures\n- Project documentation\n- Client files\n- Support tickets\n- Contracts\n- Product information\n- Safety documentation\n\n### Step 2: Create embeddings\n\nEach piece of text is sent to Gemini Embedding 2.\n\nThe model returns a vector such as:\n\njson [   0.0245,   -0.8121,   0.4431,   ... ] \n\nThis vector is stored in a vector database.\n\n### Step 3: User asks a question\n\nFor example:\n\n> How do I add a user to the system?\n\nThis question is also converted into an embedding.\n\n### Step 4: Search for similar knowledge\n\nVector search is used to find which documents are closest to the question.\n\nThe retrieved documents are then sent along to a Large Language Model such as Gemini, Claude, or ChatGPT.\n\nWe call this process:\n\n## Retrieval Augmented Generation (RAG)\n\nWith RAG, an AI model can provide answers based on your own knowledge rather than relying solely on its training data.\n\n---\n\n## Why is this interesting for FileMaker?\n\nMany organisations store their business knowledge in FileMaker.\n\nThink of:\n\n- CRM data\n- Tickets\n- Project files\n- Knowledge bases\n- Product documentation\n- Safety procedures\n- Contract information\n- Internal manuals\n\nTraditionally, an employee has to search using keywords.\n\nWith embeddings, a user can simply ask a question:\n\n> What procedure applies when an employee reports a near-miss?\n\nThe AI then automatically searches for the most relevant documents and generates an answer based on the information found.\n\n---\n\n## Practical example: HSE platform\n\nSuppose you manage an HSE platform containing:\n\n- Toolbox meetings\n- Safety instructions\n- Risk analyses\n- Incident reports\n- Procedures\n- Work permits\n\nBy embedding all documents, an intelligent knowledge assistant is created.\n\nUsers can ask questions such as:\n\n- What should I do in the event of a fall incident?\n- Which PPE is mandatory for working at height?\n- What does our procedure say about reporting a near miss?\n- What training is required for these activities?\n\nThe AI searches directly across all available documentation and presents an answer including source references.\n\n---\n\n## Combining Gemini Embedding 2 with FileMaker\n\nA possible architecture looks like this:\n\ntext FileMaker     │     ├── Documents     ├── Tickets     ├── Procedures     └── CRM data             │             ▼     Gemini Embedding 2             │             ▼       Vector Database  (Pinecone \u002F Weaviate \u002F Qdrant \u002F pgvector)             │             ▼  Gemini \u002F Claude \u002F ChatGPT             │             ▼         Answer \n\nNew documents can be processed automatically as soon as they are saved in FileMaker.\n\nThis keeps the knowledge base up to date at all times.\n\n---\n\n## When do you use embeddings?\n\nEmbeddings are valuable when you:\n\n- Have more than a few hundred documents\n- Want to support natural language use\n- Want AI to answer based on your own knowledge\n- Want to build intelligent search functionality\n- Want to feed chatbots with business information\n- Want to automate support processes\n- Want to unlock knowledge currently hidden within documents\n\nFor simple keyword search, embeddings are often not necessary.\n\nFor AI-driven knowledge platforms, they have become virtually indispensable.\n\n---\n\n## Practical applications\n\nWithin FileMaker, we are seeing applications like the following increasingly often:\n\n### AI Helpdesk\n\nAllow users to ask questions about manuals, procedures, and work instructions.\n\n### Smart document search\n\nFind documents by meaning rather than by keywords.\n\n### Customer support\n\nAutomatically retrieve relevant support tickets from the past.\n\n### Safety management\n\nMake safety procedures directly accessible to employees on site.\n\n### CRM Intelligence\n\nLet AI gather relevant customer information from thousands of notes and contact moments.\n\n### Project assistant\n\nQuickly find previous project experiences, solutions, and documentation.\n\n---\n\n## Conclusion\n\nGemini Embedding 2 forms an essential building block for modern AI solutions.\n\nBy converting business knowledge into vectors, it becomes possible to retrieve information not just by words, but above all by meaning.\n\nFor FileMaker developers, this opens the door to:\n\n- Intelligent knowledge bases\n- AI assistants\n- Semantic search engines\n- Advanced RAG solutions\n- Smarter helpdesks\n- Knowledge-driven chatbots\n\nWhere Large Language Models handle the generation of answers, embeddings ensure that the right knowledge is found.\n\nAnd it is precisely that combination that makes business AI truly valuable.\n\n---\n\n## Want to know more?\n\nWould you like to know how to combine Gemini Embedding 2 with FileMaker, a vector database, and an AI model such as Gemini, Claude, or ChatGPT?\n\nGet in touch with Loggix. We help organisations build AI solutions that leverage their own data, processes, and knowledge.","\u003Ch1>Gemini Embedding 2: Give Your FileMaker Solution an AI Memory\u003C\u002Fh1>\n\u003Cp>AI has long since stopped being just about chatting. The real power emerges when an AI model understands and can retrieve your own knowledge, documents, manuals, emails, or project information. That's where embeddings come in.\u003C\u002Fp>\n\u003Cp>With the introduction of Gemini Embedding 2, Google has made one of the most powerful embedding models available today. But what exactly are embeddings, why do they matter, and how can you use them within a FileMaker solution?\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>What are embeddings?\u003C\u002Fh2>\n\u003Cp>An embedding can be seen as a numerical representation of text.\u003C\u002Fp>\n\u003Cp>When you pass a document, manual, or email through an embedding model, it is converted into a long list of numbers (a vector). Those numbers do not represent the exact words, but rather the meaning of the text.\u003C\u002Fp>\n\u003Cp>As a result, two texts that share the same meaning can lie close together in what is called the vector space, even if entirely different words are used.\u003C\u002Fp>\n\u003Ch3>Example\u003C\u002Fh3>\n\u003Cp>Document\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>How do I create an invoice in FileMaker?\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>User question\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>What is the way to generate a new bill?\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>To a traditional search engine, these look like two different texts. To an embedding model, they are virtually identical.\u003C\u002Fp>\n\u003Cp>This is what makes semantic search possible.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Why Gemini Embedding 2?\u003C\u002Fh2>\n\u003Cp>Google developed Gemini Embedding 2 as the successor to earlier embedding models.\u003C\u002Fp>\n\u003Cp>Key advantages include:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Higher accuracy in semantic search\u003C\u002Fli>\n\u003Cli>Strong performance on business documents\u003C\u002Fli>\n\u003Cli>Support for multiple languages\u003C\u002Fli>\n\u003Cli>Suitable for large knowledge bases\u003C\u002Fli>\n\u003Cli>Lower cost than repeatedly sending complete documents to a Large Language Model\u003C\u002Fli>\n\u003Cli>Fast processing of large volumes of data\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>For organisations that want to combine AI with their own knowledge, this is an essential building block.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>How does it work?\u003C\u002Fh2>\n\u003Cp>The process consists of four steps.\u003C\u002Fp>\n\u003Ch3>Step 1: Gather your knowledge\u003C\u002Fh3>\n\u003Cp>Think of:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Manuals\u003C\u002Fli>\n\u003Cli>Procedures\u003C\u002Fli>\n\u003Cli>Project documentation\u003C\u002Fli>\n\u003Cli>Client files\u003C\u002Fli>\n\u003Cli>Support tickets\u003C\u002Fli>\n\u003Cli>Contracts\u003C\u002Fli>\n\u003Cli>Product information\u003C\u002Fli>\n\u003Cli>Safety documentation\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Step 2: Create embeddings\u003C\u002Fh3>\n\u003Cp>Each piece of text is sent to Gemini Embedding 2.\u003C\u002Fp>\n\u003Cp>The model returns a vector such as:\u003C\u002Fp>\n\u003Cp>json [   0.0245,   -0.8121,   0.4431,   ... ] \u003C\u002Fp>\n\u003Cp>This vector is stored in a vector database.\u003C\u002Fp>\n\u003Ch3>Step 3: User asks a question\u003C\u002Fh3>\n\u003Cp>For example:\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>How do I add a user to the system?\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>This question is also converted into an embedding.\u003C\u002Fp>\n\u003Ch3>Step 4: Search for similar knowledge\u003C\u002Fh3>\n\u003Cp>Vector search is used to find which documents are closest to the question.\u003C\u002Fp>\n\u003Cp>The retrieved documents are then sent along to a Large Language Model such as Gemini, Claude, or ChatGPT.\u003C\u002Fp>\n\u003Cp>We call this process:\u003C\u002Fp>\n\u003Ch2>Retrieval Augmented Generation (RAG)\u003C\u002Fh2>\n\u003Cp>With RAG, an AI model can provide answers based on your own knowledge rather than relying solely on its training data.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Why is this interesting for FileMaker?\u003C\u002Fh2>\n\u003Cp>Many organisations store their business knowledge in FileMaker.\u003C\u002Fp>\n\u003Cp>Think of:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>CRM data\u003C\u002Fli>\n\u003Cli>Tickets\u003C\u002Fli>\n\u003Cli>Project files\u003C\u002Fli>\n\u003Cli>Knowledge bases\u003C\u002Fli>\n\u003Cli>Product documentation\u003C\u002Fli>\n\u003Cli>Safety procedures\u003C\u002Fli>\n\u003Cli>Contract information\u003C\u002Fli>\n\u003Cli>Internal manuals\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Traditionally, an employee has to search using keywords.\u003C\u002Fp>\n\u003Cp>With embeddings, a user can simply ask a question:\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>What procedure applies when an employee reports a near-miss?\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>The AI then automatically searches for the most relevant documents and generates an answer based on the information found.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Practical example: HSE platform\u003C\u002Fh2>\n\u003Cp>Suppose you manage an HSE platform containing:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Toolbox meetings\u003C\u002Fli>\n\u003Cli>Safety instructions\u003C\u002Fli>\n\u003Cli>Risk analyses\u003C\u002Fli>\n\u003Cli>Incident reports\u003C\u002Fli>\n\u003Cli>Procedures\u003C\u002Fli>\n\u003Cli>Work permits\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>By embedding all documents, an intelligent knowledge assistant is created.\u003C\u002Fp>\n\u003Cp>Users can ask questions such as:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>What should I do in the event of a fall incident?\u003C\u002Fli>\n\u003Cli>Which PPE is mandatory for working at height?\u003C\u002Fli>\n\u003Cli>What does our procedure say about reporting a near miss?\u003C\u002Fli>\n\u003Cli>What training is required for these activities?\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The AI searches directly across all available documentation and presents an answer including source references.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Combining Gemini Embedding 2 with FileMaker\u003C\u002Fh2>\n\u003Cp>A possible architecture looks like this:\u003C\u002Fp>\n\u003Cp>text FileMaker     │     ├── Documents     ├── Tickets     ├── Procedures     └── CRM data             │             ▼     Gemini Embedding 2             │             ▼       Vector Database  (Pinecone \u002F Weaviate \u002F Qdrant \u002F pgvector)             │             ▼  Gemini \u002F Claude \u002F ChatGPT             │             ▼         Answer \u003C\u002Fp>\n\u003Cp>New documents can be processed automatically as soon as they are saved in FileMaker.\u003C\u002Fp>\n\u003Cp>This keeps the knowledge base up to date at all times.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>When do you use embeddings?\u003C\u002Fh2>\n\u003Cp>Embeddings are valuable when you:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Have more than a few hundred documents\u003C\u002Fli>\n\u003Cli>Want to support natural language use\u003C\u002Fli>\n\u003Cli>Want AI to answer based on your own knowledge\u003C\u002Fli>\n\u003Cli>Want to build intelligent search functionality\u003C\u002Fli>\n\u003Cli>Want to feed chatbots with business information\u003C\u002Fli>\n\u003Cli>Want to automate support processes\u003C\u002Fli>\n\u003Cli>Want to unlock knowledge currently hidden within documents\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>For simple keyword search, embeddings are often not necessary.\u003C\u002Fp>\n\u003Cp>For AI-driven knowledge platforms, they have become virtually indispensable.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Practical applications\u003C\u002Fh2>\n\u003Cp>Within FileMaker, we are seeing applications like the following increasingly often:\u003C\u002Fp>\n\u003Ch3>AI Helpdesk\u003C\u002Fh3>\n\u003Cp>Allow users to ask questions about manuals, procedures, and work instructions.\u003C\u002Fp>\n\u003Ch3>Smart document search\u003C\u002Fh3>\n\u003Cp>Find documents by meaning rather than by keywords.\u003C\u002Fp>\n\u003Ch3>Customer support\u003C\u002Fh3>\n\u003Cp>Automatically retrieve relevant support tickets from the past.\u003C\u002Fp>\n\u003Ch3>Safety management\u003C\u002Fh3>\n\u003Cp>Make safety procedures directly accessible to employees on site.\u003C\u002Fp>\n\u003Ch3>CRM Intelligence\u003C\u002Fh3>\n\u003Cp>Let AI gather relevant customer information from thousands of notes and contact moments.\u003C\u002Fp>\n\u003Ch3>Project assistant\u003C\u002Fh3>\n\u003Cp>Quickly find previous project experiences, solutions, and documentation.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Conclusion\u003C\u002Fh2>\n\u003Cp>Gemini Embedding 2 forms an essential building block for modern AI solutions.\u003C\u002Fp>\n\u003Cp>By converting business knowledge into vectors, it becomes possible to retrieve information not just by words, but above all by meaning.\u003C\u002Fp>\n\u003Cp>For FileMaker developers, this opens the door to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Intelligent knowledge bases\u003C\u002Fli>\n\u003Cli>AI assistants\u003C\u002Fli>\n\u003Cli>Semantic search engines\u003C\u002Fli>\n\u003Cli>Advanced RAG solutions\u003C\u002Fli>\n\u003Cli>Smarter helpdesks\u003C\u002Fli>\n\u003Cli>Knowledge-driven chatbots\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Where Large Language Models handle the generation of answers, embeddings ensure that the right knowledge is found.\u003C\u002Fp>\n\u003Cp>And it is precisely that combination that makes business AI truly valuable.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Want to know more?\u003C\u002Fh2>\n\u003Cp>Would you like to know how to combine Gemini Embedding 2 with FileMaker, a vector database, and an AI model such as Gemini, Claude, or ChatGPT?\u003C\u002Fp>\n\u003Cp>Get in touch with Loggix. We help organisations build AI solutions that leverage their own data, processes, and knowledge.\u003C\u002Fp>\n",1781001771000,[87,430,86],"Vectorstore","\u002Fapi\u002Fknowledge\u002Fimage\u002F23\u002F?v=f1cbc3ee8c96",{"id":433,"idKnowledge":434,"idDomain":15,"idCluster":15,"slug":435,"title":436,"description":437,"bodyMarkdown":438,"bodyHtml":439,"author":378,"date":415,"createdAt":440,"topics":441,"image":442,"hasDownload":28,"fileName":15,"youtubeId":27},"22","29E675F5-8FB2-AD4C-AFA2-5293DE52ED25","deploy-ai-agents-apis-and-backends-in-minutes-with-railway","Deploy AI Agents, APIs, and Backends in Minutes with Railway","Did you know you can deploy an AI agent, Python API, MCP server, or backend application without managing servers?\nRailway is a modern cloud deployment platform that allows developers to deploy applications directly from GitHub with almost zero DevOps experience.\nInstead of configuring virtual machines, Docker servers, SSL certificates, networking, and scaling infrastructure manually, Railway automatically builds, deploys, monitors, and scales your applications.\nWhether you're building a FastAPI backend, LangGraph agent, CrewAI workflow, Open WebUI instance, MCP server, Pipecat voice agent, or a full SaaS application, Railway makes deployment incredibly simple.","## Key Features\n\n* GitHub-based deployments\n* Automatic CI\u002FCD\n* Supports Python, Node.js, Go, Java, Rust, and Docker\n* Built-in PostgreSQL\n* Built-in Redis\n* Built-in MySQL\n* Environment variable management\n* Automatic HTTPS\n* Custom domains\n* Background workers\n* Scheduled cron jobs\n* Deployment logs\n* Metrics and monitoring\n* Automatic vertical scaling\n* Manual horizontal scaling using replicas\n* AI agent hosting\n* Template marketplace\n\n---\n\n## What is Railway?\n\nRailway is a cloud platform designed to simplify application deployment.\n\nDevelopers connect a GitHub repository, and Railway automatically:\n\n* Detects the framework\n* Builds the application\n* Deploys the application\n* Generates a public URL\n* Provides SSL certificates\n* Manages infrastructure\n\nThis eliminates much of the complexity traditionally associated with cloud providers like AWS, Azure, or Google Cloud. Railway automatically deploys applications from GitHub repositories and provides built-in deployment workflows.\n\n---\n\n## Why AI Developers Love Railway\n\nRailway has become one of the most popular deployment platforms for AI projects because it works exceptionally well with:\n\n### AI Agents\n\n* LangGraph\n* CrewAI\n* AutoGen\n* Pydantic AI\n* OpenAI Agents SDK\n\n### AI Applications\n\n* Open WebUI\n* Chatbots\n* RAG Systems\n* Knowledge Bases\n* AI Dashboards\n\n### Voice Agents\n\n* Pipecat\n* Twilio Voice Agents\n* SIP Agents\n* Customer Support Bots\n\n### MCP Servers\n\n* Model Context Protocol Servers\n* Tool Servers\n* Internal Automation Services\n\n### APIs\n\n* FastAPI\n* Flask\n* Express.js\n* NestJS\n\nMost AI agents are simply Python or Node.js applications, making Railway a natural deployment choice.\n\n---\n\n## How Railway Works\n\n### Deployment Workflow\n\n```text\nDeveloper\n     ↓\nPush Code to GitHub\n     ↓\nRailway Detects Changes\n     ↓\nAutomatic Build\n     ↓\nAutomatic Deployment\n     ↓\nPublic URL Generated\n     ↓\nApplication Live\n```\n\nWhenever code is pushed to GitHub, Railway can automatically rebuild and redeploy the application.\n\n---\n\n## Step 1 – Create a Railway Account\n\nVisit:\n\n```text\nhttps:\u002F\u002Frailway.com\n```\n\nSign up using:\n\n* GitHub\n* Google\n\nGitHub authentication is recommended because Railway integrates directly with repositories.\n\n---\n\n## Step 2 – Create a New Project\n\nAfter logging in:\n\n1. Click **New Project**\n2. Select:\n\n```text\nDeploy from GitHub Repo\n```\n\n3. Connect GitHub\n4. Select your repository\n\nRailway will automatically import the project.\n\n---\n\n## Step 3 – Deploy Your AI Agent\n\nSuppose you have:\n\n```text\nmy-agent\u002F\n├── main.py\n├── requirements.txt\n├── .env\n└── Procfile\n```\n\nOr:\n\n```text\nmy-agent\u002F\n├── app.py\n├── requirements.txt\n└── railway.json\n```\n\nRailway automatically detects Python projects and starts building them. Common frameworks are automatically recognized.\n\nExamples:\n\n* FastAPI Agent\n* CrewAI Workflow\n* LangGraph Agent\n* OpenAI Agent SDK App\n* MCP Server\n\ncan usually be deployed without additional infrastructure setup.\n\n---\n\n## Step 4 – Configure Environment Variables\n\nAI applications usually require API keys.\n\nOpen:\n\n```text\nProject\n  → Service\n     → Variables\n```\n\nAdd:\n\n```env\nOPENAI_API_KEY=xxxx\nANTHROPIC_API_KEY=xxxx\nGEMINI_API_KEY=xxxx\nTAVILY_API_KEY=xxxx\nSUPABASE_URL=xxxx\nSUPABASE_KEY=xxxx\n```\n\nRailway provides a dedicated Variables section and can even suggest variables detected from your repository.\n\n---\n\n## Step 5 – Generate a Public URL\n\nAfter deployment:\n\n1. Open your service\n2. Go to Settings\n3. Generate Domain\n\nRailway creates:\n\n```text\nhttps:\u002F\u002Fyour-app.up.railway.app\n```\n\nYour AI application is now publicly accessible.\n\n---\n\n## Step 6 – Enable Automatic Deployments\n\nRailway supports GitHub Auto Deploys.\n\nEvery time you push code:\n\n```bash\ngit add .\ngit commit -m \"update agent\"\ngit push\n```\n\nRailway automatically:\n\n* Pulls new code\n* Builds application\n* Deploys update\n\nNo manual deployment is required.\n\n---\n\n## Deploying a FastAPI AI Agent\n\nExample:\n\n```python\nfrom fastapi import FastAPI\n\napp = FastAPI()\n\n@app.get(\"\u002F\")\ndef home():\n    return {\"status\": \"running\"}\n```\n\nPush to GitHub.\n\nConnect the repository to Railway.\n\nRailway builds and deploys automatically.\n\nYour API becomes available through:\n\n```text\nhttps:\u002F\u002Fyour-app.up.railway.app\n```\n\n---\n\n## Deploying LangGraph Agents\n\nRailway is excellent for:\n\n* LangGraph APIs\n* Multi-Agent Systems\n* Agent Workflows\n* RAG Pipelines\n\nTypical architecture:\n\n```text\nUser\n  ↓\nFrontend\n  ↓\nRailway Hosted Agent\n  ↓\nOpenAI \u002F Claude\n  ↓\nTools & Databases\n```\n\n---\n\n## Deploying Open WebUI\n\nMany developers deploy Open WebUI on Railway.\n\nBenefits:\n\n* No server management\n* Automatic updates\n* Public access\n* Managed infrastructure\n\nSimply deploy using Docker or a GitHub repository.\n\n---\n\n## Deploying MCP Servers\n\nRailway is ideal for MCP servers because:\n\n* Always online\n* Public endpoints\n* Easy environment management\n* Automatic redeployment\n\nExamples:\n\n* Database MCP Server\n* CRM MCP Server\n* Knowledge Base MCP Server\n* Internal Tool MCP Server\n\n---\n\n## Databases on Railway\n\nRailway provides managed databases.\n\nAvailable options include:\n\n### PostgreSQL\n\nIdeal for:\n\n* AI Applications\n* SaaS Products\n* Agent Memory\n\n### Redis\n\nIdeal for:\n\n* Caching\n* Session Storage\n* Agent State\n\n### MySQL\n\nIdeal for:\n\n* Business Applications\n* Legacy Systems\n\nDatabases can be added directly from the Railway dashboard.\n\n---\n\n## Auto Scaling Explained\n\nOne of Railway's most useful features is scaling.\n\n### Vertical Autoscaling\n\nRailway automatically adjusts compute resources as demand increases. Vertical autoscaling is available out of the box.\n\nExample:\n\n```text\n100 Requests\n      ↓\nSmall Resources\n\n5,000 Requests\n      ↓\nMore CPU & Memory\n```\n\nThis is useful for:\n\n* AI APIs\n* RAG Applications\n* Agent Platforms\n\n---\n\n### Horizontal Scaling\n\nRailway also supports replicas.\n\nExample:\n\n```text\nReplica 1\nReplica 2\nReplica 3\n```\n\nIncoming traffic is distributed across multiple instances.\n\nUseful for:\n\n* High-traffic APIs\n* Voice Agents\n* AI SaaS Platforms\n* Production Agent Systems\n\nRailway documentation describes horizontal scaling through configurable replicas.\n\n---\n\n## Monitoring and Logs\n\nRailway provides:\n\n* Real-time logs\n* CPU usage\n* Memory usage\n* Deployment history\n* Error tracking\n\nThis helps developers debug AI agents and backend services quickly.\n\n---\n\n## Example Business Use Cases\n\n### AI Customer Support Agent\n\nDeploy a support bot powered by OpenAI.\n\n### AI Knowledge Base\n\nDeploy a RAG application using company documents.\n\n### Voice AI Agent\n\nDeploy a Pipecat voice backend.\n\n### Internal Company Assistant\n\nDeploy a private AI assistant for employees.\n\n### MCP Server\n\nExpose tools and business systems to AI agents.\n\n### SaaS Backend\n\nDeploy APIs, workers, and databases together.\n\n---\n\n## Why Use Railway?\n\nTraditional cloud providers require:\n\n* Server setup\n* Networking\n* SSL management\n* Infrastructure configuration\n* Deployment pipelines\n\nRailway removes almost all of this complexity.\n\nDevelopers simply:\n\n```text\nWrite Code\n     ↓\nPush to GitHub\n     ↓\nRailway Deploys\n```\n\nFor AI developers building agents, APIs, voice systems, MCP servers, and RAG applications, Railway is one of the fastest ways to get from code to production.\n\n---","\u003Ch2>Key Features\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>GitHub-based deployments\u003C\u002Fli>\n\u003Cli>Automatic CI\u002FCD\u003C\u002Fli>\n\u003Cli>Supports Python, Node.js, Go, Java, Rust, and Docker\u003C\u002Fli>\n\u003Cli>Built-in PostgreSQL\u003C\u002Fli>\n\u003Cli>Built-in Redis\u003C\u002Fli>\n\u003Cli>Built-in MySQL\u003C\u002Fli>\n\u003Cli>Environment variable management\u003C\u002Fli>\n\u003Cli>Automatic HTTPS\u003C\u002Fli>\n\u003Cli>Custom domains\u003C\u002Fli>\n\u003Cli>Background workers\u003C\u002Fli>\n\u003Cli>Scheduled cron jobs\u003C\u002Fli>\n\u003Cli>Deployment logs\u003C\u002Fli>\n\u003Cli>Metrics and monitoring\u003C\u002Fli>\n\u003Cli>Automatic vertical scaling\u003C\u002Fli>\n\u003Cli>Manual horizontal scaling using replicas\u003C\u002Fli>\n\u003Cli>AI agent hosting\u003C\u002Fli>\n\u003Cli>Template marketplace\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Chr>\n\u003Ch2>What is Railway?\u003C\u002Fh2>\n\u003Cp>Railway is a cloud platform designed to simplify application deployment.\u003C\u002Fp>\n\u003Cp>Developers connect a GitHub repository, and Railway automatically:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Detects the framework\u003C\u002Fli>\n\u003Cli>Builds the application\u003C\u002Fli>\n\u003Cli>Deploys the application\u003C\u002Fli>\n\u003Cli>Generates a public URL\u003C\u002Fli>\n\u003Cli>Provides SSL certificates\u003C\u002Fli>\n\u003Cli>Manages infrastructure\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This eliminates much of the complexity traditionally associated with cloud providers like AWS, Azure, or Google Cloud. Railway automatically deploys applications from GitHub repositories and provides built-in deployment workflows.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Why AI Developers Love Railway\u003C\u002Fh2>\n\u003Cp>Railway has become one of the most popular deployment platforms for AI projects because it works exceptionally well with:\u003C\u002Fp>\n\u003Ch3>AI Agents\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>LangGraph\u003C\u002Fli>\n\u003Cli>CrewAI\u003C\u002Fli>\n\u003Cli>AutoGen\u003C\u002Fli>\n\u003Cli>Pydantic AI\u003C\u002Fli>\n\u003Cli>OpenAI Agents SDK\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>AI Applications\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Open WebUI\u003C\u002Fli>\n\u003Cli>Chatbots\u003C\u002Fli>\n\u003Cli>RAG Systems\u003C\u002Fli>\n\u003Cli>Knowledge Bases\u003C\u002Fli>\n\u003Cli>AI Dashboards\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Voice Agents\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Pipecat\u003C\u002Fli>\n\u003Cli>Twilio Voice Agents\u003C\u002Fli>\n\u003Cli>SIP Agents\u003C\u002Fli>\n\u003Cli>Customer Support Bots\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>MCP Servers\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Model Context Protocol Servers\u003C\u002Fli>\n\u003Cli>Tool Servers\u003C\u002Fli>\n\u003Cli>Internal Automation Services\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>APIs\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>FastAPI\u003C\u002Fli>\n\u003Cli>Flask\u003C\u002Fli>\n\u003Cli>Express.js\u003C\u002Fli>\n\u003Cli>NestJS\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Most AI agents are simply Python or Node.js applications, making Railway a natural deployment choice.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>How Railway Works\u003C\u002Fh2>\n\u003Ch3>Deployment Workflow\u003C\u002Fh3>\n\u003Cpre>\u003Ccode class=\"language-text\">Developer\n     ↓\nPush Code to GitHub\n     ↓\nRailway Detects Changes\n     ↓\nAutomatic Build\n     ↓\nAutomatic Deployment\n     ↓\nPublic URL Generated\n     ↓\nApplication Live\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Whenever code is pushed to GitHub, Railway can automatically rebuild and redeploy the application.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Step 1 – Create a Railway Account\u003C\u002Fh2>\n\u003Cp>Visit:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-text\">https:\u002F\u002Frailway.com\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Sign up using:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>GitHub\u003C\u002Fli>\n\u003Cli>Google\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>GitHub authentication is recommended because Railway integrates directly with repositories.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Step 2 – Create a New Project\u003C\u002Fh2>\n\u003Cp>After logging in:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Click \u003Cstrong>New Project\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Select:\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cpre>\u003Ccode class=\"language-text\">Deploy from GitHub Repo\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Col start=\"3\">\n\u003Cli>Connect GitHub\u003C\u002Fli>\n\u003Cli>Select your repository\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Railway will automatically import the project.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Step 3 – Deploy Your AI Agent\u003C\u002Fh2>\n\u003Cp>Suppose you have:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-text\">my-agent\u002F\n├── main.py\n├── requirements.txt\n├── .env\n└── Procfile\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Or:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-text\">my-agent\u002F\n├── app.py\n├── requirements.txt\n└── railway.json\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Railway automatically detects Python projects and starts building them. Common frameworks are automatically recognized.\u003C\u002Fp>\n\u003Cp>Examples:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>FastAPI Agent\u003C\u002Fli>\n\u003Cli>CrewAI Workflow\u003C\u002Fli>\n\u003Cli>LangGraph Agent\u003C\u002Fli>\n\u003Cli>OpenAI Agent SDK App\u003C\u002Fli>\n\u003Cli>MCP Server\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>can usually be deployed without additional infrastructure setup.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Step 4 – Configure Environment Variables\u003C\u002Fh2>\n\u003Cp>AI applications usually require API keys.\u003C\u002Fp>\n\u003Cp>Open:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-text\">Project\n  → Service\n     → Variables\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Add:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-env\">OPENAI_API_KEY=xxxx\nANTHROPIC_API_KEY=xxxx\nGEMINI_API_KEY=xxxx\nTAVILY_API_KEY=xxxx\nSUPABASE_URL=xxxx\nSUPABASE_KEY=xxxx\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Railway provides a dedicated Variables section and can even suggest variables detected from your repository.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Step 5 – Generate a Public URL\u003C\u002Fh2>\n\u003Cp>After deployment:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Open your service\u003C\u002Fli>\n\u003Cli>Go to Settings\u003C\u002Fli>\n\u003Cli>Generate Domain\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Railway creates:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-text\">https:\u002F\u002Fyour-app.up.railway.app\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Your AI application is now publicly accessible.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Step 6 – Enable Automatic Deployments\u003C\u002Fh2>\n\u003Cp>Railway supports GitHub Auto Deploys.\u003C\u002Fp>\n\u003Cp>Every time you push code:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">git add .\ngit commit -m "update agent"\ngit push\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Railway automatically:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Pulls new code\u003C\u002Fli>\n\u003Cli>Builds application\u003C\u002Fli>\n\u003Cli>Deploys update\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>No manual deployment is required.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Deploying a FastAPI AI Agent\u003C\u002Fh2>\n\u003Cp>Example:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-python\">from fastapi import FastAPI\n\napp = FastAPI()\n\n@app.get("\u002F")\ndef home():\n    return {"status": "running"}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Push to GitHub.\u003C\u002Fp>\n\u003Cp>Connect the repository to Railway.\u003C\u002Fp>\n\u003Cp>Railway builds and deploys automatically.\u003C\u002Fp>\n\u003Cp>Your API becomes available through:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-text\">https:\u002F\u002Fyour-app.up.railway.app\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Chr>\n\u003Ch2>Deploying LangGraph Agents\u003C\u002Fh2>\n\u003Cp>Railway is excellent for:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>LangGraph APIs\u003C\u002Fli>\n\u003Cli>Multi-Agent Systems\u003C\u002Fli>\n\u003Cli>Agent Workflows\u003C\u002Fli>\n\u003Cli>RAG Pipelines\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Typical architecture:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-text\">User\n  ↓\nFrontend\n  ↓\nRailway Hosted Agent\n  ↓\nOpenAI \u002F Claude\n  ↓\nTools & Databases\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Chr>\n\u003Ch2>Deploying Open WebUI\u003C\u002Fh2>\n\u003Cp>Many developers deploy Open WebUI on Railway.\u003C\u002Fp>\n\u003Cp>Benefits:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>No server management\u003C\u002Fli>\n\u003Cli>Automatic updates\u003C\u002Fli>\n\u003Cli>Public access\u003C\u002Fli>\n\u003Cli>Managed infrastructure\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Simply deploy using Docker or a GitHub repository.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Deploying MCP Servers\u003C\u002Fh2>\n\u003Cp>Railway is ideal for MCP servers because:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Always online\u003C\u002Fli>\n\u003Cli>Public endpoints\u003C\u002Fli>\n\u003Cli>Easy environment management\u003C\u002Fli>\n\u003Cli>Automatic redeployment\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Examples:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Database MCP Server\u003C\u002Fli>\n\u003Cli>CRM MCP Server\u003C\u002Fli>\n\u003Cli>Knowledge Base MCP Server\u003C\u002Fli>\n\u003Cli>Internal Tool MCP Server\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Chr>\n\u003Ch2>Databases on Railway\u003C\u002Fh2>\n\u003Cp>Railway provides managed databases.\u003C\u002Fp>\n\u003Cp>Available options include:\u003C\u002Fp>\n\u003Ch3>PostgreSQL\u003C\u002Fh3>\n\u003Cp>Ideal for:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>AI Applications\u003C\u002Fli>\n\u003Cli>SaaS Products\u003C\u002Fli>\n\u003Cli>Agent Memory\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Redis\u003C\u002Fh3>\n\u003Cp>Ideal for:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Caching\u003C\u002Fli>\n\u003Cli>Session Storage\u003C\u002Fli>\n\u003Cli>Agent State\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>MySQL\u003C\u002Fh3>\n\u003Cp>Ideal for:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Business Applications\u003C\u002Fli>\n\u003Cli>Legacy Systems\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Databases can be added directly from the Railway dashboard.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Auto Scaling Explained\u003C\u002Fh2>\n\u003Cp>One of Railway's most useful features is scaling.\u003C\u002Fp>\n\u003Ch3>Vertical Autoscaling\u003C\u002Fh3>\n\u003Cp>Railway automatically adjusts compute resources as demand increases. Vertical autoscaling is available out of the box.\u003C\u002Fp>\n\u003Cp>Example:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-text\">100 Requests\n      ↓\nSmall Resources\n\n5,000 Requests\n      ↓\nMore CPU & Memory\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>This is useful for:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>AI APIs\u003C\u002Fli>\n\u003Cli>RAG Applications\u003C\u002Fli>\n\u003Cli>Agent Platforms\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Chr>\n\u003Ch3>Horizontal Scaling\u003C\u002Fh3>\n\u003Cp>Railway also supports replicas.\u003C\u002Fp>\n\u003Cp>Example:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-text\">Replica 1\nReplica 2\nReplica 3\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Incoming traffic is distributed across multiple instances.\u003C\u002Fp>\n\u003Cp>Useful for:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>High-traffic APIs\u003C\u002Fli>\n\u003Cli>Voice Agents\u003C\u002Fli>\n\u003Cli>AI SaaS Platforms\u003C\u002Fli>\n\u003Cli>Production Agent Systems\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Railway documentation describes horizontal scaling through configurable replicas.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Monitoring and Logs\u003C\u002Fh2>\n\u003Cp>Railway provides:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Real-time logs\u003C\u002Fli>\n\u003Cli>CPU usage\u003C\u002Fli>\n\u003Cli>Memory usage\u003C\u002Fli>\n\u003Cli>Deployment history\u003C\u002Fli>\n\u003Cli>Error tracking\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This helps developers debug AI agents and backend services quickly.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Example Business Use Cases\u003C\u002Fh2>\n\u003Ch3>AI Customer Support Agent\u003C\u002Fh3>\n\u003Cp>Deploy a support bot powered by OpenAI.\u003C\u002Fp>\n\u003Ch3>AI Knowledge Base\u003C\u002Fh3>\n\u003Cp>Deploy a RAG application using company documents.\u003C\u002Fp>\n\u003Ch3>Voice AI Agent\u003C\u002Fh3>\n\u003Cp>Deploy a Pipecat voice backend.\u003C\u002Fp>\n\u003Ch3>Internal Company Assistant\u003C\u002Fh3>\n\u003Cp>Deploy a private AI assistant for employees.\u003C\u002Fp>\n\u003Ch3>MCP Server\u003C\u002Fh3>\n\u003Cp>Expose tools and business systems to AI agents.\u003C\u002Fp>\n\u003Ch3>SaaS Backend\u003C\u002Fh3>\n\u003Cp>Deploy APIs, workers, and databases together.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Why Use Railway?\u003C\u002Fh2>\n\u003Cp>Traditional cloud providers require:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Server setup\u003C\u002Fli>\n\u003Cli>Networking\u003C\u002Fli>\n\u003Cli>SSL management\u003C\u002Fli>\n\u003Cli>Infrastructure configuration\u003C\u002Fli>\n\u003Cli>Deployment pipelines\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Railway removes almost all of this complexity.\u003C\u002Fp>\n\u003Cp>Developers simply:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-text\">Write Code\n     ↓\nPush to GitHub\n     ↓\nRailway Deploys\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>For AI developers building agents, APIs, voice systems, MCP servers, and RAG applications, Railway is one of the fastest ways to get from code to production.\u003C\u002Fp>\n\u003Chr>\n",1780997990000,[86],"\u002Fapi\u002Fknowledge\u002Fimage\u002F22\u002F?v=9a3433d456e1",{"id":444,"idKnowledge":445,"idDomain":15,"idCluster":15,"slug":446,"title":447,"description":448,"bodyMarkdown":449,"bodyHtml":450,"author":378,"date":415,"createdAt":451,"topics":452,"image":454,"hasDownload":28,"fileName":15,"youtubeId":27},"21","8C8AC1AD-D42B-4E46-BD46-8C33F6488E49","run-your-own-private-ai-workspace-for-free-with-open-webui","Run Your Own Private AI Workspace for Free with Open WebUI","Did you know you can run your own ChatGPT-like interface locally without paying for expensive AI platforms?\nOpen WebUI is an open-source, self-hosted AI platform that provides a beautiful web interface for interacting with AI models. It supports local models through Ollama, cloud models such as OpenAI and Gemini, knowledge bases, AI agents, pipelines, and multi-user collaboration.\nWhether you're an AI enthusiast, developer, consultant, or business owner, Open WebUI makes it easy to create your own private AI workspace.","## Key Features\n\n* Completely open source\n* Self-hosted AI platform\n* Works with Ollama local models\n* Supports OpenAI, Gemini, Claude, and other APIs\n* ChatGPT-like user interface\n* Document and knowledge base support\n* AI Agents and Pipelines\n* Multi-user authentication\n* Custom model management\n* RAG (Retrieval-Augmented Generation) support\n* Voice input support\n* Mobile-friendly interface\n\n---\n\n## What is Open WebUI?\n\nOpen WebUI is a self-hosted AI platform that provides a modern interface for interacting with large language models.\n\nInstead of relying on a single AI provider, Open WebUI allows users to connect local models, cloud-based AI services, custom APIs, and knowledge bases through a unified interface.\n\nIt acts as a central hub where teams and individuals can access AI tools securely while maintaining control over their data and infrastructure.\n\n---\n\n## What Can You Build?\n\nOpen WebUI can be used for:\n\n* Private ChatGPT Alternatives\n* Internal Company AI Assistants\n* Knowledge Management Systems\n* AI-Powered Customer Support\n* Document Analysis Platforms\n* AI Research Workspaces\n* Team Collaboration Tools\n* Personal AI Assistants\n* RAG Applications\n* Multi-Model AI Platforms\n\n---\n\n## How Open WebUI Works\n\nOpen WebUI sits between users and AI models.\n\n### Workflow\n\n```text\nUser\n  ↓\nOpen WebUI Interface\n  ↓\nAI Model Provider\n(Ollama, OpenAI, Gemini, Claude)\n  ↓\nResponse\n  ↓\nUser\n```\n\nThe platform manages:\n\n* Conversations\n* User authentication\n* Model selection\n* Knowledge bases\n* AI pipelines\n* File uploads\n* Agent workflows\n\nThis allows users to access multiple AI systems through a single interface.\n\n---\n\n## Prerequisites\n\nBefore installing Open WebUI, ensure you have one of the following:\n\n### Option 1 – Docker (Recommended)\n\nVerify Docker installation:\n\n```bash\ndocker --version\n```\n\n### Option 2 – Python\n\nVerify Python installation:\n\n```bash\npython --version\n```\n\nPython 3.11 or newer is recommended.\n\n---\n\n## Step 1 – Install Open WebUI Using Docker\n\nThe quickest installation method is Docker.\n\nRun:\n\n```bash\ndocker run -d \\\n-p 3000:8080 \\\n-v open-webui:\u002Fapp\u002Fbackend\u002Fdata \\\n--name open-webui \\\nghcr.io\u002Fopen-webui\u002Fopen-webui:main\n```\n\nThis command:\n\n* Downloads Open WebUI\n* Creates persistent storage\n* Starts the application\n* Exposes the web interface on port 3000\n\n---\n\n## Step 2 – Open the Application\n\nOpen your browser and navigate to:\n\n```text\nhttp:\u002F\u002Flocalhost:3000\n```\n\nYou will see the Open WebUI welcome screen.\n\n---\n\n## Step 3 – Create an Administrator Account\n\nWhen Open WebUI starts for the first time:\n\n1. Create your administrator account.\n2. Enter your email.\n3. Create a password.\n4. Complete the setup process.\n\nThe first registered user automatically becomes the administrator.\n\n---\n\n## Step 4 – Connect AI Models\n\nOpen WebUI supports both local and cloud-based AI models.\n\n### Option A – Connect Ollama\n\nInstall Ollama:\n\n```bash\ncurl -fsSL https:\u002F\u002Follama.com\u002Finstall.sh | sh\n```\n\nDownload a model:\n\n```bash\nollama pull llama3\n```\n\nStart Ollama:\n\n```bash\nollama serve\n```\n\nOpen WebUI automatically detects the Ollama server.\n\n---\n\n### Option B – Connect OpenAI\n\nNavigate to:\n\n```text\nSettings → Connections → OpenAI\n```\n\nAdd your API key:\n\n```text\nOPENAI_API_KEY\n```\n\nSave the configuration.\n\n---\n\n### Option C – Connect Gemini\n\nNavigate to:\n\n```text\nSettings → Connections → Google Gemini\n```\n\nAdd your Gemini API key.\n\n---\n\n### Option D – Connect Claude\n\nNavigate to:\n\n```text\nSettings → Connections → Anthropic\n```\n\nAdd your Anthropic API key.\n\n---\n\n## Step 5 – Start Chatting\n\nOnce a model is connected:\n\n1. Click New Chat.\n2. Select a model.\n3. Enter your prompt.\n4. Receive AI-generated responses.\n\nOpen WebUI supports switching between multiple models from a single interface.\n\n---\n\n## Step 6 – Upload Documents\n\nOpen WebUI supports file uploads.\n\nExamples:\n\n* PDF Files\n* Word Documents\n* Text Files\n* Knowledge Bases\n\nUploaded files can be used to provide context during conversations.\n\nThis enables document-based AI interactions.\n\n---\n\n## Step 7 – Create Knowledge Bases\n\nKnowledge Bases allow AI models to answer questions using your own data.\n\nExamples:\n\n* Company Documentation\n* Product Manuals\n* Internal SOPs\n* Research Material\n* Client Information\n\nThe AI can search these sources before generating responses.\n\n---\n\n## Step 8 – Create AI Agents\n\nOpen WebUI supports agent-based workflows.\n\nExamples:\n\n### Customer Support Agent\n\nAnswers customer questions using company knowledge.\n\n### Research Agent\n\nSearches and summarizes information.\n\n### Documentation Agent\n\nCreates technical documentation.\n\n### Internal Assistant\n\nHelps employees access company information.\n\nAgents can be customized with instructions, tools, and knowledge sources.\n\n---\n\n## Step 9 – Use Pipelines\n\nPipelines extend Open WebUI functionality.\n\nExamples:\n\n* Custom Workflows\n* External API Integrations\n* Data Processing\n* AI Automations\n* Business Logic\n\nPipelines allow developers to build complex AI systems without modifying the core platform.\n\n---\n\n## Advanced Features\n\n### Multi-Model Support\n\nUse multiple models simultaneously:\n\n* GPT Models\n* Gemini Models\n* Claude Models\n* Llama Models\n* Mistral Models\n* Qwen Models\n\n---\n\n### Role-Based Access Control\n\nManage:\n\n* Administrators\n* Team Members\n* End Users\n\nThis makes Open WebUI suitable for organizations.\n\n---\n\n### Voice Input\n\nUsers can interact with AI using voice instead of typing.\n\n---\n\n### Model Management\n\nAdministrators can:\n\n* Add new models\n* Remove models\n* Configure providers\n* Control availability\n\n---\n\n### User Management\n\nManage:\n\n* Teams\n* Permissions\n* User Accounts\n* Shared Resources\n\n---\n\n## Example Business Use Cases\n\n### Internal Company Assistant\n\nProvide employees with instant access to company knowledge.\n\n### AI Knowledge Base\n\nSearch internal documentation using natural language.\n\n### Customer Support Portal\n\nHelp customers find answers quickly.\n\n### Research Workspace\n\nAnalyze reports, PDFs, and documents.\n\n### AI Consultancy Platform\n\nProvide clients access to multiple AI models through a single interface.\n\n### Private ChatGPT Alternative\n\nRun AI entirely on your own infrastructure.\n\n---\n\n## Deployment Options\n\nOpen WebUI can be deployed on:\n\n* Local Machines\n* VPS Servers\n* AWS\n* Azure\n* Google Cloud\n* DigitalOcean\n* Kubernetes Clusters\n* Private Infrastructure\n\nThis flexibility allows organizations to maintain full ownership of their data.\n\n---\n\n## Why Use Open WebUI?\n\nMany AI platforms lock users into a single provider and store conversations on external infrastructure.\n\nOpen WebUI gives users:\n\n* Complete ownership of data\n* Local AI support\n* Multi-model flexibility\n* Open-source transparency\n* Team collaboration features\n* Knowledge base integrations\n* AI agents and workflows\n* Enterprise deployment options\n\nBecause it is self-hosted and highly extensible, Open WebUI has become one of the most popular open-source AI platforms available today.","\u003Ch2>Key Features\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Completely open source\u003C\u002Fli>\n\u003Cli>Self-hosted AI platform\u003C\u002Fli>\n\u003Cli>Works with Ollama local models\u003C\u002Fli>\n\u003Cli>Supports OpenAI, Gemini, Claude, and other APIs\u003C\u002Fli>\n\u003Cli>ChatGPT-like user interface\u003C\u002Fli>\n\u003Cli>Document and knowledge base support\u003C\u002Fli>\n\u003Cli>AI Agents and Pipelines\u003C\u002Fli>\n\u003Cli>Multi-user authentication\u003C\u002Fli>\n\u003Cli>Custom model management\u003C\u002Fli>\n\u003Cli>RAG (Retrieval-Augmented Generation) support\u003C\u002Fli>\n\u003Cli>Voice input support\u003C\u002Fli>\n\u003Cli>Mobile-friendly interface\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Chr>\n\u003Ch2>What is Open WebUI?\u003C\u002Fh2>\n\u003Cp>Open WebUI is a self-hosted AI platform that provides a modern interface for interacting with large language models.\u003C\u002Fp>\n\u003Cp>Instead of relying on a single AI provider, Open WebUI allows users to connect local models, cloud-based AI services, custom APIs, and knowledge bases through a unified interface.\u003C\u002Fp>\n\u003Cp>It acts as a central hub where teams and individuals can access AI tools securely while maintaining control over their data and infrastructure.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>What Can You Build?\u003C\u002Fh2>\n\u003Cp>Open WebUI can be used for:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Private ChatGPT Alternatives\u003C\u002Fli>\n\u003Cli>Internal Company AI Assistants\u003C\u002Fli>\n\u003Cli>Knowledge Management Systems\u003C\u002Fli>\n\u003Cli>AI-Powered Customer Support\u003C\u002Fli>\n\u003Cli>Document Analysis Platforms\u003C\u002Fli>\n\u003Cli>AI Research Workspaces\u003C\u002Fli>\n\u003Cli>Team Collaboration Tools\u003C\u002Fli>\n\u003Cli>Personal AI Assistants\u003C\u002Fli>\n\u003Cli>RAG Applications\u003C\u002Fli>\n\u003Cli>Multi-Model AI Platforms\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Chr>\n\u003Ch2>How Open WebUI Works\u003C\u002Fh2>\n\u003Cp>Open WebUI sits between users and AI models.\u003C\u002Fp>\n\u003Ch3>Workflow\u003C\u002Fh3>\n\u003Cpre>\u003Ccode class=\"language-text\">User\n  ↓\nOpen WebUI Interface\n  ↓\nAI Model Provider\n(Ollama, OpenAI, Gemini, Claude)\n  ↓\nResponse\n  ↓\nUser\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The platform manages:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Conversations\u003C\u002Fli>\n\u003Cli>User authentication\u003C\u002Fli>\n\u003Cli>Model selection\u003C\u002Fli>\n\u003Cli>Knowledge bases\u003C\u002Fli>\n\u003Cli>AI pipelines\u003C\u002Fli>\n\u003Cli>File uploads\u003C\u002Fli>\n\u003Cli>Agent workflows\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This allows users to access multiple AI systems through a single interface.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Prerequisites\u003C\u002Fh2>\n\u003Cp>Before installing Open WebUI, ensure you have one of the following:\u003C\u002Fp>\n\u003Ch3>Option 1 – Docker (Recommended)\u003C\u002Fh3>\n\u003Cp>Verify Docker installation:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">docker --version\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>Option 2 – Python\u003C\u002Fh3>\n\u003Cp>Verify Python installation:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">python --version\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Python 3.11 or newer is recommended.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Step 1 – Install Open WebUI Using Docker\u003C\u002Fh2>\n\u003Cp>The quickest installation method is Docker.\u003C\u002Fp>\n\u003Cp>Run:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">docker run -d \\\n-p 3000:8080 \\\n-v open-webui:\u002Fapp\u002Fbackend\u002Fdata \\\n--name open-webui \\\nghcr.io\u002Fopen-webui\u002Fopen-webui:main\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>This command:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Downloads Open WebUI\u003C\u002Fli>\n\u003Cli>Creates persistent storage\u003C\u002Fli>\n\u003Cli>Starts the application\u003C\u002Fli>\n\u003Cli>Exposes the web interface on port 3000\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Chr>\n\u003Ch2>Step 2 – Open the Application\u003C\u002Fh2>\n\u003Cp>Open your browser and navigate to:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-text\">http:\u002F\u002Flocalhost:3000\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>You will see the Open WebUI welcome screen.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Step 3 – Create an Administrator Account\u003C\u002Fh2>\n\u003Cp>When Open WebUI starts for the first time:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Create your administrator account.\u003C\u002Fli>\n\u003Cli>Enter your email.\u003C\u002Fli>\n\u003Cli>Create a password.\u003C\u002Fli>\n\u003Cli>Complete the setup process.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>The first registered user automatically becomes the administrator.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Step 4 – Connect AI Models\u003C\u002Fh2>\n\u003Cp>Open WebUI supports both local and cloud-based AI models.\u003C\u002Fp>\n\u003Ch3>Option A – Connect Ollama\u003C\u002Fh3>\n\u003Cp>Install Ollama:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">curl -fsSL https:\u002F\u002Follama.com\u002Finstall.sh | sh\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Download a model:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">ollama pull llama3\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Start Ollama:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">ollama serve\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Open WebUI automatically detects the Ollama server.\u003C\u002Fp>\n\u003Chr>\n\u003Ch3>Option B – Connect OpenAI\u003C\u002Fh3>\n\u003Cp>Navigate to:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-text\">Settings → Connections → OpenAI\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Add your API key:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-text\">OPENAI_API_KEY\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Save the configuration.\u003C\u002Fp>\n\u003Chr>\n\u003Ch3>Option C – Connect Gemini\u003C\u002Fh3>\n\u003Cp>Navigate to:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-text\">Settings → Connections → Google Gemini\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Add your Gemini API key.\u003C\u002Fp>\n\u003Chr>\n\u003Ch3>Option D – Connect Claude\u003C\u002Fh3>\n\u003Cp>Navigate to:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-text\">Settings → Connections → Anthropic\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Add your Anthropic API key.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Step 5 – Start Chatting\u003C\u002Fh2>\n\u003Cp>Once a model is connected:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Click New Chat.\u003C\u002Fli>\n\u003Cli>Select a model.\u003C\u002Fli>\n\u003Cli>Enter your prompt.\u003C\u002Fli>\n\u003Cli>Receive AI-generated responses.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Open WebUI supports switching between multiple models from a single interface.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Step 6 – Upload Documents\u003C\u002Fh2>\n\u003Cp>Open WebUI supports file uploads.\u003C\u002Fp>\n\u003Cp>Examples:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>PDF Files\u003C\u002Fli>\n\u003Cli>Word Documents\u003C\u002Fli>\n\u003Cli>Text Files\u003C\u002Fli>\n\u003Cli>Knowledge Bases\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Uploaded files can be used to provide context during conversations.\u003C\u002Fp>\n\u003Cp>This enables document-based AI interactions.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Step 7 – Create Knowledge Bases\u003C\u002Fh2>\n\u003Cp>Knowledge Bases allow AI models to answer questions using your own data.\u003C\u002Fp>\n\u003Cp>Examples:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Company Documentation\u003C\u002Fli>\n\u003Cli>Product Manuals\u003C\u002Fli>\n\u003Cli>Internal SOPs\u003C\u002Fli>\n\u003Cli>Research Material\u003C\u002Fli>\n\u003Cli>Client Information\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The AI can search these sources before generating responses.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Step 8 – Create AI Agents\u003C\u002Fh2>\n\u003Cp>Open WebUI supports agent-based workflows.\u003C\u002Fp>\n\u003Cp>Examples:\u003C\u002Fp>\n\u003Ch3>Customer Support Agent\u003C\u002Fh3>\n\u003Cp>Answers customer questions using company knowledge.\u003C\u002Fp>\n\u003Ch3>Research Agent\u003C\u002Fh3>\n\u003Cp>Searches and summarizes information.\u003C\u002Fp>\n\u003Ch3>Documentation Agent\u003C\u002Fh3>\n\u003Cp>Creates technical documentation.\u003C\u002Fp>\n\u003Ch3>Internal Assistant\u003C\u002Fh3>\n\u003Cp>Helps employees access company information.\u003C\u002Fp>\n\u003Cp>Agents can be customized with instructions, tools, and knowledge sources.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Step 9 – Use Pipelines\u003C\u002Fh2>\n\u003Cp>Pipelines extend Open WebUI functionality.\u003C\u002Fp>\n\u003Cp>Examples:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Custom Workflows\u003C\u002Fli>\n\u003Cli>External API Integrations\u003C\u002Fli>\n\u003Cli>Data Processing\u003C\u002Fli>\n\u003Cli>AI Automations\u003C\u002Fli>\n\u003Cli>Business Logic\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Pipelines allow developers to build complex AI systems without modifying the core platform.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Advanced Features\u003C\u002Fh2>\n\u003Ch3>Multi-Model Support\u003C\u002Fh3>\n\u003Cp>Use multiple models simultaneously:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>GPT Models\u003C\u002Fli>\n\u003Cli>Gemini Models\u003C\u002Fli>\n\u003Cli>Claude Models\u003C\u002Fli>\n\u003Cli>Llama Models\u003C\u002Fli>\n\u003Cli>Mistral Models\u003C\u002Fli>\n\u003Cli>Qwen Models\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Chr>\n\u003Ch3>Role-Based Access Control\u003C\u002Fh3>\n\u003Cp>Manage:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Administrators\u003C\u002Fli>\n\u003Cli>Team Members\u003C\u002Fli>\n\u003Cli>End Users\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This makes Open WebUI suitable for organizations.\u003C\u002Fp>\n\u003Chr>\n\u003Ch3>Voice Input\u003C\u002Fh3>\n\u003Cp>Users can interact with AI using voice instead of typing.\u003C\u002Fp>\n\u003Chr>\n\u003Ch3>Model Management\u003C\u002Fh3>\n\u003Cp>Administrators can:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Add new models\u003C\u002Fli>\n\u003Cli>Remove models\u003C\u002Fli>\n\u003Cli>Configure providers\u003C\u002Fli>\n\u003Cli>Control availability\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Chr>\n\u003Ch3>User Management\u003C\u002Fh3>\n\u003Cp>Manage:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Teams\u003C\u002Fli>\n\u003Cli>Permissions\u003C\u002Fli>\n\u003Cli>User Accounts\u003C\u002Fli>\n\u003Cli>Shared Resources\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Chr>\n\u003Ch2>Example Business Use Cases\u003C\u002Fh2>\n\u003Ch3>Internal Company Assistant\u003C\u002Fh3>\n\u003Cp>Provide employees with instant access to company knowledge.\u003C\u002Fp>\n\u003Ch3>AI Knowledge Base\u003C\u002Fh3>\n\u003Cp>Search internal documentation using natural language.\u003C\u002Fp>\n\u003Ch3>Customer Support Portal\u003C\u002Fh3>\n\u003Cp>Help customers find answers quickly.\u003C\u002Fp>\n\u003Ch3>Research Workspace\u003C\u002Fh3>\n\u003Cp>Analyze reports, PDFs, and documents.\u003C\u002Fp>\n\u003Ch3>AI Consultancy Platform\u003C\u002Fh3>\n\u003Cp>Provide clients access to multiple AI models through a single interface.\u003C\u002Fp>\n\u003Ch3>Private ChatGPT Alternative\u003C\u002Fh3>\n\u003Cp>Run AI entirely on your own infrastructure.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Deployment Options\u003C\u002Fh2>\n\u003Cp>Open WebUI can be deployed on:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Local Machines\u003C\u002Fli>\n\u003Cli>VPS Servers\u003C\u002Fli>\n\u003Cli>AWS\u003C\u002Fli>\n\u003Cli>Azure\u003C\u002Fli>\n\u003Cli>Google Cloud\u003C\u002Fli>\n\u003Cli>DigitalOcean\u003C\u002Fli>\n\u003Cli>Kubernetes Clusters\u003C\u002Fli>\n\u003Cli>Private Infrastructure\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This flexibility allows organizations to maintain full ownership of their data.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Why Use Open WebUI?\u003C\u002Fh2>\n\u003Cp>Many AI platforms lock users into a single provider and store conversations on external infrastructure.\u003C\u002Fp>\n\u003Cp>Open WebUI gives users:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Complete ownership of data\u003C\u002Fli>\n\u003Cli>Local AI support\u003C\u002Fli>\n\u003Cli>Multi-model flexibility\u003C\u002Fli>\n\u003Cli>Open-source transparency\u003C\u002Fli>\n\u003Cli>Team collaboration features\u003C\u002Fli>\n\u003Cli>Knowledge base integrations\u003C\u002Fli>\n\u003Cli>AI agents and workflows\u003C\u002Fli>\n\u003Cli>Enterprise deployment options\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Because it is self-hosted and highly extensible, Open WebUI has become one of the most popular open-source AI platforms available today.\u003C\u002Fp>\n",1780996773000,[453],"localAI","\u002Fapi\u002Fknowledge\u002Fimage\u002F21\u002F?v=544d3740986c",{"id":456,"idKnowledge":457,"idDomain":15,"idCluster":15,"slug":458,"title":459,"description":460,"bodyMarkdown":461,"bodyHtml":462,"author":378,"date":415,"createdAt":463,"topics":464,"image":466,"hasDownload":28,"fileName":15,"youtubeId":27},"20","A9A9FFAA-466F-5345-8BAE-7481348E1D46","build-your-own-ai-voice-agent-for-free-with-pipecat","Build Your Own AI Voice Agent for Free with Pipecat","Do you know you can build a real-time AI voice agent without paying for expensive voice agent platforms?\nPipecat is an open-source Python framework for building real-time voice and multimodal AI agents.\nInstead of manually connecting speech-to-text, AI models, and voice generation services, Pipecat orchestrates everything through a low-latency pipeline designed for natural conversations.\nWhether you're building an AI receptionist, appointment booking assistant, customer support agent, or phone-based AI assistant, Pipecat provides the tools needed to get started quickly.","## Key Features\n\n* Completely open source\n* Real-time voice conversations\n* Supports OpenAI, Gemini, Claude, and local LLMs\n* Works with multiple speech-to-text providers\n* Supports various text-to-speech engines\n* WebRTC support for low-latency communication\n* Multi-agent workflows\n* Telephony integrations\n* Highly customizable pipelines\n* Production-ready architecture\n\n---\n\n## What Can You Build?\n\nPipecat can be used to create:\n\n* AI Receptionists\n* Customer Support Agents\n* Appointment Booking Assistants\n* Lead Qualification Agents\n* Recruitment Assistants\n* Internal Company Assistants\n* AI Phone Agents\n* Voice-Based SaaS Products\n* Multimodal Voice + Video Applications\n\n---\n\n## How Pipecat Works\n\nPipecat connects multiple AI services into a real-time conversational pipeline.\n\n### Voice Pipeline\n\n```text\nUser Speaks\n      ↓\nSpeech-to-Text (STT)\n      ↓\nLarge Language Model (LLM)\n      ↓\nText-to-Speech (TTS)\n      ↓\nVoice Response\n```\n\nA typical interaction follows this flow:\n\n1. User speaks through a browser, mobile app, or phone call.\n2. Speech-to-text converts audio into text.\n3. The AI model processes the request.\n4. Text-to-speech converts the response into audio.\n5. The response is streamed back to the user.\n\nPipecat manages this entire pipeline automatically while maintaining low latency and natural conversations.\n\n---\n\n## Prerequisites\n\nBefore creating your first voice agent, install the following:\n\n### Python\n\nPipecat requires Python 3.11 or newer.\n\n```bash\npython --version\n```\n\n### UV Package Manager\n\nInstall UV:\n\n```bash\npip install uv\n```\n\nOr:\n\n```bash\ncurl -LsSf https:\u002F\u002Fastral.sh\u002Fuv\u002Finstall.sh | sh\n```\n\n---\n\n## Step 1 – Install Pipecat CLI\n\nPipecat now provides a CLI that can generate complete voice agent projects automatically.\n\nInstall the CLI:\n\n```bash\nuv tool install pipecat-ai-cli\n```\n\nVerify installation:\n\n```bash\npipecat --version\n```\n\n---\n\n## Step 2 – Create a New Voice Agent\n\nLaunch the project wizard:\n\n```bash\npipecat init\n```\n\nOr generate the official quickstart project:\n\n```bash\npipecat init quickstart\n```\n\nThe wizard will guide you through selecting:\n\n### Platform\n\n* Web Application\n* Mobile Application\n* Phone Agent\n\n### Speech-to-Text Provider\n\nExamples:\n\n* Deepgram\n* Speechmatics\n* Gladia\n\n### AI Model\n\nExamples:\n\n* OpenAI\n* Gemini\n* Claude\n* Local LLMs\n\n### Text-to-Speech Provider\n\nExamples:\n\n* Cartesia\n* ElevenLabs\n* LMNT\n\nPipecat automatically generates the project structure and starter code.\n\n---\n\n## Step 3 – Configure API Keys\n\nCreate your environment file:\n\n```bash\ncp env.example .env\n```\n\nAdd your API keys:\n\n```env\nOPENAI_API_KEY=your_key\nDEEPGRAM_API_KEY=your_key\nCARTESIA_API_KEY=your_key\n```\n\nThe official Quickstart commonly uses:\n\n* OpenAI\n* Deepgram\n* Cartesia\n\nYou can replace these with other supported providers.\n\n---\n\n## Step 4 – Install Project Dependencies\n\nNavigate into your project folder:\n\n```bash\ncd my-pipecat-agent\n```\n\nInstall dependencies:\n\n```bash\nuv sync\n```\n\nThis installs all required packages for your voice agent.\n\n---\n\n## Step 5 – Run Your Voice Agent\n\nStart the application:\n\n```bash\nuv run bot.py\n```\n\nOnce started, open the local application in your browser and connect to your AI assistant.\n\nYour voice agent is now ready for testing.\n\n---\n\n## Supported AI Providers\n\n### Speech-to-Text\n\n* Deepgram\n* OpenAI STT\n* Speechmatics\n* Gladia\n\n### Large Language Models\n\n* OpenAI\n* Gemini\n* Claude\n* Local Models\n\n### Text-to-Speech\n\n* Cartesia\n* ElevenLabs\n* LMNT\n* Deepgram TTS\n\nDevelopers can mix and match providers depending on their requirements.\n\n---\n\n## Advanced Features\n\n### Multi-Agent Workflows\n\nCreate specialized agents that can hand conversations to one another.\n\nExamples:\n\n* Reception Agent\n* Sales Agent\n* Support Agent\n\n### Structured Conversation Flows\n\nBuild guided workflows such as:\n\n* Appointment Booking\n* Customer Qualification\n* Customer Support\n* Lead Collection\n\n### Telephony Integrations\n\nConnect AI agents directly to:\n\n* Twilio\n* SIP\n* PSTN Networks\n* Phone Systems\n\nThis allows AI agents to answer and place phone calls automatically.\n\n---\n\n## Example Business Use Cases\n\n### AI Receptionist\n\nAnswer incoming calls and collect customer information.\n\n### Appointment Booking Assistant\n\nSchedule appointments automatically.\n\n### Lead Qualification Agent\n\nAsk qualifying questions before transferring prospects to a sales representative.\n\n### Customer Support Agent\n\nHandle frequently asked questions 24\u002F7.\n\n### Recruitment Assistant\n\nConduct initial candidate screening interviews.\n\n### Internal Company Assistant\n\nProvide employees with instant access to company information.\n\n### Phone-Based AI Agent\n\nHandle inbound and outbound calls for businesses.\n\n---\n\n## Deployment Options\n\nAfter testing locally, you can deploy your Pipecat application to:\n\n* Pipecat Cloud\n* AWS\n* Fly.io\n* Modal\n* Cerebrium\n* Dedicated Servers\n* Self-Hosted Infrastructure\n\nThis makes Pipecat suitable for both small projects and enterprise-scale deployments.\n\n---\n\n## Why Use Pipecat?\n\nMany voice-agent platforms charge monthly fees and limit customization.\n\nPipecat gives developers:\n\n* Full control over the conversation pipeline\n* Freedom to choose AI providers\n* Open-source flexibility\n* Production scalability\n* Telephony support\n* Multi-provider integrations\n* Real-time low-latency conversations\n\nBecause it is open source, businesses can create highly customized voice agents without being locked into a single vendor.","\u003Ch2>Key Features\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Completely open source\u003C\u002Fli>\n\u003Cli>Real-time voice conversations\u003C\u002Fli>\n\u003Cli>Supports OpenAI, Gemini, Claude, and local LLMs\u003C\u002Fli>\n\u003Cli>Works with multiple speech-to-text providers\u003C\u002Fli>\n\u003Cli>Supports various text-to-speech engines\u003C\u002Fli>\n\u003Cli>WebRTC support for low-latency communication\u003C\u002Fli>\n\u003Cli>Multi-agent workflows\u003C\u002Fli>\n\u003Cli>Telephony integrations\u003C\u002Fli>\n\u003Cli>Highly customizable pipelines\u003C\u002Fli>\n\u003Cli>Production-ready architecture\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Chr>\n\u003Ch2>What Can You Build?\u003C\u002Fh2>\n\u003Cp>Pipecat can be used to create:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>AI Receptionists\u003C\u002Fli>\n\u003Cli>Customer Support Agents\u003C\u002Fli>\n\u003Cli>Appointment Booking Assistants\u003C\u002Fli>\n\u003Cli>Lead Qualification Agents\u003C\u002Fli>\n\u003Cli>Recruitment Assistants\u003C\u002Fli>\n\u003Cli>Internal Company Assistants\u003C\u002Fli>\n\u003Cli>AI Phone Agents\u003C\u002Fli>\n\u003Cli>Voice-Based SaaS Products\u003C\u002Fli>\n\u003Cli>Multimodal Voice + Video Applications\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Chr>\n\u003Ch2>How Pipecat Works\u003C\u002Fh2>\n\u003Cp>Pipecat connects multiple AI services into a real-time conversational pipeline.\u003C\u002Fp>\n\u003Ch3>Voice Pipeline\u003C\u002Fh3>\n\u003Cpre>\u003Ccode class=\"language-text\">User Speaks\n      ↓\nSpeech-to-Text (STT)\n      ↓\nLarge Language Model (LLM)\n      ↓\nText-to-Speech (TTS)\n      ↓\nVoice Response\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>A typical interaction follows this flow:\u003C\u002Fp>\n\u003Col>\n\u003Cli>User speaks through a browser, mobile app, or phone call.\u003C\u002Fli>\n\u003Cli>Speech-to-text converts audio into text.\u003C\u002Fli>\n\u003Cli>The AI model processes the request.\u003C\u002Fli>\n\u003Cli>Text-to-speech converts the response into audio.\u003C\u002Fli>\n\u003Cli>The response is streamed back to the user.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Pipecat manages this entire pipeline automatically while maintaining low latency and natural conversations.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Prerequisites\u003C\u002Fh2>\n\u003Cp>Before creating your first voice agent, install the following:\u003C\u002Fp>\n\u003Ch3>Python\u003C\u002Fh3>\n\u003Cp>Pipecat requires Python 3.11 or newer.\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">python --version\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>UV Package Manager\u003C\u002Fh3>\n\u003Cp>Install UV:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">pip install uv\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Or:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">curl -LsSf https:\u002F\u002Fastral.sh\u002Fuv\u002Finstall.sh | sh\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Chr>\n\u003Ch2>Step 1 – Install Pipecat CLI\u003C\u002Fh2>\n\u003Cp>Pipecat now provides a CLI that can generate complete voice agent projects automatically.\u003C\u002Fp>\n\u003Cp>Install the CLI:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">uv tool install pipecat-ai-cli\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Verify installation:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">pipecat --version\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Chr>\n\u003Ch2>Step 2 – Create a New Voice Agent\u003C\u002Fh2>\n\u003Cp>Launch the project wizard:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">pipecat init\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Or generate the official quickstart project:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">pipecat init quickstart\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The wizard will guide you through selecting:\u003C\u002Fp>\n\u003Ch3>Platform\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Web Application\u003C\u002Fli>\n\u003Cli>Mobile Application\u003C\u002Fli>\n\u003Cli>Phone Agent\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Speech-to-Text Provider\u003C\u002Fh3>\n\u003Cp>Examples:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Deepgram\u003C\u002Fli>\n\u003Cli>Speechmatics\u003C\u002Fli>\n\u003Cli>Gladia\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>AI Model\u003C\u002Fh3>\n\u003Cp>Examples:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>OpenAI\u003C\u002Fli>\n\u003Cli>Gemini\u003C\u002Fli>\n\u003Cli>Claude\u003C\u002Fli>\n\u003Cli>Local LLMs\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Text-to-Speech Provider\u003C\u002Fh3>\n\u003Cp>Examples:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Cartesia\u003C\u002Fli>\n\u003Cli>ElevenLabs\u003C\u002Fli>\n\u003Cli>LMNT\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Pipecat automatically generates the project structure and starter code.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Step 3 – Configure API Keys\u003C\u002Fh2>\n\u003Cp>Create your environment file:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">cp env.example .env\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Add your API keys:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-env\">OPENAI_API_KEY=your_key\nDEEPGRAM_API_KEY=your_key\nCARTESIA_API_KEY=your_key\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The official Quickstart commonly uses:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>OpenAI\u003C\u002Fli>\n\u003Cli>Deepgram\u003C\u002Fli>\n\u003Cli>Cartesia\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>You can replace these with other supported providers.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Step 4 – Install Project Dependencies\u003C\u002Fh2>\n\u003Cp>Navigate into your project folder:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">cd my-pipecat-agent\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Install dependencies:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">uv sync\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>This installs all required packages for your voice agent.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Step 5 – Run Your Voice Agent\u003C\u002Fh2>\n\u003Cp>Start the application:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-bash\">uv run bot.py\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Once started, open the local application in your browser and connect to your AI assistant.\u003C\u002Fp>\n\u003Cp>Your voice agent is now ready for testing.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Supported AI Providers\u003C\u002Fh2>\n\u003Ch3>Speech-to-Text\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Deepgram\u003C\u002Fli>\n\u003Cli>OpenAI STT\u003C\u002Fli>\n\u003Cli>Speechmatics\u003C\u002Fli>\n\u003Cli>Gladia\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Large Language Models\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>OpenAI\u003C\u002Fli>\n\u003Cli>Gemini\u003C\u002Fli>\n\u003Cli>Claude\u003C\u002Fli>\n\u003Cli>Local Models\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Text-to-Speech\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Cartesia\u003C\u002Fli>\n\u003Cli>ElevenLabs\u003C\u002Fli>\n\u003Cli>LMNT\u003C\u002Fli>\n\u003Cli>Deepgram TTS\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Developers can mix and match providers depending on their requirements.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Advanced Features\u003C\u002Fh2>\n\u003Ch3>Multi-Agent Workflows\u003C\u002Fh3>\n\u003Cp>Create specialized agents that can hand conversations to one another.\u003C\u002Fp>\n\u003Cp>Examples:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Reception Agent\u003C\u002Fli>\n\u003Cli>Sales Agent\u003C\u002Fli>\n\u003Cli>Support Agent\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Structured Conversation Flows\u003C\u002Fh3>\n\u003Cp>Build guided workflows such as:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Appointment Booking\u003C\u002Fli>\n\u003Cli>Customer Qualification\u003C\u002Fli>\n\u003Cli>Customer Support\u003C\u002Fli>\n\u003Cli>Lead Collection\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Telephony Integrations\u003C\u002Fh3>\n\u003Cp>Connect AI agents directly to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Twilio\u003C\u002Fli>\n\u003Cli>SIP\u003C\u002Fli>\n\u003Cli>PSTN Networks\u003C\u002Fli>\n\u003Cli>Phone Systems\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This allows AI agents to answer and place phone calls automatically.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Example Business Use Cases\u003C\u002Fh2>\n\u003Ch3>AI Receptionist\u003C\u002Fh3>\n\u003Cp>Answer incoming calls and collect customer information.\u003C\u002Fp>\n\u003Ch3>Appointment Booking Assistant\u003C\u002Fh3>\n\u003Cp>Schedule appointments automatically.\u003C\u002Fp>\n\u003Ch3>Lead Qualification Agent\u003C\u002Fh3>\n\u003Cp>Ask qualifying questions before transferring prospects to a sales representative.\u003C\u002Fp>\n\u003Ch3>Customer Support Agent\u003C\u002Fh3>\n\u003Cp>Handle frequently asked questions 24\u002F7.\u003C\u002Fp>\n\u003Ch3>Recruitment Assistant\u003C\u002Fh3>\n\u003Cp>Conduct initial candidate screening interviews.\u003C\u002Fp>\n\u003Ch3>Internal Company Assistant\u003C\u002Fh3>\n\u003Cp>Provide employees with instant access to company information.\u003C\u002Fp>\n\u003Ch3>Phone-Based AI Agent\u003C\u002Fh3>\n\u003Cp>Handle inbound and outbound calls for businesses.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Deployment Options\u003C\u002Fh2>\n\u003Cp>After testing locally, you can deploy your Pipecat application to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Pipecat Cloud\u003C\u002Fli>\n\u003Cli>AWS\u003C\u002Fli>\n\u003Cli>Fly.io\u003C\u002Fli>\n\u003Cli>Modal\u003C\u002Fli>\n\u003Cli>Cerebrium\u003C\u002Fli>\n\u003Cli>Dedicated Servers\u003C\u002Fli>\n\u003Cli>Self-Hosted Infrastructure\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This makes Pipecat suitable for both small projects and enterprise-scale deployments.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Why Use Pipecat?\u003C\u002Fh2>\n\u003Cp>Many voice-agent platforms charge monthly fees and limit customization.\u003C\u002Fp>\n\u003Cp>Pipecat gives developers:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Full control over the conversation pipeline\u003C\u002Fli>\n\u003Cli>Freedom to choose AI providers\u003C\u002Fli>\n\u003Cli>Open-source flexibility\u003C\u002Fli>\n\u003Cli>Production scalability\u003C\u002Fli>\n\u003Cli>Telephony support\u003C\u002Fli>\n\u003Cli>Multi-provider integrations\u003C\u002Fli>\n\u003Cli>Real-time low-latency conversations\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Because it is open source, businesses can create highly customized voice agents without being locked into a single vendor.\u003C\u002Fp>\n",1780994793000,[189,465],"Opensource","\u002Fapi\u002Fknowledge\u002Fimage\u002F20\u002F?v=f3cb0c694f0e",{"id":468,"idKnowledge":469,"idDomain":15,"idCluster":15,"slug":470,"title":471,"description":472,"bodyMarkdown":473,"bodyHtml":474,"author":39,"date":475,"createdAt":476,"topics":477,"image":479,"hasDownload":480,"fileName":481,"youtubeId":27},"3","C2FC67EC-B420-4028-9E4A-DA5AA91DCFE7","voorraad-beheer-systeem","Inventory Management System","How do you handle inventory management when your assortment consists of a complex mix of products and components.","Inventory management is not always straightforward in FileMaker, especially when as a manufacturer\u002Fsupplier you are dealing with both Products and Components. Components can appear in varying quantities across different products. Focusing solely on the finished-product inventory as a product manager is then not enough — in fact, it is not recommended.\n\nYou can write complex scripts in FileMaker to manage this, but you will quickly find that FileMaker's script engine is not fast enough when it comes to more than hundreds of products and components.\n\n## The solution\n\nUsing Python and AI, we have built a beautiful app that processes your current data and delivers a report in literally seconds. Loggix has made this app available as open source:\n\n```\ngh repo clone Loggixnl\u002Fbesteladvies-app\n```\n\nContact us for more information or assistance.","\u003Cp>Inventory management is not always straightforward in FileMaker, especially when as a manufacturer\u002Fsupplier you are dealing with both Products and Components. Components can appear in varying quantities across different products. Focusing solely on the finished-product inventory as a product manager is then not enough — in fact, it is not recommended.\u003C\u002Fp>\n\u003Cp>You can write complex scripts in FileMaker to manage this, but you will quickly find that FileMaker's script engine is not fast enough when it comes to more than hundreds of products and components.\u003C\u002Fp>\n\u003Ch2>The solution\u003C\u002Fh2>\n\u003Cp>Using Python and AI, we have built a beautiful app that processes your current data and delivers a report in literally seconds. Loggix has made this app available as open source:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>gh repo clone Loggixnl\u002Fbesteladvies-app\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Contact us for more information or assistance.\u003C\u002Fp>\n","2026-06-05",1780690279000,[23,478],"Python","\u002Fapi\u002Fknowledge\u002Fimage\u002F3\u002F?v=184f1d589a81",true,"VoorraadBeheerFMFile.zip",{"id":483,"idKnowledge":484,"idDomain":15,"idCluster":15,"slug":485,"title":486,"description":487,"bodyMarkdown":488,"bodyHtml":489,"author":39,"date":475,"createdAt":490,"topics":491,"image":494,"hasDownload":28,"fileName":15,"youtubeId":27},"2","FFF26D48-7F9D-4A47-80E9-74D43F6E62E0","filemaker-claude-skill","FileMaker Claude Skill","Use the FileMaker Claude Skill to hook up your vibe coded app to FileMaker data.","# Connect Your AI-Built App to FileMaker in Minutes with the FileMaker Claude Skill\r\rThe world of software development has changed dramatically over the past year.\r\rTools like Claude Code and Cursor have made it possible to create complete applications simply by describing what you want. User interfaces, business logic, APIs, dashboards, portals, and even mobile applications can now be generated in hours instead of weeks.\r\rMany developers are discovering a new way of building software:\r\r> Describe. Generate. Refine. Ship.\r\rBut there is still one challenge that often slows everything down:\r\rConnecting your application to real business data.\r\rFor many FileMaker developers, entrepreneurs, and businesses, their most valuable data already lives inside FileMaker. Customer records, orders, products, projects, inventory, planning, financial information, and business processes are already there.\r\rBuilding the frontend has become easy.\r\rConnecting it to FileMaker still requires API knowledge, authentication setup, documentation research, testing, and troubleshooting.\r\rUntil now.\r\r## Introducing the FileMaker Claude Skill\r\rThe FileMaker Claude Skill is a free skill created by Loggix that helps Claude understand your FileMaker environment and automatically generate the code needed to connect your applications to FileMaker.\r\rInstead of spending hours reading FileMaker Data API documentation, configuring authentication flows, creating API wrappers, and debugging requests, the skill guides Claude through the entire process.\r\rSimply install the skill, answer a few questions, and start building.\r\rWhether you're creating:\r\r- Customer portals\r- Internal business tools\r- Mobile applications\r- Dashboards\r- CRM extensions\r- Employee portals\r- SaaS products\r- Reporting tools\r- AI-powered applications\r\rthe FileMaker Claude Skill helps bridge the gap between modern AI development and your existing FileMaker solution.\r\r## Get the Skill\r\rThe FileMaker Claude Skill is available free on GitHub.\r\rClone the repository:\r\rbash gh repo clone Loggixnl\u002Ffilemaker_claude_skill \r\rOnce installed in Claude, you're ready to start connecting your applications to FileMaker.\r\r## Why We Built It\r\rAt Loggix, we've spent years building integrations between FileMaker and external systems.\r\rWe've connected FileMaker to:\r\r- Shopify\r- Magento\r- Exact Online\r- DHL\r- Mollie\r- Stripe\r- Microsoft 365\r- Google Maps\r- OpenAI\r- SendGrid\r\rand countless other APIs.\r\rWhen AI coding tools started becoming mainstream, we noticed something interesting.\r\rDevelopers could create beautiful applications in minutes, but they were still spending significant time figuring out how to connect those applications to FileMaker.\r\rThe questions kept coming:\r\r> How do I authenticate?\r\r> Which Data API endpoint should I use?\r\r> How do I create records?\r\r> How do I update records?\r\r> How do I structure my requests?\r\r> How do I handle layouts?\r\rThese are not difficult problems, but they interrupt the creative flow.\r\rThe goal of the FileMaker Claude Skill is simple:\r\rKeep developers in flow.\r\rInstead of learning the details of the FileMaker Data API, you can focus on building your application.\r\r## What the Skill Does\r\rThe skill helps Claude understand how to work with FileMaker.\r\rIt can assist with:\r\r### Authentication\r\rGenerate login logic and session handling.\r\r### Data Retrieval\r\rCreate queries to retrieve records from FileMaker.\r\r### Record Creation\r\rGenerate code to create new records.\r\r### Record Updates\r\rHandle editing and updating existing records.\r\r### Record Deletion\r\rGenerate delete operations when required.\r\r### Layout Selection\r\rGuide you in choosing the correct layouts for API access.\r\r### Framework Integration\r\rWorks with modern frameworks including:\r\r- Vue.js\r- React\r- Next.js\r- Nuxt\r- Express\r- Node.js\r- Mobile applications\r\r### Troubleshooting\r\rHelp diagnose API and connection issues.\r\r## How Installation Works\r\rInstalling the skill only takes a few minutes.\r\r### Step 1: Clone the Repository\r\rOpen your terminal and run:\r\rbash gh repo clone Loggixnl\u002Ffilemaker_claude_skill \r\r### Step 2: Add the Skill to Claude\r\rFollow the standard Claude Skill installation process and import the FileMaker Claude Skill.\r\r### Step 3: Start a New Conversation\r\rOpen a new Claude conversation.\r\r### Step 4: Activate the Skill\r\rSimply tell Claude:\r\rtext I want to connect my application to a FileMaker database. Use the FileMaker Skill. \r\rThe skill will immediately begin gathering the information it needs.\r\r### Step 5: Answer a Few Questions\r\rThe skill may ask questions such as:\r\r- What is your FileMaker Server URL?\r- What database are you connecting to?\r- Which layouts should be used?\r- What framework are you using?\r- How do you want authentication handled?\r\rOnce this information is provided, Claude has the context needed to generate working code.\r\r## Building Your First Application\r\rAfter setup, development becomes incredibly simple.\r\rImagine you want to create a customer management application.\r\rInstead of spending hours on integration setup, you can simply say:\r\rtext Create a customer management application connected to FileMaker. \r\rOr:\r\rtext Build a dashboard that shows sales statistics from FileMaker. \r\rOr:\r\rtext Create a product administration screen with search and editing capabilities. \r\rClaude will generate the frontend code while automatically incorporating the FileMaker integration requirements.\r\r## Example Use Cases\r\r### Customer Portal\r\rCreate a secure portal where customers can view and update their information.\r\r### Employee Dashboard\r\rBuild dashboards that display real-time business data from FileMaker.\r\r### Inventory Management\r\rCreate inventory applications with barcode scanning and stock management.\r\r### Mobile Apps\r\rConnect mobile applications directly to your FileMaker backend.\r\r### AI Assistants\r\rCombine OpenAI or Claude with FileMaker data to create intelligent assistants for your business.\r\r### Reporting Platforms\r\rBuild modern reporting interfaces without rebuilding your backend infrastructure.\r\r## Why This Matters\r\rFor years, businesses had to choose between:\r\r- Keeping everything inside FileMaker\r- Rebuilding everything outside FileMaker\r\rToday there is a third option.\r\rUse FileMaker as the business engine and use modern AI-driven development tools to build whatever frontend experience you need.\r\rThe FileMaker Claude Skill accelerates that process.\r\rYou don't need to replace your FileMaker solution.\r\rYou simply extend it.\r\rYour data stays where it is.\r\rYour business logic remains intact.\r\rYour development speed increases dramatically.\r\r## Who Should Use It?\r\rThe FileMaker Claude Skill is ideal for:\r\r### FileMaker Developers\r\rBuild modern web and mobile applications faster.\r\r### Consultants\r\rDeliver customer solutions in a fraction of the time.\r\r### Entrepreneurs\r\rTurn FileMaker databases into full SaaS products.\r\r### Internal Development Teams\r\rRapidly prototype and deploy business applications.\r\r### AI-First Developers\r\rLeverage FileMaker as a powerful backend without becoming an expert in its APIs.\r\r## Open and Free\r\rWe believe FileMaker has an important role to play in the future of software development.\r\rAI tools have lowered the barrier to creating software, and FileMaker remains one of the fastest ways to model and manage business data.\r\rThe FileMaker Claude Skill combines both worlds.\r\rThat's why we've made it available for everyone.\r\rUse it, improve it, share feedback, and let us know what you build.\r\r## Need Help?\r\rAt Loggix, we specialize in FileMaker development, API integrations, web applications, AI solutions, and business automation.\r\rIf you're building something ambitious and need help with architecture, integrations, scaling, or custom development, we'd love to hear from you.\r\r---\r\r### Ready to Start?\r\rClone the repository:\r\rbash gh repo clone Loggixnl\u002Ffilemaker_claude_skill \r\rInstall the skill, open Claude, and start building.\r\rYour next FileMaker-powered application may be only a few prompts away.","\u003Ch1>Connect Your AI-Built App to FileMaker in Minutes with the FileMaker Claude Skill\u003C\u002Fh1>\n\u003Cp>The world of software development has changed dramatically over the past year.\u003C\u002Fp>\n\u003Cp>Tools like Claude Code and Cursor have made it possible to create complete applications simply by describing what you want. User interfaces, business logic, APIs, dashboards, portals, and even mobile applications can now be generated in hours instead of weeks.\u003C\u002Fp>\n\u003Cp>Many developers are discovering a new way of building software:\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>Describe. Generate. Refine. Ship.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>But there is still one challenge that often slows everything down:\u003C\u002Fp>\n\u003Cp>Connecting your application to real business data.\u003C\u002Fp>\n\u003Cp>For many FileMaker developers, entrepreneurs, and businesses, their most valuable data already lives inside FileMaker. Customer records, orders, products, projects, inventory, planning, financial information, and business processes are already there.\u003C\u002Fp>\n\u003Cp>Building the frontend has become easy.\u003C\u002Fp>\n\u003Cp>Connecting it to FileMaker still requires API knowledge, authentication setup, documentation research, testing, and troubleshooting.\u003C\u002Fp>\n\u003Cp>Until now.\u003C\u002Fp>\n\u003Ch2>Introducing the FileMaker Claude Skill\u003C\u002Fh2>\n\u003Cp>The FileMaker Claude Skill is a free skill created by Loggix that helps Claude understand your FileMaker environment and automatically generate the code needed to connect your applications to FileMaker.\u003C\u002Fp>\n\u003Cp>Instead of spending hours reading FileMaker Data API documentation, configuring authentication flows, creating API wrappers, and debugging requests, the skill guides Claude through the entire process.\u003C\u002Fp>\n\u003Cp>Simply install the skill, answer a few questions, and start building.\u003C\u002Fp>\n\u003Cp>Whether you're creating:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Customer portals\u003C\u002Fli>\n\u003Cli>Internal business tools\u003C\u002Fli>\n\u003Cli>Mobile applications\u003C\u002Fli>\n\u003Cli>Dashboards\u003C\u002Fli>\n\u003Cli>CRM extensions\u003C\u002Fli>\n\u003Cli>Employee portals\u003C\u002Fli>\n\u003Cli>SaaS products\u003C\u002Fli>\n\u003Cli>Reporting tools\u003C\u002Fli>\n\u003Cli>AI-powered applications\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>the FileMaker Claude Skill helps bridge the gap between modern AI development and your existing FileMaker solution.\u003C\u002Fp>\n\u003Ch2>Get the Skill\u003C\u002Fh2>\n\u003Cp>The FileMaker Claude Skill is available free on GitHub.\u003C\u002Fp>\n\u003Cp>Clone the repository:\u003C\u002Fp>\n\u003Cp>bash gh repo clone Loggixnl\u002Ffilemaker_claude_skill \u003C\u002Fp>\n\u003Cp>Once installed in Claude, you're ready to start connecting your applications to FileMaker.\u003C\u002Fp>\n\u003Ch2>Why We Built It\u003C\u002Fh2>\n\u003Cp>At Loggix, we've spent years building integrations between FileMaker and external systems.\u003C\u002Fp>\n\u003Cp>We've connected FileMaker to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Shopify\u003C\u002Fli>\n\u003Cli>Magento\u003C\u002Fli>\n\u003Cli>Exact Online\u003C\u002Fli>\n\u003Cli>DHL\u003C\u002Fli>\n\u003Cli>Mollie\u003C\u002Fli>\n\u003Cli>Stripe\u003C\u002Fli>\n\u003Cli>Microsoft 365\u003C\u002Fli>\n\u003Cli>Google Maps\u003C\u002Fli>\n\u003Cli>OpenAI\u003C\u002Fli>\n\u003Cli>SendGrid\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>and countless other APIs.\u003C\u002Fp>\n\u003Cp>When AI coding tools started becoming mainstream, we noticed something interesting.\u003C\u002Fp>\n\u003Cp>Developers could create beautiful applications in minutes, but they were still spending significant time figuring out how to connect those applications to FileMaker.\u003C\u002Fp>\n\u003Cp>The questions kept coming:\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>How do I authenticate?\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cblockquote>\n\u003Cp>Which Data API endpoint should I use?\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cblockquote>\n\u003Cp>How do I create records?\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cblockquote>\n\u003Cp>How do I update records?\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cblockquote>\n\u003Cp>How do I structure my requests?\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cblockquote>\n\u003Cp>How do I handle layouts?\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>These are not difficult problems, but they interrupt the creative flow.\u003C\u002Fp>\n\u003Cp>The goal of the FileMaker Claude Skill is simple:\u003C\u002Fp>\n\u003Cp>Keep developers in flow.\u003C\u002Fp>\n\u003Cp>Instead of learning the details of the FileMaker Data API, you can focus on building your application.\u003C\u002Fp>\n\u003Ch2>What the Skill Does\u003C\u002Fh2>\n\u003Cp>The skill helps Claude understand how to work with FileMaker.\u003C\u002Fp>\n\u003Cp>It can assist with:\u003C\u002Fp>\n\u003Ch3>Authentication\u003C\u002Fh3>\n\u003Cp>Generate login logic and session handling.\u003C\u002Fp>\n\u003Ch3>Data Retrieval\u003C\u002Fh3>\n\u003Cp>Create queries to retrieve records from FileMaker.\u003C\u002Fp>\n\u003Ch3>Record Creation\u003C\u002Fh3>\n\u003Cp>Generate code to create new records.\u003C\u002Fp>\n\u003Ch3>Record Updates\u003C\u002Fh3>\n\u003Cp>Handle editing and updating existing records.\u003C\u002Fp>\n\u003Ch3>Record Deletion\u003C\u002Fh3>\n\u003Cp>Generate delete operations when required.\u003C\u002Fp>\n\u003Ch3>Layout Selection\u003C\u002Fh3>\n\u003Cp>Guide you in choosing the correct layouts for API access.\u003C\u002Fp>\n\u003Ch3>Framework Integration\u003C\u002Fh3>\n\u003Cp>Works with modern frameworks including:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Vue.js\u003C\u002Fli>\n\u003Cli>React\u003C\u002Fli>\n\u003Cli>Next.js\u003C\u002Fli>\n\u003Cli>Nuxt\u003C\u002Fli>\n\u003Cli>Express\u003C\u002Fli>\n\u003Cli>Node.js\u003C\u002Fli>\n\u003Cli>Mobile applications\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Troubleshooting\u003C\u002Fh3>\n\u003Cp>Help diagnose API and connection issues.\u003C\u002Fp>\n\u003Ch2>How Installation Works\u003C\u002Fh2>\n\u003Cp>Installing the skill only takes a few minutes.\u003C\u002Fp>\n\u003Ch3>Step 1: Clone the Repository\u003C\u002Fh3>\n\u003Cp>Open your terminal and run:\u003C\u002Fp>\n\u003Cp>bash gh repo clone Loggixnl\u002Ffilemaker_claude_skill \u003C\u002Fp>\n\u003Ch3>Step 2: Add the Skill to Claude\u003C\u002Fh3>\n\u003Cp>Follow the standard Claude Skill installation process and import the FileMaker Claude Skill.\u003C\u002Fp>\n\u003Ch3>Step 3: Start a New Conversation\u003C\u002Fh3>\n\u003Cp>Open a new Claude conversation.\u003C\u002Fp>\n\u003Ch3>Step 4: Activate the Skill\u003C\u002Fh3>\n\u003Cp>Simply tell Claude:\u003C\u002Fp>\n\u003Cp>text I want to connect my application to a FileMaker database. Use the FileMaker Skill. \u003C\u002Fp>\n\u003Cp>The skill will immediately begin gathering the information it needs.\u003C\u002Fp>\n\u003Ch3>Step 5: Answer a Few Questions\u003C\u002Fh3>\n\u003Cp>The skill may ask questions such as:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>What is your FileMaker Server URL?\u003C\u002Fli>\n\u003Cli>What database are you connecting to?\u003C\u002Fli>\n\u003Cli>Which layouts should be used?\u003C\u002Fli>\n\u003Cli>What framework are you using?\u003C\u002Fli>\n\u003Cli>How do you want authentication handled?\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Once this information is provided, Claude has the context needed to generate working code.\u003C\u002Fp>\n\u003Ch2>Building Your First Application\u003C\u002Fh2>\n\u003Cp>After setup, development becomes incredibly simple.\u003C\u002Fp>\n\u003Cp>Imagine you want to create a customer management application.\u003C\u002Fp>\n\u003Cp>Instead of spending hours on integration setup, you can simply say:\u003C\u002Fp>\n\u003Cp>text Create a customer management application connected to FileMaker. \u003C\u002Fp>\n\u003Cp>Or:\u003C\u002Fp>\n\u003Cp>text Build a dashboard that shows sales statistics from FileMaker. \u003C\u002Fp>\n\u003Cp>Or:\u003C\u002Fp>\n\u003Cp>text Create a product administration screen with search and editing capabilities. \u003C\u002Fp>\n\u003Cp>Claude will generate the frontend code while automatically incorporating the FileMaker integration requirements.\u003C\u002Fp>\n\u003Ch2>Example Use Cases\u003C\u002Fh2>\n\u003Ch3>Customer Portal\u003C\u002Fh3>\n\u003Cp>Create a secure portal where customers can view and update their information.\u003C\u002Fp>\n\u003Ch3>Employee Dashboard\u003C\u002Fh3>\n\u003Cp>Build dashboards that display real-time business data from FileMaker.\u003C\u002Fp>\n\u003Ch3>Inventory Management\u003C\u002Fh3>\n\u003Cp>Create inventory applications with barcode scanning and stock management.\u003C\u002Fp>\n\u003Ch3>Mobile Apps\u003C\u002Fh3>\n\u003Cp>Connect mobile applications directly to your FileMaker backend.\u003C\u002Fp>\n\u003Ch3>AI Assistants\u003C\u002Fh3>\n\u003Cp>Combine OpenAI or Claude with FileMaker data to create intelligent assistants for your business.\u003C\u002Fp>\n\u003Ch3>Reporting Platforms\u003C\u002Fh3>\n\u003Cp>Build modern reporting interfaces without rebuilding your backend infrastructure.\u003C\u002Fp>\n\u003Ch2>Why This Matters\u003C\u002Fh2>\n\u003Cp>For years, businesses had to choose between:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Keeping everything inside FileMaker\u003C\u002Fli>\n\u003Cli>Rebuilding everything outside FileMaker\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Today there is a third option.\u003C\u002Fp>\n\u003Cp>Use FileMaker as the business engine and use modern AI-driven development tools to build whatever frontend experience you need.\u003C\u002Fp>\n\u003Cp>The FileMaker Claude Skill accelerates that process.\u003C\u002Fp>\n\u003Cp>You don't need to replace your FileMaker solution.\u003C\u002Fp>\n\u003Cp>You simply extend it.\u003C\u002Fp>\n\u003Cp>Your data stays where it is.\u003C\u002Fp>\n\u003Cp>Your business logic remains intact.\u003C\u002Fp>\n\u003Cp>Your development speed increases dramatically.\u003C\u002Fp>\n\u003Ch2>Who Should Use It?\u003C\u002Fh2>\n\u003Cp>The FileMaker Claude Skill is ideal for:\u003C\u002Fp>\n\u003Ch3>FileMaker Developers\u003C\u002Fh3>\n\u003Cp>Build modern web and mobile applications faster.\u003C\u002Fp>\n\u003Ch3>Consultants\u003C\u002Fh3>\n\u003Cp>Deliver customer solutions in a fraction of the time.\u003C\u002Fp>\n\u003Ch3>Entrepreneurs\u003C\u002Fh3>\n\u003Cp>Turn FileMaker databases into full SaaS products.\u003C\u002Fp>\n\u003Ch3>Internal Development Teams\u003C\u002Fh3>\n\u003Cp>Rapidly prototype and deploy business applications.\u003C\u002Fp>\n\u003Ch3>AI-First Developers\u003C\u002Fh3>\n\u003Cp>Leverage FileMaker as a powerful backend without becoming an expert in its APIs.\u003C\u002Fp>\n\u003Ch2>Open and Free\u003C\u002Fh2>\n\u003Cp>We believe FileMaker has an important role to play in the future of software development.\u003C\u002Fp>\n\u003Cp>AI tools have lowered the barrier to creating software, and FileMaker remains one of the fastest ways to model and manage business data.\u003C\u002Fp>\n\u003Cp>The FileMaker Claude Skill combines both worlds.\u003C\u002Fp>\n\u003Cp>That's why we've made it available for everyone.\u003C\u002Fp>\n\u003Cp>Use it, improve it, share feedback, and let us know what you build.\u003C\u002Fp>\n\u003Ch2>Need Help?\u003C\u002Fh2>\n\u003Cp>At Loggix, we specialize in FileMaker development, API integrations, web applications, AI solutions, and business automation.\u003C\u002Fp>\n\u003Cp>If you're building something ambitious and need help with architecture, integrations, scaling, or custom development, we'd love to hear from you.\u003C\u002Fp>\n\u003Chr>\n\u003Ch3>Ready to Start?\u003C\u002Fh3>\n\u003Cp>Clone the repository:\u003C\u002Fp>\n\u003Cp>bash gh repo clone Loggixnl\u002Ffilemaker_claude_skill \u003C\u002Fp>\n\u003Cp>Install the skill, open Claude, and start building.\u003C\u002Fp>\n\u003Cp>Your next FileMaker-powered application may be only a few prompts away.\u003C\u002Fp>\n",1780674139000,[23,492,493],"Claude","Skills","\u002Fapi\u002Fknowledge\u002Fimage\u002F2\u002F?v=c3995c676671",{"id":496,"idKnowledge":497,"idDomain":15,"idCluster":15,"slug":498,"title":499,"description":500,"bodyMarkdown":501,"bodyHtml":502,"author":354,"date":475,"createdAt":503,"topics":504,"image":505,"hasDownload":28,"fileName":15,"youtubeId":27},"1","4A879D62-83D7-4B0E-B5E5-74085EB03313","transcribe-with-local-llm-right-into-filemaker","Transcribe with local LLM right into FileMaker","Transcribr for FileMaker lets you convert speech to text directly inside FileMaker with no cloud services, no API keys, and no data leaving your device.","Transcribr for FileMaker lets you convert speech to text directly inside FileMaker with no cloud services, no API keys, and no data leaving your device.\r\r## Key Features\r\r- 100% local processing\r- No API costs\r- No internet required\r- No OpenAI account required\r- Fast transcription using local machine resources\r- Easy integration with FileMaker solutions\r- Privacy-friendly for sensitive business data\r\r## How to Download for Free\r\r### Step 1 – Download the Installer\r\rVisit: https:\u002F\u002Ftransformingdigital.gumroad.com\u002Fl\u002Faroqx\r\r1. Click the **\"I Want This!\"** button in the top-right corner.\r2. Enter **0** as the price and proceed through the checkout process.\r3. After completing the checkout, click **Download Now**.\r\rYou will receive:\r\r**Transcribr-Installer.dmg**\r\r### Step 2 – Install Transcribr\r\r1. Locate **Transcribr-Installer.dmg** in your Downloads folder.\r2. Double-click the DMG file.\r3. Follow the installation instructions provided by the installer.\r4. Complete the installation process.\r5. Launch Transcribr from your Applications folder.\r\r## Using Transcribr with FileMaker\r\r### Quick Workflow\r\r**Audio File → Transcribr → Transcript → FileMaker**\r\r### Setup\r\r1. Create a Container field (`Audio_File`) to store recordings.\r2. Create a Text field (`Transcript`) to store transcription results.\r3. Upload or record an audio file (MP3, WAV, M4A, etc.).\r4. Export the audio from FileMaker.\r5. Pass the file to Transcribr using your preferred integration method (MBS, BaseElements, AppleScript, Shell Script, etc.).\r6. Save the returned text into the `Transcript` field.\r\r## Example Use Cases\r\r- Meeting notes\r- Customer support calls\r- HR interviews\r- Voice memos\r- Field service reports\r\r## Conclusion\r\rTranscribr provides a simple and privacy-focused way to add speech-to-text functionality to FileMaker. Since all processing happens locally, you get accurate transcriptions without cloud services, API keys, subscriptions, or data privacy concerns.\r\r## Slug\r\rtranscribr-for-filemaker-local-speech-to-text-guide\r\r## Short Description\r\rLearn how to install and use Transcribr for FileMaker to convert audio recordings into text completely offline with no APIs, cloud services, or subscription costs.","\u003Cp>Transcribr for FileMaker lets you convert speech to text directly inside FileMaker with no cloud services, no API keys, and no data leaving your device.\u003C\u002Fp>\n\u003Ch2>Key Features\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>100% local processing\u003C\u002Fli>\n\u003Cli>No API costs\u003C\u002Fli>\n\u003Cli>No internet required\u003C\u002Fli>\n\u003Cli>No OpenAI account required\u003C\u002Fli>\n\u003Cli>Fast transcription using local machine resources\u003C\u002Fli>\n\u003Cli>Easy integration with FileMaker solutions\u003C\u002Fli>\n\u003Cli>Privacy-friendly for sensitive business data\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>How to Download for Free\u003C\u002Fh2>\n\u003Ch3>Step 1 – Download the Installer\u003C\u002Fh3>\n\u003Cp>Visit: \u003Ca href=\"https:\u002F\u002Ftransformingdigital.gumroad.com\u002Fl\u002Faroqx\">https:\u002F\u002Ftransformingdigital.gumroad.com\u002Fl\u002Faroqx\u003C\u002Fa>\u003C\u002Fp>\n\u003Col>\n\u003Cli>Click the \u003Cstrong>"I Want This!"\u003C\u002Fstrong> button in the top-right corner.\u003C\u002Fli>\n\u003Cli>Enter \u003Cstrong>0\u003C\u002Fstrong> as the price and proceed through the checkout process.\u003C\u002Fli>\n\u003Cli>After completing the checkout, click \u003Cstrong>Download Now\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>You will receive:\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Transcribr-Installer.dmg\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch3>Step 2 – Install Transcribr\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Locate \u003Cstrong>Transcribr-Installer.dmg\u003C\u002Fstrong> in your Downloads folder.\u003C\u002Fli>\n\u003Cli>Double-click the DMG file.\u003C\u002Fli>\n\u003Cli>Follow the installation instructions provided by the installer.\u003C\u002Fli>\n\u003Cli>Complete the installation process.\u003C\u002Fli>\n\u003Cli>Launch Transcribr from your Applications folder.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2>Using Transcribr with FileMaker\u003C\u002Fh2>\n\u003Ch3>Quick Workflow\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Audio File → Transcribr → Transcript → FileMaker\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch3>Setup\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Create a Container field (\u003Ccode>Audio_File\u003C\u002Fcode>) to store recordings.\u003C\u002Fli>\n\u003Cli>Create a Text field (\u003Ccode>Transcript\u003C\u002Fcode>) to store transcription results.\u003C\u002Fli>\n\u003Cli>Upload or record an audio file (MP3, WAV, M4A, etc.).\u003C\u002Fli>\n\u003Cli>Export the audio from FileMaker.\u003C\u002Fli>\n\u003Cli>Pass the file to Transcribr using your preferred integration method (MBS, BaseElements, AppleScript, Shell Script, etc.).\u003C\u002Fli>\n\u003Cli>Save the returned text into the \u003Ccode>Transcript\u003C\u002Fcode> field.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2>Example Use Cases\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Meeting notes\u003C\u002Fli>\n\u003Cli>Customer support calls\u003C\u002Fli>\n\u003Cli>HR interviews\u003C\u002Fli>\n\u003Cli>Voice memos\u003C\u002Fli>\n\u003Cli>Field service reports\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Conclusion\u003C\u002Fh2>\n\u003Cp>Transcribr provides a simple and privacy-focused way to add speech-to-text functionality to FileMaker. Since all processing happens locally, you get accurate transcriptions without cloud services, API keys, subscriptions, or data privacy concerns.\u003C\u002Fp>\n\u003Ch2>Slug\u003C\u002Fh2>\n\u003Cp>transcribr-for-filemaker-local-speech-to-text-guide\u003C\u002Fp>\n\u003Ch2>Short Description\u003C\u002Fh2>\n\u003Cp>Learn how to install and use Transcribr for FileMaker to convert audio recordings into text completely offline with no APIs, cloud services, or subscription costs.\u003C\u002Fp>\n",1780670347000,[23,86],"\u002Fapi\u002Fknowledge\u002Fimage\u002F1\u002F?v=71fbe057b922",{"id":507,"idKnowledge":508,"idDomain":15,"idCluster":15,"slug":509,"title":510,"description":511,"bodyMarkdown":512,"bodyHtml":513,"author":514,"date":515,"createdAt":516,"topics":517,"image":519,"hasDownload":28,"fileName":15,"youtubeId":27},"66","83EA2CA3-1DCE-5544-8E78-F00C567441A1","filemaker-mcp-server-ai-and-hosted-fm-files","FileMaker MCP server – Ai and hosted FM files.","Connecting FileMaker to AI via MCP sounds simple — until it isn’t. From Node version traps and misleading error messages to token handling and PATH issues, setting up FileMaker with the Model Context Protocol can be a real challenge. But once everything clicks, the payoff is big: live AI access to y","![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F12\u002Fmcp.jpg)\n\n**Connecting FileMaker to modern AI tooling via the Model Context Protocol (MCP) feels, at first, like opening a door to the future. And it is. But it’s also one of those integrations where everything needs to be just right — or nothing works at all. This article walks through what MCP is, where things commonly go wrong, and why it’s absolutely worth pushing through.**\n\n#### What Is MCP — and Why FileMaker Developers Care?\n\n**MCP (Model Context Protocol)** is a standardized way for AI models (like Claude) to:\n\n-   Discover available tools and schemas\n-   Query external systems\n-   Reason over live data instead of static prompts\n\nFor **FileMaker developers**, this is huge:\n\n-   Your FileMaker file becomes queryable context\n    \n-   Scripts, tables, and data models can be exposed as AI tools\n    \n-   Claude can reason _with_ your business data, not just about it\n    \n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F12\u002FFileMakerMcpFlow-scaled.png)\n\n#### How to get started?\n\nStart by reading:  [https:\u002F\u002Fwww.claris.com\u002Fblog\u002F2025\u002Fwhy-mcp-matters-for-claris-filemaker-developers](https:\u002F\u002Fwww.claris.com\u002Fblog\u002F2025\u002Fwhy-mcp-matters-for-claris-filemaker-developers)\n\nAnd then dive in deeper:  [https:\u002F\u002Fhelp.claris.com\u002Fen\u002Fclaris-mcp-help\u002Fcontent\u002Fgetting-started.html](https:\u002F\u002Fhelp.claris.com\u002Fen\u002Fclaris-mcp-help\u002Fcontent\u002Fgetting-started.html)\n\nOr sit back and watch:  [https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=PAUQiULMghk](https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=PAUQiULMghk)\n\n#### Where Things might Hurt 😅\n\nOn paper, the setup looks straightforward. Just Enable Data API \u002F OData, create a Claris MCP context, add an MCP server config in Claude (or you MCP Client of choice) and Done. In reality, there are a few **sharp edges** that might catch you if you are not a pro...\n\n\"Error: Preflight connection failed: Unable to connect to FileMaker server. Verify account credentials and ensure the account has the appropriate extended privileges enabled (fmodata and fmrest).\"\n\nThis is the most misleading error. In many cases, your credentials _are_ correct and fmrest and fmodata _are_ enabled. Yet MCP still fails — because the error often isn’t FileMaker at all.\n\n##### **Solution: Node.js version mismatches (the silent killer)**\n\nMCP tooling (mcp-remote) depends on modern Node features via undici. If Claude ends up running: Node 18 (or earlier), via nvm or via an inherited PATH you didn’t expect, Clause might throw errors that are not easy to explain.\n\nErrors like \"ReferenceError: File is not defined\" have nothing to do with FileMaker and might point you in the wrong direction. On macOS, GUI apps (like Claude Desktop) **do not inherit your shell environment**. So even if node -v looks fine in Terminal, Claude may still be using an older runtime.  \n  \nIf you run into this, you might try this MCP Config >\n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F12\u002Fclaude.jpg)\n\n{\n  \"mcpServers\": {\n    \"claris\": {\n      \"command\": \"\u002Fusr\u002Flocal\u002Fopt\u002Fnode@22\u002Fbin\u002Fnode\",\n      \"args\": \\[\n        \"\u002Fusr\u002Flocal\u002Fopt\u002Fnode@22\u002Flib\u002Fnode\\_modules\u002Fnpm\u002Fbin\u002Fnpx-cli.js\",\n        \"-y\",\n        \"mcp-remote@latest\",\n        \"https:\u002F\u002Fmcp.connect.claris.com\u002Forg\u002F290\u002Fctx\u002F7go8e7jfykoga\u002Fsse\",\n        \"--header\",\n        \"Authorization: static YOUR\\_REAL\\_TOKEN\\_HERE\",\n        \"--transport\",\n        \"sse-only\"\n      \\],\n      \"env\": {\n        \"PATH\": \"\u002Fusr\u002Flocal\u002Fopt\u002Fnode@22\u002Fbin:\u002Fusr\u002Flocal\u002Fbin:\u002Fusr\u002Fbin:\u002Fbin:\u002Fusr\u002Fsbin:\u002Fsbin\"\n      }\n    }\n  }\n}\n\n#### Why It’s Worth It (Really)\n\nOnce everything clicks into place, something shifts. Suddenly:\n\n-   Claude understands your FileMaker schema\n    \n-   You can expose **domain-specific tools**\n    \n-   Queries become _contextual_, not generic\n    \n-   You stop copy-pasting data into prompts\n    \n\n#### Real benefits for FileMaker solutions\n\n-   **AI-assisted reporting** directly on live data\n    \n-   **Natural-language querying** of business records\n    \n-   **Script orchestration** via AI reasoning\n    \n-   **Safer AI usage**, because access is structured and scoped\n    \n\nInstead of “AI guessing”, you get **AI collaborating**.\n\n##### After reading and watching still running into problems? Use ChatGPT or call a human at Loggix 😅\n\nShare\n\n[](https:\u002F\u002Fwww.facebook.com\u002Fsharer\u002Fsharer.php?u=https%3A%2F%2Floggix.com%2Ffilemaker-mcp-server-ai-and-hosted-fm-files-36551%2F)[](https:\u002F\u002Ftwitter.com\u002Fintent\u002Ftweet?text=FileMaker+MCP+server+-+Ai+and+hosted+FM+files.+-+Loggix+%7C+Software+Development.+https%3A%2F%2Floggix.com%2Ffilemaker-mcp-server-ai-and-hosted-fm-files-36551%2F)[](https:\u002F\u002Fwww.linkedin.com\u002FshareArticle?mini=true&url=https%3A%2F%2Floggix.com%2Ffilemaker-mcp-server-ai-and-hosted-fm-files-36551%2F)[](https:\u002F\u002Fpinterest.com\u002Fpin\u002Ffind\u002F?url=https%3A%2F%2Floggix.com%2Ffilemaker-mcp-server-ai-and-hosted-fm-files-36551%2F)","\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F12\u002Fmcp.jpg\" alt=\"\">\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Connecting FileMaker to modern AI tooling via the Model Context Protocol (MCP) feels, at first, like opening a door to the future. And it is. But it’s also one of those integrations where everything needs to be just right — or nothing works at all. This article walks through what MCP is, where things commonly go wrong, and why it’s absolutely worth pushing through.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch4>What Is MCP — and Why FileMaker Developers Care?\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>MCP (Model Context Protocol)\u003C\u002Fstrong> is a standardized way for AI models (like Claude) to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Discover available tools and schemas\u003C\u002Fli>\n\u003Cli>Query external systems\u003C\u002Fli>\n\u003Cli>Reason over live data instead of static prompts\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>For \u003Cstrong>FileMaker developers\u003C\u002Fstrong>, this is huge:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cp>Your FileMaker file becomes queryable context\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>Scripts, tables, and data models can be exposed as AI tools\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>Claude can reason \u003Cem>with\u003C\u002Fem> your business data, not just about it\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F12\u002FFileMakerMcpFlow-scaled.png\" alt=\"\">\u003C\u002Fp>\n\u003Ch4>How to get started?\u003C\u002Fh4>\n\u003Cp>Start by reading:  \u003Ca href=\"https:\u002F\u002Fwww.claris.com\u002Fblog\u002F2025\u002Fwhy-mcp-matters-for-claris-filemaker-developers\">https:\u002F\u002Fwww.claris.com\u002Fblog\u002F2025\u002Fwhy-mcp-matters-for-claris-filemaker-developers\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>And then dive in deeper:  \u003Ca href=\"https:\u002F\u002Fhelp.claris.com\u002Fen\u002Fclaris-mcp-help\u002Fcontent\u002Fgetting-started.html\">https:\u002F\u002Fhelp.claris.com\u002Fen\u002Fclaris-mcp-help\u002Fcontent\u002Fgetting-started.html\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>Or sit back and watch:  \u003Ca href=\"https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=PAUQiULMghk\">https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=PAUQiULMghk\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch4>Where Things might Hurt 😅\u003C\u002Fh4>\n\u003Cp>On paper, the setup looks straightforward. Just Enable Data API \u002F OData, create a Claris MCP context, add an MCP server config in Claude (or you MCP Client of choice) and Done. In reality, there are a few \u003Cstrong>sharp edges\u003C\u002Fstrong> that might catch you if you are not a pro...\u003C\u002Fp>\n\u003Cp>"Error: Preflight connection failed: Unable to connect to FileMaker server. Verify account credentials and ensure the account has the appropriate extended privileges enabled (fmodata and fmrest)."\u003C\u002Fp>\n\u003Cp>This is the most misleading error. In many cases, your credentials \u003Cem>are\u003C\u002Fem> correct and fmrest and fmodata \u003Cem>are\u003C\u002Fem> enabled. Yet MCP still fails — because the error often isn’t FileMaker at all.\u003C\u002Fp>\n\u003Ch5>\u003Cstrong>Solution: Node.js version mismatches (the silent killer)\u003C\u002Fstrong>\u003C\u002Fh5>\n\u003Cp>MCP tooling (mcp-remote) depends on modern Node features via undici. If Claude ends up running: Node 18 (or earlier), via nvm or via an inherited PATH you didn’t expect, Clause might throw errors that are not easy to explain.\u003C\u002Fp>\n\u003Cp>Errors like "ReferenceError: File is not defined" have nothing to do with FileMaker and might point you in the wrong direction. On macOS, GUI apps (like Claude Desktop) \u003Cstrong>do not inherit your shell environment\u003C\u002Fstrong>. So even if node -v looks fine in Terminal, Claude may still be using an older runtime.  \u003C\u002Fp>\n\u003Cp>If you run into this, you might try this MCP Config >\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F12\u002Fclaude.jpg\" alt=\"\">\u003C\u002Fp>\n\u003Cp>{\n  "mcpServers": {\n    "claris": {\n      "command": "\u002Fusr\u002Flocal\u002Fopt\u002Fnode@22\u002Fbin\u002Fnode",\n      "args": [\n        "\u002Fusr\u002Flocal\u002Fopt\u002Fnode@22\u002Flib\u002Fnode_modules\u002Fnpm\u002Fbin\u002Fnpx-cli.js",\n        "-y",\n        "mcp-remote@latest",\n        "\u003Ca href=\"https:\u002F\u002Fmcp.connect.claris.com\u002Forg\u002F290\u002Fctx\u002F7go8e7jfykoga\u002Fsse\">https:\u002F\u002Fmcp.connect.claris.com\u002Forg\u002F290\u002Fctx\u002F7go8e7jfykoga\u002Fsse\u003C\u002Fa>",\n        "--header",\n        "Authorization: static YOUR_REAL_TOKEN_HERE",\n        "--transport",\n        "sse-only"\n      ],\n      "env": {\n        "PATH": "\u002Fusr\u002Flocal\u002Fopt\u002Fnode@22\u002Fbin:\u002Fusr\u002Flocal\u002Fbin:\u002Fusr\u002Fbin:\u002Fbin:\u002Fusr\u002Fsbin:\u002Fsbin"\n      }\n    }\n  }\n}\u003C\u002Fp>\n\u003Ch4>Why It’s Worth It (Really)\u003C\u002Fh4>\n\u003Cp>Once everything clicks into place, something shifts. Suddenly:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cp>Claude understands your FileMaker schema\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>You can expose \u003Cstrong>domain-specific tools\u003C\u002Fstrong>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>Queries become \u003Cem>contextual\u003C\u002Fem>, not generic\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>You stop copy-pasting data into prompts\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Real benefits for FileMaker solutions\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cp>\u003Cstrong>AI-assisted reporting\u003C\u002Fstrong> directly on live data\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>\u003Cstrong>Natural-language querying\u003C\u002Fstrong> of business records\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>\u003Cstrong>Script orchestration\u003C\u002Fstrong> via AI reasoning\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>\u003Cstrong>Safer AI usage\u003C\u002Fstrong>, because access is structured and scoped\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Instead of “AI guessing”, you get \u003Cstrong>AI collaborating\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Ch5>After reading and watching still running into problems? Use ChatGPT or call a human at Loggix 😅\u003C\u002Fh5>\n\u003Cp>Share\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwww.facebook.com\u002Fsharer\u002Fsharer.php?u=https%3A%2F%2Floggix.com%2Ffilemaker-mcp-server-ai-and-hosted-fm-files-36551%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Ftwitter.com\u002Fintent\u002Ftweet?text=FileMaker+MCP+server+-+Ai+and+hosted+FM+files.+-+Loggix+%7C+Software+Development.+https%3A%2F%2Floggix.com%2Ffilemaker-mcp-server-ai-and-hosted-fm-files-36551%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Fwww.linkedin.com\u002FshareArticle?mini=true&url=https%3A%2F%2Floggix.com%2Ffilemaker-mcp-server-ai-and-hosted-fm-files-36551%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Fpinterest.com\u002Fpin\u002Ffind\u002F?url=https%3A%2F%2Floggix.com%2Ffilemaker-mcp-server-ai-and-hosted-fm-files-36551%2F\">\u003C\u002Fa>\u003C\u002Fp>\n","jeroen","2025-12-20",1781520659000,[23,518],"FMBetterForms","\u002Fapi\u002Fknowledge\u002Fimage\u002F66\u002F?v=3ec65f011ce3",{"id":521,"idKnowledge":522,"idDomain":15,"idCluster":15,"slug":523,"title":524,"description":525,"bodyMarkdown":526,"bodyHtml":527,"author":514,"date":515,"createdAt":528,"topics":529,"image":530,"hasDownload":28,"fileName":15,"youtubeId":27},"65","1467ACDF-8301-7F47-A91A-DE48D7B018DF","talking-to-your-data-with-the-filemaker-app-assistant","Talking to Your Data with the FileMaker App Assistant","Discover how to add AI-powered chat to your custom apps with App Assistant. This new Claris FileMaker 2025 add-on leverages natural language script steps to let users query their data through a familiar chat interface.","**For years, we’ve built our Claris FileMaker apps with a specific philosophy: if a user wants to find something, we build a button. If they need a report, we design a layout. We’ve spent decades creating complex filters and intricate search scripts, all to help users navigate their own data.**\n\n**But the way we interact with technology is shifting. We no longer want to hunt through menus; we want to ask a question and get an answer. With the release of the new App Assistant, Claris is handing us the keys to that future.**\n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F12\u002FAdd_on1-scaled-e1766244089825.png)\n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F12\u002FAdd_on2-scaled-e1766245393969.png)\n\n#### The End of the \"Find\" Mode Struggle\n\nImagine a sales manager named Sarah. She’s in a hurry and needs to know which clients in the Northeast haven’t placed an order in the last six months. In a traditional app, Sarah has to navigate to the \"Invoices\" layout, enter Find mode, select a date range, choose a region, and click \"Perform Find.\"\n\nWith the App Assistant integrated into her FileMaker solution, Sarah simply types: _\"Show me my Northeast clients who have been quiet for half a year.\"_\n\nThe magic isn't just that the app understands her; it’s that the app knows how to act on it. Within seconds, the App Assistant translates her natural language into a FileMaker script, filters the records, and presents her with exactly what she needs.\n\n#### How the Magic Works (Without the Complexity)\n\nUnder the hood, the App Assistant isn't just a simple chatbot. It’s a sophisticated bridge between your local FileMaker data and the power of Large Language Models (LLMs).\n\nUsing the new natural language script steps introduced in FileMaker 2025, the App Assistant looks at your tables and fields and learns the \"language\" of your app. When a user asks a question, the assistant uses Semantic Search to understand the intent behind the words. It doesn't just look for keywords; it understands context.\n\nThe best part for developers? It’s an add-on. You don’t have to spend weeks coding a custom AI engine. Claris has provided the App Assistant as a blueprint, showing us exactly how to implement AI-powered chat, history tracking, and data visualization in a way that feels native to the FileMaker experience.\n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F12\u002FAdd_on3-scaled-e1766245370877.png)\n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F12\u002FAdd_on4-scaled-e1766245346403.png)\n\n#### Beyond Simple Searches\n\nThe real \"aha!\" moment comes when you realize the App Assistant can do more than just find records. Because it is deeply integrated with the FileMaker platform, it can perform actions. You can ask it to summarize a long list of meeting notes, draft a follow-up email based on a customer's history, or even suggest a restock level for a specific product.\n\nWe are moving away from apps that are just digital filing cabinets and toward apps that act as intelligent partners.\n\n#### Stepping Into the Future\n\nIntegrating AI into your workflow can feel like a daunting leap, but the App Assistant is designed to be the perfect first step. It’s an educational tool as much as it is a feature, giving developers a clear path to follow as they modernize their custom apps.\n\nThe era of \"clicking and searching\" is slowly giving way to the era of \"asking and doing.\" By bringing the App Assistant into your FileMaker toolkit, you aren't just updating your software—you’re changing the conversation your users have with their data.\n\n##### Ready to get started?\n\nYou can download the App Assistant example and documentation directly from the Claris Support site. It’s time to give your FileMaker apps Ai intelligence. If you need help with that, feel free to contact us.\n\nShare\n\n[](https:\u002F\u002Fwww.facebook.com\u002Fsharer\u002Fsharer.php?u=https%3A%2F%2Floggix.com%2Ftalking-to-your-data-with-the-filemaker-app-assistant-36558%2F)[](https:\u002F\u002Ftwitter.com\u002Fintent\u002Ftweet?text=Talking+to+Your+Data+with+the+FileMaker+App+Assistant+-+Loggix+%7C+Software+Development.+https%3A%2F%2Floggix.com%2Ftalking-to-your-data-with-the-filemaker-app-assistant-36558%2F)[](https:\u002F\u002Fwww.linkedin.com\u002FshareArticle?mini=true&url=https%3A%2F%2Floggix.com%2Ftalking-to-your-data-with-the-filemaker-app-assistant-36558%2F)[](https:\u002F\u002Fpinterest.com\u002Fpin\u002Ffind\u002F?url=https%3A%2F%2Floggix.com%2Ftalking-to-your-data-with-the-filemaker-app-assistant-36558%2F)","\u003Cp>\u003Cstrong>For years, we’ve built our Claris FileMaker apps with a specific philosophy: if a user wants to find something, we build a button. If they need a report, we design a layout. We’ve spent decades creating complex filters and intricate search scripts, all to help users navigate their own data.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>But the way we interact with technology is shifting. We no longer want to hunt through menus; we want to ask a question and get an answer. With the release of the new App Assistant, Claris is handing us the keys to that future.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F12\u002FAdd_on1-scaled-e1766244089825.png\" alt=\"\">\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F12\u002FAdd_on2-scaled-e1766245393969.png\" alt=\"\">\u003C\u002Fp>\n\u003Ch4>The End of the "Find" Mode Struggle\u003C\u002Fh4>\n\u003Cp>Imagine a sales manager named Sarah. She’s in a hurry and needs to know which clients in the Northeast haven’t placed an order in the last six months. In a traditional app, Sarah has to navigate to the "Invoices" layout, enter Find mode, select a date range, choose a region, and click "Perform Find."\u003C\u002Fp>\n\u003Cp>With the App Assistant integrated into her FileMaker solution, Sarah simply types: \u003Cem>"Show me my Northeast clients who have been quiet for half a year."\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>The magic isn't just that the app understands her; it’s that the app knows how to act on it. Within seconds, the App Assistant translates her natural language into a FileMaker script, filters the records, and presents her with exactly what she needs.\u003C\u002Fp>\n\u003Ch4>How the Magic Works (Without the Complexity)\u003C\u002Fh4>\n\u003Cp>Under the hood, the App Assistant isn't just a simple chatbot. It’s a sophisticated bridge between your local FileMaker data and the power of Large Language Models (LLMs).\u003C\u002Fp>\n\u003Cp>Using the new natural language script steps introduced in FileMaker 2025, the App Assistant looks at your tables and fields and learns the "language" of your app. When a user asks a question, the assistant uses Semantic Search to understand the intent behind the words. It doesn't just look for keywords; it understands context.\u003C\u002Fp>\n\u003Cp>The best part for developers? It’s an add-on. You don’t have to spend weeks coding a custom AI engine. Claris has provided the App Assistant as a blueprint, showing us exactly how to implement AI-powered chat, history tracking, and data visualization in a way that feels native to the FileMaker experience.\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F12\u002FAdd_on3-scaled-e1766245370877.png\" alt=\"\">\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F12\u002FAdd_on4-scaled-e1766245346403.png\" alt=\"\">\u003C\u002Fp>\n\u003Ch4>Beyond Simple Searches\u003C\u002Fh4>\n\u003Cp>The real "aha!" moment comes when you realize the App Assistant can do more than just find records. Because it is deeply integrated with the FileMaker platform, it can perform actions. You can ask it to summarize a long list of meeting notes, draft a follow-up email based on a customer's history, or even suggest a restock level for a specific product.\u003C\u002Fp>\n\u003Cp>We are moving away from apps that are just digital filing cabinets and toward apps that act as intelligent partners.\u003C\u002Fp>\n\u003Ch4>Stepping Into the Future\u003C\u002Fh4>\n\u003Cp>Integrating AI into your workflow can feel like a daunting leap, but the App Assistant is designed to be the perfect first step. It’s an educational tool as much as it is a feature, giving developers a clear path to follow as they modernize their custom apps.\u003C\u002Fp>\n\u003Cp>The era of "clicking and searching" is slowly giving way to the era of "asking and doing." By bringing the App Assistant into your FileMaker toolkit, you aren't just updating your software—you’re changing the conversation your users have with their data.\u003C\u002Fp>\n\u003Ch5>Ready to get started?\u003C\u002Fh5>\n\u003Cp>You can download the App Assistant example and documentation directly from the Claris Support site. It’s time to give your FileMaker apps Ai intelligence. If you need help with that, feel free to contact us.\u003C\u002Fp>\n\u003Cp>Share\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwww.facebook.com\u002Fsharer\u002Fsharer.php?u=https%3A%2F%2Floggix.com%2Ftalking-to-your-data-with-the-filemaker-app-assistant-36558%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Ftwitter.com\u002Fintent\u002Ftweet?text=Talking+to+Your+Data+with+the+FileMaker+App+Assistant+-+Loggix+%7C+Software+Development.+https%3A%2F%2Floggix.com%2Ftalking-to-your-data-with-the-filemaker-app-assistant-36558%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Fwww.linkedin.com\u002FshareArticle?mini=true&url=https%3A%2F%2Floggix.com%2Ftalking-to-your-data-with-the-filemaker-app-assistant-36558%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Fpinterest.com\u002Fpin\u002Ffind\u002F?url=https%3A%2F%2Floggix.com%2Ftalking-to-your-data-with-the-filemaker-app-assistant-36558%2F\">\u003C\u002Fa>\u003C\u002Fp>\n",1781520657000,[23,518],"\u002Fapi\u002Fknowledge\u002Fimage\u002F65\u002F?v=5eaeb2d0f6c3",{"id":532,"idKnowledge":533,"idDomain":15,"idCluster":15,"slug":534,"title":535,"description":536,"bodyMarkdown":537,"bodyHtml":538,"author":514,"date":539,"createdAt":540,"topics":541,"image":542,"hasDownload":28,"fileName":15,"youtubeId":27},"30","D967ED27-44CE-4740-B156-364B9D6446C9","using-n8n-as-an-automation-agent-for-filemaker-solutions","Using n8n as an Automation Agent for FileMaker Solutions","Many FileMaker developers know the situation: your solution needs to react to incoming events, talk to external APIs, enrich data with AI, or run background tasks that should not depend on user actions. FileMaker can handle a lot internally, but sometimes you need a reliable worker behind the scenes","![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F12\u002Fn8n.jpg)\n\n##### **How low-code automation brings intelligence, API orchestration, and background agents to your Claris FileMaker stack**\n\nMany FileMaker developers know the situation: your solution needs to react to incoming events, talk to external APIs, enrich data with AI, or run background tasks that should not depend on user actions. FileMaker can handle a lot internally, but sometimes you need a reliable worker behind the scenes.\n\nThis is exactly what n8n provides.\n\nThink of n8n as an automation agent that runs next to your FileMaker system. It can respond to triggers (emails, webhooks, schedules), call AI models, connect to APIs, and write enriched, structured results back into FileMaker via the Data API. You design these workflows visually, without building a custom integration layer yourself.\n\nIn this article, we’ll walk through a real example:\n\nAutomatically analyzing incoming emails, detecting sentiment, and creating a prioritized Feedback record in FileMaker.\n\nThe entire workflow runs autonomously in n8n and enhances your FileMaker system without requiring new server-side scripts.\n\n* * *\n\n##### **Why Use n8n With FileMaker?**\n\nFileMaker excels at custom business applications, UI, and workflows. However, some tasks are simply easier (and cleaner) to run outside FileMaker:\n\n• Reacting to external triggers such as incoming mail or webhooks\n\n• Consuming modern REST APIs using OAuth and JSON\n\n• Running AI models like GPT\n\n• Handling asynchronous or multi-step workflows\n\n• Scheduling jobs and adding retry logic\n\n• Automating cross-platform processes\n\nn8n provides exactly this functionality. It becomes the automation layer, while FileMaker remains the authoritative system for data, business rules, and UI.\n\n* * *\n\n##### **Example Workflow: Email Sentiment Agent**\n\nHere’s the process explained in plain language.\n\n1.  Gmail Trigger\n    \n    The workflow fires automatically when a new email arrives. This gives you event-driven automation without polling or schedules.\n    \n2.  Preparing the Email Content\n    \n    n8n can clean up the text, remove signatures, ignore quoted replies, and prepare a clear text body for AI analysis.\n    \n3.  Gmail Labelling Agent (AI)\n    \n    n8n uses an AI model (OpenAI or similar) to understand the email.\n    \n    This step can classify the type of message, extract key information, and understand context.\n    \n    In your workflow, it also used memory to help the AI make better decisions.\n    \n4.  Sentiment Analysis\n    \n    Another AI step evaluates the tone of the message: Positive, Neutral, or Negative.\n    \n    This determines how your FileMaker dashboard will prioritize the feedback.\n    \n5.  Create Feedback in FileMaker\n    \n    Using the FileMaker Data API, n8n creates a new record in your Feedback table with:\n    \n    • Email body\n    \n    • Sender\n    \n    • Sentiment\n    \n    • Priority flag\n    \n    • Related student or contract ID\n    \n\nIf the email is negative, for example, FileMaker receives a record marked as High Priority, instantly visible on your dashboard.\n\nThis gives your FileMaker users a smarter inbox without them ever reading the email manually.\n\n* * *\n\n##### **Required API Connections (Explained Simply)**\n\nYou only need a few API connections to make this work. They are easy to configure inside n8n.\n\n###### **1\\. FileMaker Data API**\n\nUsed to create, update, or query records.\n\nYou provide:\n\n• FileMaker Server URL\n\n• Database name\n\n• Layout name\n\n• REST-privileged username + password\n\nn8n handles authentication by requesting a token and reusing it for later calls.\n\n###### **2\\. Gmail OAuth**\n\nBuilt-in to n8n.\n\nAuthenticate once and n8n can read messages, labels, send replies, or trigger flows.\n\n###### **3\\. OpenAI or another AI provider**\n\nJust supply your API key.\n\nn8n’s nodes support:\n\n• Chat models\n\n• Embeddings\n\n• JSON mode\n\n• Function\u002Ftool calling\n\n###### **4\\. Optional memory storage**\n\nn8n supports different memory types so your agent can build context over time.\n\n* * *\n\n##### **What This Adds to Your FileMaker System**\n\nUsing n8n as a companion system brings several advantages:\n\n• Autonomous background processing\n\n• AI-powered email understanding\n\n• Instant triage of high-priority messages\n\n• Clean separation between UI\u002Fbusiness logic and automation logic\n\n• Faster development of API integrations\n\n• No need for complex FileMaker scripts to talk to external services\n\nThe result is a modern hybrid FileMaker architecture where FileMaker remains your operational backbone, while n8n becomes the automation and AI engine.\n\n* * *\n\n##### **When To Use n8n as an Agent for FileMaker**\n\nHere is a simple guideline:\n\nUse n8n for:\n\n• API integrations\n\n• AI processing\n\n• Email automation\n\n• Webhooks\n\n• Scheduling\n\n• Multi-step flows\n\n• Error handling and retries\n\nUse FileMaker for:\n\n• Layouts and UI\n\n• Data storage\n\n• Security\n\n• Business logic\n\n• Reporting\n\n• Dashboards\n\nTogether they create a scalable, maintainable automation ecosystem.\n\n* * *\n\n##### **Conclusion**\n\nn8n allows FileMaker developers to add intelligent automation to their systems without building and maintaining complex integration code. In the example workflow, a simple incoming email turns into:\n\n• Structured content\n\n• AI-generated sentiment\n\n• Automatic Gmail labelling\n\n• A new Feedback record in FileMaker\n\n• Priority handling on the dashboard\n\nAll orchestrated by n8n in the background.\n\nIf you are building modern FileMaker solutions that need more automated intelligence, n8n is one of the most powerful companions you can add to your stack.\n\nShare\n\n[](https:\u002F\u002Fwww.facebook.com\u002Fsharer\u002Fsharer.php?u=https%3A%2F%2Floggix.com%2Fbebuilder-36532%2F)[](https:\u002F\u002Ftwitter.com\u002Fintent\u002Ftweet?text=Using+n8n+as+an+Automation+Agent+for+FileMaker+Solutions+-+Loggix+%7C+Software+Development.+https%3A%2F%2Floggix.com%2Fbebuilder-36532%2F)[](https:\u002F\u002Fwww.linkedin.com\u002FshareArticle?mini=true&url=https%3A%2F%2Floggix.com%2Fbebuilder-36532%2F)[](https:\u002F\u002Fpinterest.com\u002Fpin\u002Ffind\u002F?url=https%3A%2F%2Floggix.com%2Fbebuilder-36532%2F)","\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F12\u002Fn8n.jpg\" alt=\"\">\u003C\u002Fp>\n\u003Ch5>\u003Cstrong>How low-code automation brings intelligence, API orchestration, and background agents to your Claris FileMaker stack\u003C\u002Fstrong>\u003C\u002Fh5>\n\u003Cp>Many FileMaker developers know the situation: your solution needs to react to incoming events, talk to external APIs, enrich data with AI, or run background tasks that should not depend on user actions. FileMaker can handle a lot internally, but sometimes you need a reliable worker behind the scenes.\u003C\u002Fp>\n\u003Cp>This is exactly what n8n provides.\u003C\u002Fp>\n\u003Cp>Think of n8n as an automation agent that runs next to your FileMaker system. It can respond to triggers (emails, webhooks, schedules), call AI models, connect to APIs, and write enriched, structured results back into FileMaker via the Data API. You design these workflows visually, without building a custom integration layer yourself.\u003C\u002Fp>\n\u003Cp>In this article, we’ll walk through a real example:\u003C\u002Fp>\n\u003Cp>Automatically analyzing incoming emails, detecting sentiment, and creating a prioritized Feedback record in FileMaker.\u003C\u002Fp>\n\u003Cp>The entire workflow runs autonomously in n8n and enhances your FileMaker system without requiring new server-side scripts.\u003C\u002Fp>\n\u003Chr>\n\u003Ch5>\u003Cstrong>Why Use n8n With FileMaker?\u003C\u002Fstrong>\u003C\u002Fh5>\n\u003Cp>FileMaker excels at custom business applications, UI, and workflows. However, some tasks are simply easier (and cleaner) to run outside FileMaker:\u003C\u002Fp>\n\u003Cp>• Reacting to external triggers such as incoming mail or webhooks\u003C\u002Fp>\n\u003Cp>• Consuming modern REST APIs using OAuth and JSON\u003C\u002Fp>\n\u003Cp>• Running AI models like GPT\u003C\u002Fp>\n\u003Cp>• Handling asynchronous or multi-step workflows\u003C\u002Fp>\n\u003Cp>• Scheduling jobs and adding retry logic\u003C\u002Fp>\n\u003Cp>• Automating cross-platform processes\u003C\u002Fp>\n\u003Cp>n8n provides exactly this functionality. It becomes the automation layer, while FileMaker remains the authoritative system for data, business rules, and UI.\u003C\u002Fp>\n\u003Chr>\n\u003Ch5>\u003Cstrong>Example Workflow: Email Sentiment Agent\u003C\u002Fstrong>\u003C\u002Fh5>\n\u003Cp>Here’s the process explained in plain language.\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cp>Gmail Trigger\u003C\u002Fp>\n\u003Cp>The workflow fires automatically when a new email arrives. This gives you event-driven automation without polling or schedules.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>Preparing the Email Content\u003C\u002Fp>\n\u003Cp>n8n can clean up the text, remove signatures, ignore quoted replies, and prepare a clear text body for AI analysis.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>Gmail Labelling Agent (AI)\u003C\u002Fp>\n\u003Cp>n8n uses an AI model (OpenAI or similar) to understand the email.\u003C\u002Fp>\n\u003Cp>This step can classify the type of message, extract key information, and understand context.\u003C\u002Fp>\n\u003Cp>In your workflow, it also used memory to help the AI make better decisions.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>Sentiment Analysis\u003C\u002Fp>\n\u003Cp>Another AI step evaluates the tone of the message: Positive, Neutral, or Negative.\u003C\u002Fp>\n\u003Cp>This determines how your FileMaker dashboard will prioritize the feedback.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>Create Feedback in FileMaker\u003C\u002Fp>\n\u003Cp>Using the FileMaker Data API, n8n creates a new record in your Feedback table with:\u003C\u002Fp>\n\u003Cp>• Email body\u003C\u002Fp>\n\u003Cp>• Sender\u003C\u002Fp>\n\u003Cp>• Sentiment\u003C\u002Fp>\n\u003Cp>• Priority flag\u003C\u002Fp>\n\u003Cp>• Related student or contract ID\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>If the email is negative, for example, FileMaker receives a record marked as High Priority, instantly visible on your dashboard.\u003C\u002Fp>\n\u003Cp>This gives your FileMaker users a smarter inbox without them ever reading the email manually.\u003C\u002Fp>\n\u003Chr>\n\u003Ch5>\u003Cstrong>Required API Connections (Explained Simply)\u003C\u002Fstrong>\u003C\u002Fh5>\n\u003Cp>You only need a few API connections to make this work. They are easy to configure inside n8n.\u003C\u002Fp>\n\u003Ch6>\u003Cstrong>1. FileMaker Data API\u003C\u002Fstrong>\u003C\u002Fh6>\n\u003Cp>Used to create, update, or query records.\u003C\u002Fp>\n\u003Cp>You provide:\u003C\u002Fp>\n\u003Cp>• FileMaker Server URL\u003C\u002Fp>\n\u003Cp>• Database name\u003C\u002Fp>\n\u003Cp>• Layout name\u003C\u002Fp>\n\u003Cp>• REST-privileged username + password\u003C\u002Fp>\n\u003Cp>n8n handles authentication by requesting a token and reusing it for later calls.\u003C\u002Fp>\n\u003Ch6>\u003Cstrong>2. Gmail OAuth\u003C\u002Fstrong>\u003C\u002Fh6>\n\u003Cp>Built-in to n8n.\u003C\u002Fp>\n\u003Cp>Authenticate once and n8n can read messages, labels, send replies, or trigger flows.\u003C\u002Fp>\n\u003Ch6>\u003Cstrong>3. OpenAI or another AI provider\u003C\u002Fstrong>\u003C\u002Fh6>\n\u003Cp>Just supply your API key.\u003C\u002Fp>\n\u003Cp>n8n’s nodes support:\u003C\u002Fp>\n\u003Cp>• Chat models\u003C\u002Fp>\n\u003Cp>• Embeddings\u003C\u002Fp>\n\u003Cp>• JSON mode\u003C\u002Fp>\n\u003Cp>• Function\u002Ftool calling\u003C\u002Fp>\n\u003Ch6>\u003Cstrong>4. Optional memory storage\u003C\u002Fstrong>\u003C\u002Fh6>\n\u003Cp>n8n supports different memory types so your agent can build context over time.\u003C\u002Fp>\n\u003Chr>\n\u003Ch5>\u003Cstrong>What This Adds to Your FileMaker System\u003C\u002Fstrong>\u003C\u002Fh5>\n\u003Cp>Using n8n as a companion system brings several advantages:\u003C\u002Fp>\n\u003Cp>• Autonomous background processing\u003C\u002Fp>\n\u003Cp>• AI-powered email understanding\u003C\u002Fp>\n\u003Cp>• Instant triage of high-priority messages\u003C\u002Fp>\n\u003Cp>• Clean separation between UI\u002Fbusiness logic and automation logic\u003C\u002Fp>\n\u003Cp>• Faster development of API integrations\u003C\u002Fp>\n\u003Cp>• No need for complex FileMaker scripts to talk to external services\u003C\u002Fp>\n\u003Cp>The result is a modern hybrid FileMaker architecture where FileMaker remains your operational backbone, while n8n becomes the automation and AI engine.\u003C\u002Fp>\n\u003Chr>\n\u003Ch5>\u003Cstrong>When To Use n8n as an Agent for FileMaker\u003C\u002Fstrong>\u003C\u002Fh5>\n\u003Cp>Here is a simple guideline:\u003C\u002Fp>\n\u003Cp>Use n8n for:\u003C\u002Fp>\n\u003Cp>• API integrations\u003C\u002Fp>\n\u003Cp>• AI processing\u003C\u002Fp>\n\u003Cp>• Email automation\u003C\u002Fp>\n\u003Cp>• Webhooks\u003C\u002Fp>\n\u003Cp>• Scheduling\u003C\u002Fp>\n\u003Cp>• Multi-step flows\u003C\u002Fp>\n\u003Cp>• Error handling and retries\u003C\u002Fp>\n\u003Cp>Use FileMaker for:\u003C\u002Fp>\n\u003Cp>• Layouts and UI\u003C\u002Fp>\n\u003Cp>• Data storage\u003C\u002Fp>\n\u003Cp>• Security\u003C\u002Fp>\n\u003Cp>• Business logic\u003C\u002Fp>\n\u003Cp>• Reporting\u003C\u002Fp>\n\u003Cp>• Dashboards\u003C\u002Fp>\n\u003Cp>Together they create a scalable, maintainable automation ecosystem.\u003C\u002Fp>\n\u003Chr>\n\u003Ch5>\u003Cstrong>Conclusion\u003C\u002Fstrong>\u003C\u002Fh5>\n\u003Cp>n8n allows FileMaker developers to add intelligent automation to their systems without building and maintaining complex integration code. In the example workflow, a simple incoming email turns into:\u003C\u002Fp>\n\u003Cp>• Structured content\u003C\u002Fp>\n\u003Cp>• AI-generated sentiment\u003C\u002Fp>\n\u003Cp>• Automatic Gmail labelling\u003C\u002Fp>\n\u003Cp>• A new Feedback record in FileMaker\u003C\u002Fp>\n\u003Cp>• Priority handling on the dashboard\u003C\u002Fp>\n\u003Cp>All orchestrated by n8n in the background.\u003C\u002Fp>\n\u003Cp>If you are building modern FileMaker solutions that need more automated intelligence, n8n is one of the most powerful companions you can add to your stack.\u003C\u002Fp>\n\u003Cp>Share\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwww.facebook.com\u002Fsharer\u002Fsharer.php?u=https%3A%2F%2Floggix.com%2Fbebuilder-36532%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Ftwitter.com\u002Fintent\u002Ftweet?text=Using+n8n+as+an+Automation+Agent+for+FileMaker+Solutions+-+Loggix+%7C+Software+Development.+https%3A%2F%2Floggix.com%2Fbebuilder-36532%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Fwww.linkedin.com\u002FshareArticle?mini=true&url=https%3A%2F%2Floggix.com%2Fbebuilder-36532%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Fpinterest.com\u002Fpin\u002Ffind\u002F?url=https%3A%2F%2Floggix.com%2Fbebuilder-36532%2F\">\u003C\u002Fa>\u003C\u002Fp>\n","2025-12-06",1781519867000,[73,23],"\u002Fapi\u002Fknowledge\u002Fimage\u002F30\u002F?v=97bae1916e12",{"id":544,"idKnowledge":545,"idDomain":15,"idCluster":15,"slug":546,"title":547,"description":548,"bodyMarkdown":549,"bodyHtml":550,"author":514,"date":539,"createdAt":551,"topics":552,"image":553,"hasDownload":28,"fileName":15,"youtubeId":27},"29","E886E1C3-A24D-AE45-98E8-D803F98F8860","figma-plugin-for-fmbetterforms","Figma Plugin for FMBetterForms","The new Figma-to-FMBetterForms plugin makes it easier than ever to design your UI before you build it. Create your layout visually in Figma, click a button, and instantly generate clean schema code ready to paste into FMBetterForms. This design-first workflow speeds up development, reduces rework, a","![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F12\u002FSCR-20251206-nity-scaled-e1765030657712.png)\n\n##### **In modern application development, designing before you build has become the standard—not just for large software teams, but also for FileMaker developers delivering business-critical solutions. Good design leads to clearer requirements, smoother development, faster iterations, and happier users. With the arrival of the new Figma-to-FMBetterForms Plugin, this workflow becomes easier than ever. You can now design an interface directly in Figma, click a button, and instantly generate clean FMBetterForms layout code ready to paste into your page schema. No more guessing, no more pixel-pushing inside JSON, and no more back-and-forth between UI ideas and development.**\n\nBelow, we’ll explain why this new workflow is such a game-changer and how you can start using it today.  \n  \n\n##### **Why Design First?**\n\nEven seasoned FileMaker developers sometimes jump directly into building layouts or BF schemas before fully defining the user experience. But starting with design has several clear advantages:\n\n###### **1.** **Faster Iteration**\n\nDesign tools like Figma let you move elements around instantly, test variations, explore spacing and hierarchy, and experiment with modern UI patterns—all before writing a single line of code.\n\n###### **2.** **Better Feedback From Clients and Stakeholders**\n\nA Figma mockup feels tangible. Users can react to it much earlier than they would to a JSON schema or a FileMaker prototype. This reduces misunderstandings and clarifies expectations.\n\n###### **3.** **More Consistent User Interfaces**\n\nFigma supports component libraries, design tokens, and reusable styles. This ensures your FileMaker + FMBetterForms solution looks consistent across all pages and devices.\n\n###### **4.** **Lower Development Cost**\n\nIf the layout is validated visually early on, developers spend less time rebuilding or refactoring UI logic later.\n\nIn short: **designing first prevents rework**, and rework is the biggest hidden cost in custom development.\n\n##### **What the Figma-to-FMBetterForms Plugin Does**\n\nThe new plugin bridges the gap between design and code. Here’s what it offers:\n\n###### **✔ One-click conversion**\n\nSelect your Figma frame or component and click **Generate FMBF Code**. The plugin translates your design into FMBetterForms schema blocks, HTML, and Tailwind utility classes.\n\n###### **✔ Clean, readable code**\n\nThe output is structured following BF best practices—groups, fields and HTML blocks that reflect the original design hierarchy. No messy inline styling.\n\n###### **✔ Automatic Tailwind mapping**\n\nSpacing, font sizes, colors, alignment, rounded corners, icons—everything is translated to classes understood by FMBF’s Tailwind implementation.\n\n###### **✔ Easy to paste into your existing schema**\n\nJust copy the generated code and paste it into your schema.groups\\[x\\].fields structure. That’s it. Your design becomes a live FMBetterForms interface.\n\n###### **✔ Consistent results**\n\nBecause the translation is rules-based, you get predictable code every time. This makes it easier for teams to adopt a shared design-to-build workflow.\n\n##### **How the Workflow Looks**\n\nThe plugin makes the entire process extremely straightforward:\n\n###### **1\\. Design your interface in Figma**\n\nStart with frames sized around real devices: desktop, tablet, phone. Use buttons, cards, containers, icons—anything you want. Apply the styling you expect to see in the final app.\n\n###### **2\\. Run the plugin**\n\nOpen the plugin from the Figma Plugins menu, select your frame, and press **Convert**.\n\n###### **3\\. Copy the generated FMBF schema**\n\nThe plugin displays ready-to-use JSON\u002FHTML snippet blocks. Simply copy them.\n\n###### **4\\. Paste into your FMBetterForms page**\n\nOpen your FileMaker layout or FMBF page manager, paste the schema, and refresh. Your UI appears instantly.\n\nThe result is a workflow that feels natural, visual, and extremely fast.\n\n##### **Why This Is a Big Win for FileMaker Developers**\n\nFMBetterForms has always been a powerful way to build modern, responsive web interfaces on top of FileMaker. The challenge has always been the same: **designing visually inside a JSON-based layout system is not ideal**.\n\nThis plugin fixes that completely.\n\n###### **Instead of:**\n\n-   adjusting Tailwind classes by hand\n    \n-   guessing spacing\n    \n-   tweaking schema blocks\n    \n-   reloading repeatedly to see changes\n    \n\n###### **You now:**\n\n-   design with a real visual UI editor\n    \n-   get instant conversion\n    \n-   paste once and move on\n    \n\nThis saves hours—or even days—per page.\n\nAdditionally, semi-technical developers or designers can now contribute directly. A team member who is comfortable in Figma but not in FileMaker scripting can still produce production-ready layouts.\n\n##### **Practical Use Cases**\n\nThis plugin is especially valuable for:\n\n-   **Client portal pages**\n    \n-   **Forms with custom layout requirements**\n    \n-   **Dashboards with card components**\n    \n-   **Mobile-first UIs**\n    \n-   **Internal tools needing rapid iteration**\n    \n-   **Rebuilding older web-direct pages in a modernized UI**\n    \n\nIf you build with FMBetterForms, this plugin will quickly become part of your daily workflow.\n\n##### **Final Thoughts**\n\nThe new **Figma-to-FMBetterForms Plugin** is more than a convenient tool—it’s the missing link between design intention and development reality. It encourages better UI planning, improves collaboration, and dramatically reduces the time required to build polished web interfaces inside FileMaker solutions.\n\nBy designing first and building second, you get:\n\n-   clearer requirements\n    \n-   faster development\n    \n-   cleaner code\n    \n-   more satisfied users\n    \n\nAnd now—with this plugin—you get that workflow without any extra friction.\n\nIf you’re developing modern FileMaker apps, this is the moment to upgrade your UI process.\n\nShare\n\n[](https:\u002F\u002Fwww.facebook.com\u002Fsharer\u002Fsharer.php?u=https%3A%2F%2Floggix.com%2Fbebuilder-36541%2F)[](https:\u002F\u002Ftwitter.com\u002Fintent\u002Ftweet?text=Figma+Plugin+for+FMBetterForms+-+Loggix+%7C+Software+Development.+https%3A%2F%2Floggix.com%2Fbebuilder-36541%2F)[](https:\u002F\u002Fwww.linkedin.com\u002FshareArticle?mini=true&url=https%3A%2F%2Floggix.com%2Fbebuilder-36541%2F)[](https:\u002F\u002Fpinterest.com\u002Fpin\u002Ffind\u002F?url=https%3A%2F%2Floggix.com%2Fbebuilder-36541%2F)","\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F12\u002FSCR-20251206-nity-scaled-e1765030657712.png\" alt=\"\">\u003C\u002Fp>\n\u003Ch5>\u003Cstrong>In modern application development, designing before you build has become the standard—not just for large software teams, but also for FileMaker developers delivering business-critical solutions. Good design leads to clearer requirements, smoother development, faster iterations, and happier users. With the arrival of the new Figma-to-FMBetterForms Plugin, this workflow becomes easier than ever. You can now design an interface directly in Figma, click a button, and instantly generate clean FMBetterForms layout code ready to paste into your page schema. No more guessing, no more pixel-pushing inside JSON, and no more back-and-forth between UI ideas and development.\u003C\u002Fstrong>\u003C\u002Fh5>\n\u003Cp>Below, we’ll explain why this new workflow is such a game-changer and how you can start using it today.  \u003C\u002Fp>\n\u003Ch5>\u003Cstrong>Why Design First?\u003C\u002Fstrong>\u003C\u002Fh5>\n\u003Cp>Even seasoned FileMaker developers sometimes jump directly into building layouts or BF schemas before fully defining the user experience. But starting with design has several clear advantages:\u003C\u002Fp>\n\u003Ch6>\u003Cstrong>1.\u003C\u002Fstrong> \u003Cstrong>Faster Iteration\u003C\u002Fstrong>\u003C\u002Fh6>\n\u003Cp>Design tools like Figma let you move elements around instantly, test variations, explore spacing and hierarchy, and experiment with modern UI patterns—all before writing a single line of code.\u003C\u002Fp>\n\u003Ch6>\u003Cstrong>2.\u003C\u002Fstrong> \u003Cstrong>Better Feedback From Clients and Stakeholders\u003C\u002Fstrong>\u003C\u002Fh6>\n\u003Cp>A Figma mockup feels tangible. Users can react to it much earlier than they would to a JSON schema or a FileMaker prototype. This reduces misunderstandings and clarifies expectations.\u003C\u002Fp>\n\u003Ch6>\u003Cstrong>3.\u003C\u002Fstrong> \u003Cstrong>More Consistent User Interfaces\u003C\u002Fstrong>\u003C\u002Fh6>\n\u003Cp>Figma supports component libraries, design tokens, and reusable styles. This ensures your FileMaker + FMBetterForms solution looks consistent across all pages and devices.\u003C\u002Fp>\n\u003Ch6>\u003Cstrong>4.\u003C\u002Fstrong> \u003Cstrong>Lower Development Cost\u003C\u002Fstrong>\u003C\u002Fh6>\n\u003Cp>If the layout is validated visually early on, developers spend less time rebuilding or refactoring UI logic later.\u003C\u002Fp>\n\u003Cp>In short: \u003Cstrong>designing first prevents rework\u003C\u002Fstrong>, and rework is the biggest hidden cost in custom development.\u003C\u002Fp>\n\u003Ch5>\u003Cstrong>What the Figma-to-FMBetterForms Plugin Does\u003C\u002Fstrong>\u003C\u002Fh5>\n\u003Cp>The new plugin bridges the gap between design and code. Here’s what it offers:\u003C\u002Fp>\n\u003Ch6>\u003Cstrong>✔ One-click conversion\u003C\u002Fstrong>\u003C\u002Fh6>\n\u003Cp>Select your Figma frame or component and click \u003Cstrong>Generate FMBF Code\u003C\u002Fstrong>. The plugin translates your design into FMBetterForms schema blocks, HTML, and Tailwind utility classes.\u003C\u002Fp>\n\u003Ch6>\u003Cstrong>✔ Clean, readable code\u003C\u002Fstrong>\u003C\u002Fh6>\n\u003Cp>The output is structured following BF best practices—groups, fields and HTML blocks that reflect the original design hierarchy. No messy inline styling.\u003C\u002Fp>\n\u003Ch6>\u003Cstrong>✔ Automatic Tailwind mapping\u003C\u002Fstrong>\u003C\u002Fh6>\n\u003Cp>Spacing, font sizes, colors, alignment, rounded corners, icons—everything is translated to classes understood by FMBF’s Tailwind implementation.\u003C\u002Fp>\n\u003Ch6>\u003Cstrong>✔ Easy to paste into your existing schema\u003C\u002Fstrong>\u003C\u002Fh6>\n\u003Cp>Just copy the generated code and paste it into your schema.groups[x].fields structure. That’s it. Your design becomes a live FMBetterForms interface.\u003C\u002Fp>\n\u003Ch6>\u003Cstrong>✔ Consistent results\u003C\u002Fstrong>\u003C\u002Fh6>\n\u003Cp>Because the translation is rules-based, you get predictable code every time. This makes it easier for teams to adopt a shared design-to-build workflow.\u003C\u002Fp>\n\u003Ch5>\u003Cstrong>How the Workflow Looks\u003C\u002Fstrong>\u003C\u002Fh5>\n\u003Cp>The plugin makes the entire process extremely straightforward:\u003C\u002Fp>\n\u003Ch6>\u003Cstrong>1. Design your interface in Figma\u003C\u002Fstrong>\u003C\u002Fh6>\n\u003Cp>Start with frames sized around real devices: desktop, tablet, phone. Use buttons, cards, containers, icons—anything you want. Apply the styling you expect to see in the final app.\u003C\u002Fp>\n\u003Ch6>\u003Cstrong>2. Run the plugin\u003C\u002Fstrong>\u003C\u002Fh6>\n\u003Cp>Open the plugin from the Figma Plugins menu, select your frame, and press \u003Cstrong>Convert\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Ch6>\u003Cstrong>3. Copy the generated FMBF schema\u003C\u002Fstrong>\u003C\u002Fh6>\n\u003Cp>The plugin displays ready-to-use JSON\u002FHTML snippet blocks. Simply copy them.\u003C\u002Fp>\n\u003Ch6>\u003Cstrong>4. Paste into your FMBetterForms page\u003C\u002Fstrong>\u003C\u002Fh6>\n\u003Cp>Open your FileMaker layout or FMBF page manager, paste the schema, and refresh. Your UI appears instantly.\u003C\u002Fp>\n\u003Cp>The result is a workflow that feels natural, visual, and extremely fast.\u003C\u002Fp>\n\u003Ch5>\u003Cstrong>Why This Is a Big Win for FileMaker Developers\u003C\u002Fstrong>\u003C\u002Fh5>\n\u003Cp>FMBetterForms has always been a powerful way to build modern, responsive web interfaces on top of FileMaker. The challenge has always been the same: \u003Cstrong>designing visually inside a JSON-based layout system is not ideal\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>This plugin fixes that completely.\u003C\u002Fp>\n\u003Ch6>\u003Cstrong>Instead of:\u003C\u002Fstrong>\u003C\u002Fh6>\n\u003Cul>\n\u003Cli>\u003Cp>adjusting Tailwind classes by hand\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>guessing spacing\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>tweaking schema blocks\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>reloading repeatedly to see changes\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch6>\u003Cstrong>You now:\u003C\u002Fstrong>\u003C\u002Fh6>\n\u003Cul>\n\u003Cli>\u003Cp>design with a real visual UI editor\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>get instant conversion\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>paste once and move on\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This saves hours—or even days—per page.\u003C\u002Fp>\n\u003Cp>Additionally, semi-technical developers or designers can now contribute directly. A team member who is comfortable in Figma but not in FileMaker scripting can still produce production-ready layouts.\u003C\u002Fp>\n\u003Ch5>\u003Cstrong>Practical Use Cases\u003C\u002Fstrong>\u003C\u002Fh5>\n\u003Cp>This plugin is especially valuable for:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cp>\u003Cstrong>Client portal pages\u003C\u002Fstrong>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>\u003Cstrong>Forms with custom layout requirements\u003C\u002Fstrong>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>\u003Cstrong>Dashboards with card components\u003C\u002Fstrong>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>\u003Cstrong>Mobile-first UIs\u003C\u002Fstrong>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>\u003Cstrong>Internal tools needing rapid iteration\u003C\u002Fstrong>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>\u003Cstrong>Rebuilding older web-direct pages in a modernized UI\u003C\u002Fstrong>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If you build with FMBetterForms, this plugin will quickly become part of your daily workflow.\u003C\u002Fp>\n\u003Ch5>\u003Cstrong>Final Thoughts\u003C\u002Fstrong>\u003C\u002Fh5>\n\u003Cp>The new \u003Cstrong>Figma-to-FMBetterForms Plugin\u003C\u002Fstrong> is more than a convenient tool—it’s the missing link between design intention and development reality. It encourages better UI planning, improves collaboration, and dramatically reduces the time required to build polished web interfaces inside FileMaker solutions.\u003C\u002Fp>\n\u003Cp>By designing first and building second, you get:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cp>clearer requirements\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>faster development\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>cleaner code\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>more satisfied users\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>And now—with this plugin—you get that workflow without any extra friction.\u003C\u002Fp>\n\u003Cp>If you’re developing modern FileMaker apps, this is the moment to upgrade your UI process.\u003C\u002Fp>\n\u003Cp>Share\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwww.facebook.com\u002Fsharer\u002Fsharer.php?u=https%3A%2F%2Floggix.com%2Fbebuilder-36541%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Ftwitter.com\u002Fintent\u002Ftweet?text=Figma+Plugin+for+FMBetterForms+-+Loggix+%7C+Software+Development.+https%3A%2F%2Floggix.com%2Fbebuilder-36541%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Fwww.linkedin.com\u002FshareArticle?mini=true&url=https%3A%2F%2Floggix.com%2Fbebuilder-36541%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Fpinterest.com\u002Fpin\u002Ffind\u002F?url=https%3A%2F%2Floggix.com%2Fbebuilder-36541%2F\">\u003C\u002Fa>\u003C\u002Fp>\n",1781519866000,[23,518],"\u002Fapi\u002Fknowledge\u002Fimage\u002F29\u002F?v=59ba81dd7c54",{"id":555,"idKnowledge":556,"idDomain":15,"idCluster":15,"slug":557,"title":558,"description":559,"bodyMarkdown":560,"bodyHtml":561,"author":514,"date":562,"createdAt":563,"topics":564,"image":565,"hasDownload":28,"fileName":15,"youtubeId":27},"32","343370E4-E1CF-854A-A242-E825AF392FDD","filemaker-2025-is-here","FileMaker 2025 is here!","Ai further integrated in this FileMaker upgrade.","**Claris FileMaker 2025 has officially landed, and it marks a notable turning point for developers, business users, and IT teams looking to build smarter, more integrated custom apps. With this release, Claris is clearly positioning itself as an AI-first platform—putting artificial intelligence, local model control, and seamless integration at the heart of its development roadmap.**\n\nClaris FileMaker 2025 has officially landed, and it marks a notable turning point for developers, business users, and IT teams looking to build smarter, more integrated custom apps. With this release, Claris is clearly positioning itself as an AI-first platform—putting artificial intelligence, local model control, and seamless integration at the heart of its development roadmap.\n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F07\u002Ffmai.png)\n\n**Claris FileMaker 2025: A New Chapter for AI-Driven Custom Apps**\n\nOne of the most anticipated updates is the introduction of native AI capabilities directly into the FileMaker platform. Developers can now leverage built-in script steps and functions for tasks like semantic search, natural language processing, and even PDF summarization. Crucially, these AI features are designed to be model-agnostic: users can connect to cloud-based services like OpenAI, Cohere, or Anthropic—or choose to run open-source LLMs on-premise for full data sovereignty.\n\n**Improvements in Script Manager**  \nOn the development side, FileMaker 2025 brings several long-requested features that improve day-to-day scripting and layout work. Custom functions can finally be organized into folders, making complex systems easier to manage. Script steps are now collapsible, which significantly improves script readability—especially in long workflows. There are also several new functions, such as GetRecordIDsFromFoundSet() and GoToListOfRecords(), which give developers more powerful ways to manipulate found sets and user interactions.\n\n**Change in SQL parser**  \nPerhaps one of the more technical yet important changes is FileMaker’s updated SQL parser, which now uses ANTLR4. This enhancement enables support for more sophisticated SQL statements, including INTERVAL, FETCH NEXT, and table renaming—features that open up new options for working with complex data logic. On the server side, OData endpoints have been upgraded to support aggregate functions like sum, average, and group-by operations, enabling more efficient reporting and analytics.\n\n**Connect & Studio**  \nClaris is also introducing a new licensing model that unifies the platform under one simplified plan. With a single license, users gain access to FileMaker, Claris Studio, and Claris Connect—removing barriers between tools and encouraging deeper integration across workflows. The Starter tier includes 50 live Connect flows and unlimited use of Claris Studio web views (until September 8, 2025), while the Max tier offers unlimited flows and access to advanced features. Claris Studio continues to evolve as a front-end builder for public-facing data collection apps. With support for iFrames, custom views, and prefilled forms, Studio becomes an essential tool for creating lightweight, customer-friendly interfaces—perfectly integrated via Claris Connect.\n\n**FileMaker Server 2025**  \nOn the infrastructure side, FileMaker Server 2025 adds meaningful enhancements. There’s now native support for Ubuntu 24 and Let’s Encrypt SSL, which simplifies deployment and automates certificate management. Admins can configure and manage AI models directly from the Admin Console—including token limits, model access, and fine-tuning options—bringing enterprise-level AI control to the platform. Improvements to WebDirect include support for right-click paste and copy, better browser navigation warnings, and more stability overall.\n\n**Conclusion**  \nClaris FileMaker 2025 is a maturing platform embracing the future of app development—where AI, integration, and ease of use intersect. For developers and teams already working within the Claris ecosystem, this release offers real opportunities to modernize and future-proof their custom solutions. Whether you’re looking to enhance workflows with AI or simply improve how you build and manage layouts and scripts, FileMaker 2025 is worth exploring.  \n  \nMore tips and tricks on Claris FileMaker 2025 in the next posts...\n\nShare\n\n[](https:\u002F\u002Fwww.facebook.com\u002Fsharer\u002Fsharer.php?u=https%3A%2F%2Floggix.com%2Ffilemaker-2025-is-here-36514%2F)[](https:\u002F\u002Ftwitter.com\u002Fintent\u002Ftweet?text=FileMaker+2025+is+here%21+-+Loggix+%7C+Software+Development.+https%3A%2F%2Floggix.com%2Ffilemaker-2025-is-here-36514%2F)[](https:\u002F\u002Fwww.linkedin.com\u002FshareArticle?mini=true&url=https%3A%2F%2Floggix.com%2Ffilemaker-2025-is-here-36514%2F)[](https:\u002F\u002Fpinterest.com\u002Fpin\u002Ffind\u002F?url=https%3A%2F%2Floggix.com%2Ffilemaker-2025-is-here-36514%2F)","\u003Cp>\u003Cstrong>Claris FileMaker 2025 has officially landed, and it marks a notable turning point for developers, business users, and IT teams looking to build smarter, more integrated custom apps. With this release, Claris is clearly positioning itself as an AI-first platform—putting artificial intelligence, local model control, and seamless integration at the heart of its development roadmap.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Claris FileMaker 2025 has officially landed, and it marks a notable turning point for developers, business users, and IT teams looking to build smarter, more integrated custom apps. With this release, Claris is clearly positioning itself as an AI-first platform—putting artificial intelligence, local model control, and seamless integration at the heart of its development roadmap.\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F07\u002Ffmai.png\" alt=\"\">\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Claris FileMaker 2025: A New Chapter for AI-Driven Custom Apps\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>One of the most anticipated updates is the introduction of native AI capabilities directly into the FileMaker platform. Developers can now leverage built-in script steps and functions for tasks like semantic search, natural language processing, and even PDF summarization. Crucially, these AI features are designed to be model-agnostic: users can connect to cloud-based services like OpenAI, Cohere, or Anthropic—or choose to run open-source LLMs on-premise for full data sovereignty.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Improvements in Script Manager\u003C\u002Fstrong>\u003Cbr>On the development side, FileMaker 2025 brings several long-requested features that improve day-to-day scripting and layout work. Custom functions can finally be organized into folders, making complex systems easier to manage. Script steps are now collapsible, which significantly improves script readability—especially in long workflows. There are also several new functions, such as GetRecordIDsFromFoundSet() and GoToListOfRecords(), which give developers more powerful ways to manipulate found sets and user interactions.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Change in SQL parser\u003C\u002Fstrong>\u003Cbr>Perhaps one of the more technical yet important changes is FileMaker’s updated SQL parser, which now uses ANTLR4. This enhancement enables support for more sophisticated SQL statements, including INTERVAL, FETCH NEXT, and table renaming—features that open up new options for working with complex data logic. On the server side, OData endpoints have been upgraded to support aggregate functions like sum, average, and group-by operations, enabling more efficient reporting and analytics.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Connect & Studio\u003C\u002Fstrong>\u003Cbr>Claris is also introducing a new licensing model that unifies the platform under one simplified plan. With a single license, users gain access to FileMaker, Claris Studio, and Claris Connect—removing barriers between tools and encouraging deeper integration across workflows. The Starter tier includes 50 live Connect flows and unlimited use of Claris Studio web views (until September 8, 2025), while the Max tier offers unlimited flows and access to advanced features. Claris Studio continues to evolve as a front-end builder for public-facing data collection apps. With support for iFrames, custom views, and prefilled forms, Studio becomes an essential tool for creating lightweight, customer-friendly interfaces—perfectly integrated via Claris Connect.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>FileMaker Server 2025\u003C\u002Fstrong>\u003Cbr>On the infrastructure side, FileMaker Server 2025 adds meaningful enhancements. There’s now native support for Ubuntu 24 and Let’s Encrypt SSL, which simplifies deployment and automates certificate management. Admins can configure and manage AI models directly from the Admin Console—including token limits, model access, and fine-tuning options—bringing enterprise-level AI control to the platform. Improvements to WebDirect include support for right-click paste and copy, better browser navigation warnings, and more stability overall.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Conclusion\u003C\u002Fstrong>\u003Cbr>Claris FileMaker 2025 is a maturing platform embracing the future of app development—where AI, integration, and ease of use intersect. For developers and teams already working within the Claris ecosystem, this release offers real opportunities to modernize and future-proof their custom solutions. Whether you’re looking to enhance workflows with AI or simply improve how you build and manage layouts and scripts, FileMaker 2025 is worth exploring.  \u003C\u002Fp>\n\u003Cp>More tips and tricks on Claris FileMaker 2025 in the next posts...\u003C\u002Fp>\n\u003Cp>Share\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwww.facebook.com\u002Fsharer\u002Fsharer.php?u=https%3A%2F%2Floggix.com%2Ffilemaker-2025-is-here-36514%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Ftwitter.com\u002Fintent\u002Ftweet?text=FileMaker+2025+is+here%21+-+Loggix+%7C+Software+Development.+https%3A%2F%2Floggix.com%2Ffilemaker-2025-is-here-36514%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Fwww.linkedin.com\u002FshareArticle?mini=true&url=https%3A%2F%2Floggix.com%2Ffilemaker-2025-is-here-36514%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Fpinterest.com\u002Fpin\u002Ffind\u002F?url=https%3A%2F%2Floggix.com%2Ffilemaker-2025-is-here-36514%2F\">\u003C\u002Fa>\u003C\u002Fp>\n","2025-07-09",1781519868000,[23],"\u002Fapi\u002Fknowledge\u002Fimage\u002F32\u002F?v=6d10a0ee7628",{"id":567,"idKnowledge":568,"idDomain":15,"idCluster":15,"slug":569,"title":570,"description":571,"bodyMarkdown":572,"bodyHtml":573,"author":514,"date":562,"createdAt":540,"topics":574,"image":575,"hasDownload":28,"fileName":15,"youtubeId":27},"31","EC7A8F70-5DA1-784A-9FF3-FF0F26118F1E","filemaker-2025-tip-warning","FileMaker 2025 Tip & Warning","Claris introduced Filemaker 2025, actually and update on the 2024 version and therefore no icon change… and that might be not so cool.","**With FileMaker 2025 Claris introduces powerful new AI tools, streamlined development features, and improved server capabilities. With native support for local and cloud-based LLMs, it’s now easier to build intelligent custom apps. Developers benefit from better scripting, layout introspection, and modern SQL support. A unified license gives access to FileMaker, Studio, and Connect. This release marks a big step toward smarter, integrated app development.**\n\nThis 2025 update is not without discussion. Claris still lacks behind when it comes to full AI integration for developers... Although low-code, in comparison to the Cursor's and Lovable's of this world our  development environment looks a bit ancient. But let us agree that this is a good client side update, the next one will definitely be (or should) a developers treat. \n\n**Warning updating to 2025**  \nBut indeed first a warning for those developers that are ready to install 2025. This install is a UPDATE, not a full new installation. This means you will update your current (21.x) version to 2025 (22.x). And that means that you will NOT be able to open databases that are currently hosted on FMS19 servers!  \n  \n**With FM2025 you can connect to FileMaker Server running 21.0., 21.1.x and 22.0.**\n\n**Little trick to help you out.**  \nSo install a second instance of your 2024 (21.x) version and only update this version. Your now will have two instances of FileMaker on your machine, one that will still open FM19 and above. And one that ca be used to support the new 2025 features.  \n  \n**For Mac users:** in your application bar at the bottom TWO versions of filemaker might now show up. Both with the same icon. Annoying! So with this little trick you can make your live a bit easier....   \n  \n1\\. Download this file:  [FM25Icon](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F07\u002Ffm25.png)  \n2\\. Go to your Applications Folder  \n3\\. Right-Click on the FM2025 application icon  \n4\\. Choose the \"Show Info\" option  \n5\\. Replace the icon in the top left corner with the downloaded file\n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F07\u002Freplace.png)\n\n**That's it for today, enjoy the new Claris FileMaker 2025!**\n\nShare\n\n[](https:\u002F\u002Fwww.facebook.com\u002Fsharer\u002Fsharer.php?u=https%3A%2F%2Floggix.com%2Ffilemaker-2025-tip-warning-36519%2F)[](https:\u002F\u002Ftwitter.com\u002Fintent\u002Ftweet?text=FileMaker+2025+Tip+%26amp%3B+Warning+-+Loggix+%7C+Software+Development.+https%3A%2F%2Floggix.com%2Ffilemaker-2025-tip-warning-36519%2F)[](https:\u002F\u002Fwww.linkedin.com\u002FshareArticle?mini=true&url=https%3A%2F%2Floggix.com%2Ffilemaker-2025-tip-warning-36519%2F)[](https:\u002F\u002Fpinterest.com\u002Fpin\u002Ffind\u002F?url=https%3A%2F%2Floggix.com%2Ffilemaker-2025-tip-warning-36519%2F)","\u003Cp>\u003Cstrong>With FileMaker 2025 Claris introduces powerful new AI tools, streamlined development features, and improved server capabilities. With native support for local and cloud-based LLMs, it’s now easier to build intelligent custom apps. Developers benefit from better scripting, layout introspection, and modern SQL support. A unified license gives access to FileMaker, Studio, and Connect. This release marks a big step toward smarter, integrated app development.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>This 2025 update is not without discussion. Claris still lacks behind when it comes to full AI integration for developers... Although low-code, in comparison to the Cursor's and Lovable's of this world our  development environment looks a bit ancient. But let us agree that this is a good client side update, the next one will definitely be (or should) a developers treat. \u003C\u002Fp>\n\u003Cp>\u003Cstrong>Warning updating to 2025\u003C\u002Fstrong>\u003Cbr>But indeed first a warning for those developers that are ready to install 2025. This install is a UPDATE, not a full new installation. This means you will update your current (21.x) version to 2025 (22.x). And that means that you will NOT be able to open databases that are currently hosted on FMS19 servers!  \u003C\u002Fp>\n\u003Cp>\u003Cstrong>With FM2025 you can connect to FileMaker Server running 21.0., 21.1.x and 22.0.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Little trick to help you out.\u003C\u002Fstrong>\u003Cbr>So install a second instance of your 2024 (21.x) version and only update this version. Your now will have two instances of FileMaker on your machine, one that will still open FM19 and above. And one that ca be used to support the new 2025 features.  \u003C\u002Fp>\n\u003Cp>\u003Cstrong>For Mac users:\u003C\u002Fstrong> in your application bar at the bottom TWO versions of filemaker might now show up. Both with the same icon. Annoying! So with this little trick you can make your live a bit easier....   \u003C\u002Fp>\n\u003Cp>1. Download this file:  \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F07\u002Ffm25.png\">FM25Icon\u003C\u002Fa>\u003Cbr>2. Go to your Applications Folder\u003Cbr>3. Right-Click on the FM2025 application icon\u003Cbr>4. Choose the "Show Info" option\u003Cbr>5. Replace the icon in the top left corner with the downloaded file\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F07\u002Freplace.png\" alt=\"\">\u003C\u002Fp>\n\u003Cp>\u003Cstrong>That's it for today, enjoy the new Claris FileMaker 2025!\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Share\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwww.facebook.com\u002Fsharer\u002Fsharer.php?u=https%3A%2F%2Floggix.com%2Ffilemaker-2025-tip-warning-36519%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Ftwitter.com\u002Fintent\u002Ftweet?text=FileMaker+2025+Tip+%26amp%3B+Warning+-+Loggix+%7C+Software+Development.+https%3A%2F%2Floggix.com%2Ffilemaker-2025-tip-warning-36519%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Fwww.linkedin.com\u002FshareArticle?mini=true&url=https%3A%2F%2Floggix.com%2Ffilemaker-2025-tip-warning-36519%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Fpinterest.com\u002Fpin\u002Ffind\u002F?url=https%3A%2F%2Floggix.com%2Ffilemaker-2025-tip-warning-36519%2F\">\u003C\u002Fa>\u003C\u002Fp>\n",[23],"\u002Fapi\u002Fknowledge\u002Fimage\u002F31\u002F?v=1a9205422807",{"id":577,"idKnowledge":578,"idDomain":15,"idCluster":15,"slug":579,"title":580,"description":581,"bodyMarkdown":582,"bodyHtml":583,"author":514,"date":584,"createdAt":563,"topics":585,"image":586,"hasDownload":28,"fileName":15,"youtubeId":27},"33","1B2AA056-B29F-DE4F-90C9-4DA6342904BD","filemaker-app-cross-borders-working-with-exchange-rates-timezones-vat-validation-and-address-autocompletion","FileMaker App cross borders: Working with Exchange Rates, Timezones, VAT Validation and Address Autocompletion","Want to internationalize your FileMaker solution? This article walks you through APIs and Insert from URL examples for exchange rates, timezones, VAT validation, and address auto-completion.”","As a FileMaker developer, you're often focused on solving business problems—managing clients, tracking hours, generating invoices, etc. But what happens when your application needs to **cross borders**? Whether you're building a solution used by international teams, or serving clients in different countries, you'll likely need to support **currency conversion, timezone awareness, VAT validation, and international address input**.\n\nIn this post, we’ll walk through some **ready-to-use API examples** that can help you make your FileMaker app truly international.\n\n#### 1\\. Currency Conversion with CurrencyFreaks\n\n##### 🔗 API: [api.currencyfreaks.com](https:\u002F\u002Fcurrencyfreaks.com\u002F)\n\nUse this to fetch real-time exchange rates. You're generating an invoice in USD, but your client pays in EUR. You want to show the conversion rate.\n\nSet Variable \\[ $url ;\n  \"https:\u002F\u002Fapi.currencyfreaks.com\u002Flatest?apikey=YOUR\\_API\\_KEY&symbols=EUR,GBP&base=USD\" \\]\nInsert from URL \\[\n  Select ;\n  With dialog: Off ;\n  Target: $json ;\n  $url\n\\]\nSet Variable \\[ $eurRate ; JSONGetElement ( $json ; \"rates.EUR\" ) \\]\n\n#### 2\\. IP-Based Timezone Recognition with IPGeolocation\n\n##### 🔗 API: api.ipgeolocation.io\u002Ftimezone\n\nDetect the timezone of a user based on IP, ideal for language or Timezone recognition. You want to display a time field or send a reminder based on the user’s local timezone.\n\nSet Variable \\[ $ip ; Get ( SysteemIPadres ) \\] \u002F\u002F Or fetch dynamically via another API\nSet Variable \\[ $url ;\n  \"https:\u002F\u002Fapi.ipgeolocation.io\u002Ftimezone?apiKey=YOUR\\_API\\_KEY&ip=\" & $ip \\]\nInsert from URL \\[\n  Select ;\n  With dialog: Off ;\n  Target: $json ;\n  $url\n\\]\nSet Variable \\[ $timezone ; JSONGetElement ( $json ; \"timezone\" ) \\]\nSet Variable \\[ $localTime ; JSONGetElement ( $json ; \"date\\_time\\_txt\" ) \\]\n\n#### 3\\. Validate EU VAT Numbers\n\n##### 🔗 API: [controleerbtwnummer.eu](https:\u002F\u002Fcontroleerbtwnummer.eu\u002F)\n\nValidate the format and status of EU VAT numbers.You're onboarding a new B2B client and need to validate their VAT number automatically.\n\nSet Variable \\[ $vat ; \"NL123456789B01\" \\]  \u002F\u002FEnter new VAT number\nSet Variable \\[ $url ;\n  \"https:\u002F\u002Fapi.controleerbtwnummer.eu\u002Fv1\u002F\" & $vat & \"?apikey=YOUR\\_API\\_KEY\" \\]\nInsert from URL \\[\n  Select ;\n  With dialog: Off ;\n  Target: $json ;\n  $url\n\\]\nSet Variable \\[ $valid ; JSONGetElement ( $json ; \"valid\" ) \\]  \u002F\u002F Check if API return 'valid'\n\n#### 4\\. Address Autocomplete with Pro6PP\n\n##### 🔗 API: pro6pp.nl\n\nAutocomplete addresses based on postal codes and house numbers. You want to speed up form-filling during checkout or registration by auto-filling city\u002Fstreet.\n\nSet Variable \\[ $postcode ; \"1012JS\" \\]\nSet Variable \\[ $number ; \"1\" \\]\nSet Variable \\[ $url ;\n  \"https:\u002F\u002Fapi.pro6pp.nl\u002Fv1\u002Fautocomplete?authKey=YOUR\\_API\\_KEY&postalcode=\" & $postcode & \"&number=\" & $number \\]\nInsert from URL \\[\n  Select ;\n  With dialog: Off ;\n  Target: $json ;\n  $url\n\\]\nSet Variable \\[ $street ; JSONGetElement ( $json ; \"results\\[0\\].street\" ) \\]\nSet Variable \\[ $city ; JSONGetElement ( $json ; \"results\\[0\\].city\" ) \\]\n\n#### 🔐 A Note on Security\n\nWhen using `Insert from URL` and external APIs:\n\n-   Always use **SSL (HTTPS)** endpoints.\n    \n-   Store API keys **securely** (use FileMaker's encrypted credentials or a protected table).\n    \n-   Handle errors using `Get(LastError)` and JSON validation logic.\n    \n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F07\u002Flock-e1751484350541.jpg)\n\n#### 🎯 Wrapping Up\n\nInternationalizing your FileMaker app doesn’t mean rebuilding it from scratch. With a few well-placed `Insert from URL`scripts and third-party APIs, you can surprise your clients and make your tool more valuable with minimum  effort. These tools let you build smarter, more context-aware apps that scale across borders. 🌐  \n  \nLoggix has build +100 different API connections over the years. If you need any help, let is know!\n\nShare\n\n[](https:\u002F\u002Fwww.facebook.com\u002Fsharer\u002Fsharer.php?u=https%3A%2F%2Floggix.com%2Ffilemaker-app-cross-borders-working-with-exchange-rates-timezones-vat-validation-and-address-autocompletion-36507%2F)[](https:\u002F\u002Ftwitter.com\u002Fintent\u002Ftweet?text=FileMaker+App+cross+borders%3A+Working+with+Exchange+Rates%2C+Timezones%2C+VAT+Validation+and+Address+Autocompletion+-+Loggix+%7C+Software+Development.+https%3A%2F%2Floggix.com%2Ffilemaker-app-cross-borders-working-with-exchange-rates-timezones-vat-validation-and-address-autocompletion-36507%2F)[](https:\u002F\u002Fwww.linkedin.com\u002FshareArticle?mini=true&url=https%3A%2F%2Floggix.com%2Ffilemaker-app-cross-borders-working-with-exchange-rates-timezones-vat-validation-and-address-autocompletion-36507%2F)[](https:\u002F\u002Fpinterest.com\u002Fpin\u002Ffind\u002F?url=https%3A%2F%2Floggix.com%2Ffilemaker-app-cross-borders-working-with-exchange-rates-timezones-vat-validation-and-address-autocompletion-36507%2F)","\u003Cp>As a FileMaker developer, you're often focused on solving business problems—managing clients, tracking hours, generating invoices, etc. But what happens when your application needs to \u003Cstrong>cross borders\u003C\u002Fstrong>? Whether you're building a solution used by international teams, or serving clients in different countries, you'll likely need to support \u003Cstrong>currency conversion, timezone awareness, VAT validation, and international address input\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>In this post, we’ll walk through some \u003Cstrong>ready-to-use API examples\u003C\u002Fstrong> that can help you make your FileMaker app truly international.\u003C\u002Fp>\n\u003Ch4>1. Currency Conversion with CurrencyFreaks\u003C\u002Fh4>\n\u003Ch5>🔗 API: \u003Ca href=\"https:\u002F\u002Fcurrencyfreaks.com\u002F\">api.currencyfreaks.com\u003C\u002Fa>\u003C\u002Fh5>\n\u003Cp>Use this to fetch real-time exchange rates. You're generating an invoice in USD, but your client pays in EUR. You want to show the conversion rate.\u003C\u002Fp>\n\u003Cp>Set Variable [ $url ;\n  "\u003Ca href=\"https:\u002F\u002Fapi.currencyfreaks.com\u002Flatest?apikey=YOUR%5C_API%5C_KEY&symbols=EUR,GBP&base=USD\">https:\u002F\u002Fapi.currencyfreaks.com\u002Flatest?apikey=YOUR\\_API\\_KEY&symbols=EUR,GBP&base=USD\u003C\u002Fa>" ]\nInsert from URL [\n  Select ;\n  With dialog: Off ;\n  Target: $json ;\n  $url\n]\nSet Variable [ $eurRate ; JSONGetElement ( $json ; "rates.EUR" ) ]\u003C\u002Fp>\n\u003Ch4>2. IP-Based Timezone Recognition with IPGeolocation\u003C\u002Fh4>\n\u003Ch5>🔗 API: api.ipgeolocation.io\u002Ftimezone\u003C\u002Fh5>\n\u003Cp>Detect the timezone of a user based on IP, ideal for language or Timezone recognition. You want to display a time field or send a reminder based on the user’s local timezone.\u003C\u002Fp>\n\u003Cp>Set Variable [ $ip ; Get ( SysteemIPadres ) ] \u002F\u002F Or fetch dynamically via another API\nSet Variable [ $url ;\n  "\u003Ca href=\"https:\u002F\u002Fapi.ipgeolocation.io\u002Ftimezone?apiKey=YOUR%5C_API%5C_KEY&ip=\">https:\u002F\u002Fapi.ipgeolocation.io\u002Ftimezone?apiKey=YOUR\\_API\\_KEY&ip=\u003C\u002Fa>" & $ip ]\nInsert from URL [\n  Select ;\n  With dialog: Off ;\n  Target: $json ;\n  $url\n]\nSet Variable [ $timezone ; JSONGetElement ( $json ; "timezone" ) ]\nSet Variable [ $localTime ; JSONGetElement ( $json ; "date_time_txt" ) ]\u003C\u002Fp>\n\u003Ch4>3. Validate EU VAT Numbers\u003C\u002Fh4>\n\u003Ch5>🔗 API: \u003Ca href=\"https:\u002F\u002Fcontroleerbtwnummer.eu\u002F\">controleerbtwnummer.eu\u003C\u002Fa>\u003C\u002Fh5>\n\u003Cp>Validate the format and status of EU VAT numbers.You're onboarding a new B2B client and need to validate their VAT number automatically.\u003C\u002Fp>\n\u003Cp>Set Variable [ $vat ; "NL123456789B01" ]  \u002F\u002FEnter new VAT number\nSet Variable [ $url ;\n  "\u003Ca href=\"https:\u002F\u002Fapi.controleerbtwnummer.eu\u002Fv1\u002F\">https:\u002F\u002Fapi.controleerbtwnummer.eu\u002Fv1\u002F\u003C\u002Fa>" & $vat & "?apikey=YOUR_API_KEY" ]\nInsert from URL [\n  Select ;\n  With dialog: Off ;\n  Target: $json ;\n  $url\n]\nSet Variable [ $valid ; JSONGetElement ( $json ; "valid" ) ]  \u002F\u002F Check if API return 'valid'\u003C\u002Fp>\n\u003Ch4>4. Address Autocomplete with Pro6PP\u003C\u002Fh4>\n\u003Ch5>🔗 API: pro6pp.nl\u003C\u002Fh5>\n\u003Cp>Autocomplete addresses based on postal codes and house numbers. You want to speed up form-filling during checkout or registration by auto-filling city\u002Fstreet.\u003C\u002Fp>\n\u003Cp>Set Variable [ $postcode ; "1012JS" ]\nSet Variable [ $number ; "1" ]\nSet Variable [ $url ;\n  "\u003Ca href=\"https:\u002F\u002Fapi.pro6pp.nl\u002Fv1\u002Fautocomplete?authKey=YOUR%5C_API%5C_KEY&postalcode=\">https:\u002F\u002Fapi.pro6pp.nl\u002Fv1\u002Fautocomplete?authKey=YOUR\\_API\\_KEY&postalcode=\u003C\u002Fa>" & $postcode & "&number=" & $number ]\nInsert from URL [\n  Select ;\n  With dialog: Off ;\n  Target: $json ;\n  $url\n]\nSet Variable [ $street ; JSONGetElement ( $json ; "results[0].street" ) ]\nSet Variable [ $city ; JSONGetElement ( $json ; "results[0].city" ) ]\u003C\u002Fp>\n\u003Ch4>🔐 A Note on Security\u003C\u002Fh4>\n\u003Cp>When using \u003Ccode>Insert from URL\u003C\u002Fcode> and external APIs:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cp>Always use \u003Cstrong>SSL (HTTPS)\u003C\u002Fstrong> endpoints.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>Store API keys \u003Cstrong>securely\u003C\u002Fstrong> (use FileMaker's encrypted credentials or a protected table).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>Handle errors using \u003Ccode>Get(LastError)\u003C\u002Fcode> and JSON validation logic.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F07\u002Flock-e1751484350541.jpg\" alt=\"\">\u003C\u002Fp>\n\u003Ch4>🎯 Wrapping Up\u003C\u002Fh4>\n\u003Cp>Internationalizing your FileMaker app doesn’t mean rebuilding it from scratch. With a few well-placed \u003Ccode>Insert from URL\u003C\u002Fcode>scripts and third-party APIs, you can surprise your clients and make your tool more valuable with minimum  effort. These tools let you build smarter, more context-aware apps that scale across borders. 🌐  \u003C\u002Fp>\n\u003Cp>Loggix has build +100 different API connections over the years. If you need any help, let is know!\u003C\u002Fp>\n\u003Cp>Share\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwww.facebook.com\u002Fsharer\u002Fsharer.php?u=https%3A%2F%2Floggix.com%2Ffilemaker-app-cross-borders-working-with-exchange-rates-timezones-vat-validation-and-address-autocompletion-36507%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Ftwitter.com\u002Fintent\u002Ftweet?text=FileMaker+App+cross+borders%3A+Working+with+Exchange+Rates%2C+Timezones%2C+VAT+Validation+and+Address+Autocompletion+-+Loggix+%7C+Software+Development.+https%3A%2F%2Floggix.com%2Ffilemaker-app-cross-borders-working-with-exchange-rates-timezones-vat-validation-and-address-autocompletion-36507%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Fwww.linkedin.com\u002FshareArticle?mini=true&url=https%3A%2F%2Floggix.com%2Ffilemaker-app-cross-borders-working-with-exchange-rates-timezones-vat-validation-and-address-autocompletion-36507%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Fpinterest.com\u002Fpin\u002Ffind\u002F?url=https%3A%2F%2Floggix.com%2Ffilemaker-app-cross-borders-working-with-exchange-rates-timezones-vat-validation-and-address-autocompletion-36507%2F\">\u003C\u002Fa>\u003C\u002Fp>\n","2025-07-02",[23],"\u002Fapi\u002Fknowledge\u002Fimage\u002F33\u002F?v=89a145486f30",{"id":588,"idKnowledge":589,"idDomain":15,"idCluster":15,"slug":590,"title":591,"description":592,"bodyMarkdown":593,"bodyHtml":594,"author":514,"date":595,"createdAt":563,"topics":596,"image":597,"hasDownload":28,"fileName":15,"youtubeId":27},"34","53CA4347-9113-F84E-89F4-56618778E7CF","useful-tools-for-vue-js-developers","Useful Tools for Vue.js Developers","Discover must-have websites that every Vue.js developer should bookmark. From UI inspiration to workflow boosters, these tools will help you build better, faster, and cleaner user interfaces.","##### Vue.js is an important Framework we rely on to hook up Claris FileMaker to the web. Many of the projects at Loggix are co-pair-developments between a backend (Filemaker) and a frontend developer. For our Vue.js developers, building clean and functional user interfaces is crucial. Luckily, whether they are working with Tailwind CSS, designing component libraries, or just looking to speed up their workflow, there’s a wealth of tools available online.\n\nIn this post, we will curate useful websites for you as Vue.js developer. These tools will also boost your productivity, inspire your design ideas and help you build better UIs—faster. As new tools come to our disposal on a daily basis, we will keep an eye out and extend this post when we think you might be missing out on some of the pearls.\n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F07\u002FOmatsuni-e1751381584418.jpg)\n\n### #1. Omatsuri Triangle Generator\n\nNeed a CSS triangle for a tooltip, dropdown, or custom component? The Omatsuri Triangle Generator is a super simple yet powerful tool that lets you customize triangle size, direction, and color—and instantly get the  \nCSS code. 💡 Perfect for: Custom popovers, arrows in tooltips, CSS-only designs.\n\n[Go to website](https:\u002F\u002Fomatsuri.app\u002Ftriangle-generator)\n\n### #2. Uiverse.io\n\nThis is a goldmine for frontend devs. Uiverse offers hundreds of stylish and responsive UI components—like loaders, toggle switches, modals, buttons, and more. All elements are created by the community and easy to drop into your Vue components.💡 Perfect for: Rapid prototyping, UI inspiration, reusable components.\n\n[Go to website](https:\u002F\u002Fuiverse.io\u002Felements)\n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F07\u002FUiverse-e1751382162774.jpg)\n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F07\u002Fhyperui-e1751382597738.jpg)\n\n### #3. Hyperui.dev\n\nHyperUI provides high-quality, production-ready Tailwind CSS components—completely free. Includes layouts,modals, form inputs, and more. Every component follows best design practices, making them ideal for Vue-based projects. 💡 Perfect for: Building dashboards, admin panels, marketing sites.\n\n[Go to website](https:\u002F\u002Fwww.hyperui.dev\u002F)\n\nMore to come soon...\n\nShare\n\n[](https:\u002F\u002Fwww.facebook.com\u002Fsharer\u002Fsharer.php?u=https%3A%2F%2Floggix.com%2Fuseful-tools-for-vue-js-developers-36496%2F)[](https:\u002F\u002Ftwitter.com\u002Fintent\u002Ftweet?text=Useful+Tools+for+Vue.js+Developers+-+Loggix+%7C+Software+Development.+https%3A%2F%2Floggix.com%2Fuseful-tools-for-vue-js-developers-36496%2F)[](https:\u002F\u002Fwww.linkedin.com\u002FshareArticle?mini=true&url=https%3A%2F%2Floggix.com%2Fuseful-tools-for-vue-js-developers-36496%2F)[](https:\u002F\u002Fpinterest.com\u002Fpin\u002Ffind\u002F?url=https%3A%2F%2Floggix.com%2Fuseful-tools-for-vue-js-developers-36496%2F)","\u003Ch5>Vue.js is an important Framework we rely on to hook up Claris FileMaker to the web. Many of the projects at Loggix are co-pair-developments between a backend (Filemaker) and a frontend developer. For our Vue.js developers, building clean and functional user interfaces is crucial. Luckily, whether they are working with Tailwind CSS, designing component libraries, or just looking to speed up their workflow, there’s a wealth of tools available online.\u003C\u002Fh5>\n\u003Cp>In this post, we will curate useful websites for you as Vue.js developer. These tools will also boost your productivity, inspire your design ideas and help you build better UIs—faster. As new tools come to our disposal on a daily basis, we will keep an eye out and extend this post when we think you might be missing out on some of the pearls.\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F07\u002FOmatsuni-e1751381584418.jpg\" alt=\"\">\u003C\u002Fp>\n\u003Ch3>#1. Omatsuri Triangle Generator\u003C\u002Fh3>\n\u003Cp>Need a CSS triangle for a tooltip, dropdown, or custom component? The Omatsuri Triangle Generator is a super simple yet powerful tool that lets you customize triangle size, direction, and color—and instantly get the\u003Cbr>CSS code. 💡 Perfect for: Custom popovers, arrows in tooltips, CSS-only designs.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fomatsuri.app\u002Ftriangle-generator\">Go to website\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>#2. Uiverse.io\u003C\u002Fh3>\n\u003Cp>This is a goldmine for frontend devs. Uiverse offers hundreds of stylish and responsive UI components—like loaders, toggle switches, modals, buttons, and more. All elements are created by the community and easy to drop into your Vue components.💡 Perfect for: Rapid prototyping, UI inspiration, reusable components.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fuiverse.io\u002Felements\">Go to website\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F07\u002FUiverse-e1751382162774.jpg\" alt=\"\">\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F07\u002Fhyperui-e1751382597738.jpg\" alt=\"\">\u003C\u002Fp>\n\u003Ch3>#3. Hyperui.dev\u003C\u002Fh3>\n\u003Cp>HyperUI provides high-quality, production-ready Tailwind CSS components—completely free. Includes layouts,modals, form inputs, and more. Every component follows best design practices, making them ideal for Vue-based projects. 💡 Perfect for: Building dashboards, admin panels, marketing sites.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwww.hyperui.dev\u002F\">Go to website\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>More to come soon...\u003C\u002Fp>\n\u003Cp>Share\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwww.facebook.com\u002Fsharer\u002Fsharer.php?u=https%3A%2F%2Floggix.com%2Fuseful-tools-for-vue-js-developers-36496%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Ftwitter.com\u002Fintent\u002Ftweet?text=Useful+Tools+for+Vue.js+Developers+-+Loggix+%7C+Software+Development.+https%3A%2F%2Floggix.com%2Fuseful-tools-for-vue-js-developers-36496%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Fwww.linkedin.com\u002FshareArticle?mini=true&url=https%3A%2F%2Floggix.com%2Fuseful-tools-for-vue-js-developers-36496%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Fpinterest.com\u002Fpin\u002Ffind\u002F?url=https%3A%2F%2Floggix.com%2Fuseful-tools-for-vue-js-developers-36496%2F\">\u003C\u002Fa>\u003C\u002Fp>\n","2025-07-01",[23],"\u002Fapi\u002Fknowledge\u002Fimage\u002F34\u002F?v=6c84bda8e848",{"id":599,"idKnowledge":600,"idDomain":15,"idCluster":15,"slug":601,"title":602,"description":603,"bodyMarkdown":604,"bodyHtml":605,"author":514,"date":606,"createdAt":607,"topics":608,"image":609,"hasDownload":28,"fileName":15,"youtubeId":27},"67","DDD9E3F4-F70A-B64E-B8F6-AD4FD56ED07C","why-your-filemaker-crm-needs-a-data-upgrade-and-how-to-start-today","Why Your FileMaker CRM Needs a Data Upgrade (and How to Start Today)","Most FileMaker CRMs suffer from outdated or incomplete data. In this post, we explore smart ways to clean, enrich, and maintain your CRM using tools like Google Places API, Hunter.io, and ChatGPT—combined with automation via n8n and FileMaker scripting. A must-read if your database needs a health ch","##### \\[PART 1\\]\n\n**The majority of the FileMaker databases and solutions out in the field have a CRM-related component in them. They hold client (address) information that is used on a daily basis by sales departments for marketing, cold calling, quote or order creation.**\n\n[FileMaker](http:\u002F\u002Fwww.claris.com) offers great flexibility in the way you want to store or use this data. Unfortunately, this flexibility comes with a price. CRM systems are easily poorly maintained; they quickly contain old, irrelevant, or incomplete data. The way data is entered is often inconsistent—if at all sources or creators are mentioned. Besides, in most use cases, we see a lack of assigned responsibility for data maintenance.\n\nAnd yet, your CRM is only as valuable as the data it holds.\n\n**What Does Good Data Management Look Like?**\n\nBefore diving into practical upgrades, let’s quickly outline the core steps for proper CRM data hygiene—something we’ll cover more extensively in future blog posts:\n\n1.  1.  **Define ownership** – Make someone responsible for data quality.\n    2.  **Standardize input** – Use validations, dropdowns, and templates to guide consistent data entry.\n    3.  **Enrich existing records** – Use external sources to fill in missing info (more on this below).\n    4.  **Detect duplicates** – Regularly run deduplication scripts or use fuzzy matching tools.\n    5.  **Clean up stale data** – Archive or remove contacts that are outdated or unresponsive.\n    6.  **Audit trails** – Track changes and edits to ensure accountability.\n    7.  **Review routines** – Schedule periodic checks to keep your data healthy.\n\n[\n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002FgoogleApi-e1751200342515.jpg)](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002FgoogleApi-e1751200342515.jpg#36492)\n\n[](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002FgoogleApi-e1751200342515.jpg#36492)\n\n**Enriching Data: Smarter Records with the help of API's and AI**\n\nEven with good input practices, most CRMs are still born incomplete. Addresses without coordinates, companies without phone numbers, leads without email verification—the gaps are real. Fortunately, the modern web offers powerful tools to enrich this data without relying on manual research.  \n  \n\n**📍 Google Places API: Turn a Company Name into a Real Address**\n\nWhen you have only the company name and city, Google Places API can often return:\n\n-   -   Full address and coordinates\n    -   Website and phone number\n    -   Business category\n    -   User reviews (sometimes surprisingly insightful)\n\nFor example, entering _“Hofleverancier van der Laan, Utrecht”_ can return a rich structured record with just a simple API call. This is especially valuable when cleaning up lead lists, verifying company locations, or mapping contacts for sales reps.\n\n[\n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002Fscraper-e1751199772493.jpg)](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002Fscraper-e1751199772493.jpg#36491)\n\n[](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002Fscraper-e1751199772493.jpg#36491)\n\n**🔍 Hunter.io & Similar Tools: Fill In the Blanks (Legally)**\n\nHunter, Clearbit, and similar services allow you to:\n\n-   -   Find email addresses linked to a company domain\n    -   Validate whether emails are deliverable\n    -   Discover social profiles of leads\n    -   Identify job titles and roles\n\nUse cases?\n\n-   -   **You have a list of domains but no contact emails.**\n    -   **You want to verify that a contact still works at a given company.**\n    -   **You want to target only marketing managers or CTOs.**\n\nWith the right tools (and FileMaker’s support for REST APIs), all of this can be integrated directly into your CRM workflow—automatically enriching your records without a single Google search.\n\n**And of course, let’s not forget AI.**\n\nIntegrating your CRM with AI tools like ChatGPT opens up unprecedented possibilities for data enrichment. In many cases, simply providing ChatGPT with a name or address can already yield valuable insights—though the results may vary depending on context and formatting.\n\nWhen combined with automation platforms like n8n and well-crafted prompts, the quality and consistency of enrichment improve significantly. However, it’s important to note that ChatGPT is not well-suited for processing large datasets in bulk through a single prompt. For such cases, a FileMaker script with a loop—feeding individual records to ChatGPT one at a time—can offer a more stable and controlled approach to AI-assisted enrichment.\n\n**It is not hard to start cleaning up**\n\nIf your CRM is a graveyard of outdated leads, unstructured company names, or broken email addresses, you’re not alone. But you also don’t have to start from scratch.\n\nBy assigning ownership, structuring inputs, and connecting to external data sources like Google Places and Hunter in combination with ChatGPT, you can transform your FileMaker system into a truly intelligent CRM—one that works for you instead of the other way around.\n\n**In the next blog posts, we’ll dive deeper into each step: from duplicate detection strategies to automated company lookups and building a simple enrichment flow using FileMaker scripts + APIs + AI.  \n  \n****Can't wait? Contact us and we can work on your next project!**\n\nShare\n\n[](https:\u002F\u002Fwww.facebook.com\u002Fsharer\u002Fsharer.php?u=https%3A%2F%2Floggix.com%2Fenrich-build-up-lead-database-in-filemaker-36489%2F)[](https:\u002F\u002Ftwitter.com\u002Fintent\u002Ftweet?text=Why+Your+FileMaker+CRM+Needs+a+Data+Upgrade+%28and+How+to+Start+Today%29+-+Loggix+%7C+Software+Development.+https%3A%2F%2Floggix.com%2Fenrich-build-up-lead-database-in-filemaker-36489%2F)[](https:\u002F\u002Fwww.linkedin.com\u002FshareArticle?mini=true&url=https%3A%2F%2Floggix.com%2Fenrich-build-up-lead-database-in-filemaker-36489%2F)[](https:\u002F\u002Fpinterest.com\u002Fpin\u002Ffind\u002F?url=https%3A%2F%2Floggix.com%2Fenrich-build-up-lead-database-in-filemaker-36489%2F)","\u003Ch5>[PART 1]\u003C\u002Fh5>\n\u003Cp>\u003Cstrong>The majority of the FileMaker databases and solutions out in the field have a CRM-related component in them. They hold client (address) information that is used on a daily basis by sales departments for marketing, cold calling, quote or order creation.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"http:\u002F\u002Fwww.claris.com\">FileMaker\u003C\u002Fa> offers great flexibility in the way you want to store or use this data. Unfortunately, this flexibility comes with a price. CRM systems are easily poorly maintained; they quickly contain old, irrelevant, or incomplete data. The way data is entered is often inconsistent—if at all sources or creators are mentioned. Besides, in most use cases, we see a lack of assigned responsibility for data maintenance.\u003C\u002Fp>\n\u003Cp>And yet, your CRM is only as valuable as the data it holds.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What Does Good Data Management Look Like?\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Before diving into practical upgrades, let’s quickly outline the core steps for proper CRM data hygiene—something we’ll cover more extensively in future blog posts:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Col>\n\u003Cli>\u003Cstrong>Define ownership\u003C\u002Fstrong> – Make someone responsible for data quality.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Standardize input\u003C\u002Fstrong> – Use validations, dropdowns, and templates to guide consistent data entry.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Enrich existing records\u003C\u002Fstrong> – Use external sources to fill in missing info (more on this below).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Detect duplicates\u003C\u002Fstrong> – Regularly run deduplication scripts or use fuzzy matching tools.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Clean up stale data\u003C\u002Fstrong> – Archive or remove contacts that are outdated or unresponsive.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Audit trails\u003C\u002Fstrong> – Track changes and edits to ensure accountability.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Review routines\u003C\u002Fstrong> – Schedule periodic checks to keep your data healthy.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>[\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002FgoogleApi-e1751200342515.jpg\" alt=\"\">](\u003Ca href=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002FgoogleApi-e1751200342515.jpg#36492\">https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002FgoogleApi-e1751200342515.jpg#36492\u003C\u002Fa>)\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002FgoogleApi-e1751200342515.jpg#36492\">\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Enriching Data: Smarter Records with the help of API's and AI\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Even with good input practices, most CRMs are still born incomplete. Addresses without coordinates, companies without phone numbers, leads without email verification—the gaps are real. Fortunately, the modern web offers powerful tools to enrich this data without relying on manual research.  \u003C\u002Fp>\n\u003Cp>\u003Cstrong>📍 Google Places API: Turn a Company Name into a Real Address\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>When you have only the company name and city, Google Places API can often return:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cul>\n\u003Cli>Full address and coordinates\u003C\u002Fli>\n\u003Cli>Website and phone number\u003C\u002Fli>\n\u003Cli>Business category\u003C\u002Fli>\n\u003Cli>User reviews (sometimes surprisingly insightful)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>For example, entering \u003Cem>“Hofleverancier van der Laan, Utrecht”\u003C\u002Fem> can return a rich structured record with just a simple API call. This is especially valuable when cleaning up lead lists, verifying company locations, or mapping contacts for sales reps.\u003C\u002Fp>\n\u003Cp>[\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002Fscraper-e1751199772493.jpg\" alt=\"\">](\u003Ca href=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002Fscraper-e1751199772493.jpg#36491\">https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002Fscraper-e1751199772493.jpg#36491\u003C\u002Fa>)\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002Fscraper-e1751199772493.jpg#36491\">\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>🔍 Hunter.io & Similar Tools: Fill In the Blanks (Legally)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Hunter, Clearbit, and similar services allow you to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cul>\n\u003Cli>Find email addresses linked to a company domain\u003C\u002Fli>\n\u003Cli>Validate whether emails are deliverable\u003C\u002Fli>\n\u003Cli>Discover social profiles of leads\u003C\u002Fli>\n\u003Cli>Identify job titles and roles\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Use cases?\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cul>\n\u003Cli>\u003Cstrong>You have a list of domains but no contact emails.\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>You want to verify that a contact still works at a given company.\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>You want to target only marketing managers or CTOs.\u003C\u002Fstrong>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>With the right tools (and FileMaker’s support for REST APIs), all of this can be integrated directly into your CRM workflow—automatically enriching your records without a single Google search.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>And of course, let’s not forget AI.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Integrating your CRM with AI tools like ChatGPT opens up unprecedented possibilities for data enrichment. In many cases, simply providing ChatGPT with a name or address can already yield valuable insights—though the results may vary depending on context and formatting.\u003C\u002Fp>\n\u003Cp>When combined with automation platforms like n8n and well-crafted prompts, the quality and consistency of enrichment improve significantly. However, it’s important to note that ChatGPT is not well-suited for processing large datasets in bulk through a single prompt. For such cases, a FileMaker script with a loop—feeding individual records to ChatGPT one at a time—can offer a more stable and controlled approach to AI-assisted enrichment.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>It is not hard to start cleaning up\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>If your CRM is a graveyard of outdated leads, unstructured company names, or broken email addresses, you’re not alone. But you also don’t have to start from scratch.\u003C\u002Fp>\n\u003Cp>By assigning ownership, structuring inputs, and connecting to external data sources like Google Places and Hunter in combination with ChatGPT, you can transform your FileMaker system into a truly intelligent CRM—one that works for you instead of the other way around.\u003C\u002Fp>\n\u003Cp>**In the next blog posts, we’ll dive deeper into each step: from duplicate detection strategies to automated company lookups and building a simple enrichment flow using FileMaker scripts + APIs + AI.  \u003C\u002Fp>\n\u003Cp>**\u003Cstrong>Can't wait? Contact us and we can work on your next project!\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Share\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwww.facebook.com\u002Fsharer\u002Fsharer.php?u=https%3A%2F%2Floggix.com%2Fenrich-build-up-lead-database-in-filemaker-36489%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Ftwitter.com\u002Fintent\u002Ftweet?text=Why+Your+FileMaker+CRM+Needs+a+Data+Upgrade+%28and+How+to+Start+Today%29+-+Loggix+%7C+Software+Development.+https%3A%2F%2Floggix.com%2Fenrich-build-up-lead-database-in-filemaker-36489%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Fwww.linkedin.com\u002FshareArticle?mini=true&url=https%3A%2F%2Floggix.com%2Fenrich-build-up-lead-database-in-filemaker-36489%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Fpinterest.com\u002Fpin\u002Ffind\u002F?url=https%3A%2F%2Floggix.com%2Fenrich-build-up-lead-database-in-filemaker-36489%2F\">\u003C\u002Fa>\u003C\u002Fp>\n","2025-06-28",1781520660000,[23],"\u002Fapi\u002Fknowledge\u002Fimage\u002F67\u002F?v=6547b3483a2c",{"id":611,"idKnowledge":612,"idDomain":15,"idCluster":15,"slug":613,"title":614,"description":615,"bodyMarkdown":616,"bodyHtml":617,"author":514,"date":618,"createdAt":619,"topics":620,"image":621,"hasDownload":28,"fileName":15,"youtubeId":27},"68","1A8B310B-C997-034B-A221-DCFF087ED24A","printing-from-filemaker-server-is-possible","Printing from FileMaker Server is possible","In some business processes it is of great use if prints are available without executing the print command from a client workstation. In a high capacity workflow like i.e. order picking, printing is basically a waste of time. Having a server print packing slips as orders come in, is much easier and f","[\n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002FFMS_Printing.jpg)](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002FFMS_Printing.jpg#36452)\n\n[](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002FFMS_Printing.jpg#36452)\n\n##### **In some business processes it is of great use if prints are available without executing the print command from a client workstation. In a high capacity workflow like i.e. order picking, printing is basically a waste of time. Having a server print packing slips as orders come in, is much easier and faster.**\n\nUnfortunately [FileMaker](http:\u002F\u002Ffilemaker.com\u002F) does not support the print functionality when executed in a script on the server. Filemaker Server (FMS) is what we call ‘headless’ and does support printer setup but not the actual print command. This renders the standard “scheduled scripts” as execution option useless. Even when you could print, where would you print to? The server is usually a cloud-machine that has not printers connected right?  \n  \nNow, is printing from a cloud FMS to local printers possible?\n\nSetup FMS Printing\n\nYes, if you want to prevent a ‘workstation as printer robot’ in your network and would like FMS Server to take care of the printing, this is possible. Even when your FileMaker Server is in the cloud and you do not have a in-house print server! There are 4 steps needed to print from FMS:  \n  \n1\\. a document to print (i.e. a PDF file)  \n2\\. a system script that can handle the documents and offer them to get printed  \n3\\. PDF reader that can open en print the document  \n4\\. a network printer that can receive the print command and output your document.\n\n**Ad. 1 Generating a File from a script**\n\nGenerating a file (i.e. a PDF) from a Filemaker script is luckily an option that is supported by FMS. The option “Save record as PDF” for example will give you the option to save your selected record(s) based on the current layout to a (multi page) PDF file. There are also plugins that can help you do this.  \n  \nAd. 2. System Scripts\n\nFileMaker Server offers us the option to execute scheduled FileMaker Scripts, this must be a familiar option to most of you. But besides scheduling Filemaker Scripts, FMS will let you also execute so called System Scripts. These are scripts that run on the server (i.e. Applescripts on Mac or PowerShell scripts on Windows).  \n  \nUsing this System Script option we are able to call “Print” functionality outside of FMS that is not available inside FMS. Below you find an example of some basic scripts that can be used to achieve printing from FMS by a Windows PowerShell script (ps1). Because FMS does not handle .ps1 script very well, in this example we call a batch script (.bat) that in itself calls the .ps1 script.\n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002Fscripts.jpg)\n\nSo as seen in the screen shot above we call: run-printscript.bat which looks like this:\n\npowershell.exe -ExecutionPolicy Bypass -File \"C:\\\\Program Files\\\\FileMaker\\\\FileMaker Server\\\\Data\\\\Scripts\\\\print-pdfs.ps1\"\n\nAnd the “run-printscript.bat” will call: print-pdfs.ps1 which looks like this:\n\n$watchFolder = \"C:\\\\PrintQueue\"\n$logFile = \"$watchFolder\\\\fms-print-log.txt\"\n$printedPath = Join-Path -Path $watchFolder -ChildPath \"Printed\"\n$failedPath = Join-Path -Path $watchFolder -ChildPath \"Failed\"\n$sumatraPath = \"C:\\\\Program Files\\\\SumatraPDF\\\\SumatraPDF.exe\"\n\n# Ensure subfolders exist\nif (!(Test-Path -Path $printedPath)) {\n    New-Item -ItemType Directory -Path $printedPath | Out-Null\n}\nif (!(Test-Path -Path $failedPath)) {\n    New-Item -ItemType Directory -Path $failedPath | Out-Null\n}\n\n$printerMap = @{\n    \"P1\" = \"Kyocera ECOSYS M5526cdn\"\n    \"P2\" = \"Kyocera ECOSYS P2040dn KX\"\n    \"P3\" = \"Kyocera P2040dn Bol Printer\"\n    \"P4\" = \"Kyocera Filemaker-KBLANCO\"\n}\n\nAdd-Content -Path $logFile -Value \"\\`n\\[$(Get-Date)\\] Starting print job...\"\n\nGet-ChildItem -Path $watchFolder -Filter \\*.pdf | ForEach-Object {\n    $pdf = $\\_.FullName\n    $fileName = $\\_.Name\n\n    Add-Content -Path $logFile -Value \"\\[$(Get-Date)\\] Found file: ${fileName}\"\n\n    $prefixMatched = $false\n    if ($fileName -match \"^(P\\\\d+)\\_\") {\n        $prefix = $matches\\[1\\]\n        $prefixMatched = $true\n        Add-Content -Path $logFile -Value \"\\[$(Get-Date)\\] Matched prefix: ${prefix}\"\n\n        if ($printerMap.ContainsKey($prefix)) {\n            $printerName = $printerMap\\[$prefix\\]\n            Add-Content -Path $logFile -Value \"\\[$(Get-Date)\\] Printer mapped: ${printerName}\"\n        }\n        else {\n            Add-Content -Path $logFile -Value \"\\[$(Get-Date)\\] Unknown prefix: ${prefix}\"\n        }\n    }\n\n    if ($prefixMatched) {\n        try {\n            Add-Content -Path $logFile -Value \"\\[$(Get-Date)\\] Attempting to print ${fileName} with SumatraPDF...\"\n            $p = Start-Process -FilePath $sumatraPath -ArgumentList \"-print-to \\`\"$printerName\\`\" \\`\"$pdf\\`\"\" -PassThru\n            $p | Wait-Process -Timeout 20\n            if ($p.HasExited) {\n                $destination = Join-Path -Path $printedPath -ChildPath $fileName\n                Move-Item -Path $pdf -Destination $destination\n                Add-Content -Path $logFile -Value \"\\[$(Get-Date)\\] SUCCESS: Printed ${fileName}\"\n            } else {\n                Stop-Process -Id $p.Id -Force\n                $failedDest = Join-Path -Path $failedPath -ChildPath $fileName\n                Move-Item -Path $pdf -Destination $failedDest\n                Add-Content -Path $logFile -Value \"\\[$(Get-Date)\\] ERROR: Timeout printing ${fileName}\"\n            }\n        } catch {\n            Add-Content -Path $logFile -Value \"\\[$(Get-Date)\\] ERROR printing ${fileName}: ${\\_}\"\n            $failedDest = Join-Path -Path $failedPath -ChildPath $fileName\n            Move-Item -Path $pdf -Destination $failedDest\n        }\n    } else {\n        Add-Content -Path $logFile -Value \"\\[$(Get-Date)\\] Skipped ${fileName}: no valid prefix\"\n        $skippedDest = Join-Path -Path $failedPath -ChildPath $fileName\n        Move-Item -Path $pdf -Destination $skippedDest\n    }\n}\n\nAdd-Content -Path $logFile -Value \"\\[$(Get-Date)\\] Print job finished.\"\nexit 0\n\n**Ad.3. PDF Software**\n\nAs you can see in the code above we call with this script the [SumatraPDF](https:\u002F\u002Fwww.sumatrapdfreader.org\u002Ffree-pdf-reader) software. This is a lightweight PDFreader that we prefer (because of size and ‘silent printing option’) over Adobe Acrobat. So to make this happen download and installe SumatraPDF on the server. Make sure the path to the .exe is correct.\n\n**  \nAd.4. Contact the printer**\n\nLast but not least we need to reach a printer. In the code above you see we wrote some additional lines to make printing to several different printers possible. Depending on the prefix we route the print to the corresponding network printer. What do we mean by network printer, because FMS has no printers conected right? Correct, and here is where the last magic comes in. We installed: [Printix](https:\u002F\u002Fprintix.net\u002F).\n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002Fimage.png)\n\nPrintix is a cloud-printing-service that is extremely affordable and easy to use in combination with your FileMaker Server. Simply install a printix client in your office network and on your database server and all printers in your office will become available to any application on your cloud based database server. Which means: a print command executed on the FMS will end up printing on your local office printer!\n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002Fimage-1.png)\n\nConclusion\n\nPrinting from FileMaker Server is possible. And in the right production process it is actually more then necessary. Based on above code do not forget to create a PrintQueue folder with a “printed” and “failed” folder inside. Any document saved in the PrintQueue will automatically be printed to the assigned printer. When anything goes wrong – printer not available etc. – documents might end up in the “failed” folder. You can another script to keep track of the fails and i.e. message an administrator when this happens.\n\nIf you’re considering or operating with FileMaker for your business, now is the perfect time to contact us and see how we can help you automate your processes.\n\nDo not hesitate to contact us if you want to know more!\n\nShare\n\n[](https:\u002F\u002Fwww.facebook.com\u002Fsharer\u002Fsharer.php?u=https%3A%2F%2Floggix.com%2Fprinting-from-filemaker-server-is-possible%2F)[](https:\u002F\u002Ftwitter.com\u002Fintent\u002Ftweet?text=Printing+from+FileMaker+Server+is+possible+-+Loggix+%7C+Software+Development.+https%3A%2F%2Floggix.com%2Fprinting-from-filemaker-server-is-possible%2F)[](https:\u002F\u002Fwww.linkedin.com\u002FshareArticle?mini=true&url=https%3A%2F%2Floggix.com%2Fprinting-from-filemaker-server-is-possible%2F)[](https:\u002F\u002Fpinterest.com\u002Fpin\u002Ffind\u002F?url=https%3A%2F%2Floggix.com%2Fprinting-from-filemaker-server-is-possible%2F)","\u003Cp>[\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002FFMS_Printing.jpg\" alt=\"\">](\u003Ca href=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002FFMS_Printing.jpg#36452\">https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002FFMS_Printing.jpg#36452\u003C\u002Fa>)\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002FFMS_Printing.jpg#36452\">\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch5>\u003Cstrong>In some business processes it is of great use if prints are available without executing the print command from a client workstation. In a high capacity workflow like i.e. order picking, printing is basically a waste of time. Having a server print packing slips as orders come in, is much easier and faster.\u003C\u002Fstrong>\u003C\u002Fh5>\n\u003Cp>Unfortunately \u003Ca href=\"http:\u002F\u002Ffilemaker.com\u002F\">FileMaker\u003C\u002Fa> does not support the print functionality when executed in a script on the server. Filemaker Server (FMS) is what we call ‘headless’ and does support printer setup but not the actual print command. This renders the standard “scheduled scripts” as execution option useless. Even when you could print, where would you print to? The server is usually a cloud-machine that has not printers connected right?  \u003C\u002Fp>\n\u003Cp>Now, is printing from a cloud FMS to local printers possible?\u003C\u002Fp>\n\u003Cp>Setup FMS Printing\u003C\u002Fp>\n\u003Cp>Yes, if you want to prevent a ‘workstation as printer robot’ in your network and would like FMS Server to take care of the printing, this is possible. Even when your FileMaker Server is in the cloud and you do not have a in-house print server! There are 4 steps needed to print from FMS:  \u003C\u002Fp>\n\u003Cp>1. a document to print (i.e. a PDF file)\u003Cbr>2. a system script that can handle the documents and offer them to get printed\u003Cbr>3. PDF reader that can open en print the document\u003Cbr>4. a network printer that can receive the print command and output your document.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Ad. 1 Generating a File from a script\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Generating a file (i.e. a PDF) from a Filemaker script is luckily an option that is supported by FMS. The option “Save record as PDF” for example will give you the option to save your selected record(s) based on the current layout to a (multi page) PDF file. There are also plugins that can help you do this.  \u003C\u002Fp>\n\u003Cp>Ad. 2. System Scripts\u003C\u002Fp>\n\u003Cp>FileMaker Server offers us the option to execute scheduled FileMaker Scripts, this must be a familiar option to most of you. But besides scheduling Filemaker Scripts, FMS will let you also execute so called System Scripts. These are scripts that run on the server (i.e. Applescripts on Mac or PowerShell scripts on Windows).  \u003C\u002Fp>\n\u003Cp>Using this System Script option we are able to call “Print” functionality outside of FMS that is not available inside FMS. Below you find an example of some basic scripts that can be used to achieve printing from FMS by a Windows PowerShell script (ps1). Because FMS does not handle .ps1 script very well, in this example we call a batch script (.bat) that in itself calls the .ps1 script.\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002Fscripts.jpg\" alt=\"\">\u003C\u002Fp>\n\u003Cp>So as seen in the screen shot above we call: run-printscript.bat which looks like this:\u003C\u002Fp>\n\u003Cp>powershell.exe -ExecutionPolicy Bypass -File "C:\\Program Files\\FileMaker\\FileMaker Server\\Data\\Scripts\\print-pdfs.ps1"\u003C\u002Fp>\n\u003Cp>And the “run-printscript.bat” will call: print-pdfs.ps1 which looks like this:\u003C\u002Fp>\n\u003Cp>$watchFolder = "C:\\PrintQueue"\n$logFile = "$watchFolder\\fms-print-log.txt"\n$printedPath = Join-Path -Path $watchFolder -ChildPath "Printed"\n$failedPath = Join-Path -Path $watchFolder -ChildPath "Failed"\n$sumatraPath = "C:\\Program Files\\SumatraPDF\\SumatraPDF.exe"\u003C\u002Fp>\n\u003Ch1>Ensure subfolders exist\u003C\u002Fh1>\n\u003Cp>if (!(Test-Path -Path $printedPath)) {\n    New-Item -ItemType Directory -Path $printedPath | Out-Null\n}\nif (!(Test-Path -Path $failedPath)) {\n    New-Item -ItemType Directory -Path $failedPath | Out-Null\n}\u003C\u002Fp>\n\u003Cp>$printerMap = @{\n    "P1" = "Kyocera ECOSYS M5526cdn"\n    "P2" = "Kyocera ECOSYS P2040dn KX"\n    "P3" = "Kyocera P2040dn Bol Printer"\n    "P4" = "Kyocera Filemaker-KBLANCO"\n}\u003C\u002Fp>\n\u003Cp>Add-Content -Path $logFile -Value "`n[$(Get-Date)] Starting print job..."\u003C\u002Fp>\n\u003Cp>Get-ChildItem -Path $watchFolder -Filter *.pdf | ForEach-Object {\n    $pdf = $_.FullName\n    $fileName = $_.Name\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Add-Content -Path $logFile -Value "\\[$(Get-Date)\\] Found file: ${fileName}"\n\n$prefixMatched = $false\nif ($fileName -match "^(P\\\\d+)\\_") {\n    $prefix = $matches\\[1\\]\n    $prefixMatched = $true\n    Add-Content -Path $logFile -Value "\\[$(Get-Date)\\] Matched prefix: ${prefix}"\n\n    if ($printerMap.ContainsKey($prefix)) {\n        $printerName = $printerMap\\[$prefix\\]\n        Add-Content -Path $logFile -Value "\\[$(Get-Date)\\] Printer mapped: ${printerName}"\n    }\n    else {\n        Add-Content -Path $logFile -Value "\\[$(Get-Date)\\] Unknown prefix: ${prefix}"\n    }\n}\n\nif ($prefixMatched) {\n    try {\n        Add-Content -Path $logFile -Value "\\[$(Get-Date)\\] Attempting to print ${fileName} with SumatraPDF..."\n        $p = Start-Process -FilePath $sumatraPath -ArgumentList "-print-to \\`"$printerName\\`" \\`"$pdf\\`"" -PassThru\n        $p | Wait-Process -Timeout 20\n        if ($p.HasExited) {\n            $destination = Join-Path -Path $printedPath -ChildPath $fileName\n            Move-Item -Path $pdf -Destination $destination\n            Add-Content -Path $logFile -Value "\\[$(Get-Date)\\] SUCCESS: Printed ${fileName}"\n        } else {\n            Stop-Process -Id $p.Id -Force\n            $failedDest = Join-Path -Path $failedPath -ChildPath $fileName\n            Move-Item -Path $pdf -Destination $failedDest\n            Add-Content -Path $logFile -Value "\\[$(Get-Date)\\] ERROR: Timeout printing ${fileName}"\n        }\n    } catch {\n        Add-Content -Path $logFile -Value "\\[$(Get-Date)\\] ERROR printing ${fileName}: ${\\_}"\n        $failedDest = Join-Path -Path $failedPath -ChildPath $fileName\n        Move-Item -Path $pdf -Destination $failedDest\n    }\n} else {\n    Add-Content -Path $logFile -Value "\\[$(Get-Date)\\] Skipped ${fileName}: no valid prefix"\n    $skippedDest = Join-Path -Path $failedPath -ChildPath $fileName\n    Move-Item -Path $pdf -Destination $skippedDest\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>}\u003C\u002Fp>\n\u003Cp>Add-Content -Path $logFile -Value "[$(Get-Date)] Print job finished."\nexit 0\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Ad.3. PDF Software\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>As you can see in the code above we call with this script the \u003Ca href=\"https:\u002F\u002Fwww.sumatrapdfreader.org\u002Ffree-pdf-reader\">SumatraPDF\u003C\u002Fa> software. This is a lightweight PDFreader that we prefer (because of size and ‘silent printing option’) over Adobe Acrobat. So to make this happen download and installe SumatraPDF on the server. Make sure the path to the .exe is correct.\u003C\u002Fp>\n\u003Cp>**\u003Cbr>Ad.4. Contact the printer**\u003C\u002Fp>\n\u003Cp>Last but not least we need to reach a printer. In the code above you see we wrote some additional lines to make printing to several different printers possible. Depending on the prefix we route the print to the corresponding network printer. What do we mean by network printer, because FMS has no printers conected right? Correct, and here is where the last magic comes in. We installed: \u003Ca href=\"https:\u002F\u002Fprintix.net\u002F\">Printix\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002Fimage.png\" alt=\"\">\u003C\u002Fp>\n\u003Cp>Printix is a cloud-printing-service that is extremely affordable and easy to use in combination with your FileMaker Server. Simply install a printix client in your office network and on your database server and all printers in your office will become available to any application on your cloud based database server. Which means: a print command executed on the FMS will end up printing on your local office printer!\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002Fimage-1.png\" alt=\"\">\u003C\u002Fp>\n\u003Cp>Conclusion\u003C\u002Fp>\n\u003Cp>Printing from FileMaker Server is possible. And in the right production process it is actually more then necessary. Based on above code do not forget to create a PrintQueue folder with a “printed” and “failed” folder inside. Any document saved in the PrintQueue will automatically be printed to the assigned printer. When anything goes wrong – printer not available etc. – documents might end up in the “failed” folder. You can another script to keep track of the fails and i.e. message an administrator when this happens.\u003C\u002Fp>\n\u003Cp>If you’re considering or operating with FileMaker for your business, now is the perfect time to contact us and see how we can help you automate your processes.\u003C\u002Fp>\n\u003Cp>Do not hesitate to contact us if you want to know more!\u003C\u002Fp>\n\u003Cp>Share\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwww.facebook.com\u002Fsharer\u002Fsharer.php?u=https%3A%2F%2Floggix.com%2Fprinting-from-filemaker-server-is-possible%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Ftwitter.com\u002Fintent\u002Ftweet?text=Printing+from+FileMaker+Server+is+possible+-+Loggix+%7C+Software+Development.+https%3A%2F%2Floggix.com%2Fprinting-from-filemaker-server-is-possible%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Fwww.linkedin.com\u002FshareArticle?mini=true&url=https%3A%2F%2Floggix.com%2Fprinting-from-filemaker-server-is-possible%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Fpinterest.com\u002Fpin\u002Ffind\u002F?url=https%3A%2F%2Floggix.com%2Fprinting-from-filemaker-server-is-possible%2F\">\u003C\u002Fa>\u003C\u002Fp>\n","2025-06-27",1781520661000,[23],"\u002Fapi\u002Fknowledge\u002Fimage\u002F68\u002F?v=9c4c2097338b",{"id":623,"idKnowledge":624,"idDomain":15,"idCluster":15,"slug":625,"title":626,"description":627,"bodyMarkdown":628,"bodyHtml":629,"author":514,"date":630,"createdAt":619,"topics":631,"image":632,"hasDownload":28,"fileName":15,"youtubeId":27},"69","6D14B786-9C82-2842-BE07-76C08D04CA0E","webapps-based-on-filemaker","WebApps based on FileMaker","FM BetterForms is a web application framework specifically built for FileMaker. It lets you create fully customised, responsive web and mobile apps that connect directly to your FileMaker server via the Data API—without the need for middleware, sync engines, or external databases.","[\n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002FFileMaker_FMBetterforms-scaled-e1750927150375.jpg)](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002FFMS_Printing.jpg#36452)\n\n[](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002FFMS_Printing.jpg#36452)\n\n**If you have a business that communicates with the world around you (and which business doesn’t?), the use of mobile and web applications is becoming increasingly vital as a data transfer tool.**\n\nInforming clients about shipments, receiving reservations from visitors, collecting data to enhance your CRM, sending out automated emails or SMS—whatever process you can think of, it likely involves a database and some form of communication.\n\nIn your case, that database might actually be FileMaker. Claris FileMaker is one of the earliest and most mature low-code\u002Fno-code platforms—_or to use a modern term: vibe-code_. It has always been at the forefront of user-friendly database development.\n\nBut nowadays, setting up a database is not enough. **We recognize that interacting with your data is just as important as storing it.**\n\n**How to interact with your FileMaker data(base) through the web**\n\nIf your FileMaker solution is hosted on a FileMaker Server (and connected to the web), there are several ways to allow external parties to read, write, or engage with your data. We group these into three categories:\n\n**1\\. Native Web Interfaces (Claris standard building tools)**\n\n-   -   **WebDirect -** The simplest way to publish FileMaker layouts to the browser. No coding required. It’s quick to set up but better suited to internal use cases. Performance and mobile support can be limiting in more demanding scenarios.\n        \n    -   **Claris Studio -** A newer addition in the Claris ecosystem. Studio enables web-based form entry, dashboards, and some level of cloud data handling. It’s still evolving but gives a glimpse into Claris’ cloud-first future.\n        \n\n**2\\. Integration Protocols (Connectors on which to build your own frontend)**\n\n1.  -   **FileMaker Data API -** RESTful, secure, and scalable. Ideal for building modern web apps or mobile interfaces using tools like Vue, React, or Flutter. Also great for integrating with external platforms.\n        \n    -   **OData -** A standard protocol designed for analytics and business intelligence tools. Best suited for dashboards, charts, and data extraction via Power BI, Tableau, or Excel.\n        \n    -   **ODBC\u002FJDBC -** SQL-based connections for reporting and integrations with legacy enterprise systems. Powerful but limited to structured, tabular queries.\n        \n    -   **Custom Web Publishing (CWP) -** The original web integration method via PHP\u002FXML. Still supported and powerful, but considered legacy. Requires more setup and technical knowledge.\n        \n\n#### **3\\. A smarter approach: FM BetterForms**\n\n-   -   While the above options serve different purposes, they often require trade-offs in speed, design flexibility, or scalability. That’s where **[FM BetterForms](fmbetterforms.com)** comes in. **FM BetterForms** is a web application framework specifically built for FileMaker. It lets you create fully customised, responsive web and mobile apps that connect _directly_ to your FileMaker server via the Data API—without the need for middleware, sync engines, or external databases. FMBetterForms offers:\n        -   Modern Vue.js-based interface\n        -   Secure, scalable, mobile-ready\n        -   Rich UI components and two-way data binding\n        -   Works natively with FileMaker scripts, layouts, and logic\n        -   Ideal for client portals, scheduling, onboarding, data capture, and more\n\n**We build anything with FM BetterForms**\n\nBelow you will find a couple examples of fully browser based WebApps build on and connected with a 100% FileMaker backend (database).\n\n##### ResourcePlanner\n\nFileMaker as basis for a full blown project management system including a drag-and-drop resource planner.\n\n##### GoogleMaps Integration\n\nA WordPress website with a integrated GoogleMap that interacts live with data coming from a FileMaker.\n\n##### SaaS Application\n\nA HSE SaaS application fully browser based including a mobile app run on tables, fields and scripts from FM.\n\n##### Calendar Planning\n\nA live driving lesson planner servicing 1000+ calls a day, fully responsive and driven by a 10 year old FM database.\n\nShare\n\n[](https:\u002F\u002Fwww.facebook.com\u002Fsharer\u002Fsharer.php?u=https%3A%2F%2Floggix.com%2Fwebapps-based-on-filemaker-36480%2F)[](https:\u002F\u002Ftwitter.com\u002Fintent\u002Ftweet?text=WebApps+based+on+FileMaker+-+Loggix+%7C+Software+Development.+https%3A%2F%2Floggix.com%2Fwebapps-based-on-filemaker-36480%2F)[](https:\u002F\u002Fwww.linkedin.com\u002FshareArticle?mini=true&url=https%3A%2F%2Floggix.com%2Fwebapps-based-on-filemaker-36480%2F)[](https:\u002F\u002Fpinterest.com\u002Fpin\u002Ffind\u002F?url=https%3A%2F%2Floggix.com%2Fwebapps-based-on-filemaker-36480%2F)","\u003Cp>[\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002FFileMaker_FMBetterforms-scaled-e1750927150375.jpg\" alt=\"\">](\u003Ca href=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002FFMS_Printing.jpg#36452\">https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002FFMS_Printing.jpg#36452\u003C\u002Fa>)\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F06\u002FFMS_Printing.jpg#36452\">\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>If you have a business that communicates with the world around you (and which business doesn’t?), the use of mobile and web applications is becoming increasingly vital as a data transfer tool.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Informing clients about shipments, receiving reservations from visitors, collecting data to enhance your CRM, sending out automated emails or SMS—whatever process you can think of, it likely involves a database and some form of communication.\u003C\u002Fp>\n\u003Cp>In your case, that database might actually be FileMaker. Claris FileMaker is one of the earliest and most mature low-code\u002Fno-code platforms—\u003Cem>or to use a modern term: vibe-code\u003C\u002Fem>. It has always been at the forefront of user-friendly database development.\u003C\u002Fp>\n\u003Cp>But nowadays, setting up a database is not enough. \u003Cstrong>We recognize that interacting with your data is just as important as storing it.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>How to interact with your FileMaker data(base) through the web\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>If your FileMaker solution is hosted on a FileMaker Server (and connected to the web), there are several ways to allow external parties to read, write, or engage with your data. We group these into three categories:\u003C\u002Fp>\n\u003Cp>\u003Cstrong>1. Native Web Interfaces (Claris standard building tools)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cul>\n\u003Cli>\u003Cp>\u003Cstrong>WebDirect -\u003C\u002Fstrong> The simplest way to publish FileMaker layouts to the browser. No coding required. It’s quick to set up but better suited to internal use cases. Performance and mobile support can be limiting in more demanding scenarios.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>\u003Cstrong>Claris Studio -\u003C\u002Fstrong> A newer addition in the Claris ecosystem. Studio enables web-based form entry, dashboards, and some level of cloud data handling. It’s still evolving but gives a glimpse into Claris’ cloud-first future.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>2. Integration Protocols (Connectors on which to build your own frontend)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cul>\n\u003Cli>\u003Cp>\u003Cstrong>FileMaker Data API -\u003C\u002Fstrong> RESTful, secure, and scalable. Ideal for building modern web apps or mobile interfaces using tools like Vue, React, or Flutter. Also great for integrating with external platforms.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>\u003Cstrong>OData -\u003C\u002Fstrong> A standard protocol designed for analytics and business intelligence tools. Best suited for dashboards, charts, and data extraction via Power BI, Tableau, or Excel.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>\u003Cstrong>ODBC\u002FJDBC -\u003C\u002Fstrong> SQL-based connections for reporting and integrations with legacy enterprise systems. Powerful but limited to structured, tabular queries.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Cp>\u003Cstrong>Custom Web Publishing (CWP) -\u003C\u002Fstrong> The original web integration method via PHP\u002FXML. Still supported and powerful, but considered legacy. Requires more setup and technical knowledge.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>\u003Cstrong>3. A smarter approach: FM BetterForms\u003C\u002Fstrong>\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cul>\n\u003Cli>While the above options serve different purposes, they often require trade-offs in speed, design flexibility, or scalability. That’s where \u003Cstrong>\u003Ca href=\"fmbetterforms.com\">FM BetterForms\u003C\u002Fa>\u003C\u002Fstrong> comes in. \u003Cstrong>FM BetterForms\u003C\u002Fstrong> is a web application framework specifically built for FileMaker. It lets you create fully customised, responsive web and mobile apps that connect \u003Cem>directly\u003C\u002Fem> to your FileMaker server via the Data API—without the need for middleware, sync engines, or external databases. FMBetterForms offers:\u003Cul>\n\u003Cli>Modern Vue.js-based interface\u003C\u002Fli>\n\u003Cli>Secure, scalable, mobile-ready\u003C\u002Fli>\n\u003Cli>Rich UI components and two-way data binding\u003C\u002Fli>\n\u003Cli>Works natively with FileMaker scripts, layouts, and logic\u003C\u002Fli>\n\u003Cli>Ideal for client portals, scheduling, onboarding, data capture, and more\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>We build anything with FM BetterForms\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Below you will find a couple examples of fully browser based WebApps build on and connected with a 100% FileMaker backend (database).\u003C\u002Fp>\n\u003Ch5>ResourcePlanner\u003C\u002Fh5>\n\u003Cp>FileMaker as basis for a full blown project management system including a drag-and-drop resource planner.\u003C\u002Fp>\n\u003Ch5>GoogleMaps Integration\u003C\u002Fh5>\n\u003Cp>A WordPress website with a integrated GoogleMap that interacts live with data coming from a FileMaker.\u003C\u002Fp>\n\u003Ch5>SaaS Application\u003C\u002Fh5>\n\u003Cp>A HSE SaaS application fully browser based including a mobile app run on tables, fields and scripts from FM.\u003C\u002Fp>\n\u003Ch5>Calendar Planning\u003C\u002Fh5>\n\u003Cp>A live driving lesson planner servicing 1000+ calls a day, fully responsive and driven by a 10 year old FM database.\u003C\u002Fp>\n\u003Cp>Share\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwww.facebook.com\u002Fsharer\u002Fsharer.php?u=https%3A%2F%2Floggix.com%2Fwebapps-based-on-filemaker-36480%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Ftwitter.com\u002Fintent\u002Ftweet?text=WebApps+based+on+FileMaker+-+Loggix+%7C+Software+Development.+https%3A%2F%2Floggix.com%2Fwebapps-based-on-filemaker-36480%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Fwww.linkedin.com\u002FshareArticle?mini=true&url=https%3A%2F%2Floggix.com%2Fwebapps-based-on-filemaker-36480%2F\">\u003C\u002Fa>\u003Ca href=\"https:\u002F\u002Fpinterest.com\u002Fpin\u002Ffind\u002F?url=https%3A%2F%2Floggix.com%2Fwebapps-based-on-filemaker-36480%2F\">\u003C\u002Fa>\u003C\u002Fp>\n","2025-06-26",[23,518],"\u002Fapi\u002Fknowledge\u002Fimage\u002F69\u002F?v=72b56b694b61",{"id":634,"idKnowledge":635,"idDomain":15,"idCluster":15,"slug":636,"title":637,"description":638,"bodyMarkdown":639,"bodyHtml":640,"author":514,"date":641,"createdAt":642,"topics":643,"image":644,"hasDownload":28,"fileName":15,"youtubeId":27},"38","47E5969D-3EB9-F44A-BCD1-D92AF078EBC9","your-filemaker-server-still-on-tls-1-1","Your FileMaker Server still on TLS 1.1?","We still find clients with FileMaker Server installed on Servers supporting TLS 1.1., which is not a good situation to be in! If you’re running […]","We still find clients with FileMaker Server installed on Servers supporting TLS 1.1., which is not a good situation to be in!  \n  \nIf you’re running **FileMaker Server**, ensuring a secure connection between clients and your database is crucial. One security risk that still lurks in some configurations is **TLS 1.1**—a deprecated encryption protocol that should no longer be used.\n\nTLS 1.1 was officially **deprecated by the [Internet Engineering Task Force](https:\u002F\u002Fwww.ietf.org\u002F) (IETF) in 2020** due to multiple security vulnerabilities. It lacks modern cryptographic protections, making it susceptible to attacks such as **[BEAST](https:\u002F\u002Fdocs.digicert.com\u002Fen\u002Fcertcentral\u002Fcertificate-tools\u002Fdiscovery-user-guide\u002Ftls-ssl-endpoint-vulnerabilities\u002Fbeast.html#:~:text=In%20a%20BEAST%20attack%2C%20the,e.g.%2C%20HTTP%20authentication%20cookies\\).) (Browser Exploit Against SSL\u002FTLS)** and **padding oracle attacks**. Major browsers and platforms, including **Google Chrome, Mozilla Firefox, Apple Safari, and Microsoft Edge**, have already stopped supporting it.\n\nFileMaker Server relies on **TLS to encrypt data transmissions**, ensuring that sensitive information remains protected. Keeping **TLS 1.1 enabled weakens this security**, leaving your FileMaker database exposed to potential exploits. Additionally, many modern compliance standards, such as **GDPR, PCI DSS, and HIPAA**, require the use of **TLS 1.2 or higher**.  \n  \nAre you in doubt if your server is save, do a check here: [https:\u002F\u002Fwww.ssllabs.com\u002Fssltest\u002Fanalyze.html](https:\u002F\u002Fwww.ssllabs.com\u002Fssltest\u002Fanalyze.html)\n\nTo maintain security and compliance, you should **disable TLS 1.1 on your FileMaker Server** and ensure that only **TLS 1.2+** is used. By doing so, you safeguard your system from outdated encryption risks and protect your data from unauthorized access.\n\n**Need help disabling TLS 1.1?** Contact us for guidance on securing your FileMaker Server today or try it yourself and follow the steps below (this is a Windows example):  \n  \n1\\. On windows open the REGISTRATION EDITOR.\n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F02\u002Ftls_2.png)\n\n2\\. Go to the blow path:\n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F02\u002Ftls_3.png)\n\n3\\. Add the following keys and values and restart your server.\n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F02\u002Ftls_4.png)","\u003Cp>We still find clients with FileMaker Server installed on Servers supporting TLS 1.1., which is not a good situation to be in!  \u003C\u002Fp>\n\u003Cp>If you’re running \u003Cstrong>FileMaker Server\u003C\u002Fstrong>, ensuring a secure connection between clients and your database is crucial. One security risk that still lurks in some configurations is \u003Cstrong>TLS 1.1\u003C\u002Fstrong>—a deprecated encryption protocol that should no longer be used.\u003C\u002Fp>\n\u003Cp>TLS 1.1 was officially \u003Cstrong>deprecated by the \u003Ca href=\"https:\u002F\u002Fwww.ietf.org\u002F\">Internet Engineering Task Force\u003C\u002Fa> (IETF) in 2020\u003C\u002Fstrong> due to multiple security vulnerabilities. It lacks modern cryptographic protections, making it susceptible to attacks such as \u003Cstrong>\u003Ca href=\"https:\u002F\u002Fdocs.digicert.com\u002Fen\u002Fcertcentral\u002Fcertificate-tools\u002Fdiscovery-user-guide\u002Ftls-ssl-endpoint-vulnerabilities\u002Fbeast.html#:~:text=In%20a%20BEAST%20attack%2C%20the,e.g.%2C%20HTTP%20authentication%20cookies).\">BEAST\u003C\u002Fa> (Browser Exploit Against SSL\u002FTLS)\u003C\u002Fstrong> and \u003Cstrong>padding oracle attacks\u003C\u002Fstrong>. Major browsers and platforms, including \u003Cstrong>Google Chrome, Mozilla Firefox, Apple Safari, and Microsoft Edge\u003C\u002Fstrong>, have already stopped supporting it.\u003C\u002Fp>\n\u003Cp>FileMaker Server relies on \u003Cstrong>TLS to encrypt data transmissions\u003C\u002Fstrong>, ensuring that sensitive information remains protected. Keeping \u003Cstrong>TLS 1.1 enabled weakens this security\u003C\u002Fstrong>, leaving your FileMaker database exposed to potential exploits. Additionally, many modern compliance standards, such as \u003Cstrong>GDPR, PCI DSS, and HIPAA\u003C\u002Fstrong>, require the use of \u003Cstrong>TLS 1.2 or higher\u003C\u002Fstrong>.  \u003C\u002Fp>\n\u003Cp>Are you in doubt if your server is save, do a check here: \u003Ca href=\"https:\u002F\u002Fwww.ssllabs.com\u002Fssltest\u002Fanalyze.html\">https:\u002F\u002Fwww.ssllabs.com\u002Fssltest\u002Fanalyze.html\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>To maintain security and compliance, you should \u003Cstrong>disable TLS 1.1 on your FileMaker Server\u003C\u002Fstrong> and ensure that only \u003Cstrong>TLS 1.2+\u003C\u002Fstrong> is used. By doing so, you safeguard your system from outdated encryption risks and protect your data from unauthorized access.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Need help disabling TLS 1.1?\u003C\u002Fstrong> Contact us for guidance on securing your FileMaker Server today or try it yourself and follow the steps below (this is a Windows example):  \u003C\u002Fp>\n\u003Cp>1. On windows open the REGISTRATION EDITOR.\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F02\u002Ftls_2.png\" alt=\"\">\u003C\u002Fp>\n\u003Cp>2. Go to the blow path:\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F02\u002Ftls_3.png\" alt=\"\">\u003C\u002Fp>\n\u003Cp>3. Add the following keys and values and restart your server.\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F02\u002Ftls_4.png\" alt=\"\">\u003C\u002Fp>\n","2025-02-12",1781519870000,[23],"\u002Fapi\u002Fknowledge\u002Fimage\u002F38\u002F?v=7358ef296d5e",{"id":646,"idKnowledge":647,"idDomain":15,"idCluster":15,"slug":648,"title":649,"description":650,"bodyMarkdown":651,"bodyHtml":652,"author":514,"date":653,"createdAt":642,"topics":654,"image":655,"hasDownload":28,"fileName":15,"youtubeId":27},"39","4BC7865F-351D-AD41-BACF-F90B22930331","why-use-filemaker-features-importance-and-ai-integration","Why Use FileMaker? Features, Importance, and AI Integration","In today’s fast-paced business environment, having a flexible, user-friendly, and powerful database solution is essential for managing data efficiently. FileMaker, developed by Claris (an Apple […]","In today’s fast-paced business environment, having a flexible, user-friendly, and powerful database solution is essential for managing data efficiently. **[FileMaker](http:\u002F\u002Ffilemaker.com)**, developed by [Claris](http:\u002F\u002Fclaris.com) (an Apple subsidiary), is one such platform that stands out due to its versatility, ease of use, and scalability. Whether you’re a small business, a growing enterprise, or a large corporation, FileMaker can help streamline operations, automate workflows, and enhance productivity.\n\n**What is FileMaker?**\n\nFileMaker is a **low-code database development platform** that allows users to create custom apps tailored to their specific business needs. It enables businesses to store, organize, and analyze data while integrating seamlessly with various systems, including **iOS, macOS, Windows, and web applications**. FileMaker’s drag-and-drop interface and scripting capabilities make it an excellent choice for both developers and non-technical users.\n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F02\u002FHRK92-e1739273580493.jpg)\n\n**Why Use FileMaker?**\n\n**1\\. Easy Customization & Low-Code Development**\n\nUnlike traditional databases that require extensive coding knowledge, FileMaker provides an **intuitive drag-and-drop interface** and **low-code scripting**. This means users can quickly design and modify applications without deep programming skills, making it ideal for businesses that need tailored solutions.\n\n**2\\. Cross-Platform Compatibility**\n\nFileMaker works on **Windows, macOS, iOS, and the web**, ensuring that teams can access and update data from any device. The ability to create apps that function seamlessly across multiple platforms makes FileMaker a valuable tool for remote work and collaboration.\n\n**3\\. Powerful Data Management**\n\nFileMaker provides an efficient way to **store, manage, and retrieve** large volumes of structured and unstructured data. Its relational database model allows users to link different data sets, reducing redundancy and improving efficiency.\n\n**4\\. Integration with Other Applications**\n\nFileMaker integrates with **third-party applications** like:\n\n-   **Microsoft SQL Server, MySQL, and Oracle** for database connectivity\n-   **[REST](http:\u002F\u002FRESTful) [](https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FREST)[APIs](http:\u002F\u002FRESTful)** for connecting with cloud services\n-   **JSON, XML, and OData** for seamless data exchange\n-   **[Claris Connect](https:\u002F\u002Fwww.claris.com\u002Fconnect\u002F)** for automating workflows with apps like Slack, Dropbox, and Google Drive\n\n**5\\. Robust Security Features**\n\nData security is crucial for businesses, and FileMaker offers **encryption, authentication, and access control** to ensure sensitive information is protected. Admins can define roles and permissions to restrict access, preventing unauthorized users from modifying critical data.\n\n**6\\. Automation & Workflow Optimization**\n\nWith built-in **scripting and automation tools**, FileMaker can handle repetitive tasks such as data entry, report generation, and notifications. Businesses can streamline their workflows and improve efficiency by reducing manual work.\n\n**7\\. AI Integration in FileMaker**\n\nOne of the most exciting advancements in FileMaker is its ability to integrate **Artificial Intelligence (AI)** to enhance automation and decision-making. With AI, businesses can:\n\n-   **Automate data entry and validation** using machine learning models.\n-   **Analyze trends and patterns** to generate intelligent insights.\n-   **Implement chatbots and virtual assistants** to enhance customer service.\n-   **Use AI-driven OCR (Optical Character Recognition)** for document processing and text extraction.\n-   **Integrate AI-powered speech-to-text and text-to-speech** for accessibility.\n\nBy leveraging APIs like **OpenAI, Google AI, or AWS Machine Learning**, FileMaker can become even more powerful, offering **predictive analytics, intelligent automation, and advanced data processing** capabilities.\n\n**8\\. Scalability for Growing Businesses**\n\nWhether you’re a **startup or a large enterprise**, FileMaker scales with your business. It supports small teams and enterprise-level deployments, allowing companies to expand their applications as their needs evolve.\n\n**9\\. Cloud and On-Premise Deployment**\n\nFileMaker offers both **on-premise hosting (FileMaker Server)** and **cloud hosting (FileMaker Cloud)**, giving businesses the flexibility to choose the best option based on security, cost, and accessibility requirements. Loggix uses one of Europe’s biggest hosting parties [TransIP](https:\u002F\u002Fwww.transip.nl\u002F) for solid and fast FileMaker hosting.\n\n**Importance of FileMaker in Business**\n\n**1\\. Streamlining Business Processes**\n\nFileMaker helps businesses manage their operations by creating custom workflows that fit their needs. From inventory tracking to customer relationship management (CRM), companies can optimize various business functions.\n\n**2\\. Cost-Effective Solution**\n\nCompared to hiring a development team to build a custom database application, FileMaker provides an affordable solution that is **easy to maintain and modify**.\n\n**3\\. Enhancing Collaboration**\n\nWith multi-user access and cloud synchronization, teams can **work together in real-time**, ensuring better communication and coordination.\n\n**4\\. Supporting Digital Transformation**\n\nFileMaker enables businesses to move from paper-based and manual systems to **digitized, automated processes**, improving efficiency and decision-making.\n\n**Conclusion**\n\nFileMaker is an **all-in-one** database solution that combines ease of use, powerful features, and cross-platform functionality. Its ability to create **custom apps** quickly, integrate with third-party tools, and enhance security makes it a **valuable asset for businesses** looking to streamline their operations.\n\nWith the added power of **AI integration**, FileMaker can go beyond just data management to offer **intelligent automation, predictive analytics, and enhanced user experiences**. Whether you’re managing a small company or running a large organization, FileMaker provides the flexibility and power to support your growth.\n\nIf you’re considering **FileMaker for your business**, now is the perfect time to explore its capabilities and start building efficient, AI-powered solutions tailored to your needs.\n\nDo not hesitate to contact us if you want to know more!","\u003Cp>In today’s fast-paced business environment, having a flexible, user-friendly, and powerful database solution is essential for managing data efficiently. \u003Cstrong>\u003Ca href=\"http:\u002F\u002Ffilemaker.com\">FileMaker\u003C\u002Fa>\u003C\u002Fstrong>, developed by \u003Ca href=\"http:\u002F\u002Fclaris.com\">Claris\u003C\u002Fa> (an Apple subsidiary), is one such platform that stands out due to its versatility, ease of use, and scalability. Whether you’re a small business, a growing enterprise, or a large corporation, FileMaker can help streamline operations, automate workflows, and enhance productivity.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What is FileMaker?\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>FileMaker is a \u003Cstrong>low-code database development platform\u003C\u002Fstrong> that allows users to create custom apps tailored to their specific business needs. It enables businesses to store, organize, and analyze data while integrating seamlessly with various systems, including \u003Cstrong>iOS, macOS, Windows, and web applications\u003C\u002Fstrong>. FileMaker’s drag-and-drop interface and scripting capabilities make it an excellent choice for both developers and non-technical users.\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F02\u002FHRK92-e1739273580493.jpg\" alt=\"\">\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Why Use FileMaker?\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>1. Easy Customization & Low-Code Development\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Unlike traditional databases that require extensive coding knowledge, FileMaker provides an \u003Cstrong>intuitive drag-and-drop interface\u003C\u002Fstrong> and \u003Cstrong>low-code scripting\u003C\u002Fstrong>. This means users can quickly design and modify applications without deep programming skills, making it ideal for businesses that need tailored solutions.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>2. Cross-Platform Compatibility\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>FileMaker works on \u003Cstrong>Windows, macOS, iOS, and the web\u003C\u002Fstrong>, ensuring that teams can access and update data from any device. The ability to create apps that function seamlessly across multiple platforms makes FileMaker a valuable tool for remote work and collaboration.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>3. Powerful Data Management\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>FileMaker provides an efficient way to \u003Cstrong>store, manage, and retrieve\u003C\u002Fstrong> large volumes of structured and unstructured data. Its relational database model allows users to link different data sets, reducing redundancy and improving efficiency.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>4. Integration with Other Applications\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>FileMaker integrates with \u003Cstrong>third-party applications\u003C\u002Fstrong> like:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Microsoft SQL Server, MySQL, and Oracle\u003C\u002Fstrong> for database connectivity\u003C\u002Fli>\n\u003Cli>\u003Cstrong>\u003Ca href=\"http:\u002F\u002FRESTful\">REST\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FREST\">\u003C\u002Fa>\u003Ca href=\"http:\u002F\u002FRESTful\">APIs\u003C\u002Fa>\u003C\u002Fstrong> for connecting with cloud services\u003C\u002Fli>\n\u003Cli>\u003Cstrong>JSON, XML, and OData\u003C\u002Fstrong> for seamless data exchange\u003C\u002Fli>\n\u003Cli>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fwww.claris.com\u002Fconnect\u002F\">Claris Connect\u003C\u002Fa>\u003C\u002Fstrong> for automating workflows with apps like Slack, Dropbox, and Google Drive\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>5. Robust Security Features\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Data security is crucial for businesses, and FileMaker offers \u003Cstrong>encryption, authentication, and access control\u003C\u002Fstrong> to ensure sensitive information is protected. Admins can define roles and permissions to restrict access, preventing unauthorized users from modifying critical data.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>6. Automation & Workflow Optimization\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>With built-in \u003Cstrong>scripting and automation tools\u003C\u002Fstrong>, FileMaker can handle repetitive tasks such as data entry, report generation, and notifications. Businesses can streamline their workflows and improve efficiency by reducing manual work.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>7. AI Integration in FileMaker\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>One of the most exciting advancements in FileMaker is its ability to integrate \u003Cstrong>Artificial Intelligence (AI)\u003C\u002Fstrong> to enhance automation and decision-making. With AI, businesses can:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Automate data entry and validation\u003C\u002Fstrong> using machine learning models.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Analyze trends and patterns\u003C\u002Fstrong> to generate intelligent insights.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Implement chatbots and virtual assistants\u003C\u002Fstrong> to enhance customer service.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Use AI-driven OCR (Optical Character Recognition)\u003C\u002Fstrong> for document processing and text extraction.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Integrate AI-powered speech-to-text and text-to-speech\u003C\u002Fstrong> for accessibility.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>By leveraging APIs like \u003Cstrong>OpenAI, Google AI, or AWS Machine Learning\u003C\u002Fstrong>, FileMaker can become even more powerful, offering \u003Cstrong>predictive analytics, intelligent automation, and advanced data processing\u003C\u002Fstrong> capabilities.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>8. Scalability for Growing Businesses\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Whether you’re a \u003Cstrong>startup or a large enterprise\u003C\u002Fstrong>, FileMaker scales with your business. It supports small teams and enterprise-level deployments, allowing companies to expand their applications as their needs evolve.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>9. Cloud and On-Premise Deployment\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>FileMaker offers both \u003Cstrong>on-premise hosting (FileMaker Server)\u003C\u002Fstrong> and \u003Cstrong>cloud hosting (FileMaker Cloud)\u003C\u002Fstrong>, giving businesses the flexibility to choose the best option based on security, cost, and accessibility requirements. Loggix uses one of Europe’s biggest hosting parties \u003Ca href=\"https:\u002F\u002Fwww.transip.nl\u002F\">TransIP\u003C\u002Fa> for solid and fast FileMaker hosting.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Importance of FileMaker in Business\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>1. Streamlining Business Processes\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>FileMaker helps businesses manage their operations by creating custom workflows that fit their needs. From inventory tracking to customer relationship management (CRM), companies can optimize various business functions.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>2. Cost-Effective Solution\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Compared to hiring a development team to build a custom database application, FileMaker provides an affordable solution that is \u003Cstrong>easy to maintain and modify\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>3. Enhancing Collaboration\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>With multi-user access and cloud synchronization, teams can \u003Cstrong>work together in real-time\u003C\u002Fstrong>, ensuring better communication and coordination.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>4. Supporting Digital Transformation\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>FileMaker enables businesses to move from paper-based and manual systems to \u003Cstrong>digitized, automated processes\u003C\u002Fstrong>, improving efficiency and decision-making.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Conclusion\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>FileMaker is an \u003Cstrong>all-in-one\u003C\u002Fstrong> database solution that combines ease of use, powerful features, and cross-platform functionality. Its ability to create \u003Cstrong>custom apps\u003C\u002Fstrong> quickly, integrate with third-party tools, and enhance security makes it a \u003Cstrong>valuable asset for businesses\u003C\u002Fstrong> looking to streamline their operations.\u003C\u002Fp>\n\u003Cp>With the added power of \u003Cstrong>AI integration\u003C\u002Fstrong>, FileMaker can go beyond just data management to offer \u003Cstrong>intelligent automation, predictive analytics, and enhanced user experiences\u003C\u002Fstrong>. Whether you’re managing a small company or running a large organization, FileMaker provides the flexibility and power to support your growth.\u003C\u002Fp>\n\u003Cp>If you’re considering \u003Cstrong>FileMaker for your business\u003C\u002Fstrong>, now is the perfect time to explore its capabilities and start building efficient, AI-powered solutions tailored to your needs.\u003C\u002Fp>\n\u003Cp>Do not hesitate to contact us if you want to know more!\u003C\u002Fp>\n","2025-02-11",[23],"\u002Fapi\u002Fknowledge\u002Fimage\u002F39\u002F?v=a7d005206d22",{"id":657,"idKnowledge":658,"idDomain":15,"idCluster":15,"slug":659,"title":660,"description":661,"bodyMarkdown":662,"bodyHtml":663,"author":514,"date":664,"createdAt":665,"topics":666,"image":667,"hasDownload":28,"fileName":15,"youtubeId":27},"70","6545FB72-9F3D-364F-ADA9-9E635799CAB6","deepseek-filemaker-apexcharts","DeepSeek – FileMaker – ApexCharts","What does the new Ai tool DeepSeek know about FileMaker and can it help create an ApexChart connection script in FileMaker.","In my quest to see how much the hyped DeepSeek (https:\u002F\u002Fwww.deepseek.com\u002F) model knows about FileMaker, I though it would be fun to ask is to write me a solution to use ApexCharts (https:\u002F\u002Fapexcharts.com\u002F) inside a FileMaker webviewer using data from my Sales table.  \n  \nIn this video I walk you through the steps advised by DeepSeek (this is just one of the ways to do this) and build a quick FileMaker solution.","\u003Cp>In my quest to see how much the hyped DeepSeek (\u003Ca href=\"https:\u002F\u002Fwww.deepseek.com\u002F\">https:\u002F\u002Fwww.deepseek.com\u002F\u003C\u002Fa>) model knows about FileMaker, I though it would be fun to ask is to write me a solution to use ApexCharts (\u003Ca href=\"https:\u002F\u002Fapexcharts.com\u002F\">https:\u002F\u002Fapexcharts.com\u002F\u003C\u002Fa>) inside a FileMaker webviewer using data from my Sales table.  \u003C\u002Fp>\n\u003Cp>In this video I walk you through the steps advised by DeepSeek (this is just one of the ways to do this) and build a quick FileMaker solution.\u003C\u002Fp>\n","2025-01-28",1781520662000,[86],"\u002Fapi\u002Fknowledge\u002Fimage\u002F70\u002F?v=ae8a368062a3",{"id":669,"idKnowledge":670,"idDomain":15,"idCluster":15,"slug":671,"title":672,"description":673,"bodyMarkdown":674,"bodyHtml":675,"author":514,"date":676,"createdAt":665,"topics":677,"image":678,"hasDownload":28,"fileName":15,"youtubeId":27},"71","CB615A80-9CA5-F146-9FCC-53133849A957","seamless-payment-integration-between-filemaker-and-mollie-payment-provider","Seamless Payment Integration between FileMaker and Mollie Payment Provider.","Loggix BV integrated FileMaker and Mollie for a real estate portal, enabling seamless subscription payments. Users choose plans, complete payments via Mollie, and FileMaker automates subscription activation with recurring mandates—ensuring a frictionless, automated experience for users and administr","At Loggix BV, we pride ourselves on delivering tailored software solutions that connect the dots between backend functionality and user-friendly frontends. Our latest project involved integrating an e-commerce payment workflow for a commercial real estate portal. Built on a robust combination of Claris FileMaker and FMBetterForms, this portal offers property owners a seamless experience while allowing administrators to manage complex backend processes effortlessly.\n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F01\u002FMollie_integratie-1-1200x709.jpg)\n\n**The Challenge: Managing Subscriptions for Uploaded Properties**\n\nThe portal allows users to upload properties to the database, with address verification ensuring the property belongs to a supported region. However, users need an active subscription to upload properties in specific regions. To streamline this process, we needed to:\n\n1\\. **Provide flexible subscription options** – monthly or yearly plans.\n\n2\\. **Enable immediate payment processing** via a trusted provider.\n\n3\\. **Automate subscription activation and recurring payment mandates upon successful transactions.**\n\n**The Solution: FileMaker and Mollie API Integration**\n\nOur solution revolved around integrating the portal with Mollie, a trusted Dutch payment gateway known for its reliability and ease of use. Here’s how we brought the workflow to life:\n\n1\\. **User Subscription Process:**\n\nWhen users attempt to upload a property in a region outside their existing subscription, they are prompted to choose between a monthly or yearly plan. This option is presented seamlessly in the FMBetterForms-based frontend.\n\n2\\. **Payment Processing with Mollie:**\n\nUpon selecting a subscription plan, users are directed to Mollie’s secure payment gateway. Here, they can complete the payment using their preferred method, ensuring a smooth and trustworthy transaction experience.\n\n3\\. **Webhook Automation for Payment Status Updates:**\n\nOnce the payment is completed, Mollie triggers a webhook call to the FMBetterForms framework. This call communicates the payment status back to the FileMaker database, which processes the information in real time.\n\n4\\. **Subscription Activation and Mandate Creation:**\n\nUpon successful payment confirmation, FileMaker automatically activates the user’s subscription and generates a mandate for future recurring payments. This ensures uninterrupted access for users and simplifies subscription management for administrators.\n\n**Results: A Streamlined Experience for All**\n\nThis integration has transformed the way users interact with the portal and manage their subscriptions. Key benefits include:\n\n• **Frictionless User Experience:** Users can activate subscriptions instantly without manual intervention.\n\n• **Automated Processes:** Administrators save time with automated payment status tracking and subscription management.\n\n• **Scalable Solution:** The system is designed to handle future expansions, such as additional payment options or subscription tiers.\n\nAt Loggix BV, we thrive on solving unique challenges like these. By combining the flexibility of Claris FileMaker, the dynamic capabilities of FMBetterForms, and the reliability of Mollie, we’ve delivered a solution that ensures both client satisfaction and end-user convenience.\n\nIf you’re looking to integrate seamless payment workflows into your platform, let’s build together! Visit [Loggix.com](https:\u002F\u002Fwww.loggix.com) to learn more about our services.","\u003Cp>At Loggix BV, we pride ourselves on delivering tailored software solutions that connect the dots between backend functionality and user-friendly frontends. Our latest project involved integrating an e-commerce payment workflow for a commercial real estate portal. Built on a robust combination of Claris FileMaker and FMBetterForms, this portal offers property owners a seamless experience while allowing administrators to manage complex backend processes effortlessly.\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F01\u002FMollie_integratie-1-1200x709.jpg\" alt=\"\">\u003C\u002Fp>\n\u003Cp>\u003Cstrong>The Challenge: Managing Subscriptions for Uploaded Properties\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The portal allows users to upload properties to the database, with address verification ensuring the property belongs to a supported region. However, users need an active subscription to upload properties in specific regions. To streamline this process, we needed to:\u003C\u002Fp>\n\u003Cp>1. \u003Cstrong>Provide flexible subscription options\u003C\u002Fstrong> – monthly or yearly plans.\u003C\u002Fp>\n\u003Cp>2. \u003Cstrong>Enable immediate payment processing\u003C\u002Fstrong> via a trusted provider.\u003C\u002Fp>\n\u003Cp>3. \u003Cstrong>Automate subscription activation and recurring payment mandates upon successful transactions.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>The Solution: FileMaker and Mollie API Integration\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Our solution revolved around integrating the portal with Mollie, a trusted Dutch payment gateway known for its reliability and ease of use. Here’s how we brought the workflow to life:\u003C\u002Fp>\n\u003Cp>1. \u003Cstrong>User Subscription Process:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>When users attempt to upload a property in a region outside their existing subscription, they are prompted to choose between a monthly or yearly plan. This option is presented seamlessly in the FMBetterForms-based frontend.\u003C\u002Fp>\n\u003Cp>2. \u003Cstrong>Payment Processing with Mollie:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Upon selecting a subscription plan, users are directed to Mollie’s secure payment gateway. Here, they can complete the payment using their preferred method, ensuring a smooth and trustworthy transaction experience.\u003C\u002Fp>\n\u003Cp>3. \u003Cstrong>Webhook Automation for Payment Status Updates:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Once the payment is completed, Mollie triggers a webhook call to the FMBetterForms framework. This call communicates the payment status back to the FileMaker database, which processes the information in real time.\u003C\u002Fp>\n\u003Cp>4. \u003Cstrong>Subscription Activation and Mandate Creation:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Upon successful payment confirmation, FileMaker automatically activates the user’s subscription and generates a mandate for future recurring payments. This ensures uninterrupted access for users and simplifies subscription management for administrators.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Results: A Streamlined Experience for All\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>This integration has transformed the way users interact with the portal and manage their subscriptions. Key benefits include:\u003C\u002Fp>\n\u003Cp>• \u003Cstrong>Frictionless User Experience:\u003C\u002Fstrong> Users can activate subscriptions instantly without manual intervention.\u003C\u002Fp>\n\u003Cp>• \u003Cstrong>Automated Processes:\u003C\u002Fstrong> Administrators save time with automated payment status tracking and subscription management.\u003C\u002Fp>\n\u003Cp>• \u003Cstrong>Scalable Solution:\u003C\u002Fstrong> The system is designed to handle future expansions, such as additional payment options or subscription tiers.\u003C\u002Fp>\n\u003Cp>At Loggix BV, we thrive on solving unique challenges like these. By combining the flexibility of Claris FileMaker, the dynamic capabilities of FMBetterForms, and the reliability of Mollie, we’ve delivered a solution that ensures both client satisfaction and end-user convenience.\u003C\u002Fp>\n\u003Cp>If you’re looking to integrate seamless payment workflows into your platform, let’s build together! Visit \u003Ca href=\"https:\u002F\u002Fwww.loggix.com\">Loggix.com\u003C\u002Fa> to learn more about our services.\u003C\u002Fp>\n","2025-01-21",[23],"\u002Fapi\u002Fknowledge\u002Fimage\u002F71\u002F?v=29a51940fd93",{"id":680,"idKnowledge":681,"idDomain":15,"idCluster":15,"slug":682,"title":683,"description":684,"bodyMarkdown":15,"bodyHtml":15,"author":514,"date":685,"createdAt":665,"topics":686,"image":687,"hasDownload":28,"fileName":15,"youtubeId":27},"72","937EEBFB-C7EA-9243-9668-C30E2758FC44","extremely-clear-talk-on-ai","Extremely clear talk on AI","Grant Sanderson is talking giving an extreem clear talk about Artificial Intelligence. A must see when you are not all up to par with Ai.","2025-01-13",[86],"\u002Fapi\u002Fknowledge\u002Fimage\u002F72\u002F?v=119ef8eace05",{"id":689,"idKnowledge":690,"idDomain":15,"idCluster":15,"slug":691,"title":692,"description":693,"bodyMarkdown":694,"bodyHtml":695,"author":514,"date":696,"createdAt":697,"topics":698,"image":701,"hasDownload":28,"fileName":15,"youtubeId":27},"44","04D66E9C-080D-D543-A6B0-F4E79E2BD2A8","new-loggix-website-live","New Loggix Website live","New website Loggix.com live. Dutch and English version with from now on a strong focus on FileMaker custom Software, FMBetterForms Web Apps, APIs & AI and SaaS […]","![New website Loggix.com live. Dutch and English version with from now on a strong focus on FileMaker custom Software, FMBetterForms Web Apps, APIs & AI and SaaS development.](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F01\u002FLoggixWebsite-300x260.png)\n\nNew website Loggix.com live. Dutch and English version with from now on a strong focus on [FileMaker](https:\u002F\u002Fwww.claris.com) custom Software, [FMBetterForms](https:\u002F\u002Fwww.fmbetterforms.com\u002F) Web Apps, APIs & AI and SaaS development.  \n  \nOver the past year we have devoted a great deal of attention to building software for our clients. 2025 will be defined by building software for our own portfolio. This means a number of exciting SaaS collaborations and a number of entirely proprietary SaaS products.  \n  \nIt is going to be a wonderful, busy and exciting year!","\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2025\u002F01\u002FLoggixWebsite-300x260.png\" alt=\"New website Loggix.com live. Dutch and English version with from now on a strong focus on FileMaker custom Software, FMBetterForms Web Apps, APIs & AI and SaaS development.\">\u003C\u002Fp>\n\u003Cp>New website Loggix.com live. Dutch and English version with from now on a strong focus on \u003Ca href=\"https:\u002F\u002Fwww.claris.com\">FileMaker\u003C\u002Fa> custom Software, \u003Ca href=\"https:\u002F\u002Fwww.fmbetterforms.com\u002F\">FMBetterForms\u003C\u002Fa> Web Apps, APIs & AI and SaaS development.  \u003C\u002Fp>\n\u003Cp>Over the past year we have devoted a great deal of attention to building software for our clients. 2025 will be defined by building software for our own portfolio. This means a number of exciting SaaS collaborations and a number of entirely proprietary SaaS products.  \u003C\u002Fp>\n\u003Cp>It is going to be a wonderful, busy and exciting year!\u003C\u002Fp>\n","2025-01-10",1781519873000,[86,73,699,23,518,700],"Demo","SaaS","\u002Fapi\u002Fknowledge\u002Fimage\u002F44\u002F?v=7ea9c5b83f36",{"id":703,"idKnowledge":704,"idDomain":15,"idCluster":15,"slug":705,"title":706,"description":707,"bodyMarkdown":708,"bodyHtml":709,"author":514,"date":696,"createdAt":710,"topics":711,"image":712,"hasDownload":28,"fileName":15,"youtubeId":27},"43","56E6591F-0934-584C-AE54-4238E5017E17","12-helpful-tools-during-software-development","12 helpful tools during software development…","As software developers, we use a lot of 3rd party software development tools to make our work easier or faster. Below a small list of […]","As software developers, we use a lot of 3rd party software development tools to make our work easier or faster. Below a small list of a couple of the tools I use on pretty much a daily basis:  \n  \n1\\. ScreenStudio – [screen.studio](https:\u002F\u002Fscreen.studio\u002F) – Makes making screen videos a lot easier.  \n2\\. Whimsical – [whimsical.com](http:\u002F\u002Fwhimsical.com) – The perfect companion to make wireframes.  \n3\\. OpenArt.ai – [OpenArt.ai](http:\u002F\u002FOpenArt.ai) – Ai generated content.  \n4\\. ColorPicker – [pickcoloronline.com](https:\u002F\u002Fpickcoloronline.com\u002F) – Pick #colors straight from your screen.  \n5\\. TempMail – [temp-mail.org](https:\u002F\u002Ftemp-mail.org\u002F) – Make your API development easier with temp email addresses.  \n6\\. WebhookSite – [webhook.site](https:\u002F\u002Fwebhook.site\u002F) – Make your API development easier with a webhook test tool.  \n7\\. Unlimited Icons – [fonts.google.com\u002Ficons](https:\u002F\u002Ffonts.google.com\u002Ficons) – Pick and use from a large amount of nice icons.  \n8\\. CSS gradients – [cssgradient.io](https:\u002F\u002Fcssgradient.io\u002F) – Easily create gradients and use as your css style.  \n9\\. AutoAvatar – [i.pravatar.cc\u002F250](https:\u002F\u002Fi.pravatar.cc\u002F250) – Auto create variable pixel size avatars for test use in software.  \n10\\. SecretDesktop – [secretdesktop](https:\u002F\u002Fapps.apple.com\u002Fus\u002Fapp\u002Fsecretdesktop\u002Fid1469900735?mt=12) – On Mac hide all you desktop icons for calm focussed work.  \n11\\. CCS generator – [layout.bradwoods.io](https:\u002F\u002Flayout.bradwoods.io\u002F) – Create layout components code.  \n12\\. Screen shots – [postspark.app](https:\u002F\u002Fpostspark.app\u002F) – Quickly create beautiful screen shots.","\u003Cp>As software developers, we use a lot of 3rd party software development tools to make our work easier or faster. Below a small list of a couple of the tools I use on pretty much a daily basis:  \u003C\u002Fp>\n\u003Cp>1. ScreenStudio – \u003Ca href=\"https:\u002F\u002Fscreen.studio\u002F\">screen.studio\u003C\u002Fa> – Makes making screen videos a lot easier.\u003Cbr>2. Whimsical – \u003Ca href=\"http:\u002F\u002Fwhimsical.com\">whimsical.com\u003C\u002Fa> – The perfect companion to make wireframes.\u003Cbr>3. OpenArt.ai – \u003Ca href=\"http:\u002F\u002FOpenArt.ai\">OpenArt.ai\u003C\u002Fa> – Ai generated content.\u003Cbr>4. ColorPicker – \u003Ca href=\"https:\u002F\u002Fpickcoloronline.com\u002F\">pickcoloronline.com\u003C\u002Fa> – Pick #colors straight from your screen.\u003Cbr>5. TempMail – \u003Ca href=\"https:\u002F\u002Ftemp-mail.org\u002F\">temp-mail.org\u003C\u002Fa> – Make your API development easier with temp email addresses.\u003Cbr>6. WebhookSite – \u003Ca href=\"https:\u002F\u002Fwebhook.site\u002F\">webhook.site\u003C\u002Fa> – Make your API development easier with a webhook test tool.\u003Cbr>7. Unlimited Icons – \u003Ca href=\"https:\u002F\u002Ffonts.google.com\u002Ficons\">fonts.google.com\u002Ficons\u003C\u002Fa> – Pick and use from a large amount of nice icons.\u003Cbr>8. CSS gradients – \u003Ca href=\"https:\u002F\u002Fcssgradient.io\u002F\">cssgradient.io\u003C\u002Fa> – Easily create gradients and use as your css style.\u003Cbr>9. AutoAvatar – \u003Ca href=\"https:\u002F\u002Fi.pravatar.cc\u002F250\">i.pravatar.cc\u002F250\u003C\u002Fa> – Auto create variable pixel size avatars for test use in software.\u003Cbr>10. SecretDesktop – \u003Ca href=\"https:\u002F\u002Fapps.apple.com\u002Fus\u002Fapp\u002Fsecretdesktop\u002Fid1469900735?mt=12\">secretdesktop\u003C\u002Fa> – On Mac hide all you desktop icons for calm focussed work.\u003Cbr>11. CCS generator – \u003Ca href=\"https:\u002F\u002Flayout.bradwoods.io\u002F\">layout.bradwoods.io\u003C\u002Fa> – Create layout components code.\u003Cbr>12. Screen shots – \u003Ca href=\"https:\u002F\u002Fpostspark.app\u002F\">postspark.app\u003C\u002Fa> – Quickly create beautiful screen shots.\u003C\u002Fp>\n",1781519871000,[23],"\u002Fapi\u002Fknowledge\u002Fimage\u002F43\u002F?v=dcdb367685ee",{"id":714,"idKnowledge":715,"idDomain":15,"idCluster":15,"slug":716,"title":717,"description":718,"bodyMarkdown":719,"bodyHtml":720,"author":514,"date":721,"createdAt":722,"topics":723,"image":725,"hasDownload":28,"fileName":15,"youtubeId":27},"74","E32F4BDE-78B7-654D-A863-2C0BC484CE30","help-your-client-understand-their-own-processes","Help your client understand their own processes","Whimsical: a quick and easy way to draw up processes Translating client needs into functional software requires clear communication. To streamline this process, we use […]","**Whimsical: a quick and easy way to draw up processes**\n\nTranslating client needs into functional software requires clear communication. To streamline this process, we use Whimsical (https:\u002F\u002Fwww.whimsical.com)—a powerful tool for creating wireframes, mind maps, flowcharts, and more. This helps us visualize our clients’ ideas, ensuring that nothing gets lost in translation. The Whimsical mock ups are generally used as the starting point for our FileMaker and FMBetterforms developers.\n\n[![Whimsical mock up example used by our Filemaker developers](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2024\u002F09\u002Fwhimsical_mock-1024x644.jpeg)](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2024\u002F09\u002Fwhimsical_mock.jpeg)\n\n**Share and collaborate**\n\nWhen clients come to us with their requirements, we use Whimsical to create intuitive wireframes that map out the interface and functionality of their future software. These wireframes are simplified, high-level sketches of the screens that allow both our clients and development team to see how the final product will look and behave.\n\nThe beauty of Whimsical lies in its ease of use. It enables us to create interactive wireframes that clients can understand without technical jargon, helping bridge the gap between their vision and our technical execution. Adjustments can be made swiftly during meetings, and new ideas can be tested in real-time, making collaboration fluid and efficient.\n\nWhimsical’s versatility allows us to document client requirements in a way that is both comprehensive and easy to grasp. This collaborative approach means fewer revisions, reduced miscommunication, and more successful projects. Ultimately, using Whimsical helps us at Loggix build custom FileMaker solutions and web apps that perfectly align with our clients’ expectations.\n\n**Interested?**\n\nPlease contact us if you would like to discuss the options to bring your ideas to live.","\u003Cp>\u003Cstrong>Whimsical: a quick and easy way to draw up processes\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Translating client needs into functional software requires clear communication. To streamline this process, we use Whimsical (\u003Ca href=\"https:\u002F\u002Fwww.whimsical.com)%E2%80%94a\">https:\u002F\u002Fwww.whimsical.com)—a\u003C\u002Fa> powerful tool for creating wireframes, mind maps, flowcharts, and more. This helps us visualize our clients’ ideas, ensuring that nothing gets lost in translation. The Whimsical mock ups are generally used as the starting point for our FileMaker and FMBetterforms developers.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2024\u002F09\u002Fwhimsical_mock.jpeg\">\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2024\u002F09\u002Fwhimsical_mock-1024x644.jpeg\" alt=\"Whimsical mock up example used by our Filemaker developers\">\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Share and collaborate\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>When clients come to us with their requirements, we use Whimsical to create intuitive wireframes that map out the interface and functionality of their future software. These wireframes are simplified, high-level sketches of the screens that allow both our clients and development team to see how the final product will look and behave.\u003C\u002Fp>\n\u003Cp>The beauty of Whimsical lies in its ease of use. It enables us to create interactive wireframes that clients can understand without technical jargon, helping bridge the gap between their vision and our technical execution. Adjustments can be made swiftly during meetings, and new ideas can be tested in real-time, making collaboration fluid and efficient.\u003C\u002Fp>\n\u003Cp>Whimsical’s versatility allows us to document client requirements in a way that is both comprehensive and easy to grasp. This collaborative approach means fewer revisions, reduced miscommunication, and more successful projects. Ultimately, using Whimsical helps us at Loggix build custom FileMaker solutions and web apps that perfectly align with our clients’ expectations.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Interested?\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Please contact us if you would like to discuss the options to bring your ideas to live.\u003C\u002Fp>\n","2024-09-24",1781520668000,[23,724],"General","\u002Fapi\u002Fknowledge\u002Fimage\u002F74\u002F?v=10b764285238",{"id":727,"idKnowledge":728,"idDomain":15,"idCluster":15,"slug":729,"title":730,"description":731,"bodyMarkdown":732,"bodyHtml":733,"author":734,"date":721,"createdAt":735,"topics":736,"image":738,"hasDownload":28,"fileName":15,"youtubeId":27},"73","C841AAFD-5991-1C44-AC0C-ACE33F29DB65","the-new-css-media-query-range-syntax","The New CSS Media Query Range Syntax","We rely on CSS Media Queries for selecting and styling elements based on a targeted condition. That condition can be all kinds of things but typically fall […]","We rely on [CSS Media Queries](https:\u002F\u002Fcss-tricks.com\u002Fa-complete-guide-to-css-media-queries\u002F) for selecting and styling elements based on a targeted condition. That condition can be all kinds of things but typically fall into two camps: (1) the type of media that’s being used, and (2) a specific feature of the browser, device, or even the user’s environment.\n\nSo, say we want to apply certain CSS styling to a printed document:\n\n```\n\n    @media print { \n        .element { \n             \u002F* Style away! *\u002F \n        } \n    }\n    \n```\n\nThe fact that we can apply styles at a certain viewport width has made CSS Media Queries a core ingredient of responsive web design since Ethan Marcotte [coined the term](https:\u002F\u002Falistapart.com\u002Farticle\u002Fresponsive-web-design\u002F). If the browser’s viewport width is a certain size, then apply a set of style rules, which allows us to design elements that respond to the size of the browser.\n\n```\n\n    \u002F* When the viewport width is at least 30em... *\u002F \n    @media screen and (min-width: 30em) { \n        .element { \n            \u002F* Style away! *\u002F\n        } \n    }\n    \n```\n\nNotice the `and` in there? That’s an operator that allows us to combine statements. In that example, we combined a condition that the media type is a `screen` and that it’s `min-width` feature is set to `30em` (or above). We can do the same thing to target a range of viewport sizes:\n\n```\n\n    \u002F* When the viewport width is between 30em - 80em *\u002F\n    @media screen and (min-width: 30em) and (max-width: 80em) {\n        .element {\n            \u002F* Style away! *\u002F\n        } \n    }\n    \n```\n\nNow those styles apply to an explicit range of viewport widths rather than a single width!\n\nBut the Media Queries Level 4 specification has introduced a new syntax for targeting a range of viewport widths using common mathematical comparison operators — things like `\u003C`, `>`, and `=` — that make more sense syntactically while writing less code.\n\nLet’s dig into how that works.\n\n#### New comparison operators\n\nThat last example is a good illustration of how we’ve sort of “faked” ranges by combining conditions using the `and` operator. The big change in the Media Queries Level 4 specification is that we have new operators that compare values rather than combining them:\n\n-   `\u003C` evaluates if a value is **less than** another value\n-   `>` evaluates if a value is **greater than** another value\n-   `=` evaluates if a value is **equal** to another value\n-   `\u003C=` evaluates if a value is **less than or equal t**o another value\n-   `>=` evaluates if a value is **greater than or equal t**o another value\n\nHere’s how we might’ve written a media query that applies styles if the browser is `600px` wide or greater:\n\n```\n\n    @media (min-width: 600px) {\n        .element {\n            \u002F* Style away! *\u002F\n        } \n    }\n    \n```\n\nHere’s how it looks to write the same thing using a comparison operator:\n\n```\n\n    @media (width >= 600px) {\n        .element {\n            \u002F* Style away! *\u002F\n        } \n    }\n    \n```\n\n#### Targeting a range of viewport widths\n\nOften when we write CSS Media Queries, we’re creating what’s called a breakpoint — a condition where the design “breaks” and a set of styles are applied to fix it. A design can have a bunch of breakpoints! And they’re usually based on the viewport being between two widths: where the breakpoint starts and where the breakpoint ends.\n\nHere’s how we’ve done that using the `and` operator to combine the two breakpoint values:\n\n```\n\n    \u002F* When the browser is between 400px - 1000px *\u002F\n    @media (min-width: 400px) and (max-width: 1000px) {\n        \u002F* etc. *\u002F\n    }\n    \n```\n\nYou start to get a good sense of how much shorter and easier it is to write a media query when we ditch the Boolean `and` operator in favor of the new range comparison syntax:\n\n```\n\n    @media (400px \u003C= width \u003C= 1000px) {\n        \u002F* etc. *\u002F\n    }\n    \n```\n\nMuch easier, right? And it’s clear exactly what this media query is doing.\n\n#### Browser support\n\nThis improved media query syntax is still in its early days at the time of this writing and not as widely supported at the moment as the approach that combines `min-width` and `max-width`. We’re getting close, though! Safari is the only major holdout at this point, but [there is an open ticket for it](https:\u002F\u002Fbugs.webkit.org\u002Fshow_bug.cgi?id=180234) that you can follow.\n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2024\u002F09\u002FScreenshot_2-1.png)","\u003Cp>We rely on \u003Ca href=\"https:\u002F\u002Fcss-tricks.com\u002Fa-complete-guide-to-css-media-queries\u002F\">CSS Media Queries\u003C\u002Fa> for selecting and styling elements based on a targeted condition. That condition can be all kinds of things but typically fall into two camps: (1) the type of media that’s being used, and (2) a specific feature of the browser, device, or even the user’s environment.\u003C\u002Fp>\n\u003Cp>So, say we want to apply certain CSS styling to a printed document:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\n    @media print { \n        .element { \n             \u002F* Style away! *\u002F \n        } \n    }\n    \n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The fact that we can apply styles at a certain viewport width has made CSS Media Queries a core ingredient of responsive web design since Ethan Marcotte \u003Ca href=\"https:\u002F\u002Falistapart.com\u002Farticle\u002Fresponsive-web-design\u002F\">coined the term\u003C\u002Fa>. If the browser’s viewport width is a certain size, then apply a set of style rules, which allows us to design elements that respond to the size of the browser.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\n    \u002F* When the viewport width is at least 30em... *\u002F \n    @media screen and (min-width: 30em) { \n        .element { \n            \u002F* Style away! *\u002F\n        } \n    }\n    \n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Notice the \u003Ccode>and\u003C\u002Fcode> in there? That’s an operator that allows us to combine statements. In that example, we combined a condition that the media type is a \u003Ccode>screen\u003C\u002Fcode> and that it’s \u003Ccode>min-width\u003C\u002Fcode> feature is set to \u003Ccode>30em\u003C\u002Fcode> (or above). We can do the same thing to target a range of viewport sizes:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\n    \u002F* When the viewport width is between 30em - 80em *\u002F\n    @media screen and (min-width: 30em) and (max-width: 80em) {\n        .element {\n            \u002F* Style away! *\u002F\n        } \n    }\n    \n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Now those styles apply to an explicit range of viewport widths rather than a single width!\u003C\u002Fp>\n\u003Cp>But the Media Queries Level 4 specification has introduced a new syntax for targeting a range of viewport widths using common mathematical comparison operators — things like \u003Ccode><\u003C\u002Fcode>, \u003Ccode>>\u003C\u002Fcode>, and \u003Ccode>=\u003C\u002Fcode> — that make more sense syntactically while writing less code.\u003C\u002Fp>\n\u003Cp>Let’s dig into how that works.\u003C\u002Fp>\n\u003Ch4>New comparison operators\u003C\u002Fh4>\n\u003Cp>That last example is a good illustration of how we’ve sort of “faked” ranges by combining conditions using the \u003Ccode>and\u003C\u002Fcode> operator. The big change in the Media Queries Level 4 specification is that we have new operators that compare values rather than combining them:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode><\u003C\u002Fcode> evaluates if a value is \u003Cstrong>less than\u003C\u002Fstrong> another value\u003C\u002Fli>\n\u003Cli>\u003Ccode>>\u003C\u002Fcode> evaluates if a value is \u003Cstrong>greater than\u003C\u002Fstrong> another value\u003C\u002Fli>\n\u003Cli>\u003Ccode>=\u003C\u002Fcode> evaluates if a value is \u003Cstrong>equal\u003C\u002Fstrong> to another value\u003C\u002Fli>\n\u003Cli>\u003Ccode><=\u003C\u002Fcode> evaluates if a value is \u003Cstrong>less than or equal t\u003C\u002Fstrong>o another value\u003C\u002Fli>\n\u003Cli>\u003Ccode>>=\u003C\u002Fcode> evaluates if a value is \u003Cstrong>greater than or equal t\u003C\u002Fstrong>o another value\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Here’s how we might’ve written a media query that applies styles if the browser is \u003Ccode>600px\u003C\u002Fcode> wide or greater:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\n    @media (min-width: 600px) {\n        .element {\n            \u002F* Style away! *\u002F\n        } \n    }\n    \n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Here’s how it looks to write the same thing using a comparison operator:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\n    @media (width >= 600px) {\n        .element {\n            \u002F* Style away! *\u002F\n        } \n    }\n    \n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Targeting a range of viewport widths\u003C\u002Fh4>\n\u003Cp>Often when we write CSS Media Queries, we’re creating what’s called a breakpoint — a condition where the design “breaks” and a set of styles are applied to fix it. A design can have a bunch of breakpoints! And they’re usually based on the viewport being between two widths: where the breakpoint starts and where the breakpoint ends.\u003C\u002Fp>\n\u003Cp>Here’s how we’ve done that using the \u003Ccode>and\u003C\u002Fcode> operator to combine the two breakpoint values:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\n    \u002F* When the browser is between 400px - 1000px *\u002F\n    @media (min-width: 400px) and (max-width: 1000px) {\n        \u002F* etc. *\u002F\n    }\n    \n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>You start to get a good sense of how much shorter and easier it is to write a media query when we ditch the Boolean \u003Ccode>and\u003C\u002Fcode> operator in favor of the new range comparison syntax:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\n    @media (400px <= width <= 1000px) {\n        \u002F* etc. *\u002F\n    }\n    \n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Much easier, right? And it’s clear exactly what this media query is doing.\u003C\u002Fp>\n\u003Ch4>Browser support\u003C\u002Fh4>\n\u003Cp>This improved media query syntax is still in its early days at the time of this writing and not as widely supported at the moment as the approach that combines \u003Ccode>min-width\u003C\u002Fcode> and \u003Ccode>max-width\u003C\u002Fcode>. We’re getting close, though! Safari is the only major holdout at this point, but \u003Ca href=\"https:\u002F\u002Fbugs.webkit.org\u002Fshow_bug.cgi?id=180234\">there is an open ticket for it\u003C\u002Fa> that you can follow.\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2024\u002F09\u002FScreenshot_2-1.png\" alt=\"\">\u003C\u002Fp>\n","Ashish",1781520665000,[737],"Vue.js","\u002Fapi\u002Fknowledge\u002Fimage\u002F73\u002F?v=2884e7bee3ab",{"id":740,"idKnowledge":741,"idDomain":15,"idCluster":15,"slug":742,"title":743,"description":744,"bodyMarkdown":745,"bodyHtml":746,"author":514,"date":747,"createdAt":748,"topics":749,"image":750,"hasDownload":28,"fileName":15,"youtubeId":27},"76","8FA84874-B6BF-FE4F-AA1F-3CA0B78FFADF","ai-progress-in-the-next-year-s","AI progress in the next year(s)","A new industrial revolution At Computex 2024, NVIDIA CEO Jensen Huang unveiled groundbreaking innovations, including “NIMS” (NVIDIA Intelligent Machine System), a suite of AI-driven digital […]","###### A new industrial revolution\n\nAt Computex 2024, NVIDIA CEO Jensen Huang unveiled groundbreaking innovations, including “NIMS” (NVIDIA Intelligent Machine System), a suite of AI-driven digital humans and robots. He also introduced Earth 2.0, a high-fidelity digital twin of our planet designed for climate simulation, and announced new AI factories to accelerate the development of advanced AI models. These developments underscore NVIDIA’s leadership in AI and digital twin technologies, promising significant advancements across various industries.\n\n###### The production of tokens\n\nUntil ChatGPT AI was all about perception. Natural language understanding, computer vision, speech recognition, etc. Now we understand that AI is about ‘**generation of tokens**‘. Generative AI produces tokens that are words, images, video’s, charts, songs. But also tokens of proteins, genes, weather patterns or predictions of production processes. The next focus of AI will be on AI factories that produces tokens on a massive scale. Tokens that help robots, help other robots in production. The near future for us programmers is not to create software anymore, we will create AI models that will create software for us.\n\n###### How can this work for you\n\nAt Loggix we will try to scale the future down to understandable steps that can be taken today. Our advise is to stay attached to what is coming. Prepare your processes and software for tomorrow. Be aware that tomorrow is about **accessible data**. Only data that is accessible by Learning Models can be used by second (potential clients) and third parties around you. Feel free to contact us to discuss how your AI future will look like.","\u003Ch6>A new industrial revolution\u003C\u002Fh6>\n\u003Cp>At Computex 2024, NVIDIA CEO Jensen Huang unveiled groundbreaking innovations, including “NIMS” (NVIDIA Intelligent Machine System), a suite of AI-driven digital humans and robots. He also introduced Earth 2.0, a high-fidelity digital twin of our planet designed for climate simulation, and announced new AI factories to accelerate the development of advanced AI models. These developments underscore NVIDIA’s leadership in AI and digital twin technologies, promising significant advancements across various industries.\u003C\u002Fp>\n\u003Ch6>The production of tokens\u003C\u002Fh6>\n\u003Cp>Until ChatGPT AI was all about perception. Natural language understanding, computer vision, speech recognition, etc. Now we understand that AI is about ‘\u003Cstrong>generation of tokens\u003C\u002Fstrong>‘. Generative AI produces tokens that are words, images, video’s, charts, songs. But also tokens of proteins, genes, weather patterns or predictions of production processes. The next focus of AI will be on AI factories that produces tokens on a massive scale. Tokens that help robots, help other robots in production. The near future for us programmers is not to create software anymore, we will create AI models that will create software for us.\u003C\u002Fp>\n\u003Ch6>How can this work for you\u003C\u002Fh6>\n\u003Cp>At Loggix we will try to scale the future down to understandable steps that can be taken today. Our advise is to stay attached to what is coming. Prepare your processes and software for tomorrow. Be aware that tomorrow is about \u003Cstrong>accessible data\u003C\u002Fstrong>. Only data that is accessible by Learning Models can be used by second (potential clients) and third parties around you. Feel free to contact us to discuss how your AI future will look like.\u003C\u002Fp>\n","2024-08-19",1781520669000,[86,23],"\u002Fapi\u002Fknowledge\u002Fimage\u002F76\u002F?v=2590423468b9",{"id":752,"idKnowledge":753,"idDomain":15,"idCluster":15,"slug":754,"title":755,"description":756,"bodyMarkdown":757,"bodyHtml":758,"author":514,"date":747,"createdAt":722,"topics":759,"image":760,"hasDownload":28,"fileName":15,"youtubeId":27},"75","CFD88C8C-4F6C-654C-AE73-00A4AFB9571C","understanding-semantic-search-in-filemaker-a-game-changer-for-product-companies","Understanding Semantic Search in FileMaker: A Game-Changer for Product Companies","Semantic Search: Unlocking the Power of Embeddings and RAG Semantic search is a powerful technology that goes beyond traditional keyword-based search by understanding the meaning […]","**Semantic Search: Unlocking the Power of Embeddings and RAG**\n\n**Semantic search** is a powerful technology that goes beyond traditional keyword-based search by understanding the meaning and context of words in a query. At the heart of semantic search lies the concept of **embeddings**. Embeddings are dense **vector representations** of words, phrases, or entire documents, where similar meanings are positioned closer together in a multidimensional space. This allows the search engine to capture the nuances of language, making it possible to retrieve more relevant results even when the search terms don’t exactly match the content.\n\n![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2024\u002F08\u002FMatching-e1724067376943.jpg)\n\n**Integrating Semantic Search in FileMaker: A Practical Example**\n\nFor a product company looking to streamline its operations and enhance customer experience, integrating semantic search into their **FileMaker-based system** can be a game-changer. Let’s consider a scenario where a company sells a variety of products online and uses FileMaker to manage its inventory, customer data, and other business operations.\n\nTo enhance the user experience on their website, the company can embed their product information within a semantic search framework. By leveraging the **FM BetterForms** tool, which is highly compatible with FileMaker, they can create a seamless front-end interface for their website. FM BetterForms allows developers to build sophisticated, responsive web forms and interfaces that interact directly with FileMaker databases.\n\nHere’s how it can work: The company integrates a semantic search engine within its FileMaker system, where all product descriptions, specifications, and customer reviews are **embedded as vectors**. When a customer searches for a product on the website, the semantic search engine processes the query, retrieves relevant product information from the FileMaker database, and delivers it through the FM BetterForms interface. **This setup ensures that customers receive the most relevant product recommendations, even if their search terms are vague or imprecise.**\n\nFor instance, a customer searching for “eco-friendly water bottle” might not only get results for products explicitly labeled as “eco-friendly” but also those described as “sustainable,” “reusable,” or “biodegradable.” The result is a more intuitive and efficient search experience, driving customer satisfaction and boosting sales.\n\nIn conclusion, integrating semantic search with FileMaker, using tools like FM BetterForms, allows product companies to significantly enhance their digital offerings, making their websites smarter, more responsive, and more aligned with customer needs.\n\n**Interested?**\n\nPlease contact us if you would like to discuss the options to unlock your database to the public.","\u003Cp>\u003Cstrong>Semantic Search: Unlocking the Power of Embeddings and RAG\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Semantic search\u003C\u002Fstrong> is a powerful technology that goes beyond traditional keyword-based search by understanding the meaning and context of words in a query. At the heart of semantic search lies the concept of \u003Cstrong>embeddings\u003C\u002Fstrong>. Embeddings are dense \u003Cstrong>vector representations\u003C\u002Fstrong> of words, phrases, or entire documents, where similar meanings are positioned closer together in a multidimensional space. This allows the search engine to capture the nuances of language, making it possible to retrieve more relevant results even when the search terms don’t exactly match the content.\u003C\u002Fp>\n\u003Cp>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2024\u002F08\u002FMatching-e1724067376943.jpg\" alt=\"\">\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Integrating Semantic Search in FileMaker: A Practical Example\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>For a product company looking to streamline its operations and enhance customer experience, integrating semantic search into their \u003Cstrong>FileMaker-based system\u003C\u002Fstrong> can be a game-changer. Let’s consider a scenario where a company sells a variety of products online and uses FileMaker to manage its inventory, customer data, and other business operations.\u003C\u002Fp>\n\u003Cp>To enhance the user experience on their website, the company can embed their product information within a semantic search framework. By leveraging the \u003Cstrong>FM BetterForms\u003C\u002Fstrong> tool, which is highly compatible with FileMaker, they can create a seamless front-end interface for their website. FM BetterForms allows developers to build sophisticated, responsive web forms and interfaces that interact directly with FileMaker databases.\u003C\u002Fp>\n\u003Cp>Here’s how it can work: The company integrates a semantic search engine within its FileMaker system, where all product descriptions, specifications, and customer reviews are \u003Cstrong>embedded as vectors\u003C\u002Fstrong>. When a customer searches for a product on the website, the semantic search engine processes the query, retrieves relevant product information from the FileMaker database, and delivers it through the FM BetterForms interface. \u003Cstrong>This setup ensures that customers receive the most relevant product recommendations, even if their search terms are vague or imprecise.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>For instance, a customer searching for “eco-friendly water bottle” might not only get results for products explicitly labeled as “eco-friendly” but also those described as “sustainable,” “reusable,” or “biodegradable.” The result is a more intuitive and efficient search experience, driving customer satisfaction and boosting sales.\u003C\u002Fp>\n\u003Cp>In conclusion, integrating semantic search with FileMaker, using tools like FM BetterForms, allows product companies to significantly enhance their digital offerings, making their websites smarter, more responsive, and more aligned with customer needs.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Interested?\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Please contact us if you would like to discuss the options to unlock your database to the public.\u003C\u002Fp>\n",[86,23],"\u002Fapi\u002Fknowledge\u002Fimage\u002F75\u002F?v=f6257d6be38b",{"id":762,"idKnowledge":763,"idDomain":15,"idCluster":15,"slug":764,"title":765,"description":766,"bodyMarkdown":767,"bodyHtml":768,"author":514,"date":769,"createdAt":770,"topics":771,"image":772,"hasDownload":28,"fileName":15,"youtubeId":27},"78","7DB0E40F-389A-1040-8650-FD5F71ABCAF3","effortless-email-integration-leveraging-sendgrid-with-claris-filemaker","Effortless Email Integration: Leveraging SendGrid with Claris FileMaker","Sent professional mail from FileMaker For businesses looking to streamline their email communication, integrating SendGrid with Claris FileMaker offers a powerful and user-friendly solution. By […]","###### Sent professional mail from FileMaker\n\nFor businesses looking to streamline their email communication, integrating SendGrid with Claris FileMaker offers a powerful and user-friendly solution. By harnessing the capabilities of the SendGrid API, FileMaker users can send professional emails directly from their databases with minimal setup and maximum efficiency.\n\n###### Insert data straight from Filemaker\n\nOne of the key advantages of this integration is the ability to use SendGrid’s dynamic templates. These templates allow users to craft customized, responsive emails that can be easily personalized for each recipient. Whether sending out newsletters, promotional offers, or customer confirmations, the process is seamless. Users simply need to input their dynamic content within FileMaker, and SendGrid handles the rest—ensuring that emails are not only well-designed but also deliverable and trackable.\n\n> For ages we have been trying to consequently push out professional mail from our FileMaker Database. But only since Loggix has build the Sendgrid API we send scheduled mail and can measure the results of our efforts.\n\n###### ![](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2022\u002F06\u002Fmail-1024x598.jpg)\n\nSetting up this integration is straightforward, requiring just a few configuration steps within FileMaker to connect to the SendGrid API. Once connected, users can manage email campaigns directly from FileMaker, automating tasks that would otherwise be time-consuming.\n\n###### What is needed?\n\nJust a simple free sign up with [Sendgrid](https:\u002F\u002Fsendgrid.com\u002F)  and some script steps in FileMaker is basically enough to start with a couple of mails per day. When ready for a full blown mailer application not much more is needed. Templates can be easily managed from Sendgrid. A template builder makes knowledge of HTML obsolete.\n\n###### Below an example using html or template\n\nTo send a mail message do a **POST** call to the following endpoint:\n\n\\[gdlr\\_widget\\_box title=\"\" title-color=\"#ffffff\" background=\"#252525\" color=\"#ffffff\" \\]  \nhttps:\u002F\u002Fapi.sendgrid.com\u002Fv3\u002Fmail\u002Fsend  \n\\[\u002Fgdlr\\_widget\\_box\\]\n\n  \nIn the header add:\n\n\\[gdlr\\_widget\\_box title=\"\" title-color=\"#ffffff\" background=\"#252525\" color=\"#ffffff\" \\]  \nAuthorisation :  bearer ##Your API key##  \nContent-type: application\u002Fjson  \n\\[\u002Fgdlr\\_widget\\_box\\]\n\n  \nAnd add the below JSON in the body:\n\n\\[gdlr\\_widget\\_box title=\" title-color=\"#ffffff\" background=\"#252525\" color=\"#ffffff\" \\]  \n{  \n  \"personalizations\": \\[  \n    {  \n      \"to\": \\[  \n        {  \n          \"email\": “somebody@mail.com”  \n        }  \n      \\],  \n         \"dynamic\\_template\\_data\":{  \n           \"name”:”Someone”  \n          }  \n    }  \n  \\],  \n  \"from\": {  \n    \"email\": “test@loggix.com”  \n  },  \n  \"subject\": \"This is a test mail from Loggix | Use dynamic Template\",  \n  \"content\": \\[  \n    {  \n      \"type\": \"text\u002Fplain\",  \n      \"value\": “This plain text is overruled by the template when id is given“  \n    },  \n        {  \n      \"type\": \"text\u002Fhtml\",  \n      \"value\": \"\u003Chtml>\u003Cbody>This html text is overruled by the template when id is given\u003C\u002Fhtml>\u003C\u002Fbody>\"  \n    }  \n  \\],  \n  \"template\\_id\": \"d-2f0ce2e4e8e842b4982911eef5b604da\"  \n}  \n\\[\u002Fgdlr\\_widget\\_box\\]  \n  \n  \n\n###### Interested? Contact us.\n\nIn short, the combination of SendGrid and Claris FileMaker empowers businesses to manage their email communications more effectively, providing a professional touch with every message sent—all while keeping the process simple and intuitive. We are happy to help you out integrating Sendgrid in your solution, do not hesitate to contact us!","\u003Ch6>Sent professional mail from FileMaker\u003C\u002Fh6>\n\u003Cp>For businesses looking to streamline their email communication, integrating SendGrid with Claris FileMaker offers a powerful and user-friendly solution. By harnessing the capabilities of the SendGrid API, FileMaker users can send professional emails directly from their databases with minimal setup and maximum efficiency.\u003C\u002Fp>\n\u003Ch6>Insert data straight from Filemaker\u003C\u002Fh6>\n\u003Cp>One of the key advantages of this integration is the ability to use SendGrid’s dynamic templates. These templates allow users to craft customized, responsive emails that can be easily personalized for each recipient. Whether sending out newsletters, promotional offers, or customer confirmations, the process is seamless. Users simply need to input their dynamic content within FileMaker, and SendGrid handles the rest—ensuring that emails are not only well-designed but also deliverable and trackable.\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>For ages we have been trying to consequently push out professional mail from our FileMaker Database. But only since Loggix has build the Sendgrid API we send scheduled mail and can measure the results of our efforts.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch6>\u003Cimg src=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2022\u002F06\u002Fmail-1024x598.jpg\" alt=\"\">\u003C\u002Fh6>\n\u003Cp>Setting up this integration is straightforward, requiring just a few configuration steps within FileMaker to connect to the SendGrid API. Once connected, users can manage email campaigns directly from FileMaker, automating tasks that would otherwise be time-consuming.\u003C\u002Fp>\n\u003Ch6>What is needed?\u003C\u002Fh6>\n\u003Cp>Just a simple free sign up with \u003Ca href=\"https:\u002F\u002Fsendgrid.com\u002F\">Sendgrid\u003C\u002Fa>  and some script steps in FileMaker is basically enough to start with a couple of mails per day. When ready for a full blown mailer application not much more is needed. Templates can be easily managed from Sendgrid. A template builder makes knowledge of HTML obsolete.\u003C\u002Fp>\n\u003Ch6>Below an example using html or template\u003C\u002Fh6>\n\u003Cp>To send a mail message do a \u003Cstrong>POST\u003C\u002Fstrong> call to the following endpoint:\u003C\u002Fp>\n\u003Cp>[gdlr_widget_box title="" title-color="#ffffff" background="#252525" color="#ffffff" ]\u003Cbr>\u003Ca href=\"https:\u002F\u002Fapi.sendgrid.com\u002Fv3\u002Fmail\u002Fsend\">https:\u002F\u002Fapi.sendgrid.com\u002Fv3\u002Fmail\u002Fsend\u003C\u002Fa>\u003Cbr>[\u002Fgdlr_widget_box]\u003C\u002Fp>\n\u003Cp>In the header add:\u003C\u002Fp>\n\u003Cp>[gdlr_widget_box title="" title-color="#ffffff" background="#252525" color="#ffffff" ]\u003Cbr>Authorisation :  bearer ##Your API key##\u003Cbr>Content-type: application\u002Fjson\u003Cbr>[\u002Fgdlr_widget_box]\u003C\u002Fp>\n\u003Cp>And add the below JSON in the body:\u003C\u002Fp>\n\u003Cp>[gdlr_widget_box title=" title-color="#ffffff" background="#252525" color="#ffffff" ]\u003Cbr>{\u003Cbr>  "personalizations": [\u003Cbr>    {\u003Cbr>      "to": [\u003Cbr>        {\u003Cbr>          "email": “\u003Ca href=\"mailto:somebody@mail.com\">somebody@mail.com\u003C\u002Fa>”\u003Cbr>        }\u003Cbr>      ],\u003Cbr>         "dynamic_template_data":{\u003Cbr>           "name”:”Someone”\u003Cbr>          }\u003Cbr>    }\u003Cbr>  ],\u003Cbr>  "from": {\u003Cbr>    "email": “\u003Ca href=\"mailto:test@loggix.com\">test@loggix.com\u003C\u002Fa>”\u003Cbr>  },\u003Cbr>  "subject": "This is a test mail from Loggix | Use dynamic Template",\u003Cbr>  "content": [\u003Cbr>    {\u003Cbr>      "type": "text\u002Fplain",\u003Cbr>      "value": “This plain text is overruled by the template when id is given“\u003Cbr>    },\u003Cbr>        {\u003Cbr>      "type": "text\u002Fhtml",\u003Cbr>      "value": "\u003Chtml>\u003Cbody>This html text is overruled by the template when id is given\u003C\u002Fhtml>\u003C\u002Fbody>"\u003Cbr>    }\u003Cbr>  ],\u003Cbr>  "template_id": "d-2f0ce2e4e8e842b4982911eef5b604da"\u003Cbr>}\u003Cbr>[\u002Fgdlr_widget_box]  \u003C\u002Fp>\n\u003Ch6>Interested? Contact us.\u003C\u002Fh6>\n\u003Cp>In short, the combination of SendGrid and Claris FileMaker empowers businesses to manage their email communications more effectively, providing a professional touch with every message sent—all while keeping the process simple and intuitive. We are happy to help you out integrating Sendgrid in your solution, do not hesitate to contact us!\u003C\u002Fp>\n","2024-08-15",1781520670000,[73,23],"\u002Fapi\u002Fknowledge\u002Fimage\u002F78\u002F?v=60809c484a33",{"id":774,"idKnowledge":775,"idDomain":15,"idCluster":15,"slug":776,"title":777,"description":778,"bodyMarkdown":779,"bodyHtml":780,"author":514,"date":769,"createdAt":748,"topics":781,"image":782,"hasDownload":28,"fileName":15,"youtubeId":27},"77","21899F37-36B1-7F48-89FC-477C638C6074","import-filemaker-scripts-written-by-chatgpt","Import FileMaker scripts written by ChatGPT","Can ChatGPT help me write FileMaker scripts? Probably not new to you is that we can utilise ChatGPT to assist in writing complex FileMaker scripts. […]","###### Can ChatGPT help me write FileMaker scripts?\n\nProbably not new to you is that we can utilise ChatGPT to assist in writing complex FileMaker scripts. The tool allows you to describe your needs in natural language, and it will generate precise script code that can be used into FileMaker databases. This innovation significantly reduces the learning curve for new developers and boosts productivity for experienced users by (almost) automating the script-writing process.\n\n###### Script steps in FileMaker are XML based\n\nThere is no simple cut-paste step to get ‘visible filemaker script code’ back into filemaker. This because FileMaker uses specific XML based language in the script engine.  Give it a try, copy some script steps from one script to another, that will work, but copying these same steps to a simple text editor will not work. Nor the other way around. So let us first find a solution for this.\n\n###### Free BaseElements plugin\n\nTo get Script data from or to you FileMaker Script there is luckily a free live saving FM Plugin call [BaseElements](https:\u002F\u002Fdocs.baseelementsplugin.com\u002Farticle\u002F522-downloads). Download and install this plug in and now you can use below steps to exchange whole or partial scripts to and from the clipboard.\n\n\\[gdlr\\_widget\\_box title=\"\" title-color=\"#ffffff\" background=\"#252525\" color=\"#ffffff\" \\]\n\nBE\\_ClipboardGetText ( format )\n\nBE\\_ClipboardSetText ( text ; format )\n\n\\[\u002Fgdlr\\_widget\\_box\\]\n\nThe “format” parameter above takes a specific FileMaker code to recognise the clipboard content. The following code should be used:\n\n\\[gdlr\\_widget\\_box title=\"\" title-color=\"#ffffff\" background=\"#252525\" color=\"#ffffff\" \\] dyn.ah62d4rv4gk8zuxnxnq\n\\[\u002Fgdlr\\_widget\\_box\\]\n\nNow why is it important to also be able to Export XML?\n\n###### Let us teach ChatGPT Filemaker’s XML\n\nThe first thing to understand is that ChatGPT can reply her results in any format you like. You can ask it to reply in JSON, HTML, in a Excelsheet or as XML… it is all up to you. So, we can ask for a reply in XML format. But a format is only a structure. Filemaker uses a **library** of XML nodes that is unique to FileMaker. Thus how do we go from here?  \n\n###### ChatGPT Assistants to the rescue\n\nChatGPT Assistants can handle files as **source** to base their response upon. Thus by uploading a large Filemaker XML syntax example set, we can teach ChatGPT how to respond in proper Filemaker XML syntax!  A source file is quite simply made by exporting a (couple of) large example scripts from a Filemaker solution to a text (xml) file. The more different steps in this example script, the more library knowledge ChatGPT can take in.\n\nNow we are almost there.\n\n###### Upload you example library file and start asking questions\n\nIn a video blow I will show the result if we bind the above steps together.\n\n[https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2024\u002F08\u002Ffmscripts.mp4](https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2024\u002F08\u002Ffmscripts.mp4)\n\n###### Interested? Contact us.\n\nThe above is a hopefully a nice insight for fellow FileMaker developers. Loggix is ​​continuously exploring the limits and possibilities of software that we can use to improve our knowledge and your business processes.","\u003Ch6>Can ChatGPT help me write FileMaker scripts?\u003C\u002Fh6>\n\u003Cp>Probably not new to you is that we can utilise ChatGPT to assist in writing complex FileMaker scripts. The tool allows you to describe your needs in natural language, and it will generate precise script code that can be used into FileMaker databases. This innovation significantly reduces the learning curve for new developers and boosts productivity for experienced users by (almost) automating the script-writing process.\u003C\u002Fp>\n\u003Ch6>Script steps in FileMaker are XML based\u003C\u002Fh6>\n\u003Cp>There is no simple cut-paste step to get ‘visible filemaker script code’ back into filemaker. This because FileMaker uses specific XML based language in the script engine.  Give it a try, copy some script steps from one script to another, that will work, but copying these same steps to a simple text editor will not work. Nor the other way around. So let us first find a solution for this.\u003C\u002Fp>\n\u003Ch6>Free BaseElements plugin\u003C\u002Fh6>\n\u003Cp>To get Script data from or to you FileMaker Script there is luckily a free live saving FM Plugin call \u003Ca href=\"https:\u002F\u002Fdocs.baseelementsplugin.com\u002Farticle\u002F522-downloads\">BaseElements\u003C\u002Fa>. Download and install this plug in and now you can use below steps to exchange whole or partial scripts to and from the clipboard.\u003C\u002Fp>\n\u003Cp>[gdlr_widget_box title="" title-color="#ffffff" background="#252525" color="#ffffff" ]\u003C\u002Fp>\n\u003Cp>BE_ClipboardGetText ( format )\u003C\u002Fp>\n\u003Cp>BE_ClipboardSetText ( text ; format )\u003C\u002Fp>\n\u003Cp>[\u002Fgdlr_widget_box]\u003C\u002Fp>\n\u003Cp>The “format” parameter above takes a specific FileMaker code to recognise the clipboard content. The following code should be used:\u003C\u002Fp>\n\u003Cp>[gdlr_widget_box title="" title-color="#ffffff" background="#252525" color="#ffffff" ] dyn.ah62d4rv4gk8zuxnxnq\n[\u002Fgdlr_widget_box]\u003C\u002Fp>\n\u003Cp>Now why is it important to also be able to Export XML?\u003C\u002Fp>\n\u003Ch6>Let us teach ChatGPT Filemaker’s XML\u003C\u002Fh6>\n\u003Cp>The first thing to understand is that ChatGPT can reply her results in any format you like. You can ask it to reply in JSON, HTML, in a Excelsheet or as XML… it is all up to you. So, we can ask for a reply in XML format. But a format is only a structure. Filemaker uses a \u003Cstrong>library\u003C\u002Fstrong> of XML nodes that is unique to FileMaker. Thus how do we go from here?  \u003C\u002Fp>\n\u003Ch6>ChatGPT Assistants to the rescue\u003C\u002Fh6>\n\u003Cp>ChatGPT Assistants can handle files as \u003Cstrong>source\u003C\u002Fstrong> to base their response upon. Thus by uploading a large Filemaker XML syntax example set, we can teach ChatGPT how to respond in proper Filemaker XML syntax!  A source file is quite simply made by exporting a (couple of) large example scripts from a Filemaker solution to a text (xml) file. The more different steps in this example script, the more library knowledge ChatGPT can take in.\u003C\u002Fp>\n\u003Cp>Now we are almost there.\u003C\u002Fp>\n\u003Ch6>Upload you example library file and start asking questions\u003C\u002Fh6>\n\u003Cp>In a video blow I will show the result if we bind the above steps together.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2024\u002F08\u002Ffmscripts.mp4\">https:\u002F\u002Floggix.com\u002Fwp-content\u002Fuploads\u002F2024\u002F08\u002Ffmscripts.mp4\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch6>Interested? Contact us.\u003C\u002Fh6>\n\u003Cp>The above is a hopefully a nice insight for fellow FileMaker developers. Loggix is ​​continuously exploring the limits and possibilities of software that we can use to improve our knowledge and your business processes.\u003C\u002Fp>\n",[86,23],"\u002Fapi\u002Fknowledge\u002Fimage\u002F77\u002F?v=c88a2aed09c2",{"tree":784},{"domains":785,"dynamicDomains":1843,"recentDigest":2044},[786,914,1040,1206,1332,1458,1624,1750,1796],{"key":787,"title":788,"whitePaper":789,"clusters":792},"d1","Business Software Strategy",{"key":790,"title":788,"href":791,"matched":480,"overflow":28},"d1-whitepaper","\u002Fblog\u002Fhow-to-modernize-business-software-without-starting-over",[793,834,874],{"key":794,"title":795,"cornerstone":796,"articles":799},"d1-c1","Modernizing business software",{"key":797,"title":53,"href":791,"matched":480,"topics":798,"overflow":28},"d1-c1-corner",[23,58,45,59,60,61,62],[800,804,807,810,813,816,819,822,825,828,831],{"key":801,"title":35,"href":802,"matched":480,"topics":803,"overflow":28},"d1-c1-a01","\u002Fblog\u002Feleven-signs-that-your-business-software-is-holding-the-organisation-back",[42,43,44,45,23,46,47,48,49],{"key":805,"title":806,"href":27,"matched":28,"overflow":28},"d1-c1-a02","Modernize or replace: how to make the right decision",{"key":808,"title":809,"href":27,"matched":28,"overflow":28},"d1-c1-a03","Why old software is not necessarily bad software",{"key":811,"title":812,"href":27,"matched":28,"overflow":28},"d1-c1-a04","How to calculate the business case for software modernization",{"key":814,"title":815,"href":27,"matched":28,"overflow":28},"d1-c1-a05","How to modernize software without interrupting daily operations",{"key":817,"title":818,"href":27,"matched":28,"overflow":28},"d1-c1-a06","Which parts of an existing application should you preserve?",{"key":820,"title":821,"href":27,"matched":28,"overflow":28},"d1-c1-a07","Why modernization projects fail before development begins",{"key":823,"title":824,"href":27,"matched":28,"overflow":28},"d1-c1-a08","How to prioritize improvements in an existing system",{"key":826,"title":827,"href":27,"matched":28,"overflow":28},"d1-c1-a09","What does a phased modernization roadmap look like?",{"key":829,"title":830,"href":27,"matched":28,"overflow":28},"d1-c1-a10","How to prepare legacy software for web, mobile and AI",{"key":832,"title":833,"href":27,"matched":28,"overflow":28},"d1-c1-a11","When a complete rebuild really is the better option",{"key":835,"title":836,"cornerstone":837,"articles":840},"d1-c2","Future-proof application architecture",{"key":838,"title":839,"href":27,"matched":28,"overflow":28},"d1-c2-corner","A practical guide to future-proof business software architecture",[841,844,847,850,853,856,859,862,865,868,871],{"key":842,"title":843,"href":27,"matched":28,"overflow":28},"d1-c2-a01","What does future-proof software actually mean?",{"key":845,"title":846,"href":27,"matched":28,"overflow":28},"d1-c2-a02","Monolithic versus modular software architecture",{"key":848,"title":849,"href":27,"matched":28,"overflow":28},"d1-c2-a03","What is composable architecture?",{"key":851,"title":852,"href":27,"matched":28,"overflow":28},"d1-c2-a04","Why APIs are becoming the foundation of business software",{"key":854,"title":855,"href":27,"matched":28,"overflow":28},"d1-c2-a05","How to separate data, logic and interface",{"key":857,"title":858,"href":27,"matched":28,"overflow":28},"d1-c2-a06","When should an application become a platform?",{"key":860,"title":861,"href":27,"matched":28,"overflow":28},"d1-c2-a07","How to combine an existing back end with a modern front end",{"key":863,"title":864,"href":27,"matched":28,"overflow":28},"d1-c2-a08","What is headless software architecture?",{"key":866,"title":867,"href":27,"matched":28,"overflow":28},"d1-c2-a09","How to prevent vendor lock-in without creating unnecessary complexity",{"key":869,"title":870,"href":27,"matched":28,"overflow":28},"d1-c2-a10","Cloud, on-premise or hybrid: how should you decide?",{"key":872,"title":873,"href":27,"matched":28,"overflow":28},"d1-c2-a11","How to design software that can change without being rebuilt",{"key":875,"title":876,"cornerstone":877,"articles":880},"d1-c3","Software investment and decision-making",{"key":878,"title":879,"href":27,"matched":28,"overflow":28},"d1-c3-corner","How to make better business software investment decisions",[881,884,887,890,893,896,899,902,905,908,911],{"key":882,"title":883,"href":27,"matched":28,"overflow":28},"d1-c3-a01","Build, buy or extend: how to choose",{"key":885,"title":886,"href":27,"matched":28,"overflow":28},"d1-c3-a02","The hidden costs of standard software",{"key":888,"title":889,"href":27,"matched":28,"overflow":28},"d1-c3-a03","The hidden costs of custom software",{"key":891,"title":892,"href":27,"matched":28,"overflow":28},"d1-c3-a04","How to compare software proposals objectively",{"key":894,"title":895,"href":27,"matched":28,"overflow":28},"d1-c3-a05","Why feature lists lead to bad software decisions",{"key":897,"title":898,"href":27,"matched":28,"overflow":28},"d1-c3-a06","How to write a useful business software brief",{"key":900,"title":901,"href":27,"matched":28,"overflow":28},"d1-c3-a07","How much should business software cost?",{"key":903,"title":904,"href":27,"matched":28,"overflow":28},"d1-c3-a08","How to estimate the return on process automation",{"key":906,"title":907,"href":27,"matched":28,"overflow":28},"d1-c3-a09","What should a software proof of concept prove?",{"key":909,"title":910,"href":27,"matched":28,"overflow":28},"d1-c3-a10","How to select a software development partner",{"key":912,"title":913,"href":27,"matched":28,"overflow":28},"d1-c3-a11","How to prevent software projects from becoming open-ended",{"key":915,"title":916,"whitePaper":917,"clusters":919},"d2","Process Improvement",{"key":918,"title":916,"href":27,"matched":28,"overflow":28},"d2-whitepaper",[920,960,1000],{"key":921,"title":922,"cornerstone":923,"articles":926},"d2-c4","Process discovery and mapping",{"key":924,"title":925,"href":27,"matched":28,"overflow":28},"d2-c4-corner","How to map a business process before automating it",[927,930,933,936,939,942,945,948,951,954,957],{"key":928,"title":929,"href":27,"matched":28,"overflow":28},"d2-c4-a01","What is business process mapping?",{"key":931,"title":932,"href":27,"matched":28,"overflow":28},"d2-c4-a02","How to follow one transaction from beginning to end",{"key":934,"title":935,"href":27,"matched":28,"overflow":28},"d2-c4-a03","How to interview employees about the way work really happens",{"key":937,"title":938,"href":27,"matched":28,"overflow":28},"d2-c4-a04","How to identify handovers, delays and rework",{"key":940,"title":941,"href":27,"matched":28,"overflow":28},"d2-c4-a05","How to document exceptions without making a process unreadable",{"key":943,"title":944,"href":27,"matched":28,"overflow":28},"d2-c4-a06","What is a swimlane diagram and when should you use one?",{"key":946,"title":947,"href":27,"matched":28,"overflow":28},"d2-c4-a07","How to distinguish the official process from the real process",{"key":949,"title":950,"href":27,"matched":28,"overflow":28},"d2-c4-a08","How to find processes that depend on one employee",{"key":952,"title":953,"href":27,"matched":28,"overflow":28},"d2-c4-a09","How to map information flows between departments",{"key":955,"title":956,"href":27,"matched":28,"overflow":28},"d2-c4-a10","How detailed should a process map be?",{"key":958,"title":959,"href":27,"matched":28,"overflow":28},"d2-c4-a11","How to turn process observations into software requirements",{"key":961,"title":962,"cornerstone":963,"articles":966},"d2-c5","Operational inefficiency and process economics",{"key":964,"title":965,"href":27,"matched":28,"overflow":28},"d2-c5-corner","How to find and calculate the hidden cost of inefficient processes",[967,970,973,976,979,982,985,988,991,994,997],{"key":968,"title":969,"href":27,"matched":28,"overflow":28},"d2-c5-a01","The real cost of entering information twice",{"key":971,"title":972,"href":27,"matched":28,"overflow":28},"d2-c5-a02","Why Excel appears beside almost every business system",{"key":974,"title":975,"href":27,"matched":28,"overflow":28},"d2-c5-a03","How manual work creates invisible operational risk",{"key":977,"title":978,"href":27,"matched":28,"overflow":28},"d2-c5-a04","How to calculate the cost of a recurring administrative task",{"key":980,"title":981,"href":27,"matched":28,"overflow":28},"d2-c5-a05","What is the cost of waiting in a business process?",{"key":983,"title":984,"href":27,"matched":28,"overflow":28},"d2-c5-a06","How errors multiply across connected departments",{"key":986,"title":987,"href":27,"matched":28,"overflow":28},"d2-c5-a07","Why exception handling determines process efficiency",{"key":989,"title":990,"href":27,"matched":28,"overflow":28},"d2-c5-a08","How to measure process lead time",{"key":992,"title":993,"href":27,"matched":28,"overflow":28},"d2-c5-a09","Which process metrics actually matter?",{"key":995,"title":996,"href":27,"matched":28,"overflow":28},"d2-c5-a10","How to distinguish an irritation from a business problem",{"key":998,"title":999,"href":27,"matched":28,"overflow":28},"d2-c5-a11","How to build a financial case for workflow improvement",{"key":1001,"title":1002,"cornerstone":1003,"articles":1006},"d2-c6","Workflow design and continuous improvement",{"key":1004,"title":1005,"href":27,"matched":28,"overflow":28},"d2-c6-corner","How to redesign a workflow for people, software and AI",[1007,1010,1013,1016,1019,1022,1025,1028,1031,1034,1037],{"key":1008,"title":1009,"href":27,"matched":28,"overflow":28},"d2-c6-a01","What makes a workflow efficient?",{"key":1011,"title":1012,"href":27,"matched":28,"overflow":28},"d2-c6-a02","How to design approval workflows that do not create delays",{"key":1014,"title":1015,"href":27,"matched":28,"overflow":28},"d2-c6-a03","When should a process be standardized?",{"key":1017,"title":1018,"href":27,"matched":28,"overflow":28},"d2-c6-a04","When should users be allowed to deviate from a workflow?",{"key":1020,"title":1021,"href":27,"matched":28,"overflow":28},"d2-c6-a05","How to design useful status fields",{"key":1023,"title":1024,"href":27,"matched":28,"overflow":28},"d2-c6-a06","How to prevent work from disappearing between departments",{"key":1026,"title":1027,"href":27,"matched":28,"overflow":28},"d2-c6-a07","How to create a single operational work queue",{"key":1029,"title":1030,"href":27,"matched":28,"overflow":28},"d2-c6-a08","How to make automated processes understandable to employees",{"key":1032,"title":1033,"href":27,"matched":28,"overflow":28},"d2-c6-a09","Why exception routes are part of good workflow design",{"key":1035,"title":1036,"href":27,"matched":28,"overflow":28},"d2-c6-a10","How to test a workflow with real users",{"key":1038,"title":1039,"href":27,"matched":28,"overflow":28},"d2-c6-a11","How to improve a process without redesigning everything",{"key":1041,"title":1042,"whitePaper":1043,"clusters":1045},"d3","AI and Organizational Intelligence",{"key":1044,"title":1042,"href":27,"matched":28,"overflow":28},"d3-whitepaper",[1046,1086,1126,1166],{"key":1047,"title":1048,"cornerstone":1049,"articles":1052},"d3-c7","AI readiness and strategy",{"key":1050,"title":1051,"href":27,"matched":28,"overflow":28},"d3-c7-corner","How to determine whether your organization is ready for AI",[1053,1056,1059,1062,1065,1068,1071,1074,1077,1080,1083],{"key":1054,"title":1055,"href":27,"matched":28,"overflow":28},"d3-c7-a01","What does AI readiness mean?",{"key":1057,"title":1058,"href":27,"matched":28,"overflow":28},"d3-c7-a02","Why an AI strategy should not start with AI tools",{"key":1060,"title":1061,"href":27,"matched":28,"overflow":28},"d3-c7-a03","How to identify valuable AI use cases",{"key":1063,"title":1064,"href":27,"matched":28,"overflow":28},"d3-c7-a04","What is the difference between automation and AI?",{"key":1066,"title":1067,"href":27,"matched":28,"overflow":28},"d3-c7-a05","Which business processes are suitable for AI?",{"key":1069,"title":1070,"href":27,"matched":28,"overflow":28},"d3-c7-a06","Which processes should not be delegated to AI?",{"key":1072,"title":1073,"href":27,"matched":28,"overflow":28},"d3-c7-a07","How data quality limits AI performance",{"key":1075,"title":1076,"href":27,"matched":28,"overflow":28},"d3-c7-a08","How to run a practical AI readiness assessment",{"key":1078,"title":1079,"href":27,"matched":28,"overflow":28},"d3-c7-a09","How to prioritize AI experiments",{"key":1081,"title":1082,"href":27,"matched":28,"overflow":28},"d3-c7-a10","How to move from AI pilot to operational use",{"key":1084,"title":1085,"href":27,"matched":28,"overflow":28},"d3-c7-a11","Why an organization's AI maturity cannot exceed its ecosystem",{"key":1087,"title":1088,"cornerstone":1089,"articles":1092},"d3-c8","Human-AI collaboration",{"key":1090,"title":1091,"href":27,"matched":28,"overflow":28},"d3-c8-corner","How to design effective collaboration between people and AI",[1093,1096,1099,1102,1105,1108,1111,1114,1117,1120,1123],{"key":1094,"title":1095,"href":27,"matched":28,"overflow":28},"d3-c8-a01","What should remain a human responsibility in an AI workflow?",{"key":1097,"title":1098,"href":27,"matched":28,"overflow":28},"d3-c8-a02","What does human-in-the-loop mean?",{"key":1100,"title":1101,"href":27,"matched":28,"overflow":28},"d3-c8-a03","How can AI support judgement without replacing accountability?",{"key":1103,"title":1104,"href":27,"matched":28,"overflow":28},"d3-c8-a04","Why trust is an operational requirement for AI",{"key":1106,"title":1107,"href":27,"matched":28,"overflow":28},"d3-c8-a05","How to make AI output reviewable",{"key":1109,"title":1110,"href":27,"matched":28,"overflow":28},"d3-c8-a06","How should employees correct an AI system?",{"key":1112,"title":1113,"href":27,"matched":28,"overflow":28},"d3-c8-a07","When should AI ask for human approval?",{"key":1115,"title":1116,"href":27,"matched":28,"overflow":28},"d3-c8-a08","How to assign responsibility in partially automated processes",{"key":1118,"title":1119,"href":27,"matched":28,"overflow":28},"d3-c8-a09","Why reality checking remains a human advantage",{"key":1121,"title":1122,"href":27,"matched":28,"overflow":28},"d3-c8-a10","How AI changes the role of managers",{"key":1124,"title":1125,"href":27,"matched":28,"overflow":28},"d3-c8-a11","How to introduce AI without undermining employees",{"key":1127,"title":1128,"cornerstone":1129,"articles":1132},"d3-c9","AI agents and assistants",{"key":1130,"title":1131,"href":27,"matched":28,"overflow":28},"d3-c9-corner","A practical guide to AI agents in business operations",[1133,1136,1139,1142,1145,1148,1151,1154,1157,1160,1163],{"key":1134,"title":1135,"href":27,"matched":28,"overflow":28},"d3-c9-a01","What is an AI agent?",{"key":1137,"title":1138,"href":27,"matched":28,"overflow":28},"d3-c9-a02","What is the difference between an AI agent and a chatbot?",{"key":1140,"title":1141,"href":27,"matched":28,"overflow":28},"d3-c9-a03","What is an AI copilot?",{"key":1143,"title":1144,"href":27,"matched":28,"overflow":28},"d3-c9-a04","How can an AI agent work with business software?",{"key":1146,"title":1147,"href":27,"matched":28,"overflow":28},"d3-c9-a05","How do AI agents use APIs and tools?",{"key":1149,"title":1150,"href":27,"matched":28,"overflow":28},"d3-c9-a06","How should an AI agent access company data?",{"key":1152,"title":1153,"href":27,"matched":28,"overflow":28},"d3-c9-a07","How to prevent an AI agent from taking unintended actions",{"key":1155,"title":1156,"href":27,"matched":28,"overflow":28},"d3-c9-a08","What is agent memory and when is it useful?",{"key":1158,"title":1159,"href":27,"matched":28,"overflow":28},"d3-c9-a09","How to log and audit actions taken by AI",{"key":1161,"title":1162,"href":27,"matched":28,"overflow":28},"d3-c9-a10","When should multiple AI agents work together?",{"key":1164,"title":1165,"href":27,"matched":28,"overflow":28},"d3-c9-a11","How to build a first operational AI assistant",{"key":1167,"title":1168,"cornerstone":1169,"articles":1172},"d3-c10","AI governance, risk and accountability",{"key":1170,"title":1171,"href":27,"matched":28,"overflow":28},"d3-c10-corner","How to govern AI responsibly inside an organization",[1173,1176,1179,1182,1185,1188,1191,1194,1197,1200,1203],{"key":1174,"title":1175,"href":27,"matched":28,"overflow":28},"d3-c10-a01","What is AI governance?",{"key":1177,"title":1178,"href":27,"matched":28,"overflow":28},"d3-c10-a02","Who should own AI policy inside a company?",{"key":1180,"title":1181,"href":27,"matched":28,"overflow":28},"d3-c10-a03","How to classify AI use cases by risk",{"key":1183,"title":1184,"href":27,"matched":28,"overflow":28},"d3-c10-a04","How to document AI-supported decisions",{"key":1186,"title":1187,"href":27,"matched":28,"overflow":28},"d3-c10-a05","How to protect confidential information when using AI",{"key":1189,"title":1190,"href":27,"matched":28,"overflow":28},"d3-c10-a06","How to evaluate an AI supplier",{"key":1192,"title":1193,"href":27,"matched":28,"overflow":28},"d3-c10-a07","What should be included in an internal AI policy?",{"key":1195,"title":1196,"href":27,"matched":28,"overflow":28},"d3-c10-a08","How to manage bias in AI-assisted workflows",{"key":1198,"title":1199,"href":27,"matched":28,"overflow":28},"d3-c10-a09","How to monitor AI quality after implementation",{"key":1201,"title":1202,"href":27,"matched":28,"overflow":28},"d3-c10-a10","How to deal with hallucinations in operational processes",{"key":1204,"title":1205,"href":27,"matched":28,"overflow":28},"d3-c10-a11","How to create an AI incident procedure",{"key":1207,"title":1208,"whitePaper":1209,"clusters":1211},"d4","Data and Information Management",{"key":1210,"title":1208,"href":27,"matched":28,"overflow":28},"d4-whitepaper",[1212,1252,1292],{"key":1213,"title":1214,"cornerstone":1215,"articles":1218},"d4-c11","API and information architecture",{"key":1216,"title":1217,"href":27,"matched":28,"overflow":28},"d4-c11-corner","How APIs connect modern business systems",[1219,1222,1225,1228,1231,1234,1237,1240,1243,1246,1249],{"key":1220,"title":1221,"href":27,"matched":28,"overflow":28},"d4-c11-a01","What is an API in plain business language?",{"key":1223,"title":1224,"href":27,"matched":28,"overflow":28},"d4-c11-a02","What is a REST API?",{"key":1226,"title":1227,"href":27,"matched":28,"overflow":28},"d4-c11-a03","What is an API endpoint?",{"key":1229,"title":1230,"href":27,"matched":28,"overflow":28},"d4-c11-a04","What is the difference between GET, PUT and DELETE?",{"key":1232,"title":1233,"href":27,"matched":28,"overflow":28},"d4-c11-a05","What is JSON and why is it used in integrations?",{"key":1235,"title":1236,"href":27,"matched":28,"overflow":28},"d4-c11-a06","How should business data be exposed through an API?",{"key":1238,"title":1239,"href":27,"matched":28,"overflow":28},"d4-c11-a07","What is API-first development?",{"key":1241,"title":1242,"href":27,"matched":28,"overflow":28},"d4-c11-a08","What is an API gateway?",{"key":1244,"title":1245,"href":27,"matched":28,"overflow":28},"d4-c11-a09","How to document an API for internal use",{"key":1247,"title":1248,"href":27,"matched":28,"overflow":28},"d4-c11-a10","How to test an API without writing an application",{"key":1250,"title":1251,"href":27,"matched":28,"overflow":28},"d4-c11-a11","How to decide whether a system needs an API",{"key":1253,"title":1254,"cornerstone":1255,"articles":1258},"d4-c12","Integration design and synchronization",{"key":1256,"title":1257,"href":27,"matched":28,"overflow":28},"d4-c12-corner","How to design reliable integrations between business systems",[1259,1262,1265,1268,1271,1274,1277,1280,1283,1286,1289],{"key":1260,"title":1261,"href":27,"matched":28,"overflow":28},"d4-c12-a01","How do two business systems exchange data?",{"key":1263,"title":1264,"href":27,"matched":28,"overflow":28},"d4-c12-a02","Which system should be the source of truth?",{"key":1266,"title":1267,"href":27,"matched":28,"overflow":28},"d4-c12-a03","One-way or two-way synchronization: how to choose",{"key":1269,"title":1270,"href":27,"matched":28,"overflow":28},"d4-c12-a04","Realtime or scheduled synchronization: what is appropriate?",{"key":1272,"title":1273,"href":27,"matched":28,"overflow":28},"d4-c12-a05","How to prevent duplicate records during synchronization",{"key":1275,"title":1276,"href":27,"matched":28,"overflow":28},"d4-c12-a06","How to handle changed and deleted records",{"key":1278,"title":1279,"href":27,"matched":28,"overflow":28},"d4-c12-a07","How to retry failed integrations safely",{"key":1281,"title":1282,"href":27,"matched":28,"overflow":28},"d4-c12-a08","How to design useful integration logging",{"key":1284,"title":1285,"href":27,"matched":28,"overflow":28},"d4-c12-a09","What should happen when an external service is unavailable?",{"key":1287,"title":1288,"href":27,"matched":28,"overflow":28},"d4-c12-a10","How to migrate from manual exports to an automated integration",{"key":1290,"title":1291,"href":27,"matched":28,"overflow":28},"d4-c12-a11","The most common causes of silent integration errors",{"key":1293,"title":1294,"cornerstone":1295,"articles":1298},"d4-c13","Data quality, master data and governance",{"key":1296,"title":1297,"href":27,"matched":28,"overflow":28},"d4-c13-corner","How to improve data quality before automation or AI",[1299,1302,1305,1308,1311,1314,1317,1320,1323,1326,1329],{"key":1300,"title":1301,"href":27,"matched":28,"overflow":28},"d4-c13-a01","What is master data?",{"key":1303,"title":1304,"href":27,"matched":28,"overflow":28},"d4-c13-a02","What is a source of truth?",{"key":1306,"title":1307,"href":27,"matched":28,"overflow":28},"d4-c13-a03","Who should own customer and product data?",{"key":1309,"title":1310,"href":27,"matched":28,"overflow":28},"d4-c13-a04","How to identify duplicate records",{"key":1312,"title":1313,"href":27,"matched":28,"overflow":28},"d4-c13-a05","How to clean data without damaging history",{"key":1315,"title":1316,"href":27,"matched":28,"overflow":28},"d4-c13-a06","How to design useful validation rules",{"key":1318,"title":1319,"href":27,"matched":28,"overflow":28},"d4-c13-a07","How to manage mandatory and optional fields",{"key":1321,"title":1322,"href":27,"matched":28,"overflow":28},"d4-c13-a08","How to create consistent statuses and categories",{"key":1324,"title":1325,"href":27,"matched":28,"overflow":28},"d4-c13-a09","What is metadata and why does it matter?",{"key":1327,"title":1328,"href":27,"matched":28,"overflow":28},"d4-c13-a10","How to prepare data for an AI application",{"key":1330,"title":1331,"href":27,"matched":28,"overflow":28},"d4-c13-a11","How to measure data quality",{"key":1333,"title":1334,"whitePaper":1335,"clusters":1337},"d5","Integration and Automation",{"key":1336,"title":1334,"href":27,"matched":28,"overflow":28},"d5-whitepaper",[1338,1378,1418],{"key":1339,"title":1340,"cornerstone":1341,"articles":1344},"d5-c14","Identity, OAuth and secure access",{"key":1342,"title":1343,"href":27,"matched":28,"overflow":28},"d5-c14-corner","A practical guide to identity and OAuth for business integrations",[1345,1348,1351,1354,1357,1360,1363,1366,1369,1372,1375],{"key":1346,"title":1347,"href":27,"matched":28,"overflow":28},"d5-c14-a01","What is OAuth 2.0?",{"key":1349,"title":1350,"href":27,"matched":28,"overflow":28},"d5-c14-a02","What is the difference between authentication and authorization?",{"key":1352,"title":1353,"href":27,"matched":28,"overflow":28},"d5-c14-a03","What is an access token?",{"key":1355,"title":1356,"href":27,"matched":28,"overflow":28},"d5-c14-a04","What is a refresh token?",{"key":1358,"title":1359,"href":27,"matched":28,"overflow":28},"d5-c14-a05","Why do API tokens expire?",{"key":1361,"title":1362,"href":27,"matched":28,"overflow":28},"d5-c14-a06","What is the authorization-code flow?",{"key":1364,"title":1365,"href":27,"matched":28,"overflow":28},"d5-c14-a07","How should API credentials be stored?",{"key":1367,"title":1368,"href":27,"matched":28,"overflow":28},"d5-c14-a08","What are scopes in OAuth?",{"key":1370,"title":1371,"href":27,"matched":28,"overflow":28},"d5-c14-a09","What is single sign-on?",{"key":1373,"title":1374,"href":27,"matched":28,"overflow":28},"d5-c14-a10","How to troubleshoot an invalid authentication response",{"key":1376,"title":1377,"href":27,"matched":28,"overflow":28},"d5-c14-a11","How to revoke access to an integration safely",{"key":1379,"title":1380,"cornerstone":1381,"articles":1384},"d5-c15","Workflow automation",{"key":1382,"title":1383,"href":27,"matched":28,"overflow":28},"d5-c15-corner","How to automate business processes without losing control",[1385,1388,1391,1394,1397,1400,1403,1406,1409,1412,1415],{"key":1386,"title":1387,"href":27,"matched":28,"overflow":28},"d5-c15-a01","What is workflow automation?",{"key":1389,"title":1390,"href":27,"matched":28,"overflow":28},"d5-c15-a02","Which tasks should be automated first?",{"key":1392,"title":1393,"href":27,"matched":28,"overflow":28},"d5-c15-a03","What is the difference between RPA and API automation?",{"key":1395,"title":1396,"href":27,"matched":28,"overflow":28},"d5-c15-a04","How to automate recurring administrative work",{"key":1398,"title":1399,"href":27,"matched":28,"overflow":28},"d5-c15-a05","How to design automated notifications",{"key":1401,"title":1402,"href":27,"matched":28,"overflow":28},"d5-c15-a06","How to create a safe manual recovery route",{"key":1404,"title":1405,"href":27,"matched":28,"overflow":28},"d5-c15-a07","How to prevent automation from hiding errors",{"key":1407,"title":1408,"href":27,"matched":28,"overflow":28},"d5-c15-a08","What is idempotency and why does automation need it?",{"key":1410,"title":1411,"href":27,"matched":28,"overflow":28},"d5-c15-a09","How to monitor automated workflows",{"key":1413,"title":1414,"href":27,"matched":28,"overflow":28},"d5-c15-a10","How to document an automation",{"key":1416,"title":1417,"href":27,"matched":28,"overflow":28},"d5-c15-a11","How to calculate the return on automation",{"key":1419,"title":1420,"cornerstone":1421,"articles":1424},"d5-c16","n8n and integration orchestration",{"key":1422,"title":1423,"href":27,"matched":28,"overflow":28},"d5-c16-corner","How to use n8n as an automation layer for business software",[1425,1428,1431,1434,1437,1440,1443,1446,1449,1452,1455],{"key":1426,"title":1427,"href":27,"matched":28,"overflow":28},"d5-c16-a01","What is n8n?",{"key":1429,"title":1430,"href":27,"matched":28,"overflow":28},"d5-c16-a02","When should you use n8n instead of custom code?",{"key":1432,"title":1433,"href":27,"matched":28,"overflow":28},"d5-c16-a03","How does an n8n workflow work?",{"key":1435,"title":1436,"href":27,"matched":28,"overflow":28},"d5-c16-a04","How to connect an API to n8n",{"key":1438,"title":1439,"href":27,"matched":28,"overflow":28},"d5-c16-a05","How to receive and process a webhook in n8n",{"key":1441,"title":1442,"href":27,"matched":28,"overflow":28},"d5-c16-a06","How to handle errors in an n8n workflow",{"key":1444,"title":1445,"href":27,"matched":28,"overflow":28},"d5-c16-a07","How to store credentials securely in n8n",{"key":1447,"title":1448,"href":27,"matched":28,"overflow":28},"d5-c16-a08","How to connect n8n to FileMaker",{"key":1450,"title":1451,"href":27,"matched":28,"overflow":28},"d5-c16-a09","How to schedule a FileMaker automation with n8n",{"key":1453,"title":1454,"href":27,"matched":28,"overflow":28},"d5-c16-a10","How to use AI inside an n8n workflow",{"key":1456,"title":1457,"href":27,"matched":28,"overflow":28},"d5-c16-a11","How to monitor and maintain n8n workflows",{"key":1459,"title":1460,"whitePaper":1461,"clusters":1463},"d6","Modern Software Development",{"key":1462,"title":1460,"href":27,"matched":28,"overflow":28},"d6-whitepaper",[1464,1504,1544,1584],{"key":1465,"title":1466,"cornerstone":1467,"articles":1470},"d6-c17","Necessity-Driven Development",{"key":1468,"title":1469,"href":27,"matched":28,"overflow":28},"d6-c17-corner","Necessity-Driven Development: start with what must exist",[1471,1474,1477,1480,1483,1486,1489,1492,1495,1498,1501],{"key":1472,"title":1473,"href":27,"matched":28,"overflow":28},"d6-c17-a01","Why feature-driven development creates unnecessary software",{"key":1475,"title":1476,"href":27,"matched":28,"overflow":28},"d6-c17-a02","How to define the smallest valuable improvement",{"key":1478,"title":1479,"href":27,"matched":28,"overflow":28},"d6-c17-a03","What is the difference between an MVP and a necessary solution?",{"key":1481,"title":1482,"href":27,"matched":28,"overflow":28},"d6-c17-a04","How to prevent iterative development from creating a monster",{"key":1484,"title":1485,"href":27,"matched":28,"overflow":28},"d6-c17-a05","How AI changes the economics of custom software development",{"key":1487,"title":1488,"href":27,"matched":28,"overflow":28},"d6-c17-a06","Why documentation becomes more important when development accelerates",{"key":1490,"title":1491,"href":27,"matched":28,"overflow":28},"d6-c17-a07","How to decide what not to build",{"key":1493,"title":1494,"href":27,"matched":28,"overflow":28},"d6-c17-a08","How to use operational pain as a development backlog",{"key":1496,"title":1497,"href":27,"matched":28,"overflow":28},"d6-c17-a09","Why reuse matters more in AI-assisted development",{"key":1499,"title":1500,"href":27,"matched":28,"overflow":28},"d6-c17-a10","How to evaluate an AI-generated feature",{"key":1502,"title":1503,"href":27,"matched":28,"overflow":28},"d6-c17-a11","How Necessity-Driven Development supports continuous modernization",{"key":1505,"title":1506,"cornerstone":1507,"articles":1510},"d6-c18","Low-code, AI coding and professional development",{"key":1508,"title":1509,"href":27,"matched":28,"overflow":28},"d6-c18-corner","How low-code and AI-assisted development change business software",[1511,1514,1517,1520,1523,1526,1529,1532,1535,1538,1541],{"key":1512,"title":1513,"href":27,"matched":28,"overflow":28},"d6-c18-a01","What is low-code development?",{"key":1515,"title":1516,"href":27,"matched":28,"overflow":28},"d6-c18-a02","What is no-code development?",{"key":1518,"title":1519,"href":27,"matched":28,"overflow":28},"d6-c18-a03","What is vibe coding?",{"key":1521,"title":1522,"href":27,"matched":28,"overflow":28},"d6-c18-a04","When is vibe coding appropriate for business software?",{"key":1524,"title":1525,"href":27,"matched":28,"overflow":28},"d6-c18-a05","Why fast development does not remove the need for architecture",{"key":1527,"title":1528,"href":27,"matched":28,"overflow":28},"d6-c18-a06","How AI-assisted development changes the role of developers",{"key":1530,"title":1531,"href":27,"matched":28,"overflow":28},"d6-c18-a07","What can domain specialists build themselves?",{"key":1533,"title":1534,"href":27,"matched":28,"overflow":28},"d6-c18-a08","When should a prototype be rebuilt professionally?",{"key":1536,"title":1537,"href":27,"matched":28,"overflow":28},"d6-c18-a09","How to review AI-generated code",{"key":1539,"title":1540,"href":27,"matched":28,"overflow":28},"d6-c18-a10","How to prevent security problems in AI-generated applications",{"key":1542,"title":1543,"href":27,"matched":28,"overflow":28},"d6-c18-a11","Why experienced low-code developers may become more valuable",{"key":1545,"title":1546,"cornerstone":1547,"articles":1550},"d6-c19","Architecture, technical debt and maintainability",{"key":1548,"title":1549,"href":27,"matched":28,"overflow":28},"d6-c19-corner","How to keep business software maintainable as it grows",[1551,1554,1557,1560,1563,1566,1569,1572,1575,1578,1581],{"key":1552,"title":1553,"href":27,"matched":28,"overflow":28},"d6-c19-a01","What is technical debt?",{"key":1555,"title":1556,"href":27,"matched":28,"overflow":28},"d6-c19-a02","When is technical debt acceptable?",{"key":1558,"title":1559,"href":27,"matched":28,"overflow":28},"d6-c19-a03","How to recognize duplicated business logic",{"key":1561,"title":1562,"href":27,"matched":28,"overflow":28},"d6-c19-a04","Why hardcoded settings create future problems",{"key":1564,"title":1565,"href":27,"matched":28,"overflow":28},"d6-c19-a05","How to divide a system into maintainable modules",{"key":1567,"title":1568,"href":27,"matched":28,"overflow":28},"d6-c19-a06","What is separation of concerns?",{"key":1570,"title":1571,"href":27,"matched":28,"overflow":28},"d6-c19-a07","How to refactor without disrupting users",{"key":1573,"title":1574,"href":27,"matched":28,"overflow":28},"d6-c19-a08","How to retire obsolete functionality safely",{"key":1576,"title":1577,"href":27,"matched":28,"overflow":28},"d6-c19-a09","How to create a technical improvement backlog",{"key":1579,"title":1580,"href":27,"matched":28,"overflow":28},"d6-c19-a10","How to measure maintainability",{"key":1582,"title":1583,"href":27,"matched":28,"overflow":28},"d6-c19-a11","When should a module be rebuilt instead of repaired?",{"key":1585,"title":1586,"cornerstone":1587,"articles":1590},"d6-c20","Testing, documentation and software quality",{"key":1588,"title":1589,"href":27,"matched":28,"overflow":28},"d6-c20-corner","How to make custom business software reliable and transferable",[1591,1594,1597,1600,1603,1606,1609,1612,1615,1618,1621],{"key":1592,"title":1593,"href":27,"matched":28,"overflow":28},"d6-c20-a01","Why software documentation matters",{"key":1595,"title":1596,"href":27,"matched":28,"overflow":28},"d6-c20-a02","What should be documented in a business application?",{"key":1598,"title":1599,"href":27,"matched":28,"overflow":28},"d6-c20-a03","How to document business rules",{"key":1601,"title":1602,"href":27,"matched":28,"overflow":28},"d6-c20-a04","How to write useful script and code comments",{"key":1604,"title":1605,"href":27,"matched":28,"overflow":28},"d6-c20-a05","What is regression testing?",{"key":1607,"title":1608,"href":27,"matched":28,"overflow":28},"d6-c20-a06","How to create a practical test plan",{"key":1610,"title":1611,"href":27,"matched":28,"overflow":28},"d6-c20-a07","How to test integrations",{"key":1613,"title":1614,"href":27,"matched":28,"overflow":28},"d6-c20-a08","How to test role-based access",{"key":1616,"title":1617,"href":27,"matched":28,"overflow":28},"d6-c20-a09","How to create useful release notes",{"key":1619,"title":1620,"href":27,"matched":28,"overflow":28},"d6-c20-a10","How to introduce version control into a low-code project",{"key":1622,"title":1623,"href":27,"matched":28,"overflow":28},"d6-c20-a11","How to prevent critical knowledge from remaining with one developer",{"key":1625,"title":1626,"whitePaper":1627,"clusters":1629},"d7","FileMaker and Claris",{"key":1628,"title":1626,"href":27,"matched":28,"overflow":28},"d7-whitepaper",[1630,1670,1710],{"key":1631,"title":1632,"cornerstone":1633,"articles":1636},"d7-c21","FileMaker modernization",{"key":1634,"title":1635,"href":27,"matched":28,"overflow":28},"d7-c21-corner","How to modernize a FileMaker system step by step",[1637,1640,1643,1646,1649,1652,1655,1658,1661,1664,1667],{"key":1638,"title":1639,"href":27,"matched":28,"overflow":28},"d7-c21-a01","Is FileMaker still suitable for modern business software?",{"key":1641,"title":1642,"href":27,"matched":28,"overflow":28},"d7-c21-a02","How to determine whether a FileMaker solution needs modernization",{"key":1644,"title":1645,"href":27,"matched":28,"overflow":28},"d7-c21-a03","How to inventory an existing FileMaker solution",{"key":1647,"title":1648,"href":27,"matched":28,"overflow":28},"d7-c21-a04","How to modernize FileMaker without replacing the database",{"key":1650,"title":1651,"href":27,"matched":28,"overflow":28},"d7-c21-a05","How to improve an old FileMaker user interface",{"key":1653,"title":1654,"href":27,"matched":28,"overflow":28},"d7-c21-a06","How to combine FileMaker with a web application",{"key":1656,"title":1657,"href":27,"matched":28,"overflow":28},"d7-c21-a07","How to create a mobile layer for a FileMaker solution",{"key":1659,"title":1660,"href":27,"matched":28,"overflow":28},"d7-c21-a08","How to migrate a FileMaker solution to a newer version",{"key":1662,"title":1663,"href":27,"matched":28,"overflow":28},"d7-c21-a09","How to remove dependency on obsolete FileMaker plug-ins",{"key":1665,"title":1666,"href":27,"matched":28,"overflow":28},"d7-c21-a10","When should a FileMaker module be rebuilt?",{"key":1668,"title":1669,"href":27,"matched":28,"overflow":28},"d7-c21-a11","How to create a phased FileMaker modernization roadmap",{"key":1671,"title":1672,"cornerstone":1673,"articles":1676},"d7-c22","FileMaker data, performance and security",{"key":1674,"title":1675,"href":27,"matched":28,"overflow":28},"d7-c22-corner","How to improve the performance and structure of a FileMaker solution",[1677,1680,1683,1686,1689,1692,1695,1698,1701,1704,1707],{"key":1678,"title":1679,"href":27,"matched":28,"overflow":28},"d7-c22-a01","How does the FileMaker relationship graph work?",{"key":1681,"title":1682,"href":27,"matched":28,"overflow":28},"d7-c22-a02","How to design a maintainable FileMaker data model",{"key":1684,"title":1685,"href":27,"matched":28,"overflow":28},"d7-c22-a03","Why unstored calculations can slow FileMaker down",{"key":1687,"title":1688,"href":27,"matched":28,"overflow":28},"d7-c22-a04","How to find slow FileMaker scripts",{"key":1690,"title":1691,"href":27,"matched":28,"overflow":28},"d7-c22-a05","How to optimize FileMaker searches and sorts",{"key":1693,"title":1694,"href":27,"matched":28,"overflow":28},"d7-c22-a06","When should you use ExecuteSQL in FileMaker?",{"key":1696,"title":1697,"href":27,"matched":28,"overflow":28},"d7-c22-a07","How to use JSON effectively in FileMaker",{"key":1699,"title":1700,"href":27,"matched":28,"overflow":28},"d7-c22-a08","How to structure privilege sets in FileMaker",{"key":1702,"title":1703,"href":27,"matched":28,"overflow":28},"d7-c22-a09","How to secure external access to FileMaker Server",{"key":1705,"title":1706,"href":27,"matched":28,"overflow":28},"d7-c22-a10","How to manage container data in FileMaker",{"key":1708,"title":1709,"href":27,"matched":28,"overflow":28},"d7-c22-a11","How to diagnose FileMaker Server performance problems",{"key":1711,"title":1712,"cornerstone":1713,"articles":1716},"d7-c23","FileMaker APIs, integrations and development",{"key":1714,"title":1715,"href":27,"matched":28,"overflow":28},"d7-c23-corner","How to connect FileMaker to modern applications and services",[1717,1720,1723,1726,1729,1732,1735,1738,1741,1744,1747],{"key":1718,"title":1719,"href":27,"matched":28,"overflow":28},"d7-c23-a01","What is the FileMaker Data API?",{"key":1721,"title":1722,"href":27,"matched":28,"overflow":28},"d7-c23-a02","How to authenticate with the FileMaker Data API",{"key":1724,"title":1725,"href":27,"matched":28,"overflow":28},"d7-c23-a03","How to create records through the FileMaker Data API",{"key":1727,"title":1728,"href":27,"matched":28,"overflow":28},"d7-c23-a04","How to use FileMaker scripts through an API",{"key":1730,"title":1731,"href":27,"matched":28,"overflow":28},"d7-c23-a05","How to connect FileMaker to Exact Online",{"key":1733,"title":1734,"href":27,"matched":28,"overflow":28},"d7-c23-a06","How to connect FileMaker to Mollie",{"key":1736,"title":1737,"href":27,"matched":28,"overflow":28},"d7-c23-a07","How to connect FileMaker to Microsoft 365",{"key":1739,"title":1740,"href":27,"matched":28,"overflow":28},"d7-c23-a08","How to connect FileMaker to Shopify",{"key":1742,"title":1743,"href":27,"matched":28,"overflow":28},"d7-c23-a09","How to use webhooks with FileMaker",{"key":1745,"title":1746,"href":27,"matched":28,"overflow":28},"d7-c23-a10","How to connect Claude or another AI assistant to FileMaker",{"key":1748,"title":1749,"href":27,"matched":28,"overflow":28},"d7-c23-a11","How to use n8n as an automation agent for FileMaker",{"key":1751,"title":1752,"whitePaper":1753,"clusters":1755},"d8","Digital Operations",{"key":1754,"title":1752,"href":27,"matched":28,"overflow":28},"d8-whitepaper",[1756],{"key":1757,"title":1758,"cornerstone":1759,"articles":1762},"d8-c24","Operational platforms and digital work",{"key":1760,"title":1761,"href":27,"matched":28,"overflow":28},"d8-c24-corner","How to create a connected digital operating environment",[1763,1766,1769,1772,1775,1778,1781,1784,1787,1790,1793],{"key":1764,"title":1765,"href":27,"matched":28,"overflow":28},"d8-c24-a01","What is a digital operations platform?",{"key":1767,"title":1768,"href":27,"matched":28,"overflow":28},"d8-c24-a02","How to create one view of customers, orders and work",{"key":1770,"title":1771,"href":27,"matched":28,"overflow":28},"d8-c24-a03","How to replace disconnected spreadsheets with managed workflows",{"key":1773,"title":1774,"href":27,"matched":28,"overflow":28},"d8-c24-a04","How to design a customer self-service portal",{"key":1776,"title":1777,"href":27,"matched":28,"overflow":28},"d8-c24-a05","How to build a supplier portal",{"key":1779,"title":1780,"href":27,"matched":28,"overflow":28},"d8-c24-a06","How to support field employees with mobile software",{"key":1782,"title":1783,"href":27,"matched":28,"overflow":28},"d8-c24-a07","How to automate document generation and distribution",{"key":1785,"title":1786,"href":27,"matched":28,"overflow":28},"d8-c24-a08","How to build operational dashboards that people actually use",{"key":1788,"title":1789,"href":27,"matched":28,"overflow":28},"d8-c24-a09","How to reduce dependency on email in operational processes",{"key":1791,"title":1792,"href":27,"matched":28,"overflow":28},"d8-c24-a10","How to create real-time operational visibility",{"key":1794,"title":1795,"href":27,"matched":28,"overflow":28},"d8-c24-a11","How to connect office, field and customer workflows",{"key":1797,"title":1798,"whitePaper":1799,"clusters":1801},"d9","Security, Continuity and Governance",{"key":1800,"title":1798,"href":27,"matched":28,"overflow":28},"d9-whitepaper",[1802],{"key":1803,"title":1804,"cornerstone":1805,"articles":1808},"d9-c25","Security and business continuity",{"key":1806,"title":1807,"href":27,"matched":28,"overflow":28},"d9-c25-corner","How to secure and maintain business-critical software",[1809,1812,1815,1818,1821,1824,1827,1830,1833,1836,1839],{"key":1810,"title":1811,"href":27,"matched":28,"overflow":28},"d9-c25-a01","How to apply role-based access control",{"key":1813,"title":1814,"href":27,"matched":28,"overflow":28},"d9-c25-a02","Why employees often have more access than they need",{"key":1816,"title":1817,"href":27,"matched":28,"overflow":28},"d9-c25-a03","How to protect confidential business information",{"key":1819,"title":1820,"href":27,"matched":28,"overflow":28},"d9-c25-a04","How to create a useful audit trail",{"key":1822,"title":1823,"href":27,"matched":28,"overflow":28},"d9-c25-a05","What should be included in an application backup strategy?",{"key":1825,"title":1826,"href":27,"matched":28,"overflow":28},"d9-c25-a06","Why restoring a backup must be tested",{"key":1828,"title":1829,"href":27,"matched":28,"overflow":28},"d9-c25-a07","How to prepare for failure of an external API",{"key":1831,"title":1832,"href":27,"matched":28,"overflow":28},"d9-c25-a08","How to monitor a business-critical application",{"key":1834,"title":1835,"href":27,"matched":28,"overflow":28},"d9-c25-a09","How to manage software updates safely",{"key":1837,"title":1838,"href":27,"matched":28,"overflow":28},"d9-c25-a10","How to prepare an incident response procedure",{"key":1840,"title":11,"href":1841,"matched":480,"topics":1842,"overflow":28},"d9-c25-a11","\u002Fblog\u002Fhow-to-prevent-dependency-on-one-supplier-or-developer",[19,20,21,22,23,24,25,26],[1844,2024],{"key":1845,"title":1846,"clusters":1847},"recent-nieuws","Recent News",[1848,1980,1990,1994],{"key":1849,"title":23,"articles":1850},"recent-nieuws-filemaker",[1851,1854,1857,1860,1863,1866,1869,1872,1875,1878,1881,1884,1887,1890,1893,1896,1899,1902,1905,1908,1911,1914,1917,1920,1923,1926,1929,1932,1935,1938,1941,1944,1947,1950,1953,1956,1959,1962,1965,1968,1971,1974,1977],{"key":64,"title":67,"href":1852,"matched":480,"topics":1853,"date":16,"image":74},"\u002Fblog\u002Ffilemaker-development-zonder-kostbare-migratie",[23,73],{"key":76,"title":79,"href":1855,"matched":480,"topics":1856,"date":83,"image":94},"\u002Fblog\u002Frag-systeem-voor-een-interne-kennisbank",[86,87,88,23,89,90,91,92,93],{"key":96,"title":99,"href":1858,"matched":480,"topics":1859,"date":103,"image":107},"\u002Fblog\u002Fmaatwerk-software-die-uw-processen-vooruithelpt",[23,106],{"key":109,"title":112,"href":1861,"matched":480,"topics":1862,"date":116,"image":120},"\u002Fblog\u002Feen-mobiele-app-op-filemaker-bouwen-voor-uw-team",[23,119],{"key":122,"title":125,"href":1864,"matched":480,"topics":1865,"date":129,"image":133},"\u002Fblog\u002Fgids-voor-legacy-software-modernisering",[23,132],{"key":135,"title":138,"href":1867,"matched":480,"topics":1868,"date":142,"image":145},"\u002Fblog\u002Fwat-kost-api-integratie-voor-uw-organisatie",[73,23],{"key":147,"title":150,"href":1870,"matched":480,"topics":1871,"date":154,"image":164},"\u002Fblog\u002Flegacy-database-omzetten-naar-webapp",[157,158,159,23,160,161,162,163],{"key":192,"title":195,"href":1873,"matched":480,"topics":1874,"date":199,"image":204},"\u002Fblog\u002Fai-chatbot-voor-interne-kennisbank-werkt-het",[23,86,202,203],{"key":206,"title":209,"href":1876,"matched":480,"topics":1877,"date":213,"image":216},"\u002Fblog\u002Frag-systeem-voor-bedrijven-slim-of-te-vroeg",[87,23],{"key":231,"title":234,"href":1879,"matched":480,"topics":1880,"date":238,"image":242},"\u002Fblog\u002Flegacy-database-vervangen-of-uitbreiden",[241,23,228],{"key":244,"title":247,"href":1882,"matched":480,"topics":1883,"date":238,"image":254},"\u002Fblog\u002Fexact-online-koppelen-aan-filemaker-zo-automatiseer-je-facturen-veilig-en-foutloos",[23,253,73,44],{"key":270,"title":273,"href":1885,"matched":480,"topics":1886,"date":277,"image":281},"\u002Fblog\u002Fwebapp-op-filemaker-data-slim-aanpakken",[23,280,73],{"key":283,"title":286,"href":1888,"matched":480,"topics":1889,"date":277,"image":293},"\u002Fblog\u002Fhow-to-speed-up-data-input-in-filemaker-with-handy-free-speech-to-text-tool",[23,292,86],{"key":295,"title":298,"href":1891,"matched":480,"topics":1892,"date":302,"image":305},"\u002Fblog\u002Ffilemaker-api-koppeling-zonder-gedoe",[73,23],{"key":334,"title":337,"href":1894,"matched":480,"topics":1895,"date":314,"image":345},"\u002Fblog\u002Fhow-to-use-agentic-fm-to-generate-paste-filemaker-scripts-with-ai",[86,23,44,73,344],{"key":347,"title":350,"href":1897,"matched":480,"topics":1898,"date":314,"image":357},"\u002Fblog\u002Ffilemaker-2026-ai-gets-serious-llms-gemini-support-and-agentic-development-on-the-horizon",[86,23],{"key":359,"title":362,"href":1900,"matched":480,"topics":1901,"date":366,"image":369},"\u002Fblog\u002Ffilemaker-systeem-moderniseren-zonder-risico",[23],{"key":384,"title":387,"href":1903,"matched":480,"topics":1904,"date":391,"image":394},"\u002Fblog\u002Fnecessity-driven-development-bouw-alleen-software-die-echt-nodig-is",[23,86],{"key":396,"title":399,"href":1906,"matched":480,"topics":1907,"date":403,"image":406},"\u002Fblog\u002Fde-10-belangrijkste-nieuwe-functies-van-filemaker-2026-voor-eindgebruikers",[23,86],{"key":468,"title":471,"href":1909,"matched":480,"topics":1910,"date":475,"image":479},"\u002Fblog\u002Fvoorraad-beheer-systeem",[23,478],{"key":483,"title":486,"href":1912,"matched":480,"topics":1913,"date":475,"image":494},"\u002Fblog\u002Ffilemaker-claude-skill",[23,492,493],{"key":496,"title":499,"href":1915,"matched":480,"topics":1916,"date":475,"image":505},"\u002Fblog\u002Ftranscribe-with-local-llm-right-into-filemaker",[23,86],{"key":507,"title":510,"href":1918,"matched":480,"topics":1919,"date":515,"image":519},"\u002Fblog\u002Ffilemaker-mcp-server-ai-and-hosted-fm-files",[23,518],{"key":521,"title":524,"href":1921,"matched":480,"topics":1922,"date":515,"image":530},"\u002Fblog\u002Ftalking-to-your-data-with-the-filemaker-app-assistant",[23,518],{"key":532,"title":535,"href":1924,"matched":480,"topics":1925,"date":539,"image":542},"\u002Fblog\u002Fusing-n8n-as-an-automation-agent-for-filemaker-solutions",[73,23],{"key":544,"title":547,"href":1927,"matched":480,"topics":1928,"date":539,"image":553},"\u002Fblog\u002Ffigma-plugin-for-fmbetterforms",[23,518],{"key":555,"title":558,"href":1930,"matched":480,"topics":1931,"date":562,"image":565},"\u002Fblog\u002Ffilemaker-2025-is-here",[23],{"key":567,"title":570,"href":1933,"matched":480,"topics":1934,"date":562,"image":575},"\u002Fblog\u002Ffilemaker-2025-tip-warning",[23],{"key":577,"title":580,"href":1936,"matched":480,"topics":1937,"date":584,"image":586},"\u002Fblog\u002Ffilemaker-app-cross-borders-working-with-exchange-rates-timezones-vat-validation-and-address-autocompletion",[23],{"key":588,"title":591,"href":1939,"matched":480,"topics":1940,"date":595,"image":597},"\u002Fblog\u002Fuseful-tools-for-vue-js-developers",[23],{"key":599,"title":602,"href":1942,"matched":480,"topics":1943,"date":606,"image":609},"\u002Fblog\u002Fwhy-your-filemaker-crm-needs-a-data-upgrade-and-how-to-start-today",[23],{"key":611,"title":614,"href":1945,"matched":480,"topics":1946,"date":618,"image":621},"\u002Fblog\u002Fprinting-from-filemaker-server-is-possible",[23],{"key":623,"title":626,"href":1948,"matched":480,"topics":1949,"date":630,"image":632},"\u002Fblog\u002Fwebapps-based-on-filemaker",[23,518],{"key":634,"title":637,"href":1951,"matched":480,"topics":1952,"date":641,"image":644},"\u002Fblog\u002Fyour-filemaker-server-still-on-tls-1-1",[23],{"key":646,"title":649,"href":1954,"matched":480,"topics":1955,"date":653,"image":655},"\u002Fblog\u002Fwhy-use-filemaker-features-importance-and-ai-integration",[23],{"key":669,"title":672,"href":1957,"matched":480,"topics":1958,"date":676,"image":678},"\u002Fblog\u002Fseamless-payment-integration-between-filemaker-and-mollie-payment-provider",[23],{"key":689,"title":692,"href":1960,"matched":480,"topics":1961,"date":696,"image":701},"\u002Fblog\u002Fnew-loggix-website-live",[86,73,699,23,518,700],{"key":703,"title":706,"href":1963,"matched":480,"topics":1964,"date":696,"image":712},"\u002Fblog\u002F12-helpful-tools-during-software-development",[23],{"key":714,"title":717,"href":1966,"matched":480,"topics":1967,"date":721,"image":725},"\u002Fblog\u002Fhelp-your-client-understand-their-own-processes",[23,724],{"key":740,"title":743,"href":1969,"matched":480,"topics":1970,"date":747,"image":750},"\u002Fblog\u002Fai-progress-in-the-next-year-s",[86,23],{"key":752,"title":755,"href":1972,"matched":480,"topics":1973,"date":747,"image":760},"\u002Fblog\u002Funderstanding-semantic-search-in-filemaker-a-game-changer-for-product-companies",[86,23],{"key":762,"title":765,"href":1975,"matched":480,"topics":1976,"date":769,"image":772},"\u002Fblog\u002Feffortless-email-integration-leveraging-sendgrid-with-claris-filemaker",[73,23],{"key":774,"title":777,"href":1978,"matched":480,"topics":1979,"date":769,"image":782},"\u002Fblog\u002Fimport-filemaker-scripts-written-by-chatgpt",[86,23],{"key":1981,"title":1982,"articles":1983},"recent-nieuws-webapps","Web Apps",[1984,1987],{"key":256,"title":259,"href":1985,"matched":480,"topics":1986,"date":263,"image":268},"\u002Fblog\u002Ffilemaker-mobiele-app-bouwen-wat-werkt",[266,267],{"key":727,"title":730,"href":1988,"matched":480,"topics":1989,"date":721,"image":738},"\u002Fblog\u002Fthe-new-css-media-query-range-syntax",[737],{"key":1991,"title":1992,"articles":1993},"recent-nieuws-api","API Integrations",[],{"key":1995,"title":86,"articles":1996},"recent-nieuws-ai",[1997,2000,2003,2006,2009,2012,2015,2018,2021],{"key":179,"title":182,"href":1998,"matched":480,"topics":1999,"date":186,"image":190},"\u002Fblog\u002Fvoice-agent-voor-leadopvolging-zin-of-niet",[189,86],{"key":218,"title":221,"href":2001,"matched":480,"topics":2002,"date":225,"image":229},"\u002Fblog\u002Fbedrijfsprocessen-automatiseren-met-ai",[86,228],{"key":320,"title":323,"href":2004,"matched":480,"topics":2005,"date":314,"image":332},"\u002Fblog\u002Fremotion-a-tool-that-builds-videos-using-code-instead-of-a-timeline",[86,330,331],{"key":371,"title":374,"href":2007,"matched":480,"topics":2008,"date":379,"image":382},"\u002Fblog\u002Fhow-to-supercharge-your-ai-coding-agent-workflow-with-ecc",[344,86],{"key":421,"title":424,"href":2010,"matched":480,"topics":2011,"date":415,"image":431},"\u002Fblog\u002Fgemini-embedding-2-geef-je-filemaker-oplossing-een-ai-geheugen",[87,430,86],{"key":433,"title":436,"href":2013,"matched":480,"topics":2014,"date":415,"image":442},"\u002Fblog\u002Fdeploy-ai-agents-apis-and-backends-in-minutes-with-railway",[86],{"key":444,"title":447,"href":2016,"matched":480,"topics":2017,"date":415,"image":454},"\u002Fblog\u002Frun-your-own-private-ai-workspace-for-free-with-open-webui",[453],{"key":657,"title":660,"href":2019,"matched":480,"topics":2020,"date":664,"image":667},"\u002Fblog\u002Fdeepseek-filemaker-apexcharts",[86],{"key":680,"title":683,"href":2022,"matched":480,"topics":2023,"date":685,"image":687},"\u002Fblog\u002Fextremely-clear-talk-on-ai",[86],{"key":2025,"title":2026,"clusters":2027},"overig","Other",[2028],{"key":2029,"title":2030,"articles":2031},"overig-ongecategoriseerd","Uncategorized",[2032,2035,2038,2041],{"key":166,"title":169,"href":2033,"matched":480,"topics":2034,"date":173,"image":177},"\u002Fblog\u002Ffilemaker-koppelen-met-exact-zo-werkt-het",[176],{"key":307,"title":310,"href":2036,"matched":480,"topics":2037,"date":314,"image":318},"\u002Fblog\u002Fmaatwerk-database-software-laten-maken",[317],{"key":408,"title":411,"href":2039,"matched":480,"topics":2040,"date":415,"image":419},"\u002Fblog\u002Fwhat-if-you-could-generate-an-entire-ai-podcast-with-multiple-speakers-from-a-single-text-prompt",[418],{"key":456,"title":459,"href":2042,"matched":480,"topics":2043,"date":415,"image":466},"\u002Fblog\u002Fbuild-your-own-ai-voice-agent-for-free-with-pipecat",[189,465],[2045,2047,2049,2051],{"key":64,"title":67,"href":1852,"matched":480,"topics":2046,"date":16,"image":74},[23,73],{"key":76,"title":79,"href":1855,"matched":480,"topics":2048,"date":83,"image":94},[86,87,88,23,89,90,91,92,93],{"key":96,"title":99,"href":1858,"matched":480,"topics":2050,"date":103,"image":107},[23,106],{"key":109,"title":112,"href":1861,"matched":480,"topics":2052,"date":116,"image":120},[23,119]]