| name | lindy-security-basics |
| description | Implement security best practices for Lindy AI integrations.
Use when securing API keys, configuring permissions,
or implementing security controls.
Trigger with phrases like "lindy security", "secure lindy",
"lindy API key security", "lindy permissions".
|
| allowed-tools | Read, Write, Edit |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
Lindy Security Basics
Overview
Essential security practices for Lindy AI integrations.
Prerequisites
- Lindy account with admin access
- Understanding of security requirements
- Access to secret management solution
Instructions
Step 1: Secure API Key Storage
const apiKey = 'lnd_abc123...';
const apiKey = process.env.LINDY_API_KEY;
import { SecretManager } from '@google-cloud/secret-manager';
async function getApiKey(): Promise<string> {
const client = new SecretManager();
const [secret] = await client.accessSecretVersion({
name: 'projects/my-project/secrets/lindy-api-key/versions/latest',
});
return secret.payload?.data?.toString() || '';
}
Step 2: Environment-Specific Keys
LINDY_API_KEY=lnd_dev_xxx
LINDY_ENVIRONMENT=development
LINDY_API_KEY=lnd_prod_xxx
LINDY_ENVIRONMENT=production
function validateEnvironment(): void {
const env = process.env.LINDY_ENVIRONMENT;
const key = process.env.LINDY_API_KEY;
if (!key) {
throw new Error('LINDY_API_KEY not set');
}
if (env === 'production' && key.startsWith('lnd_dev_')) {
throw new Error('Development key used in production!');
}
}
Step 3: Configure Agent Permissions
import { Lindy } from '@lindy-ai/sdk';
const lindy = new Lindy({ apiKey: process.env.LINDY_API_KEY });
async function createSecureAgent() {
const agent = await lindy.agents.create({
name: 'Secure Agent',
instructions: 'Handle data securely.',
permissions: {
allowedTools: ['email', 'calendar'],
networkAccess: 'internal-only',
dataScopes: ['read:users', 'write:tickets'],
},
});
return agent;
}
Step 4: Audit Logging
async function withAuditLog<T>(
operation: string,
fn: () => Promise<T>
): Promise<T> {
const start = Date.now();
const requestId = crypto.randomUUID();
console.log(JSON.stringify({
type: 'audit',
operation,
requestId,
timestamp: new Date().toISOString(),
status: 'started',
}));
try {
const result = await fn();
console.log(JSON.stringify({
type: 'audit',
operation,
requestId,
duration: Date.now() - start,
status: 'completed',
}));
return result;
} catch (error: any) {
console.log(JSON.stringify({
type: 'audit',
operation,
requestId,
: .() - start,
: ,
: error.,
}));
error;
}
}
Security Checklist
[ ] API keys stored in environment variables or secret manager
[ ] Different keys for dev/staging/prod environments
[ ] Key validation on startup
[ ] Agent permissions configured (least privilege)
[ ] Audit logging enabled
[ ] Network access restricted where possible
[ ] Regular key rotation scheduled
[ ] Access reviewed quarterly
Output
- Secure API key storage patterns
- Environment-specific configuration
- Agent permission controls
- Audit logging implementation
Error Handling
| Risk | Mitigation | Implementation |
|---|
| Key exposure | Secret manager | Use cloud secrets |
| Wrong env | Validation | Check key prefix |
| Over-permission | Least privilege | Restrict agent tools |
| No audit | Logging | Log all operations |
Examples
Production-Ready Security
export async function initializeLindy(): Promise<Lindy> {
validateEnvironment();
const apiKey = await getApiKey();
const lindy = new Lindy({
apiKey,
timeout: 30000,
retries: 3,
});
await lindy.users.me();
console.log('Lindy initialized securely');
return lindy;
}
Resources
Next Steps
Proceed to lindy-prod-checklist for production readiness.