clay-local-dev-loop
Sets up a feedback loop for testing Clay enrichment and webhook processing on a local machine.
Install
mkdir -p .claude/skills/clay-local-dev-loop && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/8715" && unzip -o skill.zip -d .claude/skills/clay-local-dev-loop && rm skill.zipInstalls to .claude/skills/clay-local-dev-loop
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.
Set up a local development loop for building and testing Clay integrations.Key capabilities
- →Expose local servers via ngrok
- →Create local webhook receiver endpoints
- →Build test data sender scripts
- →Configure Clay HTTP API columns
- →Mock Clay responses for unit testing
How it works
This skill establishes a feedback loop by tunneling local endpoints via ngrok and configuring Clay HTTP API columns to POST enriched data back to those endpoints.
Inputs & outputs
When to use clay-local-dev-loop
- →Testing Clay webhook handlers
- →Iterating on enrichment pipelines
- →Setting up local test servers for Clay
About this skill
Clay Local Dev Loop
Overview
Clay is a web-based platform with no local runtime. Your local dev loop consists of: (1) scripts that push data into Clay via webhooks, (2) Clay enrichment running in the cloud, and (3) HTTP API columns pushing enriched data back to your local endpoint via ngrok. This skill sets up that feedback loop.
Prerequisites
- Completed
clay-install-authsetup - Node.js 18+ or Python 3.10+
- ngrok installed (
npm install -g ngrokor ngrok.com) - Clay table with webhook source configured
Instructions
Step 1: Expose Your Local Server via ngrok
Clay's HTTP API enrichment columns need a public URL to call your local endpoints.
# Start ngrok tunnel to your local server
ngrok http 3000
# Copy the HTTPS forwarding URL (e.g., https://abc123.ngrok-free.app)
Step 2: Create a Local Webhook Receiver
// src/clay-receiver.ts — receives enriched data from Clay HTTP API columns
import express from 'express';
const app = express();
app.use(express.json());
// Clay HTTP API column calls this endpoint
app.post('/api/clay/enriched', (req, res) => {
const enrichedData = req.body;
console.log('Enriched record received from Clay:', {
email: enrichedData.email,
company: enrichedData.company_name,
title: enrichedData.job_title,
enrichment_source: enrichedData._clay_source,
});
// Process the enriched data (save to DB, trigger outreach, etc.)
res.json({ status: 'received', timestamp: new Date().toISOString() });
});
// Health check for Clay HTTP API column testing
app.get('/api/health', (req, res) => {
res.json({ status: 'ok', service: 'clay-dev-receiver' });
});
app.listen(3000, () => {
console.log('Clay dev receiver listening on http://localhost:3000');
console.log('Configure Clay HTTP API column to POST to: <ngrok-url>/api/clay/enriched');
});
Step 3: Build a Test Data Sender
// src/send-test-leads.ts — push test data into Clay via webhook
const CLAY_WEBHOOK_URL = process.env.CLAY_WEBHOOK_URL!;
const testLeads = [
{ email: '[email protected]', domain: 'stripe.com', source: 'dev-test' },
{ email: '[email protected]', domain: 'notion.so', source: 'dev-test' },
{ email: '[email protected]', domain: 'figma.com', source: 'dev-test' },
];
async function sendTestBatch() {
for (const lead of testLeads) {
const res = await fetch(CLAY_WEBHOOK_URL, {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify(lead),
});
console.log(`Sent ${lead.email}: ${res.status}`);
await new Promise(r => setTimeout(r, 200)); // Respect rate limits
}
console.log('\nCheck your Clay table — enrichment columns should auto-run.');
console.log('Enriched data will POST back to your ngrok endpoint.');
}
sendTestBatch();
Step 4: Configure Clay HTTP API Column to Call You Back
In your Clay table:
- Click + Add Column > HTTP API
- Set Method: POST
- Set URL:
https://your-ngrok-url.ngrok-free.app/api/clay/enriched - Set Body (JSON): Map enriched columns using Clay's
{{column_name}}syntax:
{
"email": "{{Email}}",
"company_name": "{{Company Name}}",
"job_title": "{{Job Title}}",
"employee_count": "{{Employee Count}}",
"linkedin_url": "{{LinkedIn URL}}"
}
- Enable Auto-run on new rows
Step 5: Dev Loop Iteration Cycle
# Terminal 1: Run ngrok
ngrok http 3000
# Terminal 2: Run your local receiver
npx tsx src/clay-receiver.ts
# Terminal 3: Send test data to Clay
npx tsx src/send-test-leads.ts
# Watch Terminal 2 for enriched data flowing back from Clay
Iteration cycle:
- Modify enrichment columns or Claygent prompts in Clay UI
- Re-send test data via webhook
- Observe enriched results in your local receiver
- Adjust and repeat
Step 6: Mock Clay Responses for Unit Tests
// tests/clay-webhook.test.ts — test without hitting Clay
import { describe, it, expect } from 'vitest';
const mockClayEnrichedPayload = {
email: '[email protected]',
company_name: 'Stripe',
employee_count: 8000,
industry: 'Financial Technology',
job_title: 'VP Engineering',
linkedin_url: 'https://linkedin.com/in/janedoe',
_clay_source: 'clearbit',
_clay_enriched_at: '2026-03-22T10:00:00Z',
};
describe('Clay enriched data handler', () => {
it('processes enriched lead correctly', async () => {
const res = await fetch('http://localhost:3000/api/clay/enriched', {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify(mockClayEnrichedPayload),
});
expect(res.status).toBe(200);
const body = await res.json();
expect(body.status).toBe('received');
});
});
Error Handling
| Issue | Cause | Solution |
|---|---|---|
| ngrok tunnel drops | Free tier session expired | Restart ngrok or upgrade to paid plan |
| Clay HTTP API column returns error | ngrok URL changed | Update the URL in Clay column settings |
| No data flows back | Auto-run disabled | Enable auto-run on the HTTP API column |
| Webhook returns 422 | Bad JSON in test data | Validate payload with jq . <<< '$JSON' |
| Enrichment columns empty | No provider configured | Add enrichment provider in Clay table |
Output
- Local server receiving enriched data from Clay
- Test data pipeline: local script -> Clay webhook -> enrichment -> HTTP API -> local server
- Unit tests with mocked Clay payloads
Resources
Next Steps
Once your dev loop works, see clay-sdk-patterns for production-ready integration patterns.
When not to use it
- →Production environments requiring high availability
- →Scenarios where ngrok free tier session limits are unacceptable
Prerequisites
Limitations
- →Free tier ngrok sessions expire
- →Requires manual URL updates if ngrok tunnel changes
How it compares
Unlike manual testing, this automates the round-trip data flow between Clay's cloud enrichment and local development environments.
Compared to similar skills
clay-local-dev-loop side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| clay-local-dev-loop (this skill) | 0 | 27d | Caution | Intermediate |
| adk-engineer | 3 | 27d | Review | Advanced |
| lint-and-validate | 6 | 6mo | Review | Beginner |
| coverage | 6 | 5mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
adk-engineer
jeremylongshore
Execute software engineer specializing in creating production-ready ADK agents with best practices, code structure, testing, and deployment automation. Use when asked to "build ADK agent", "create agent code", or "engineer ADK application". Trigger with relevant phrases based on skill purpose.
lint-and-validate
davila7
Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, validate, types, static analysis.
coverage
alirezarezvani
Analyze test coverage gaps. Use when user says "test coverage", "what's not tested", "coverage gaps", "missing tests", "coverage report", or "what needs testing".
instantly-ci-integration
jeremylongshore
Configure Instantly CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating Instantly tests into your build process. Trigger with phrases like "instantly CI", "instantly GitHub Actions", "instantly automated tests", "CI instantly".
sentry-hello-world
jeremylongshore
Execute capture your first error with Sentry and verify it appears in the dashboard. Use when testing Sentry integration or verifying error capture works. Trigger with phrases like "test sentry", "sentry hello world", "verify sentry", "first sentry error".
agent-implementer-sparc-coder
ruvnet
Agent skill for implementer-sparc-coder - invoke with $agent-implementer-sparc-coder