Deploy to FileMaker

Deployment for an Agentic Development Toolkit (ADT) Web Viewer app means bundling the web app and storing it in your FileMaker file so it can load inside a Web Viewer layout.

This is different from deploying a browser app to a hosting provider. The deployed artifact is a single HTML file living inside the FileMaker file itself — there's no server to stand up. See How Embedded Deployment Works for the conceptual background on what deployment means and what other shapes it can take.

Ask the agent to deploy

Once the app works locally and FileMaker is connected, you can ask the agent to handle deployment for you:

Deploy the app to my connected FileMaker file.

If deployment fails, tell me what to fix.

The agent should treat deployment as a release step, not just a file copy: running available checks, building the production bundle, deploying the generated HTML, then verifying the result inside FileMaker. See Deploy an App for the exact step-by-step procedure and the production-file caution.

The final verification step is one you should review yourself: navigate to the Web Viewer layout in FileMaker and confirm the deployed app loads with real data.

Most coding agents let you disable tools or toggle automatic prompting for individual tools; keep deployment approval on unless you're intentionally working in a safe dev environment.

Next step

Continue with Preview and Edit an App for source vs. bundled Web Viewer HTML and how to redeploy updates.

Then read Agent Workflow to understand how deployment fits into the larger read, write, verify, and fix loop.