intercom-multi-env-setup

# Intercom Multi-Environment Setup ## Overview Configure separate Intercom workspaces for development, staging, and production with environment-specific access tokens, webhook URLs, and safety guards. ## Prerequisites - Separate Intercom workspaces (or at minimum, separate apps in Developer Hub) - Secret management solution (Vault, AWS Secrets Manager, GCP Secret Manager) - CI/CD pipeline with environment variable support ## Environment Strategy | Environment | Workspace | Token Type | Data | Webhooks | |-------------|-----------|-----------|------|----------| | Development | Dev/sandbox workspace | Dev access token | Test data | localhost via ngrok | | Staging | Staging workspace | Staging token | Seed data | staging.example.com | | Production | Production workspace | Production token | Real data | api.example.com | ## Instructions ### Step 1: Environment Configuration ```typescript // src/config/intercom.ts interface IntercomEnvironmentConfig { accessToken: string; webhookSecret: string; identitySecret: string; environment: "development" | "staging" | "production"; baseUrl: string; debug: boolean; cache: { enabled: boolean; ttlSeconds: number }; rateLimit: { maxConcurrency: number }; } function loadConfig(): IntercomEnvironmentConfig { const env = (process.env.NODE_ENV || "development") as IntercomEnvironmentConfig["environment"]; const shared = { accessToken: process.env.INTERCOM_ACCESS_TOKEN!, webhookSecret: process.env.INTERCOM_WEBH...