Overview
Manage secrets securely in Conductor workflows using Cloudflare Workers secrets, environment variables, and best practices for handling sensitive data.Quick Start
Cloudflare Workers Secrets
Adding Secrets
Listing Secrets
Deleting Secrets
Environment-Specific Secrets
Development
Staging
Production
Using Secrets in Workflows
AI Provider Keys
API Authentication
Database Credentials
Secret Rotation
Zero-Downtime Rotation
Automated Rotation
Security Best Practices
1. Never Commit Secrets
2. Use Secrets, Not Vars
3. Principle of Least Privilege
4. Audit Secret Access
Secrets in CI/CD
GitHub Actions
GitLab CI
Encryption at Rest
Encrypt Sensitive Data
Multi-Tenant Secrets
Per-Tenant Keys
Key Isolation
Secrets Validation
Check Secret Format
Test Secret Validity
Emergency Procedures
Leaked Secret Response
Automated Leak Detection
Monitoring Secret Usage
Track API Calls
Alert on Unusual Usage
Testing with Secrets
Mock Secrets in Tests
Best Practices
- Never commit secrets - Use .gitignore
- Use Workers Secrets - Not environment vars in wrangler.toml
- Rotate regularly - Every 90 days minimum
- Least privilege - Minimal permissions per secret
- Audit access - Log when secrets are used
- Test rotation - Ensure zero-downtime rotation works
- Monitor usage - Track API calls and costs
- Encrypt at rest - For additional sensitive data
- Separate by environment - Different keys for dev/staging/prod
- Have incident plan - Know how to respond to leaks

