Credentials
Credential Storage
Section titled “Credential Storage”Credentials are stored securely using a two-tier system:
- Infisical (primary) — External secrets manager for production deployments
- Database (fallback) — Encrypted database storage when Infisical is unavailable
Credentials are never stored in flow definitions. Instead, flows reference credentials by key name.
Credential Types
Section titled “Credential Types”| Type | Description | Example |
|---|---|---|
api_key | API key in header | X-API-Key: abc123 |
bearer | Bearer token | Authorization: Bearer token |
none | No authentication | Public APIs |
Credential References
Section titled “Credential References”In flow definitions, credentials are referenced by key:
{ "authType": "api_key", "authCredentialRef": "exa_api_key", "authHeaderName": "X-API-Key"}The runtime resolves exa_api_key to the actual secret value at execution time.
Per-User Encryption
Section titled “Per-User Encryption”Files and sensitive data are encrypted per-user with AES encryption using the platform’s ENCRYPTION_KEY. Each user’s data is isolated and encrypted independently.
Adding Credentials
Section titled “Adding Credentials”- Navigate to Settings → Credentials in the dashboard
- Click Add Credential
- Enter the credential key (used in flow references) and secret value
- Select the credential type
- The credential is encrypted and stored