CommunityTracker
Cold Email Personalisation
Grounded in Real Pain

Cold Emails That Quote Your Prospect's Actual Pain — Every Thursday

This n8n workflow matches each contact in your outreach list to a real CommunityTracker signal, then asks Claude to write a subject + body that references the specific pain point that justifies the email.

Every draft cites a real Reddit thread, LinkedIn post, or forum question — so your opener is defensible, not templated.

Thu 9AM

Weekly Batch

Claude

Sonnet-Powered

3-para

Body Format

Sheet→Send

End-to-End

How It Works

From Contact Row to Personalised Draft — Fully Automated

One sheet, one batch, one review pass. Your outbound team stops writing emails and starts closing them.

STEP 01

Read Your Outreach List

Every Thursday at 9 AM, the workflow pulls contacts from a Google Sheet where status = `cold email pending`. Columns: first_name, last_name, company_name, email, job_title, category.

STEP 02

Pull Pain Signals from CommunityTracker

For each contact's company, CT returns recent community signals (Reddit threads, LinkedIn posts, forum questions) tagged with the pain point or feature request that justifies the outreach.

STEP 03

Write Subject + Body with Claude

Claude Sonnet generates a subject line and 3-paragraph body grounded in the specific community signal. Every email cites the signal source, which means every opener is defensible.

STEP 04

Write Back & Optionally Send

Subject, body, and personalisation_source land in the Outreach sheet. Status flips to 'ready to send' — or, if Resend is wired up, the email ships automatically to the contact.

Key Features

Everything a personalised cold-email batch actually needs

Signal-grounded copy, source attribution, optional auto-send, retry logic — production-ready on day one.

Pain-Grounded Personalisation

Every email quotes a real community conversation about the prospect's problem. No 'Hope you're well' openers. No templated value props. Just specific pain → specific fix.

CT Signal + Category Lookup

The workflow tries the CT Signals API first (company-level matches). If no direct signal exists, it falls back to Category data — still relevant, never generic.

Google Sheet as Source of Truth

Your SDR controls what gets processed by editing the Status column. One sheet, one command centre — no queue management software required.

Subject + Body in Structured JSON

Claude returns subject, body, and personalisation_source separately — so your CRM, email tool, and audit log can each ingest the right field.

Weekly Batch, Minimal Overhead

One cron trigger, one pass through your contact list, every Thursday morning. Your team walks in, reviews the drafts, and ships by lunch.

Built-in Retry Logic

Every LLM call retries twice with a 5s backoff. Single contact failures don't kill the batch — the workflow logs and moves on.

Free Template

Get the Full Workflow Template

Download the n8n JSON, paste your credentials, point it at your outreach sheet, and run your first personalised batch this week.

Download the Free Workflow Template

Get the full n8n workflow template used to run this pipeline — free. Enter your email and we'll send it straight to your inbox.

No spam. Unsubscribe anytime.

Frequently asked questions

Everything you need to know about the Cold Email Personalisation workflow.

Still have questions? Contact the team

Set up in 15 minutes, runs every Thursday

Stop writing 200 emails a week. Ship 200 personalised ones instead.

Your prospects are already complaining about the problem you solve. CommunityTracker finds those conversations. This workflow turns each one into a cold email that actually belongs in their inbox.

Message Us