clay-multi-env-setup
Provides patterns to isolate Clay tables and configurations for different deployment environments.
Install
mkdir -p .claude/skills/clay-multi-env-setup && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/9205" && unzip -o skill.zip -d .claude/skills/clay-multi-env-setup && rm skill.zipInstalls to .claude/skills/clay-multi-env-setup
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Configure Clay integrations across development, staging, and productionKey capabilities
- →Create per-environment Clay tables
- →Manage environment-specific webhook URLs
- →Implement environment-aware application configuration
- →Validate Clay configurations at startup
- →Apply environment-specific safety guards
How it works
It uses separate Clay tables for each environment and environment-aware code to ensure that development, staging, and production data remain isolated.
Inputs & outputs
When to use clay-multi-env-setup
- →Setting up staging environments for Clay
- →Managing secrets across environments
- →Isolating production and dev tables
About this skill
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
// 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 = process.env.NODE_ENV || 'development';
const configs: Record<string, ClayEnvConfig> = {
development: {
webhookUrl: process.env.CLAY_WEBHOOK_URL_DEV!,
maxRowsPerBatch: 10, // Small batches to conserve credits
delayBetweenRowsMs: 500, // Slow, safe
enableCRMSync: false, // Never push dev data to real CRM
tablePrefix: '[DEV]',
},
staging: {
webhookUrl: process.env.CLAY_WEBHOOK_URL_STG!,
maxRowsPerBatch: 100,
delayBetweenRowsMs: 250,
enableCRMSync: false, // Use sandbox CRM if needed
tablePrefix: '[STG]',
},
production: {
webhookUrl: process.env.CLAY_WEBHOOK_URL!,
apiKey: process.env.CLAY_API_KEY,
maxRowsPerBatch: 1000,
delayBetweenRowsMs: 100,
enableCRMSync: true,
tablePrefix: '',
},
};
const config = configs[env];
if (!config) throw new Error(`Unknown environment: ${env}`);
if (!config.webhookUrl) throw new Error(`CLAY_WEBHOOK_URL not set for ${env}`);
return config;
}
Step 3: Environment Variable Management
# .env.development
CLAY_WEBHOOK_URL_DEV=https://app.clay.com/api/v1/webhooks/dev-webhook-id
NODE_ENV=development
# .env.staging
CLAY_WEBHOOK_URL_STG=https://app.clay.com/api/v1/webhooks/stg-webhook-id
NODE_ENV=staging
# .env.production (never in git — use secrets manager)
CLAY_WEBHOOK_URL=https://app.clay.com/api/v1/webhooks/prod-webhook-id
CLAY_API_KEY=clay_ent_production_key
NODE_ENV=production
# GitHub Actions — per-environment secrets
gh secret set CLAY_WEBHOOK_URL_DEV --body "https://app.clay.com/api/v1/webhooks/dev-id"
gh secret set CLAY_WEBHOOK_URL_STG --body "https://app.clay.com/api/v1/webhooks/stg-id"
gh secret set CLAY_WEBHOOK_URL --body "https://app.clay.com/api/v1/webhooks/prod-id"
gh secret set CLAY_API_KEY --body "clay_ent_production_key"
Step 4: Startup Validation
// src/config/validate.ts — fail fast if config is wrong
import { z } from 'zod';
const ClayConfigSchema = z.object({
webhookUrl: z.string().url().startsWith('https://'),
apiKey: z.string().startsWith('clay_ent_').optional(),
maxRowsPerBatch: z.number().positive().max(10_000),
delayBetweenRowsMs: z.number().min(0),
enableCRMSync: z.boolean(),
tablePrefix: z.string(),
});
export function validateClayConfig(config: unknown) {
const result = ClayConfigSchema.safeParse(config);
if (!result.success) {
console.error('Clay configuration invalid:', result.error.format());
process.exit(1);
}
console.log(`Clay config validated for ${process.env.NODE_ENV}`);
return result.data;
}
Step 5: Environment-Aware Safety Guards
// src/clay/guards.ts — prevent production data in dev and vice versa
function safetyCheck(env: string, rowCount: number): void {
if (env === 'development' && rowCount > 50) {
throw new Error(`Dev environment: refusing to process ${rowCount} rows (max 50). Use staging or production.`);
}
if (env === 'staging' && rowCount > 1000) {
throw new Error(`Staging environment: refusing to process ${rowCount} rows (max 1000). Use production.`);
}
}
function preventCrossEnvData(env: string, crmPushEnabled: boolean): void {
if (env !== 'production' && crmPushEnabled) {
throw new Error(`CRM sync is disabled in ${env}. Only production can push to CRM.`);
}
}
Error Handling
| Issue | Cause | Solution |
|---|---|---|
| Wrong table receives data | Dev webhook URL in production | Validate webhook URL matches environment |
| Dev data in production CRM | CRM sync enabled in dev | Guard CRM sync to production only |
| Credit waste in dev/staging | Full enrichment on test data | Set low row caps on dev/staging tables |
| Missing webhook URL at startup | Environment variable not set | Add startup validation with Zod |
Resources
Next Steps
For monitoring and observability, see clay-observability.
When not to use it
- →Single-table workflows where isolation is not required
Prerequisites
Limitations
- →Clay workspace is shared across environments
- →Requires manual table creation for each environment
How it compares
This approach enforces strict environment isolation through table prefixes and programmatic safety guards rather than relying on manual configuration.
Compared to similar skills
clay-multi-env-setup side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| clay-multi-env-setup (this skill) | 0 | 27d | Caution | Intermediate |
| gcp-cloud-run | 5 | 5mo | Review | Intermediate |
| flow-nexus-platform | 6 | 4mo | Review | Beginner |
| smithery-mcp-deployment | 8 | 8mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
gcp-cloud-run
aj-geddes
Deploy containerized applications on Google Cloud Run with automatic scaling, traffic management, and service mesh integration. Use for container-based serverless computing.
flow-nexus-platform
ruvnet
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges
smithery-mcp-deployment
CaullenOmdahl
Best practices for creating, optimizing, and deploying MCP servers to Smithery. Use this skill when:(1) Creating new MCP servers for Smithery deployment(2) Optimizing quality scores (achieving 90/100)(3) Troubleshooting deployment issues (0/0 tools, missing annotations, low scores)(4) Migrating existing MCP servers to Smithery format(5) Understanding Smithery's schema format requirements(6) Adding workflow prompts, tool annotations, or documentation resources(7) Configuring smithery.yaml and package.json for deployment
deployment-pipeline-design
wshobson
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.
vercel-deployment
davila7
Expert knowledge for deploying to Vercel with Next.js Use when: vercel, deploy, deployment, hosting, production.
netlify-deploy
openai
Deploy web projects to Netlify using the Netlify CLI (`npx netlify`). Use when the user asks to deploy, host, publish, or link a site/repo on Netlify, including preview and production deploys.