Credentials
Credentials
Securely manage API keys and authentication
Credentials
Credentials securely store authentication data like API keys, OAuth tokens, and passwords.
Why Use Credentials?
- Security - Encrypted at rest, never exposed in workflows
- Reusability - Use the same credentials across multiple workflows
- Management - Update once, applies everywhere
- Separation - Keep secrets separate from workflow logic
Creating Credentials
- Go to Settings > Credentials
- Click New Credential
- Select the credential type
- Enter your authentication details
- Click Save
Credential Types
API Key
Simple key-based authentication.
| Field | Description |
|---|---|
| Name | Credential name |
| API Key | Your API key |
Basic Auth
Username and password authentication.
| Field | Description |
|---|---|
| Username | Account username |
| Password | Account password |
Bearer Token
Token-based authentication.
| Field | Description |
|---|---|
| Token | Bearer token value |
OAuth2
OAuth-based authentication for services like Google, GitHub, etc.
| Field | Description |
|---|---|
| Client ID | OAuth client ID |
| Client Secret | OAuth client secret |
| Scopes | Permissions requested |
See OAuth Setup for detailed instructions.
Using Credentials in Nodes
- Add a node that requires authentication
- In the node properties, find the Credentials field
- Select an existing credential or create new
- The node uses the credential automatically
Managing Credentials
Editing
- Go to Settings > Credentials
- Click on the credential
- Update the values
- Save changes
Deleting
- Go to Settings > Credentials
- Click the delete icon
- Confirm deletion
Note: Deleting credentials may break workflows using them.
Testing
Some credential types have a Test button to verify they work.
Security Best Practices
Access Control
- Only create credentials you need
- Use separate credentials for dev/prod
- Regularly rotate API keys
Credential Scope
- Use minimum required permissions
- Create service-specific credentials
- Don't share credentials across unrelated workflows
Monitoring
- Review credential usage periodically
- Remove unused credentials
- Monitor for unauthorized access
Credential Storage
Credentials are:
- Encrypted using AES-256
- Stored in the database
- Never logged or exposed in UI
- Decrypted only during execution