clay-multi-env-setup

# Clay Multi-Environment Setup ## Overview Configure Clay integrations across dev/staging/prod with isolated tables, separate webhook URLs, and environment-specific enrichment settings. Clay is a single workspace per account, so multi-environment isolation requires separate tables, careful naming, and environment-aware application code. ## Prerequisites - Clay account (one workspace can hold multiple tables) - Environment variable management per deployment target - Understanding of Clay table and webhook concepts ## Instructions ### Step 1: Create Per-Environment Tables In Clay, create separate tables for each environment: | Table Name | Environment | Webhook URL | Auto-Enrich | Credit Cap | |------------|-------------|-------------|-------------|------------| | `[DEV] Outbound Leads` | Development | Dev webhook | ON (small batches) | 100 rows | | `[STG] Outbound Leads` | Staging | Staging webhook | ON | 500 rows | | `Outbound Leads` | Production | Prod webhook | ON | 10,000 rows | Each table gets its own webhook URL. Copy each URL to the appropriate environment's secrets. ### Step 2: Environment Configuration ```typescript // src/config/clay.ts — environment-aware Clay configuration interface ClayEnvConfig { webhookUrl: string; apiKey?: string; // Enterprise API (if applicable) maxRowsPerBatch: number; delayBetweenRowsMs: number; enableCRMSync: boolean; tablePrefix: string; } function getClayConfig(): ClayEnvConfig { const env = proce...