references/automation-playbook-index.md
<!-- AUTO-GENERATED shared reference: references/automation-playbook-index.md; run npm run regenerate. -->
# Automation Playbook Index
Master index of **every** GTM automation skill and toolkit playbook. Load `using-gtm-skills` Pattern 6 / 6b / 17 for orchestration order.
**Rule:** Process skills (`automation/`) define *when and why*. Tool skills (`tools/`, `leadmagic/`) define *how to configure*. Never skip data quality (`waterfall-enrichment`, `contact-verification`, `leadmagic-waterfall`) before routing automation.
---
## Category: `automation/` (12 playbooks)
| # | Skill | Playbook focus | Key artifacts |
|---|---|---|---|
| 1 | `clay-automation` | Clay rollout, table governance, enrichment QA | `skills/automation/clay-automation/references/framework-notes.md`, `skills/automation/clay-automation/templates/output-template.md` |
| 2 | `n8n-automation` | n8n vs Clay vs MCP decision, error handling | `skills/automation/n8n-automation/references/framework-notes.md`, `skills/automation/n8n-automation/references/gtm-flow-catalog.md` |
| 3 | `mcp-setup` | MCP agents → approved batch jobs | `skills/automation/mcp-setup/references/framework-notes.md` |
| 4 | `waterfall-enrichment` | Provider order, match rates, cost caps | `skills/automation/waterfall-enrichment/references/framework-notes.md` |
| 5 | `api-enrichment` | Direct API enrichment pipelines | `skills/automation/api-enrichment/references/framework-notes.md` |
| 6 | `crm-integration` | Sync rules, field mapping, conflict resolution | `skills/automation/crm-integration/references/framework-notes.md` |
| 7 | `ai-sdr-setup` | AI SDR guardrails, human-in-loop | `skills/automation/ai-sdr-setup/references/framework-notes.md`, `skills/outbound/cold-email-strategy/references/justin-michael-sales-borg.md` |
| 8 | `salesforce-setup` | SFDC automation objects, flows | `skills/automation/salesforce-setup/references/framework-notes.md` |
| 9 | `hubspot-setup` | HubSpot workflows, lifecycle | `skills/automation/hubspot-setup/references/framework-notes.md` |
| 10 | `attio-setup` | Attio automation patterns | `skills/automation/attio-setup/references/framework-notes.md` |
| 11 | `tool-selection-stack` | Build vs buy, stack consolidation | `skills/automation/tool-selection-stack/references/framework-notes.md` |
| 12 | `skills-lock` | Skill integrity verification | `skills/automation/skills-lock/references/framework-notes.md` |
---
## Category: `tools/` (15 playbooks — 9 toolkits + 6 sequencer platforms)
Cross-platform toolkits and platform-specific sequencer skills live in the same category. Use `sequencing-toolkit` for architecture and comparison; use a platform skill (`instantly-sequences`, `smartlead-workflows`, etc.) for deep setup. Upstream with `leadmagic-waterfall` + `clay-toolkit` before enrollment.
| # | Skill | Playbook focus | Key artifacts |
|---|---|---|---|
| 13 | `clay-toolkit` | Table blueprints, waterfall columns | `skills/tools/clay-toolkit/references/gtm-table-blueprints.md`, `skills/tools/clay-toolkit/templates/waterfall-config.md` |
| 14 | `clay-loops-toolkit` | Signal loops (funding, hiring, job change) | `skills/tools/clay-loops-toolkit/references/loop-catalog.md`, `skills/tools/clay-loops-toolkit/references/leadmagic-waterfall.md`, `skills/tools/clay-loops-toolkit/templates/loop-blueprint.md` |
| 15 | `n8n-toolkit` | Flow IDs: INB / OUT / SIG / LIF / REV / MCP | `skills/tools/n8n-toolkit/references/gtm-flow-catalog.md`, `skills/tools/n8n-toolkit/templates/workflow-blueprint.md` |
| 16 | `ai-prompts-toolkit` | Claygent / LLM prompt loops P01–P10 | `skills/tools/ai-prompts-toolkit/references/prompt-library.md`, `skills/tools/ai-prompts-toolkit/templates/prompt-spec.md` |
| 17 | `sequencing-toolkit` | Multi-channel sequence architecture (router) | `skills/tools/sequencing-toolkit/references/platform-comparison.md`, `skills/tools/sequencing-toolkit/templates/sequence-architecture.md` |
| 18 | `crm-toolkit` | CRM selection, blueprints, land-expand | `skills/tools/crm-toolkit/references/salesforce-blueprint.md`, `skills/tools/crm-toolkit/references/hubspot-blueprint.md` |
| 19 | `leadmagic-toolkit` | Find → Verify → Enrich column patterns | `skills/tools/leadmagic-toolkit/references/framework-notes.md` |
| 20 | `analytics-toolkit` | Stack by stage, event taxonomy | `skills/tools/analytics-toolkit/references/analytics-stack-by-stage.md` |
| 21 | `support-toolkit` | Headless support automation | `skills/tools/support-toolkit/references/platform-comparison.md` |
| 22 | `instantly-sequences` | Warmup pool, rotation, unified inbox | `skills/tools/instantly-sequences/references/clay-enrollment-handoff.md`, `skills/tools/instantly-sequences/references/framework-notes.md` |
| 23 | `smartlead-workflows` | Unlimited mailboxes, AI reply labels, Eric-scale infra | `skills/tools/smartlead-workflows/references/clay-enrollment-handoff.md`, `skills/tools/smartlead-workflows/references/framework-notes.md` |
| 24 | `lemlist-setup` | lemwarm, Guillaume multichannel, personalization | `skills/tools/lemlist-setup/references/clay-enrollment-handoff.md`, `skills/tools/lemlist-setup/references/framework-notes.md` |
| 25 | `salesloft-cadences` | Rhythm cadences, CRM verify gate | `skills/tools/salesloft-cadences/references/enrichment-enrollment-gate.md`, `skills/tools/salesloft-cadences/references/framework-notes.md` |
| 26 | `outreach-sequences` | Enterprise triggers, Clay→CRM→Outreach | `skills/tools/outreach-sequences/references/enrichment-enrollment-gate.md`, `skills/tools/outreach-sequences/references/framework-notes.md` |
| 27 | `hubspot-sequences` | Workflow enrollment, rep-triggered sequences | `skills/tools/hubspot-sequences/references/enrichment-enrollment-gate.md`, `skills/tools/hubspot-sequences/references/framework-notes.md` |
**Expert cross-refs:** Eric Nowoslawski (infra scale — Smartlead/Instantly) · Pat Spielmann (verify-before-send) · Guillaume Moubeche (lemlist) → `https://github.com/LeadMagic/gtm-skills/blob/main/references/gtm-experts-outbound-index.md`
---
## Category: `leadmagic/` (6 playbooks)
LeadMagic-specific enrichment, integration, and agent tooling. Default upstream provider for `clay-toolkit` and `clay-loops-toolkit`.
| # | Skill | Playbook focus | Key artifacts |
|---|---|---|---|
| 28 | `leadmagic-waterfall` | Clay waterfall: Find → Verify → Enrich | `skills/leadmagic/leadmagic-waterfall/references/waterfall-column-spec.md`, `skills/leadmagic/leadmagic-waterfall/references/framework-notes.md` |
| 29 | `leadmagic-integrations` | Clay, CRM, sequencer, n8n connections | `skills/leadmagic/leadmagic-integrations/references/integration-checklist.md`, `skills/leadmagic/leadmagic-integrations/references/framework-notes.md` |
| 30 | `leadmagic-cli` | Terminal find/validate/push pipelines | `skills/leadmagic/leadmagic-cli/references/cli-workflow-patterns.md`, `skills/leadmagic/leadmagic-cli/references/framework-notes.md` |
| 31 | `leadmagic-bulk-enrichment` | CSV batch INTAKE → VERIFY → EXPORT | `skills/leadmagic/leadmagic-bulk-enrichment/references/batch-pipeline-spec.md`, `skills/leadmagic/leadmagic-bulk-enrichment/references/framework-notes.md` |
| 32 | `leadmagic-mcp` | Agent tool guardrails, MCP→n8n batch | `skills/leadmagic/leadmagic-mcp/references/agent-tool-guardrails.md`, `skills/leadmagic/leadmagic-mcp/references/framework-notes.md` |
| 33 | `leadmagic-job-change` | Champion routing, clay-loops L03 | `skills/leadmagic/leadmagic-job-change/references/champion-loop-pattern.md`, `skills/leadmagic/leadmagic-job-change/references/framework-notes.md` |
**Expert cross-ref:** Pat Spielmann — Cold to Gold → `outbound/cold-email-copywriting/references/pat-spielmann-outbound-copy.md`
---
## Category: `gtm-ops/` (automation-adjacent, 5 playbooks)
| # | Skill | Playbook focus | Key artifacts |
|---|---|---|---|
| 34 | `revops-tech-stack` | Target architecture, consolidation | `skills/gtm-ops/revops-tech-stack/templates/stack-audit-scorecard.md`, `skills/gtm-ops/revops-tech-stack/templates/target-state-architecture.md` |
| 35 | `gtm-operations` | Operating cadence, RevOps maturity | `skills/gtm-ops/gtm-operations/templates/operating-cadence-calendar.md` |
| 36 | `gtm-spend-management` | Vendor cards, approvals | `skills/gtm-ops/gtm-spend-management/references/ramp-playbook.md`, `skills/gtm-ops/gtm-spend-management/templates/vendor-spend-register.md` |
| 37 | `gtm-tool-cost-model` | TCO per automation tool | `skills/gtm-ops/gtm-tool-cost-model/templates/tool-cost-sheet.md` |
| 38 | `campaign-governance` | UTM + campaign hierarchy for automation triggers | `skills/gtm-ops/campaign-governance/templates/utm-parameter-sheet.md` |
---
## Motion Skills (automation consumers)
These skills **consume** automation outputs — pair with toolkits above:
| Motion | Skills | Typical automation stack |
|---|---|---|
| Inbound routing | `inbound-triage`, `landing-pages` | n8n INB-01 → CRM → Slack |
| Outbound enrichment | `lead-enrichment`, `list-building` | leadmagic-waterfall + clay-toolkit |
| Reply handling | `reply-handling` | n8n LIF-03 + ai-prompts-toolkit |
| Signal plays | `funding-signal-play`, `social-intent-monitoring` | clay-loops-toolkit + leadmagic-job-change |
| Lifecycle | `mql-nurture`, `onboarding-sequences` | n8n + hubspot-sequences / sequencing-toolkit |
| Prospecting | `email-finding`, `contact-verification` | leadmagic-toolkit + leadmagic-waterfall |
| Cold email send | `cold-email-strategy`, `cold-email-copywriting` | leadmagic-waterfall → smartlead/instantly/lemlist |
| Champion / job change | `job-change-play`, `expansion-selling` | leadmagic-job-change + clay-loops L03 |
---
## Load Order by Use Case
### New automation build
1. `revops-tech-stack` — inventory
2. `tool-selection-stack` — Clay vs n8n vs MCP
3. `leadmagic-waterfall` + `contact-verification` — data quality
4. Motion toolkit (clay / n8n / prompts)
5. `crm-integration` — sync rules
6. Platform skill (`tools/instantly-sequences`, `tools/smartlead-workflows`, etc., or `leadmagic-integrations`)
7. `gtm-metrics` — measure pipeline impact
### Enrichment → sequencer (Pat Spielmann Cold to Gold)
1. `leadmagic-waterfall` OR `clay-toolkit` — Find → Verify → Enrich
2. `cold-email-copywriting` — Hook-Line-Sinker (pat-spielmann-outbound-copy.md)
3. `instantly-sequences` / `smartlead-workflows` / `lemlist-setup` — verify gate + enroll
4. `email-deliverability` — Eric Nowoslawski infra before scale
### Agency → in-house handoff
1. `hiring-agencies` — pilot scorecard
2. `clay-automation` or `n8n-automation` — document workflows
3. `skills-lock` — verify playbook integrity
---
## Cross-References
- GTM Ops index: `gtm-ops/gtm-operations/references/gtm-ops-skill-index.md`
- n8n flow catalog: `tools/n8n-toolkit/references/gtm-flow-catalog.md`
- Clay loop catalog: `tools/clay-loops-toolkit/references/loop-catalog.md`
- Clay LeadMagic waterfall: `tools/clay-loops-toolkit/references/leadmagic-waterfall.md`
- Outbound expert router: `https://github.com/LeadMagic/gtm-skills/blob/main/references/gtm-experts-outbound-index.md` (Pat Spielmann, Eric Nowoslawski, Guillaume)
- Pat Spielmann playbook: `outbound/cold-email-copywriting/references/pat-spielmann-outbound-copy.md`
- Eric Nowoslawski playbook: `outbound/cold-email-strategy/references/eric-nowoslawski-outbound.md`
- Automation strategy: `https://github.com/LeadMagic/gtm-skills/blob/main/references/gtm-automation-expert-playbook.md` (Jen Igartua — Pattern 30)
- Master router: `foundation/using-gtm-skills` → Pattern 6, 6b, 17, 30
**Total indexed playbooks: 38** (12 automation + 15 tools + 6 leadmagic + 5 gtm-ops) + 8 motion consumer skills
references/framework-notes.md
# N8N Automation — Framework Notes
Reference index for `SKILL.md`. Apply named frameworks to justify recommendations — not as decoration.
## Primary Frameworks
- **Jen Igartua (Go Nimbly) — RevOps automation maturity and orchestration roadmap**
- **n8n Workflow Automation Framework**
- **iPaaS Integration Patterns**
- **HubSpot Academy — CRM Automation**
## Deep-dive references
| File | Authority | Use when |
|---|---|---|
| `references/gtm-flow-catalog.md` | N8N Automation reference | Extended gtm flow catalog detail |
## Templates
- `templates/output-template.md` — Primary deliverable shell
## Agent routing
| Question | Action |
|---|---|
| Full process | Follow `SKILL.md` step-by-step |
| Build deliverable | Start from `templates/output-template.md` |
| Validate output | Run `scripts/check-output.py` |
Before final output, cite which framework shaped the recommendation.
references/gtm-automation-expert-playbook.md
<!-- AUTO-GENERATED shared reference: references/gtm-automation-expert-playbook.md; run npm run regenerate. -->
# GTM Automation Expert Playbook — RevOps Workflow Maturity
*Workflow design, human+machine division, and automation maturity — distinct from outbound copy/infra experts.*
**Canonical expert:** Jen Igartua (Go Nimbly) — RevOps automation roadmap, agentic GTM, data-first orchestration.
**Tool playbooks:** `https://github.com/LeadMagic/gtm-skills/blob/main/references/automation-playbook-index.md` (38 playbooks).
**Outbound experts (do not duplicate here):** Justin Michael (Sales Borg / Pattern 23), Eric Nowoslawski (infra / Pattern 15c), Pat Spielmann (enrichment copy / Pattern 17).
---
## When to load this playbook
| Trigger | Load |
|---|---|
| Design RevOps automation strategy | Pattern 30 · this playbook · `gtm-operations` |
| Clay vs n8n vs Cargo vs MCP | `tool-selection-stack` + Section below |
| Fix automation sprawl / broken CRM sync | Jen Igartua maturity model |
| AI agents in GTM stack | `ai-sdr-setup`, `mcp-setup` — with guardrails here |
| Scale from agency to in-house | Pattern 7 + `hiring-agencies` |
---
## Jen Igartua (Go Nimbly) — RevOps automation
**Role:** CEO, Go Nimbly — "OG RevOps agency"; fractional RevOps for Twilio, Zendesk, Intercom, Rippling.
**Domain:** GTM systems integration, automation roadmap, AI-ready architecture, RevOps as product team.
**Public channels**
- 💼 [LinkedIn](https://www.linkedin.com/in/jen-igartua/)
- 🔗 [gonimbly.com](https://www.gonimbly.com/)
- 🎙 [Revenue Hotline — efficient GTM engine](https://www.recapped.io/blog/revenue-hotline-how-to-build-a-more-efficient-gtm-engine-with-go-nimblys-ceo-jen-igartua)
- ▶ [GTM Innovators — RevOps & silo syndrome](https://www.gtminnovators.com/2058133/episodes)
**Key frameworks**
| Framework | Meaning | GTM action |
|---|---|---|
| **Must-have basics** | Clean data, integrations, opportunity tracking | Fix CRM hygiene before Clay/n8n |
| **Performance boosters** | MEDDPICC auto-fill, mutual action plans, routing | `crm-integration`, `revops-tech-stack` |
| **Delighters** | AI summaries, signal alerts, rep time saved | `ai-sdr-setup` with human-in-loop |
| **Data before AI** | AI fails on dirty CRM | Enrichment QA → `waterfall-enrichment` |
| **RevOps as product** | Roadmap, intake, prioritization | `gtm-operations` + RevOps Co-op PM patterns |
| **Automate backstage; careful frontstage** | Internal sync aggressive; customer-facing cautious | No auto-send without verify gate |
**Contrast matrix — automation experts**
| Expert | Owns | Does not own |
|---|---|---|
| **Jen Igartua** | RevOps maturity, stack orchestration, CRM automation roadmap | Cold email copy, domain infra |
| **Justin Michael** | Sales Borg, SEP human+machine outbound | CRM hygiene, finance approvals |
| **Eric Nowoslawski** | Deliverability, inbox scale, Clay crawl-walk-run campaigns | Enterprise RevOps architecture |
| **Pat Spielmann** | Verify-before-send, Hook-Line-Sinker copy | n8n error handling, MCP guardrails |
| **Matthew Volm** | RevOps Co-op PM, intake prioritization | Tool-specific column design |
---
## Automation maturity model (0–4)
| Level | State | Next action |
|---|---|---|
| **0 — Manual** | Spreadsheets, rep copy-paste | CRM single source of truth |
| **1 — Point tools** | Zapier sprawl, no ownership | `revops-tech-stack` audit |
| **2 — Orchestrated** | Clay or n8n with documented flows | `automation-playbook-index` load order |
| **3 — Governed** | Verify gates, error handling, runbooks | `crm-integration` conflict rules |
| **4 — Agentic** | MCP/agents → approved batch jobs only | `mcp-setup`, `skills-lock` |
**Gate:** Do not jump to Level 4 without Level 2 data quality — Justin Michael's semi-automation ceiling for enterprise applies.
---
## Human + machine division of labor
| Machine owns | Human owns |
|---|---|
| Enrichment, scoring, routing, CRM field updates | Discovery, negotiation, relationship |
| SLA timers, round-robin, dedupe | Manager coaching, deal strategy |
| Draft personalization (reviewed) | Sent emails that need judgment |
| Questionnaire pre-fill from trust center | Security exceptions, legal redlines |
**AI SDR guardrails:** `ai-sdr-setup` — no autonomous send without Pat Spielmann verify gate + Eric Nowoslawski infra check at scale.
---
## Tool selection (orchestration layer)
| Tool | Best for | Pair with |
|---|---|---|
| **Clay** | Enrichment tables, research, waterfall QA | `clay-toolkit`, `leadmagic-waterfall` |
| **n8n** | Event-driven INB/OUT/LIF flows, error retry | `tools/n8n-toolkit/gtm-flow-catalog.md` |
| **Cargo** | Persistent multi-agent routing at scale | RevOps engineer FTE; CRM-native upsert |
| **CRM native** (HubSpot/SF flows) | Lifecycle, simple routing | `hubspot-setup`, `salesforce-setup` |
**Decision rule:** If pain is **data in CRM** → evaluate Cargo/orchestration. If pain is **finding emails** → Clay + LeadMagic. If pain is **message** → outbound experts index, not this playbook.
---
## Load order (new automation build)
1. `revops-tech-stack` — inventory
2. `gtm-automation-expert-playbook.md` (this doc) — maturity + human/machine map
3. `tool-selection-stack` — build vs buy
4. `waterfall-enrichment` + `contact-verification` — data quality
5. Motion toolkit per `automation-playbook-index.md`
6. `gtm-metrics` — measure pipeline impact, not automation vanity metrics
---
## Cross-links
- `https://github.com/LeadMagic/gtm-skills/blob/main/references/automation-playbook-index.md` — 38 playbooks
- `https://github.com/LeadMagic/gtm-skills/blob/main/references/gtm-experts-outbound-index.md` — outbound expert router
- `gtm-ops/gtm-operations/references/gtm-ops-skill-index.md`
- `foundation/using-gtm-skills` — Pattern 6, 6b, 30
references/gtm-flow-catalog.md
# GTM Flow Catalog — n8n
Reusable workflow patterns for RevOps. Adapt node names to your stack; test in sandbox before production.
---
## CRM & data hygiene
| Flow | Trigger | Actions | Output |
|---|---|---|---|
| **Lead → CRM contact** | Webhook (form) | Dedupe, enrich, assign owner, Slack notify | Contact + task |
| **Stale opp alert** | Cron daily | CRM query stage+age | `#deal-desk` Slack |
| **Hygiene score** | Weekly | Missing fields report | Email to managers |
| **Lead routing** | New record | Round-robin / territory rules | Owner assigned |
---
## Outbound & enrichment
| Flow | Trigger | Actions | Output |
|---|---|---|---|
| **Clay → CRM** | Webhook | Map columns, upsert contact | Enriched record |
| **Job change signal** | LinkedIn/Clay | Create task for AE | CRM task |
| **Sequence complete** | Sequencer webhook | Update lifecycle stage | CRM field |
| **Bounce handler** | Email webhook | Mark invalid, pause sequence | Suppression flag |
---
## Advocacy & reviews
| Flow | Trigger | Actions | Output |
|---|---|---|---|
| **NPS promoter** | Survey 9–10 | Create CSM task "review ask" | CRM task + template link |
| **CSAT 5 ticket close** | Zendesk | Delay 24h → email draft | Review ask queue |
---
## Intent & inbound
| Flow | Trigger | Actions | Output |
|---|---|---|---|
| **G2 intent** | G2 webhook | Create lead, route SDR | CRM + SLA task |
| **Inbound demo** | Calendly | Enrich, Slack, CRM opp | Meeting booked |
| **Product signup** | App event | PQL score → sales notify | Slack + CRM |
---
## Finance & ops
| Flow | Trigger | Actions | Output |
|---|---|---|---|
| **Renewal 90d** | CRM date | CSM task + forecast flag | Task |
| **Tool usage alert** | API quota | Slack finance | Budget review |
---
## Implementation notes
1. **Error handling:** Error workflow → `#revops-alerts`
2. **Idempotency:** Dedupe keys on email + company domain
3. **Secrets:** n8n credentials vault — never hardcode API keys
4. **SOC2:** Log access; no PII to unsecured webhooks (`soc2-compliance`)
5. **Rate limits:** Batch CRM updates; respect API quotas
---
## Node stack (common)
| System | n8n node |
|---|---|
| HubSpot / Salesforce / Attio | Native or HTTP |
| Slack | Slack node |
| Clay | Webhook + HTTP |
| Google Sheets | Sheets (audit logs) |
| OpenAI | LLM enrichment (optional) |
Cross-ref `crm-integration` for field mapping standards.
scripts/check-output.py
#!/usr/bin/env python3
"""Basic output checklist for n8n-automation deliverables."""
from pathlib import Path
import sys
required = ["## Context", "## Framework Basis", "## Recommendation", "## Implementation Steps", "## Metrics", "## Quality Check"]
path = Path(sys.argv[1]) if len(sys.argv) > 1 else None
if not path or not path.exists():
print("Usage: check-output.py path/to/deliverable.md")
raise SystemExit(2)
text = path.read_text()
missing = [section for section in required if section not in text]
if missing:
print("Missing sections:", ", ".join(missing))
raise SystemExit(1)
print("OK: deliverable contains required sections")
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, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Jesse, Windsurf, Zed
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]
---
# n8n Automation
## Overview
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.
## Authoritative Foundations
- **Jen Igartua (Go Nimbly) — RevOps automation maturity and orchestration roadmap** — RevOps automation maturity and orchestration roadmap
- **n8n Workflow Automation Framework** — Workflow automation — HTTP nodes, webhooks, and GTM glue between tools.
- **iPaaS Integration Patterns** — Shapes deliverables for this skill — Clay handles enrichment workflows well.
- **HubSpot Academy — CRM Automation** — Lifecycle stages, object model, and workflow enrollment patterns.
## When to Use
- "Build an n8n workflow for GTM"
- "Automate enrichment beyond Clay"
- "Create a custom GTM automation pipeline"
- "Connect tools that Clay does not support"
## Step-by-Step Process
### Phase 1: Workflow Design
Map the complete pipeline:
```
Trigger → Enrichment → Scoring → Routing → CRM Push → Notification
```
### Phase 2: Implementation Patterns
- **HTTP Request nodes** for enrichment API calls
- **Error handling**: retry with exponential backoff (3 attempts, 1s/5s/25s)
- **Split In Batches node** for processing large lists
- **Queue mode**: pause and resume when something looks wrong
- **Webhook triggers** for real-time form-fill processing
### Phase 3: Common GTM Workflows
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.
## Output Format
n8n workflow JSON export with node documentation, error handling rules, and
maintenance guide.
## Quality Check
Before delivering, verify:
- [ ] All required sections are complete
- [ ] Output matches the user's stated need
- [ ] Named frameworks are cited for key recommendations
- [ ] No vague claims — every recommendation has a specific action
- [ ] Deliverable is ready for operational use, not just conceptual
## Common Pitfalls
1. **No error handling.** One failed API call breaks the entire pipeline.
Every HTTP Request node needs an error branch.
2. **Sequential processing for large batches.** 10K records at 1 second
each is 2.8 hours. Use Split In Batches with parallel execution.
3. **No queue.** Processing 10K records without a pause mechanism means
no recovery point if something fails at record 5,000.
4. **Credentials in workflow.** Use built-in credential store, never
hardcode API keys in nodes.
## Execution Artifacts
- `references/framework-notes.md` — named frameworks, citation anchors, and operating assumptions
- `references/gtm-flow-catalog.md` — Reusable GTM automation flow catalog
- `templates/output-template.md` — copy-paste deliverable structure for the user
- `scripts/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 (shared repository reference; 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.
## Implementation Depth
Use this section when the user asks for a finished asset, not a high-level explanation.
### Diagnostic Questions
1. What is the primary motion: founder-led, sales-led, product-led, partner-led, or lifecycle-led?
2. Which ICP tier is the output for: small business, mid-market, enterprise, or mixed?
3. What proof is available today: customer stories, usage data, third-party validation, screenshots, or none?
4. What system will execute the work: CRM, sequencer, warehouse, support desk, product analytics, or manual workflow?
5. What decision will the user make from this output: launch, prioritize, route, rewrite, score, coach, or measure?
### Framework Application
Map the recommendation explicitly to the named frameworks in this skill:
- n8n Workflow Automation Framework: apply only the part that directly improves the requested deliverable.
- iPaaS Integration Patterns: apply only the part that directly improves the requested deliverable.
- HubSpot Academy — CRM Automation: apply only the part that directly improves the requested deliverable.
### Deliverable Standard
A strong output from this skill includes:
- A crisp diagnosis of the current situation
- A recommended path with tradeoffs, not a generic list
- A concrete artifact the user can use immediately: table, script, checklist, scorecard, sequence, dashboard spec, or implementation plan
- A measurement plan with leading and lagging indicators
- Risks and edge cases called out before execution
### Adaptation Rules
- For small business: reduce complexity, shorten time-to-value, and prioritize owner/operator clarity.
- For mid-market: include workflow ownership, handoffs, integrations, and enablement assets.
- For enterprise: include governance, risk, procurement, stakeholder mapping, and proof requirements.
## Related Skills
- **n8n-toolkit**: Flow catalog, MCP patterns, node configs (primary implementation)
- **mcp-setup**: Agent-side MCP; pairs with MCP-01 n8n webhook
- **clay-automation**: Clay workflows for enrichment
- **api-enrichment**: API enrichment patterns
- **crm-integration**: CRM configuration for receiving n8n data
- **gtm-role-descriptions**: GTM Engineer hiring — n8n listed in JD and scorecard
templates/output-template.md
# N8N Automation — Deliverable
## Context
- Company / product:
- Owner:
- Date:
## Summary
[One paragraph: what this deliverable decides or enables]
## Core output
<!-- Structure derived from SKILL.md Output Format -->
n8n workflow JSON export with node documentation, error handling rules, and
maintenance guide.
## Frameworks Applied
- **Jen Igartua (Go Nimbly) — RevOps automation maturity and orchestration roadmap**
- **n8n Workflow Automation Framework**
- **iPaaS Integration Patterns**
- **HubSpot Academy — CRM Automation**
## Quality check
Before delivering, verify:
- [ ] All required sections are complete
- [ ] Output matches the user's stated need
- [ ] Named frameworks are cited for key recommendations
- [ ] No vague claims — every recommendation has a specific action
- [ ] Deliverable is ready for operational use, not just conceptual
## Next steps
1.
2.
3.