Skip to content

Credentials & connectors

Credentials are how Flero signs in to other services for you. A credential holds an OAuth sign-in, an API key, a token or a service-account key. You create it once and reuse it across workflows.

Connectors are ready-made nodes for one service (Slack, HubSpot, Outlook, Databricks, …). Each connector offers a set of operations, and often triggers, and uses a credential.

Pages in this section

Page What it covers
Managing credentials Settings → Credentials: add, edit, delete, status
OAuth flow Flero-managed sign-in, your own OAuth app, token refresh
API keys & bearer tokens Key and token credentials, and credentials for the HTTP Request node
Credential scope Personal, Workspace and Organization
Connector catalog Every connector, with setup guides for the main ones

The two questions you'll ask

"How do I let my workflow talk to ?"

  1. Check the connector catalog for a connector.
  2. Drop the connector node on the canvas. If it shows Sign in with …, click it and you are done.
  3. Otherwise, create a credential from the node's credential picker or under Settings → Credentials → Add Credential, then pick it in the node.

If there is no connector, use the HTTP Request node with a Generic / Custom HTTP credential.

"Where is the secret stored?"

In your Flero instance, encrypted. Nodes reference a credential by its ID, and Flero decrypts it only for the run that uses it. Secret values are never shown again after you save them, never returned by the API, and kept out of workflow exports and execution logs.

See Security & MFA for the wider security model.

Common pitfalls

  • Don't paste secrets into node fields. Use a credential.
  • Don't share personal credentials. If a teammate needs the same connection, ask an admin to create it at Workspace scope.
  • Rotate keys in place. Edit the credential with the new value. Workflows keep working.

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