If you’re building an integration on Flowy, register it under Developers → OAuth apps in the settings sidebar. Owners and Editors can create and manage apps; Viewers see the list read-only. This page covers the console itself. See OAuth for the authorization flow your app implements against it.
Create an app
Click Create OAuth app at /settings/oauth-apps/new and fill in:
- App details: name, description, website, and logo, all shown to users on the consent screen.
- Client type: Confidential (a server-side app; gets a client secret) or Public (PKCE) (a SPA, CLI, or native app; no secret). This can’t be changed after creation.
- Redirect URIs: where users are sent back after authorizing. HTTPS only, except
http://localhost for local development.
- Scopes: the most this app can ever request, grouped by resource (Flows, Runs, Generations, Assets, Credits, Elements). Users approve exactly the scopes you pick here when they connect.
For a confidential app, the client ID and secret are shown exactly once when you create it. Copy the secret immediately, since Flowy can’t show it again.
Manage an app
Open an app from the list at /settings/oauth-apps/:appId to:
- Copy the client ID from the list or the app’s own page.
- Regenerate the secret: rotates a confidential app’s secret; the old one stops working immediately, so update every deployment before you rotate.
- Delete the app: permanent, and you’ll type to confirm.
What users see
Every scope you select has a plain-language consent line: for example, runs:write reads as “Run your flows (uses your credits)”. Users see these when they authorize your app, and can revoke access at any time from their own Connected apps page. Last modified on August 29, 2026
