Credentials
Securely store provider secrets and connect them to workflow nodes.
On this page
What is a credential?
A credential is an account-owned provider secret or credential bundle. NexFlow encrypts it before storage and returns only safe metadata to the UI. Workflow nodes save a credential ID, not the secret value.
Keep secrets private
Never share API keys, bot tokens, OAuth client secrets, Discord interaction tokens, or NexFlow's credential-encryption key. Do not paste provider secrets into workflow text fields or documentation.
Supported credential providers
| Provider | Required values | Used by |
|---|---|---|
| Google Gemini | Gemini API Key | AI Text Generation |
| Telegram Bot | Telegram Bot Token | Telegram Trigger and Send Telegram Message |
| Discord App | Application ID and 64-character hexadecimal Public Key | Discord Trigger and signature verification |
Note
There are no OpenAI or Anthropic credential providers in the current UI or schema.
Create and assign a credential
- Open
Credentialsand selectAdd Credential. - Enter a descriptive name and choose a provider.
- For Gemini or Telegram, enter the API key or bot token. For Discord, enter the Application ID and Public Key from Discord Developer Portal; no bot token is used.
- Select
Save credential. The secret cannot be displayed again. - Open a compatible node, choose the named credential, and save the node and workflow.
Update and delete credentials
The Credentials screen supports name search, pagination, provider badges, and relative updated times. Select a row to edit its name or replace its secret. Leave replacement fields blank to keep the stored secret. Existing secret values are never returned to the browser.
Warning
Deleting a credential cannot be undone. Nodes that still reference its ID will fail because the selected credential is unavailable; provider webhook records related by the credential may also be removed or become unusable.
When a credential is missing
A missing, deleted, wrong-provider, or other-user credential is treated as unavailable. NexFlow checks ownership and provider type when saving applicable nodes and again when executing. Reopen the node, select an owned credential of the expected provider, save, and retry with a new execution.