AGENT SKILL

n8n-clay-integration

暂无简介

License 许可
MIT
最近更新
2026-11-10
Stars
★ 13
Forks
4

02 资源文件 1

03 SKILL.md 正文

n8n-clay-integration

Use this skill to build bidirectional data flows between Clay and n8n for automated enrichment, scoring, and CRM sync.

Integration Patterns

Pattern 1: Clay Webhook to n8n (Event-Driven)

Clay fires a webhook when a table row is created or updated. n8n receives the webhook and processes the data.

Setup:

  1. In n8n: create a Webhook node (POST), copy the URL
  2. In Clay: add an HTTP enrichment column pointing to the n8n webhook URL
  3. Map the payload fields Clay sends to n8n node inputs
  4. Add processing logic (scoring, routing, CRM push)
  5. Return a response to Clay for confirmation

Pattern 2: n8n HTTP Request to Clay API

n8n calls the Clay API to create rows, trigger enrichments, or read results.

Setup:

  1. In n8n: use HTTP Request node
  2. Base URL: https://api.clay.com/v1/
  3. Authentication: Bearer token in header
  4. Endpoints: tables, rows, enrichments
  5. Use Split in Batches for bulk operations (50 rows per batch)

Pattern 3: Scheduled Sync (n8n Polls Clay)

n8n runs on a schedule (Cron/Interval) and pulls new/updated rows from Clay.

Setup:

  1. Schedule Trigger node (Cron: every 15 min, 1 hour, or daily)
  2. HTTP Request to Clay API for rows with status = "ready"
  3. Process each row (score, validate, enrich further)
  4. Push to CRM or outbound tool
  5. Update Clay row status to "processed"

Data Transformation Nodes

Common n8n nodes for Clay data processing:

Node Purpose
Set Map Clay fields to CRM fields
IF Route based on enrichment results
Switch Multi-path routing by score tier
Code Complex transformations, deduplication
Split in Batches Process large Clay exports in groups
Merge Combine Clay data with CRM data

Execution Sequence

  1. Identify the data flow direction (Clay to n8n, n8n to Clay, or bidirectional).
  2. Select the appropriate integration pattern.
  3. Design the n8n workflow with error handling on every Clay API call.
  4. Test with 5 rows before enabling production.
  5. Add monitoring for API rate limits and failures.

Output Contract

Return:

  • n8n workflow design with node types and connections
  • Clay API endpoint and payload configuration
  • field mapping between Clay columns and downstream systems
  • error handling setup for API failures
  • monitoring setup for integration health

Anti-Patterns

  • calling Clay API without rate limiting in n8n
  • processing all rows at once without batching
  • not handling Clay API downtime in n8n workflows
  • hardcoded field names instead of dynamic mapping
  • missing retry logic on HTTP Request nodes to Clay

04 同仓库更多 Skills

LiamVisionary
LiamVisionary/hivemindos

tailscale-generation-skill-authoring

This skill should be used when the user asks to "create a Tailscale generation skill", "add a local generation skill", "document a generation endpoint", "add an image generation provider", "add a TTS provider", "add video generation", "add 3D generation", or needs guidance on where HivemindOS Tailscale or local generation providers belong in the shared skills shelf.

★ 13
LiamVisionary
LiamVisionary/hivemindos

localtts

This skill should be used when the user asks to "generate local TTS", "use local text to speech", "use remote TTS over Tailscale", "make speech audio", "add a TTS provider", "use Qwen3-TTS", or needs TTS endpoint setup through local or HivemindOS Tailscale routes.

★ 13
LiamVisionary
LiamVisionary/hivemindos

karpathy-guidelines

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

★ 13
LiamVisionary
LiamVisionary/hivemindos

comfyui-image-generation

This skill should be used when the user asks to "generate images", "generate images with ComfyUI", "use local ComfyUI", "use remote ComfyUI", "use Z-Image", "add an image generation provider", or needs image-generation endpoint setup through local or HivemindOS Tailscale routes.

★ 13
LiamVisionary
LiamVisionary/hivemindos

wrangler

Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.

★ 13
LiamVisionary
LiamVisionary/hivemindos

workers-best-practices

Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.

★ 13