Flomixy has two ways to let another tool act on your account: an OAuth connection and an API key. They do the same kind of job but are created and removed in different places.
At a glance
| OAuth connection | API key | |
|---|---|---|
| How you set it up | Click Sign in with Flomixy inside the other app and approve the request | Create it yourself and paste it into the tool |
| Where you manage it | Settings → Connected apps | Settings → API keys |
| Who can create it | Workspace owner | Workspace owner |
| What you see | The app name, the workspace it can use, its permissions and when it was last used | The key name, its scopes, expiry date and last use |
| How you stop it | Revoke the app on Connected apps | Revoke the key (then delete it if you want it gone from the list) |
| Secret to copy | None, you never handle a secret | The key, shown once |
OAuth connections (Connected apps)
When you connect an assistant such as Claude on the web by signing in with Flomixy, you approve what it may do and Flomixy remembers that approval as a grant. No key is created and there is nothing to paste or keep safe.
Open Settings → Connected apps to see every grant: the app name, the workspace it is limited to (or "All workspaces"), its permissions and when it last used them. Click Revoke to cut it off. The app loses access immediately and has to ask for your approval again to come back.
This page lists OAuth connections only. A key you created by hand never shows up here.
API keys
An API key is a password you create for one tool. Open Settings → API keys → New API key, name it, choose its scopes (the permissions it has) and copy it straight away, because it is shown only once. Paste it into the tool.
Give a key only the scopes it needs, and set an expiry date for temporary projects. You can revoke a key at any time and tools using it lose access immediately. See API keys: choosing the right permissions.
Which should I use?
- The assistant offers Sign in with Flomixy: use the OAuth connection. Nothing to copy, and you can revoke it in one click.
- The tool only accepts a key, or you are writing your own script or automation: use an API key.
Good to know
- Both are created by the workspace owner. Admins and team members should ask the owner.
- Posts created through either route wait for human approval by default. The assistant cannot approve or reject posts itself.
- Not sure what is connected? Check both pages: Connected apps for OAuth, API keys for keys. Revoke anything you do not recognise.