メニュー
Build n8n workflows for GTM automation — triggers, webhook-to-enrichment-to-CRM pipelines, error handling, Clay export replacement for complex cases. Use when building n8n workflows or automating GTM processes beyond Clay.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/LeadMagic/gtm-skills --skill n8n-automationコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Execute Strategic ABM (1-to-1) for 5-15 high-value accounts — custom microsites, executive engagement, direct mail, board-level connections, custom content. Triggers on: "1-to-1 ABM", "strategic ABM", "custom ABM", "key account marketing", "named account".
Execute ABM at Scale (1-to-few) for 15-50 clustered accounts — semi-custom campaigns, industry-specific content, persona-based plays. Triggers on: "1-to-few ABM", "ABM scale", "cluster ABM", "industry ABM".
Execute Programmatic ABM (1-to-many) for 50-200+ accounts — automated personalization, scaled outbound, lookalike expansion. Triggers on: "1-to-many ABM", "programmatic ABM", "scaled ABM", "automated ABM".
SOC 職業分類に基づく
SKILL.md を表示中
| name | n8n-automation |
| description | Build n8n workflows for GTM automation — triggers, webhook-to-enrichment-to-CRM pipelines, error handling, Clay export replacement for complex cases. Use when building n8n workflows or automating GTM processes beyond Clay. |
| license | MIT |
| compatibility | Claude Code, Jesse, Codex, Hermes, Windsurf, OpenCode, Gemini CLI, Copilot, Zed, VS Code, Goose |
| metadata | {"version":"1.0.0","author":"LeadMagic","category":"automation","tags":["n8n","automation","workflows","pipelines"],"frameworks":["Jen Igartua (Go Nimbly) — RevOps automation maturity and orchestration roadmap","n8n Workflow Automation Framework","iPaaS Integration Patterns","HubSpot Academy — CRM Automation"],"related_skills":["n8n-toolkit","clay-automation","mcp-setup","api-enrichment","crm-integration"]} |
Clay handles enrichment workflows well. n8n handles everything else — custom pipelines, multi-step automation with proper error handling and retry logic, and integrations Clay does not support. Use n8n when you need a queue you can pause, error recovery that does not lose data, and integrations across tools that Clay cannot reach.
Implementation detail: Load n8n-toolkit for flow blueprints (inbound,
outbound, signals, MCP triggers), node patterns, and production deployment.
This skill covers when to use n8n; the toolkit covers how to build.
Playbook index: references/automation-playbook-index.md — all 38 automation + tool + gtm-ops playbooks.
Strategy first: references/gtm-automation-expert-playbook.md (Jen Igartua — Pattern 30) before flow build.
Map the complete pipeline:
Trigger → Enrichment → Scoring → Routing → CRM Push → Notification
Full node-level specs in n8n-toolkit → references/gtm-flow-catalog.md:
| Flow ID | Motion | Summary |
|---|---|---|
| INB-01 | Inbound | Form → enrich → score → route (<60s) |
| OUT-01 | Outbound | Batch enrich → CRM (5K in 2–4h) |
| OUT-02 | Outbound | Clay/n8n → sequencer (human gate) |
| SIG-01–04 | Signal | Funding, job change, hiring, stale opp |
| LIF-03 | Lifecycle | Reply webhook → classify → route |
| MCP-01 | Agent | Approved batch jobs via webhook |
n8n vs Clay vs MCP: See decision matrix in n8n-toolkit. Agents (MCP)
research and draft; n8n executes deterministic pipelines.
n8n workflow JSON export with node documentation, error handling rules, and maintenance guide.
Before delivering, verify:
No error handling. One failed API call breaks the entire pipeline. Every HTTP Request node needs an error branch.
Sequential processing for large batches. 10K records at 1 second each is 2.8 hours. Use Split In Batches with parallel execution.
No queue. Processing 10K records without a pause mechanism means no recovery point if something fails at record 5,000.
Credentials in workflow. Use built-in credential store, never hardcode API keys in nodes.
references/framework-notes.md — named frameworks, citation anchors, and operating assumptionstemplates/output-template.md — copy-paste deliverable structure for the userscripts/check-output.py — local checklist validator for required sections
This skill includes lightweight artifacts the agent can load on demand:references/gtm-automation-expert-playbook.md — Jen Igartua RevOps automation strategy (repo root; Pattern 30)
Use the artifacts when the user asks for an implementation-ready deliverable, a repeatable workflow, or a quality check rather than generic advice.Use this section when the user asks for a finished asset, not a high-level explanation.
Map the recommendation explicitly to the named frameworks in this skill:
A strong output from this skill includes: