Adding Your First Token
Connecting a SaaS provider to Flarite takes about 2 minutes. Here's exactly how to do it.
General Steps
The flow is the same for every integration. The only difference is where you go to get the token.
Open the Integration in the Sidebar
In the Flarite dashboard, click the integration name in the left sidebar (e.g. Cloudflare, Stripe, Supabase, or Appwrite).
Click "API Tokens" in the sidebar
Under the selected integration, click the API Tokens menu item. This opens the credential management panel on the right side of the dashboard.
Click the "Get Token" button
Each integration has a branded button that opens your provider's credential page in a new tab — directly to the right place to create an API key. For example:
- Cloudflare → opens
dash.cloudflare.com/profile/api-tokens - Stripe → opens
dashboard.stripe.com/apikeys - Supabase → opens
supabase.com/dashboard/account/tokens - Appwrite → opens
cloud.appwrite.io/console
Create credentials in your provider dashboard
Follow the provider's instructions to create an API key or token. See the provider-specific guides below for exactly what permissions to grant:
Paste the credentials into Flarite
Return to the Flarite tab and paste the token(s) into the form fields. Add an optional nickname to identify this credential (useful if you have multiple accounts). Click Save & Verify.
Flarite will validate the credentials by making a test API call. If the credentials are valid, you'll see a success confirmation with your account name.
Select the credential and start chatting
After saving, click the credential to activate it. The AI will now use this token for all subsequent commands in this integration.
How are tokens stored?
Every token you add is encrypted with AES-256-GCM before being written to the database. The encryption key is a Cloudflare Worker Secret — not accessible to the database, not accessible to our team. See Token Encryption for the full technical details.
Revoking access
To remove a credential from Flarite, click the delete icon next to it in the API Tokens panel. This immediately removes the encrypted record from our database. We recommend also revoking the token directly in your provider's dashboard for maximum security.
