Secrets & integrations
The "keys" to third-party services all live in this chapter: API keys you fill in yourself (secrets), and ready-made services you can connect with one click (integrations).
The "Secrets" tab: give your app keys
Many third-party services (email, payments, AI APIs…) need an API key. In "More → Secrets", click "Add secret":
- Fill in the name following the provider's docs, e.g.
RESEND_API_KEY(uppercase with underscores is the convention); - Paste the key the provider sent you as the value;
- After saving, tell the AI in the chat: "I've set
RESEND_API_KEYin secrets, use it to send emails".
Two reassuring points: the list only shows names, never full values; and the AI can use the keys to do its job, but it can't take them away or display them in full.
The "Integrations" tab: services you can connect in one click
The integrations panel auto-detects your project; the main capabilities:
| Capability | Purpose |
|---|---|
| Backend & database | Let the app store data (contact forms, articles, arbitrary storage) |
| Sign-in | Add registration and login to the app |
| Social login | One-click sign-in with GitHub / Google |
| Payments | Collect payments, memberships, paid features |
Click "Connect with one click" and the AI does the wiring; the panel shows "Connected / Not connected". Fully static projects have no backend, so related capabilities are marked unavailable — let the AI add a backend first, then come back to connect.
Your own AI quota (optional)
If you have your own Cloudflare AI Gateway token, you can connect it via the usage badge and keep generating with your own quota: once connected, generation consumes your own AI Gateway quota but daily usage limits still apply to every account and can't be waived; when the free allowance runs out, you'll also be guided to connect Cloudflare to continue. Not having one doesn't affect normal use at all.