From GTM Skills
Build n8n workflows for GTM automation — triggers, enrichment, CRM pipelines, error handling. Use when automating GTM processes beyond Clay.
How this skill is triggered — by the user, by Claude, or both
Slash command
/gtm-skills:n8n-automationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Clay handles enrichment workflows well. n8n handles everything else — custom
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:
npx claudepluginhub leadmagic/gtm-skills --plugin gtm-skillsProvides n8n workflow blueprints for GTM motions: inbound, outbound, signals, CRM sync, and lifecycle. Includes MCP integration patterns, node design, error handling, and production deployment guidance.
Generates n8n workflow configurations for business automation tasks including email processing, spreadsheet operations, and process optimization.
Ships n8n workflows end-to-end: research community templates, author with TypeScript, validate, deploy, and test via CLI. Wraps n8n-as-code for schema research and authoring.