| name | fireflies-multi-env-setup |
| description | Configure Fireflies.ai across dev, staging, and production with isolated API keys.
Use when setting up multi-environment deployments, managing per-env secrets,
or implementing environment-specific Fireflies configurations.
Trigger with phrases like "fireflies environments", "fireflies staging",
"fireflies dev prod", "fireflies environment setup", "fireflies config by env".
|
| allowed-tools | Read, Write, Edit, Bash(gcloud:*) |
| version | 1.11.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","fireflies","deployment"] |
| compatibility | Designed for Claude Code, also compatible with Codex and OpenClaw |
Fireflies.ai Multi-Environment Setup
Overview
Configure Fireflies.ai with isolated API keys, webhook URLs, and settings per environment. Each environment gets its own Fireflies workspace or API key to prevent cross-environment data leakage.
Environment Strategy
| Environment | API Key | Webhook URL | Settings |
|---|
| Development | FIREFLIES_API_KEY_DEV | localhost (ngrok) | Debug logs, no cache |
| Staging | FIREFLIES_API_KEY_STAGING | staging.app.com/webhooks | Prod-like, short cache |
| Production | FIREFLIES_API_KEY_PROD | app.com/webhooks | Hardened, long cache |
Instructions
Step 1: Environment Configuration Module
interface FirefliesConfig {
apiKey: string;
apiUrl: string;
webhookSecret: string;
cache: { enabled: boolean; ttlSeconds: number };
debug: boolean;
timeout: number;
maxRetries: number;
}
const configs: Record<string, Partial<FirefliesConfig>> = {
development: {
apiKey: process.env.FIREFLIES_API_KEY_DEV || "",
webhookSecret: process.. || ,
: { : , : },
: ,
: ,
: ,
},
: {
: process.. || ,
: process.. || ,
: { : , : },
: ,
: ,
: ,
},
: {
: process.. || ,
: process.. || ,
: { : , : },
: ,
: ,
: ,
},
};
(): {
(process.. === ) ;
(process.. === || process.. === ) ;
;
}
(): {
env = ();
config = configs[env];
(!config?.) {
();
}
{
: ,
...config,
} ;
}