Skip to content
← Blog

How to let Claude use an app it built

After Claude builds an app on floo, it can also use it: read records, add entries, and run actions through the app's own API, as you, with no extra key. How it works from Claude chat and Claude Code, and how to give other programs their own scoped keys.

floo team

TL;DR

Once Claude builds an app on floo, it can use it too. Through the floo connector, Claude reads the app's API and calls its routes as you, with your role, so "add this to the tracker" or "what's overdue?" works from the chat. Writes are a separate tool your client can ask you to approve.

  • No extra key for team apps. Claude calls the app with the floo sign-in it already has.
  • The app sees your identity headers, so its own rules still apply.
  • Other programs get their own app API keys, scoped to the routes they need.

The app Claude built is usually a place for data: requests, renewals, inventory. The fastest way to put data in or get an answer out is often not the page. It is asking Claude, who can call the app directly.

What it looks like

In Claude chat with the floo connector:

Add a request to the requests app: Acme wants SSO by March, owner Sam, priority high.

Which renewals in the tracker are due in the next two weeks and still open?

Claude finds the matching route in the app's API, calls it as you, and answers. The app sees X-Floo-User-Email and your app role, exactly as when you click the button yourself, so a rule like "only admins can close a request" still holds.

How it works

The floo connector has three tools for this:

ToolDoes
search_app_apiReads the app's OpenAPI spec and finds the matching routes
read_app_apiSends GET or HEAD
write_app_apiSends POST, PUT, PATCH, or DELETE

Each call names an environment, dev or prod, so Claude never writes to live data by accident. Claude Code can do the same with a plain request and your floo API key:

curl -H "Authorization: Bearer $FLOO_KEY" https://requests.getfloo.app/api/requests

floo checks you are a member of the app, removes the key, and passes your identity on. The key never reaches the app.

This works on routes behind floo sign-in: an app with access_mode = "accounts", or routes declared with access = "api_key". On a public route, such as a customer portal that runs its own user accounts, floo removes the key and the call arrives anonymous, so the app's own sign-in still applies. For those apps, give Claude's calls an api_key route instead.

Help Claude find the routes

Claude works best when the app describes its own API. Ask for it when you build:

Serve an OpenAPI spec at /api/openapi.json and describe every route with a summary.

FastAPI serves /openapi.json on its own. The floo starter for Next.js serves /api/openapi.json and fails its tests when a route is undocumented.

Give other programs their own key

A script, another service, or a partner's system should not use your sign-in. Give it an app API key scoped to the routes it needs:

floo apps consumers create weekly-export
floo apps keys create weekly-export --consumer weekly-export --scope reports.access

The key only works on routes declared with access = "api_key" and that scope, and floo apps keys revoke turns it off within 30 seconds. The details are in app API keys and give your agent its own API key to an internal app.

Keep a person on the writes

Let Claude read freely and ask before it writes. write_app_api is marked destructive, so most clients ask before each call. For anything that spends money or messages a customer, have the app prepare the action and a person approve it. The full reference is in let your agent call your app.

Frequently asked questions

Can Claude use an app after it builds it?

Yes. With the floo connector, Claude can call the app's routes as you: read data, add entries, and run actions. floo checks that you are a member of the app and passes your identity to it, the same as when you open it in a browser.

Does Claude need a separate API key to call the app?

No. Claude uses the floo sign-in it already has. App API keys are for other programs, like a script or another service, that should reach only some routes.

Can Claude change data in the app without asking?

Reads and writes are separate tools. read_app_api is marked read-only and write_app_api destructive, so your client can allow reads on their own and ask you before every write.

Get your app live.

read https://getfloo.com/agents.md and set me up on floo

Get an API key
Usage-based pricing. See plans →