Loading…
How do I store credentials with Secrets?
TL;DR: Secrets are encrypted credentials stored in your Ballet workspace. Add API keys, tokens, and passwords in Secrets from the sidebar, then reference them in playbook steps and connectors. Never hardcode credentials in step code.
Who this is for
Builders managing API keys and tokens for playbooks and connectors.
How do I create a secret?
- Open Secrets from the sidebar.
- Click Add secret.
- Enter a name (e.g.
FRESHDESK_API_KEY) and the credential value. - Save. The value is encrypted and never shown again in plain text.
How do playbooks use secrets?
Reference secrets by name in Code and HTTP steps. Ask Ballet can wire secrets during Build when you describe which service needs authentication.
Example pattern in a step: read the secret by its workspace name rather than embedding the key directly.
What should I store as secrets?
- API keys and bearer tokens
- OAuth client secrets
- Webhook signing keys
- Database connection strings
Do not store secrets in step code, git repos, or shared output links.
Who can manage secrets?
Builders and Owners can create and edit secrets. Members cannot access the Secrets page.