Technical Case Study · Reusable Template

n8n Account Enrichment & ICP Scoring

A seven-node workflow that reads new company domains from Airtable, enriches firmographic data through Apollo, assigns an AI-assisted ICP grade, and writes the result back by Airtable record ID.

Status boundary: configuration-reviewed template. Credentials, field mappings, quotas, and a manual dry-run are still required before activation. This page does not claim measured production throughput or contact-email enrichment.

Workflow Schedule→ Airtable List→ Domain Filter→ Apollo Organization→ Gemini Score→ Format→ Airtable Update

7workflow nodes in the downloadable template

0API keys, personal records, or production IDs included

4activation gates: IDs, credentials, mappings, dry-run

Problem & Scope

Automate the repetitive parts, preserve review

The template is deliberately narrow: enrich an organization and score account fit. Apollo’s organization endpoint is not represented as a source of verified decision-maker emails; people search and contact enrichment belong in a separate, consent-aware workflow.

Input

Company domain

Airtable remains the operator-facing source. Only records with Status = New and a non-empty domain proceed.

Processing

Firmographics + score

Apollo returns organization data. Gemini evaluates that data against an explicit ICP rubric and returns structured JSON.

Output

Update by record ID

The code node restores the originating Airtable record ID before fields are written back to the same record.

Architecture

One source, two APIs, one guarded write

The visual groups seven n8n nodes into five responsibilities. All examples are synthetic; no client or prospect data appears on this page.

1 · AirtableList a small batch where Status is New.

2 · n8n FilterReject empty domains before consuming API credits.

3 · ApolloEnrich organization-level firmographic data.

4 · GeminiReturn structured ICP score and short rationale.

5 · AirtablePatch the originating record only after mapping review.

Data Integrity

The record ID must survive every node

HTTP nodes replace the current item payload. A common failure is to return only the API response and silently lose the source record identifier. The template reads the original Airtable node explicitly and fails closed if the ID is missing.

const sourceRecord = $('Airtable — List New Accounts').item.json;
const recordId = sourceRecord.id;

if (!recordId) {
  throw new Error('Airtable record ID is missing');
}

return {
  recordId,
  companyName,
  industry,
  headcount,
  icpScore,
  scoreReason,
  status: 'Enriched'
};

AI fallback: malformed output becomes REVIEW, not an automatic low-quality score. This keeps parse failures visible to an operator.

Field Contract

Minimal Airtable schema

Field names in an imported n8n workflow must match the destination base exactly. The template uses this small contract.

Field	Role	Written by	Validation
Company Domain	Lookup key	Operator/import	Required and normalized without `www`
Company Name / Industry / Headcount	Firmographics	Apollo response	May be empty when no match is found
ICP Score	A, B, C, or REVIEW	Gemini + parser	Constrained to the approved values
Score Reason	Short rationale	Gemini	Human-readable and reviewed in dry-run
Status	Processing guard	n8n update	Prevents the next poll from reprocessing the record

Activation Checklist

Dry-run before switching on

The downloadable JSON contains placeholders and is intentionally inactive. These are the minimum checks before production.

Replace the Airtable base, table, and credential placeholders; confirm read and update scopes.
Create separate x-api-key header credentials for Apollo and Gemini; never paste secrets into a public workflow export.
Verify the current Apollo endpoint, Gemini model, API quotas, and billing rules in official documentation.
Run one synthetic record manually and inspect the output of every node before enabling Airtable writes.
Test no-match, rate-limit, malformed-AI-output, and missing-record-ID branches.

Technical Verification

Official references used for correction

The uploaded draft was corrected to match the documented organization endpoint and header-based Gemini authentication available at the time of this review.

Apollo Organization Enrichment API — organization-level fields and endpoint contract.
Gemini API reference — generateContent and x-goog-api-key authentication.
n8n HTTP Request node — credential handling and request configuration.

Download the reviewed template

It contains placeholder IDs and credential references only. Import it into a non-production workspace, complete the checklist, and keep it inactive until the dry-run passes.

Download n8n JSON Discuss a build