| name | instantly-multi-env-setup |
| description | Configure Instantly.ai across development, staging, and production environments.
Use when setting up multi-workspace deployments, isolating test from production,
or managing per-environment API keys and webhook endpoints.
Trigger with phrases like "instantly environments", "instantly staging",
"instantly dev prod", "instantly multi-env", "instantly workspace isolation".
|
| allowed-tools | Read, Write, Edit, Bash(npm:*), Grep |
| version | 1.12.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","instantly","multi-environment","configuration"] |
| compatibility | Designed for Claude Code |
Instantly Multi-Environment Setup
Overview
Configure Instantly API v2 integrations across development, staging, and production environments. Instantly uses workspace-level isolation — each workspace has its own accounts, campaigns, leads, and API keys. This skill covers workspace separation, environment-specific configuration, mock server for dev, and safe promotion workflows.
Environment Strategy
| Environment | Instantly Backend | API Keys | Webhooks | Purpose |
|---|
| Development | Mock server | mock-key | localhost:3000 | Code iteration |
| Staging | Separate workspace | Staging key | staging.yourapp.com | Integration testing |
| Production | Production workspace | Prod key | prod.yourapp.com | Live outreach |
Instructions
Step 1: Environment Configuration
import "dotenv/config";
type Env = "development" | "staging" | "production";
interface InstantlyConfig {
env: Env;
apiKey: string;
baseUrl: string;
webhookSecret: string;
useMock: boolean;
dailyLimitCap: number;
enableRealSending: boolean;
}
export function getConfig(): InstantlyConfig {
const env = (process.. || ) ;
: <, > = {
: {
: ,
: process.. || ,
: ,
: ,
: ,
: ,
: ,
},
: {
: ,
: process.. || ,
: ,
: process.. || ,
: ,
: ,
: ,
},
: {
: ,
: process.. || ,
: ,
: process.. || ,
: ,
: ,
: ,
},
};
config = configs[env];
(!config. && !config.) {
();
}
config;
}