Configure AI Account correctly

Beginner

Use Configure AI Account with provider, endpoint, API key, and runtime scope exactly as Claris documents it.

What you'll learn

Why account names are local runtime names, not provider names
When Custom provider requires an endpoint
Why the endpoint for a custom provider must end with a slash

Configure AI Account is the gateway step for most AI work in FileMaker. It gives an account a local name, chooses a model provider or custom endpoint, and supplies the API key that authorizes requests.

Stuck is a valid status

Need a second brain on this one?

If this lesson just collided with your real schema, script stack, or deadline, book consulting and turn the confusion into a concrete plan.

Book consulting

1/3

Use a stable account name

Account Name is any calculated text expression, but every other AI step must use the same name. The name does not have to match the provider. Keep it short and consistent.

FileMaker Script

Set Error Capture [ On ]
Configure AI Account [ Account Name: "main-ai" ; Model Provider: OpenAI ; API key: Global::OpenAI_API_Key ]
Set Variable [ $error ; Value: Get ( LastError ) ]

FileMaker AI feature map: what each step is for Generate Response from Model and agentic mode