Operating Flux

Credential store

The credential store keeps API keys out of your workflow. You add a credential once, then pick it from a dropdown on any node that needs it — Flux injects it at run time and the key itself stays encrypted.

Every credential type

AI models

CredentialUsed by
OpenAI API KeyGPT Model node
Gemini API KeyGemini Model node

Speech

CredentialProvider
Google Cloud Speech-To-TextGoogle Cloud
Google Cloud Text-To-SpeechGoogle Cloud
Microsoft Azure Speech-To-TextMicrosoft Azure
Microsoft Azure Text-To-SpeechMicrosoft Azure
Eleven Labs Speech-To-TextEleven Labs
Eleven Labs Text-To-SpeechEleven Labs

Messaging

CredentialNeeds
TwilioAccount ID, Auth Token, Service ID
InfobipAPI Key, Base URL
TelegramBot token from BotFather
FacebookPage connection
InstagramAccount connection, through its page
Add once, then pick it from a dropdown wherever it is needed.

Adding one

  1. Open Credential Store from the module.
  2. Add New.
  3. Give it a name you will recognise in a dropdown later.
  4. Pick the type. The form changes to ask for what that provider needs.
  5. Fill in the fields and save.
Name credentials by what they are for, not what they are — Support WhatsApp (Twilio) beats Twilio 1 when there are six in the list and you are picking one at speed.

Your keys or Flux's

Flux's built-in keys

Leave a model node on the default and Flux uses its own OpenAI or Gemini key. Usage is billed to your project's credits wallet. Nothing to set up.

Your own key

Store it here and select it on the node. You are billed directly by the provider, on your own agreement and rate limits.

How nodes reference a credential

Through the CREDENTIAL keyword in the template language: 

{{CREDENTIAL DEFAULT}}   the built-in key
{{CREDENTIAL id}}        one of yours, by id
Do not type this expression yourself. Selecting a credential from a node's dropdown fills it in correctly. Writing it by hand causes a compilation exception, which shows up in the workflow logs.

Why it is worth the extra step

  • The key is encrypted rather than sitting in plain text in a node's configuration.
  • Rotation is one edit — update the credential and every node using it follows.
  • Templates stay shareable. Save a workflow as a template and the credential reference travels without the secret.

Rotating a key

Edit the credential and replace the value. Nodes reference it by id, so nothing on the canvas needs touching. If a key has leaked, revoke it at the provider as well — removing it from Flux stops Flux using it, not anyone else.