Skip to content

Managing credentials

Credentials live under Settings → Credentials. You add, edit and delete them there, and you can also create one from any node's credential picker.

Settings, Credentials: the Credentials table with Name, Service, Type, Scope and Last Used columns, four demo credentials (two Personal, two Workspace), the sort button and Add Credential, and the API Keys section below.Settings, Credentials: the Credentials table with Name, Service, Type, Scope and Last Used columns, four demo credentials (two Personal, two Workspace), the sort button and Add Credential, and the API Keys section below.

The Credentials table

Column Shows
Name The name you gave the credential
Service The connector it belongs to, or Generic for the HTTP Request node
Type OAuth 2.0, API Key, Basic Auth, Service Account / JWT, SAML or Custom
Scope Personal, Workspace or Organization. See Credential scope.
Last Used When a workflow last used it, or "Never"

Use the search field to filter by name or description. The sort menu orders by Name, Date Created, Last Updated or Last Used. Each row has a menu with Edit and Delete.

Adding a credential

  1. Click Add Credential.
The Select Service dialog: a search box, Generic / Custom HTTP at the top, then the services in alphabetical order (Airtable, Algolia, Anthropic, AWS, Azure and more).The Select Service dialog: a search box, Generic / Custom HTTP at the top, then the services in alphabetical order (Airtable, Algolia, Anthropic, AWS, Azure and more).
  1. Pick the service. Search the list, or choose Generic / Custom HTTP for the HTTP Request node.
  2. Credential Name: what you call it, for example "Acme support mailbox". Node pickers show this name.
  3. Description: optional.
  4. Auth type: the chips show what the connector supports. Common ones:
    • OAuth 2.0: sign in to the service in a popup. See OAuth flow.
    • API Key: paste a key or access token. See API keys & bearer tokens.
    • Basic Auth: username and password.
    • Service Account: a Google service-account key that mints its own tokens. Offered for Google Cloud only. See Google Cloud.
  5. Scope: who can use it. Only the scopes you are allowed to create appear.
  6. Fill in the fields for the auth type.
  7. For key-based types, click Test Connection. Flero checks the values on the server before you save.
  8. Click Create Credential, or for OAuth, Connect with ….

From a node

In a connector node, the credential picker lists the credentials you can use for that connector, plus an option to create a new one. Creating one there opens the same dialog. Connectors with a Flero-managed app also show a Sign in with … button. See OAuth flow.

Editing

Choose Edit from the row menu. You can change the name and description at any time.

Secret values are encrypted and never shown again. To replace them, type new values and click Update.

For OAuth credentials, Reconnect runs the sign-in again and replaces the stored tokens in place. Workflows that use the credential keep working, because they point at the credential, not at the token.

The scope is locked after creation. See Changing scope.

Status

Node pickers show the state of each credential:

Badge Meaning
Connected The credential is ready to use.
Expires soon / Expired The access token is near or past expiry. Flero refreshes OAuth tokens automatically, so this usually clears on its own.
Reconnect required The last refresh failed. Hover for the reason, then Reconnect.

Deleting

Choose Delete from the row menu and confirm. Deletion is permanent. Nodes that still reference the credential fail when they run.

Deleting a credential in Flero does not revoke the token at the service. If a credential leaked, also revoke it in the service's own settings.

Tips & gotchas

  • Never paste secrets into node fields. Put them in a credential. The HTTP Request node does not accept inline authentication.
  • One credential per account. Two credentials for the same Slack workspace confuse your teammates. Share one at Workspace scope instead.
  • Workspace variables are not secret storage. $env values are for configuration. Keys and passwords belong in credentials.
  • Check the connector page first. Each connector catalog page lists the auth options and the permissions your admin needs to grant.

Found something out of date? This page lives in the Flero docs content set.