Solutions Showcase: part 6 of 7

The complete text of the site in 7 parts. Parts:

Part 1 has the contents list of every section and case study.

Case studies in full

Newsletter Performance Agent: Daily Scoring of Every Sent Issue

An n8n workflow that finds each newsletter issue after it is sent, removes machine clicks from the numbers, scores it against the account’s own baseline, and posts an AI analysis to the team.

Section: n8n Automations

Newsletter Performance Agent: Daily Scoring of Every Sent Issue

Automatically analyze newsletter performance, filter machine-generated clicks, compare each issue against historical benchmarks, and deliver AI-powered insights to the team.

Project Overview

The Newsletter Performance Agent is an automated analytics workflow built with n8n for a publisher using Kit to distribute regular email newsletters. It identifies newly sent newsletter issues, retrieves their performance statistics, adjusts click metrics for suspected machine traffic, and compares each issue against the account's historical performance.

Claude analyzes the results using the account's existing newsletter rules and returns a structured performance assessment with evidence-based recommendations. The workflow stores the complete analysis in Airtable, sends a concise summary to the team through Telegram, and records each execution for tracking.

The system is designed to support better newsletter decisions without allowing AI-generated recommendations to become active rules automatically.

Technology stack: n8n, Kit, Airtable, Claude, Telegram.

01. The Business Problem: Reliable Newsletter Performance Analysis

Newsletter performance data can be misleading. Email security gateways may automatically click links to inspect their safety, inflating reported engagement and making it difficult to understand what readers actually clicked.

Comparing issues also requires a consistent baseline. A newsletter sent to a small segment should not necessarily be judged against a full-list send, and raw engagement figures alone cannot explain whether a particular issue performed better or worse than usual.

The main challenges were:

02. The Solution: Automated Performance Scoring and AI Analysis

A single n8n workflow runs daily at 17:00 South African time and can also be started manually.

The workflow retrieves recent issue records from Airtable and broadcasts from Kit, selects the newest completed send from the last 36 hours that has not already been logged, and collects its performance and link-click data.

Code nodes calculate adjusted metrics, establish historical comparisons, attribute clicks to products and positions, and flag uncertain data. Claude then analyzes the prepared results against the active newsletter rules stored in Airtable.

The final report is saved to Airtable. A short summary is sent to the team's Telegram feedback group, each run is logged, and any proposed rules are saved as inactive records for human review.

03. Project Snapshot

ItemDetail
Platformn8n
Newsletter serviceKit
Analytics and storageAirtable
AI analysisClaude
Team notificationsTelegram
ScheduleDaily at 17:00 South African time, with manual execution available
Issue selectionNewest completed send within the previous 36 hours that has not been logged
Historical contextLast 40 logged issues in Airtable
Click analysisMachine-click adjustment and link-level attribution
OutputPerformance score, AI analysis, recommendations, and run log
Rule activationManual approval required

04. How the System Works

The workflow follows a series of stages from issue selection through performance analysis and reporting.

Step 1: Scheduled Execution and Historical Data

The workflow starts on its daily schedule or through a manual trigger. It reads the last 40 logged issues from Airtable and retrieves the available broadcasts from Kit.

Step 2: Identify the Newsletter Issue

The workflow selects the newest completed send within the previous 36 hours that has not already been recorded.

If no eligible issue exists, the workflow stops without producing a score. The Kit broadcast ID and send date are used to prevent an issue from being scored more than once.

Step 3: Retrieve Performance Statistics

The workflow retrieves the selected issue's performance statistics and link-level click report from Kit.

If link-level data is unavailable, the workflow continues with raw click figures and marks them as unverified. This uncertainty is carried into the subsequent analysis.

Step 4: Calculate and Adjust Metrics

A code node removes suspected machine-generated clicks, calculates performance against the account's historical baseline, and attributes link clicks to product campaigns and newsletter positions.

The calculation also identifies conditions that could affect interpretation, including segment sends and missing campaign tags.

Step 5: Generate the AI Analysis

The workflow retrieves active newsletter rules from Airtable and sends Claude the calculated metrics, relevant historical context, and existing rules.

Claude returns structured analysis. A subsequent code node cleans the output, limits proposed rules, and labels each recommendation as PROPOSAL, not active.

Step 6: Save and Share the Results

The completed performance report is saved as a new record in Airtable's Performance table, including statistics, score, analysis, and recommendations.

Two follow-up branches then run:

05. Workflow Architecture

The workflow separates deterministic calculations from AI interpretation. Code handles the numerical metrics and data-quality flags, while Claude explains the results and proposes potential improvements.

Airtable serves as the historical record and source of active newsletter rules. Kit provides newsletter and performance data, and Telegram provides the team's concise reporting channel.

n8n work Flow:

06. Performance Scoring and Click Analysis

Machine-Click Adjustment

Email security gateways may automatically click links in a newsletter. This can create a flat plateau across multiple links, unlike the steeper click distribution that may be associated with genuine reader activity.

The workflow detects this plateau and subtracts the suspected machine traffic to calculate an adjusted click rate.

The supplied examples demonstrate the effect:

ExampleRaw click rateAdjusted click rate
Historical issue example 17.73%2.63%
Historical issue example 26.64%2.54%
Clean issueNo specific figure suppliedLeft unchanged

These figures illustrate the adjustment logic. They do not establish an independently verified measure of human clicks; the adjusted figures remain dependent on the workflow's machine-traffic detection method.

Historical Baseline Scoring

Each issue is compared against the median open rate and click rate of past issues.

Segment sends with fewer than half the usual recipients are excluded from the baseline comparison. This helps prevent smaller, targeted sends from distorting comparisons with normal full-list newsletters.

A score of 1.00 represents performance at the established baseline.

Product and Position Attribution

The workflow groups clicks using two dimensions:

This structure supports analysis of which product campaigns attract interest and how newsletter placement relates to engagement.

Data-Quality Flags

The workflow flags conditions that may limit confidence in the analysis, including:

These flags are passed to Claude so uncertainty can be reflected in the final report rather than hidden.

07. AI Analysis and Guardrails

Claude receives the calculated performance data and active newsletter rules from Airtable. Its task is to explain the results and identify potential improvements without overstating what the data supports.

Analysis Rules

Human Approval Before Activation

The agent recommends; it does not make policy decisions.

Proposed rules are stored as inactive records in Airtable. A person must explicitly mark a proposal as Active before it can reach the newsletter writing prompts.

This keeps the workflow useful for analysis while preserving human control over changes to newsletter strategy.

08. Reporting and Data Management

The workflow creates a consistent reporting process across three connected outputs.

ComponentPurpose
Airtable Performance tableStores issue statistics, score, analysis, and recommendations.
Telegram feedback groupReceives a short summary for the team.
Execution logRecords workflow runs for operational tracking.
Airtable Newsletter Rules tableStores proposed rules as inactive until approved.

The Kit broadcast ID and send date provide the issue-level identifiers used to prevent repeat scoring. The last 40 logged issues supply recent historical context, while active rules provide the current policy context for Claude.

09. Results and Metrics

The supplied workflow description documents the automation's capabilities and includes examples of machine-click adjustment. It does not provide a measured before-and-after evaluation of time saved, newsletter engagement improvement, recommendation adoption, or revenue impact.

Demonstrated Workflow Capabilities

Example Metric Adjustment

The provided examples show raw click rates of 7.73% and 6.64% being adjusted to 2.63% and 2.54%, respectively, while a clean issue is left unchanged.

These are examples of the calculation behavior, not evidence of improved campaign performance.

Metrics to Measure Next

To evaluate business impact, a pilot should record:

10. Key Takeaways

11. Future Development

The next stage should focus on validating the scoring method and measuring its operational value.

12. Final Outcome

The Newsletter Performance Agent provides an automated process for selecting newly sent newsletter issues, calculating adjusted engagement metrics, comparing performance with historical benchmarks, and generating a concise AI analysis for the team.

By combining Kit, n8n, Airtable, Claude, and Telegram, the workflow turns newsletter reporting into a repeatable process with explicit data-quality flags, structured recommendations, and human approval controls.

The key distinction is that the system automates analysis and recommendation management; improvements in engagement, efficiency, and revenue still need to be validated through measured use.

Page · Plain text

AI Post Rewrites and CTA Rotation for a Content Team

Two n8n workflows that rewrite a social post when a reviewer ticks Redo, and add the best call-to-action to each thread from a rotating library.

Section: n8n Automations

Project Overview

This project uses two n8n workflows to improve a content team's social media review and publishing preparation process. Drafts for X, LinkedIn, and Threads are stored in Airtable, where reviewers can request revisions and manage content before approval.

The first workflow, Redo, rewrites posts when a reviewer provides feedback and checks the Redo box. Claude applies the requested changes while preserving the existing content that does not need revision.

The second workflow, CTA Auto-Insert, selects suitable calls to action from an Airtable library, arranges them within a social thread, and tracks usage to help balance CTA rotation.

Both workflows use a shared Claude sub-workflow and retrieve their writing rules, playbook, and CTA configuration from Airtable. This allows the team to adjust content standards and CTA selection without editing the main n8n workflows.

Technology stack: n8n, Airtable, Claude, X, LinkedIn, Threads.

01. The Business Problem: Revisions and CTAs Require Consistent Handling

Social media drafts often need several rounds of review before they are ready. Reviewers may request specific changes, but applying feedback across multiple platform formats can be time-consuming and may unintentionally alter content that was already correct.

Calls to action create another challenge. A team may maintain several CTAs for different topics, campaigns, and audiences. Selecting them manually can lead to repetitive links, inconsistent placement, and excessive use of the same CTA.

The main challenges were:

The objective was to automate these repetitive tasks while retaining reviewer control and clear records of each content change.

02. The Solution: Two Connected Content Workflows

Workflow 1: Redo — AI-Powered Post Rewriting

The Redo workflow checks Airtable for cards where the reviewer has selected the Redo checkbox and provided source text.

A dispatcher can start the workflow, while an hourly scheduled run catches requests that may have been missed.

The workflow retrieves the current Post Rules and Craft Playbook from Airtable and sends Claude the original source, previous draft, and reviewer feedback. Claude produces revised versions for X, LinkedIn, and Threads, following the required platform formats and account voice.

A cleanup step removes unwanted hedging language, applies image-credit rules, and prepares the output for review. n8n then writes the revised posts back to Airtable, clears the Redo checkbox, and changes the card status to Pending Review.

The original feedback remains on the card for reference.

Workflow 2: CTA Auto-Insert — Automated CTA Selection and Rotation

The CTA workflow searches Airtable every two minutes for draft cards that do not yet have a linked CTA.

It retrieves active CTA records, filters out those that have reached their usage caps, and ranks the remaining options using weight, conversions, and previous usage.

Claude receives the post, its source material, and the ranked CTA list. It selects a primary CTA and, when appropriate, a different secondary CTA based on topic relevance and each CTA's usage notes.

The workflow builds the thread with the primary CTA as the first reply and the secondary CTA at the end. It then saves the thread, links the primary CTA record to the card, and increments the usage counters.

Operational status: The Redo workflow is live. CTA Auto-Insert is switched off in the current version because running every two minutes would use approximately 21,600 executions per month.

03. Project Snapshot

ItemDetail
Platformn8n
Content databaseAirtable
AI writing and selectionClaude
Supported platformsX, LinkedIn, Threads
Main workflowsRedo and CTA Auto-Insert
Shared componentClaude writing sub-workflow
Writing configurationPost Rules and Craft Playbook in Airtable
CTA configurationAirtable CTA library
Redo triggerDispatcher plus hourly scheduled check
CTA triggerEvery two minutes in the configured workflow
Redo statusLive
CTA Auto-Insert statusSwitched off in the current version
Duplicate preventionRedo checkbox reset; CTA record linked to card

04. How Workflow 1 Works: Redo

Step 1: Identify Revision Requests

The workflow searches Airtable for cards with Redo enabled and source text available.

Requests can be started through a dispatcher, while the hourly run catches cards that were not processed by the initial trigger.

Step 2: Load Current Writing Rules

The workflow retrieves the Post Rules and Craft Playbook from a settings record in Airtable.

These settings define the account's writing style and content requirements, allowing the team to update its standards centrally.

Step 3: Send Context and Feedback to Claude

Claude receives three inputs:

The model is instructed to apply the requested changes while retaining content that the reviewer did not ask to change.

It returns three platform-specific drafts:

PlatformRequired format
XRevised X post
LinkedIn600–1,100 characters
ThreadsApproximately 420 characters, with a maximum of 500, ending on a complete sentence

Step 4: Clean and Validate the Drafts

A cleanup step removes hedging lines such as “the source does not establish…” and applies the required image-credit formatting.

The “shared by a publisher” credit line is retained only for posts containing an image and is moved to the final line.

The prompt also enforces factual accuracy, quotation requirements, and account-specific voice rules.

Step 5: Update Airtable for Review

n8n writes all three revised drafts back to the Airtable card, unticks Redo, and sets the status to Pending Review.

Clearing the checkbox prevents the same revision request from being processed repeatedly, while retaining the feedback provides an audit trail for the reviewer.

05. How Workflow 2 Works: CTA Auto-Insert

Step 1: Find Drafts Without a CTA

The workflow checks Airtable every two minutes for draft cards that do not have a CTA linked yet.

Once a CTA is linked, the card no longer matches the search criteria, preventing it from being processed again.

Step 2: Retrieve the CTA Library

The workflow reads active CTA records from Airtable. Each record can include:

This makes CTA selection configurable without changing the n8n workflow.

Step 3: Filter and Rank CTA Options

A code step removes CTAs that have reached their usage caps and scores the remaining candidates.

The ranking formula uses the following rules:

The remaining candidates are sorted from highest to lowest score.

This ranking helps balance relevance, performance, and usage frequency. Claude still considers the topic and each CTA's usage notes before making its final selection.

Step 4: Ask Claude to Select the CTAs

Claude receives the post, its source material, and the ranked CTA options.

It selects a primary CTA that fits the topic and a different secondary CTA when appropriate. When two candidates are equally suitable, the higher-ranked option is preferred.

The generated reply follows the account's voice, and CTA links must remain exactly as stored in Airtable.

Step 5: Assemble and Save the Thread

The workflow builds the thread in this order:

  1. Lead post.
  2. Primary CTA as the first reply.
  3. Remaining thread content.
  4. Secondary CTA at the end, when selected.

Each part is numbered sequentially, such as 1/, 2/, and so on.

n8n saves the completed thread to Airtable and links the primary CTA record to the card. It then increments the Times Used counter for the primary CTA and, when a secondary CTA is included, the secondary CTA as well.

06. Workflow Architecture

Redo workflow

CTA Auto-Insert workflow

Both workflows share the same Airtable content base and Claude writing sub-workflow. This reduces duplicated writing logic and helps maintain consistent content-generation behavior.

n8n Work Flow

Image: Together, the workflows demonstrate how n8n, Airtable, and Claude can automate repetitive content operations while retaining configurable rules, traceable reviewer feedback, and human approval.

07. AI Writing Rules and Content Safeguards

The Redo workflow is designed to apply feedback without introducing unsupported information or changing unrelated content.

Factual Accuracy

Quotation Handling

If the reviewer requests a quote, the publisher's own words must remain verbatim and enclosed in quotation marks. Any interpretation or analysis must be written separately after the quotation.

Voice and Formatting

The workflow follows the account's voice rules, including a list of banned words and AI-sounding phrases.

It also applies platform-specific length requirements and cleans up unwanted hedging language before writing the drafts back to Airtable.

CTA Controls

CTA Auto-Insert filters out options that have reached their usage caps, uses a ranking system to guide selection, and preserves stored CTA links exactly.

The primary and secondary CTAs are intended to be different, helping reduce repetitive calls to action within the same thread.

These controls guide the output but do not replace a human review of factual accuracy, tone, and suitability.

08. Airtable as the Content Control Center

Airtable stores the drafts, review feedback, writing settings, and CTA library used by both workflows.

ComponentPurpose
Content cardsStore source material and platform-specific drafts.
Redo checkboxSignals that a reviewer wants the drafts rewritten.
Feedback fieldCaptures the changes requested by the reviewer.
Post RulesDefines the account's content requirements.
Craft PlaybookProvides the broader writing guidance.
CTA libraryStores CTA text, links, categories, scores, usage caps, conversions, and context notes.
Linked CTA fieldIdentifies the CTA assigned to a card and prevents repeated processing.
Times Used counterTracks CTA usage for rotation.

Centralizing these settings allows the team to modify its writing guidance and CTA options without editing the underlying workflow.

09. Results and Operational Status

The project description confirms that the Redo workflow is live and the CTA workflow is configured but switched off in the current version.

No measured figures were provided for hours saved, revision turnaround, approval rates, engagement improvements, or CTA conversion uplift.

Implemented Capabilities

Important Operational Consideration

The CTA workflow is switched off because its two-minute schedule would generate approximately 21,600 executions per month. Before enabling it, the team should evaluate a less frequent schedule or event-based triggering to reduce execution consumption.

Metrics to Measure Next

10. Key Takeaways

11. Future Development

12. Final Outcome

The project establishes a shared content-automation foundation for reviewer-requested rewrites and CTA management.

The live Redo workflow applies feedback to platform-specific drafts, enforces account writing rules, and returns revised content to Airtable for review. The separate CTA Auto-Insert workflow provides a configurable method for ranking and placing CTAs while tracking usage.

Page · Plain text

AI Lead Qualification & Sales Routing Agent

Automate lead scoring, enrich company insights, and route high-intent prospects to the right sales team with AI-powered intelligence for faster decisions and improved conversion rates.

Section: Custom SaaS Platforms

Project Overview

The AI Lead Qualification & Sales Routing Agent is an automated system that evaluates inbound leads, enriches company information, and routes prospects based on their likelihood of converting. Powered by GPT-4.1 and n8n, it scores leads across budget, urgency, purchase intent, ICP match, and email quality. The system classifies leads as HOT, WARM, or COLD and directs them to the appropriate sales follow-up channel through Slack alerts, email nurturing, and Airtable CRM integration.

Image: The lead form with a sample lead and the AI results card: score, HOT category, intent, budget, urgency, ICP match, summary and recommended action.

Business Problem

Sales teams receive inbound leads from multiple sources but often lack a consistent, automated process to qualify prospects and prioritize follow-ups. This creates several challenges:

  1. Inconsistent Lead Scoring: Qualification decisions depend on who reviews the form first, resulting in missed opportunities and wasted sales representative time.
  2. Delayed Response to Hot Leads: High-intent prospects, such as those with approved budgets and urgent timelines, may wait hours before receiving a response.
  3. Manual Company Research: Sales representatives spend valuable time researching companies behind email addresses before deciding whether a lead is worth pursuing.
  4. Lack of Tiered Routing: Without automated escalation, urgent prospects and leads requiring long-term nurturing are handled without clear prioritization.
  5. Fragmented Lead History: Repeat submissions from the same email address are recorded separately, making it difficult to maintain a complete interaction history.

Proposed Solution:

The solution is an AI-powered lead qualification and sales routing system that automates the process from lead submission to sales follow-up. It validates incoming lead data, detects duplicate submissions, and enriches company information using Clearbit. GPT-4.1 evaluates each lead across five qualification dimensions: budget, urgency, purchase intent, Ideal Customer Profile (ICP) match, and email quality, generating a score from 0–100.

Based on the score, the system classifies leads into three categories: HOT (80–100), WARM (50–79), and COLD (0–49). HOT leads trigger real-time Slack notifications, WARM leads are directed to the nurturing process, and COLD leads are archived. Airtable stores the qualified lead information, while a rule-based fallback scoring mechanism maintains basic qualification functionality if the AI service becomes unavailable.

The system also provides a dashboard for monitoring lead volume, qualification categories, average scores, conversion metrics, and lead sources. Security controls, including rate limiting, request validation, and error handling, help support reliable processing.

End-to-End Workflow

Lead Intake

  • Multiple Input Channels: Accepts leads through a hosted landing page form, direct REST API requests, embedded form webhooks, and n8n-triggered workflows.
  • Input Validation: Validates required fields, including name and email, before processing begins.
  • Data Normalization: Normalizes incoming lead data to maintain consistent formatting.
  • Duplicate Detection: Identifies repeat submissions using the email address and updates existing records instead of creating duplicates.
  • Lead Source Tracking: Records the source channel for each lead to support tracking and reporting.
  • Automated Processing: Uses a Node.js Express server and n8n workflows to coordinate lead intake and subsequent processing

AI scoring engine

  • Each lead is analysed by GPT-4.1 across five dimensions: budget signals, urgency language, purchase intent, ICP (Ideal Customer Profile) match, and email quality
  • Returns a structured score from 0–100 and classifies the lead as HOT, WARM, or COLD
  • Produces a 12-field analysis object: score, category, intent, budget, urgency, ICP match, AI summary, recommended action, key signals, risk factors, estimated deal size, and sales rep assignment
  • Falls back to a rule-based keyword scoring engine if the OpenAI API is unavailable, guaranteeing zero-downtime operation

Enrichment layer

Alerting and routing

CRM integration

How the System Works

The system processes each incoming lead through a sequence of automated steps:

  1. Lead Intake: Receives lead information from website forms, API submissions, and n8n webhooks.
  2. Data Validation: Validates incoming information, normalizes fields, and checks for duplicate email addresses. Repeat submissions are added to the existing lead history.
  3. Company Enrichment: Uses Clearbit to retrieve company details, such as industry, employee count, estimated revenue, and technology stack. If enrichment is unavailable, the system uses domain-based analysis where possible.
  4. AI-Powered Qualification: GPT-4.1 evaluates the lead based on budget, urgency, purchase intent, ICP match, and email quality. It generates a score from 0–100, a classification, a summary, key signals, risks, and recommended actions.
  5. Lead Classification: Assigns each lead to a category: HOT (80–100), WARM (50–79), or COLD (0–49).
  6. Automated Routing: Sends HOT leads to Slack for immediate attention, directs WARM leads to nurturing, and archives COLD leads.
  7. CRM and Dashboard Updates: Stores lead information in Airtable and updates the dashboard with qualification scores, lead categories, volume, and other performance metrics.

Fallback handling: If GPT-4.1 is unavailable, the system uses rule-based scoring to maintain basic lead qualification. If company enrichment fails, it falls back to domain analysis where possible.

System architecture Diagram

Benefits

Dashboard overview

Lead analysis results panel

The lead form renders a live results card immediately after submission, displaying the AI score, category, intent rating, budget signal, urgency level, ICP match, and a plain-English summary of why the lead scored the way it did, along with a specific recommended next action.

Renders in the browser within ~2 seconds of form submission

Slack alert panel

When a lead is classified as HOT, a Block Kit alert fires to the configured Slack channel. The message includes: lead name and company, email, phone, all five scoring dimensions, the AI-generated summary, recommended action, estimated deal size, and assigned sales team, formatted as a structured card with section dividers.

Delivered to the #sales-alerts channel within seconds of submission

Analytics dashboard

The /dashboard page provides a live operations view of all processed leads: total volume, HOT / WARM / COLD breakdown, average score, conversion rate, leads today, leads this week, top sources by volume, and a filterable lead feed. Data is drawn directly from the in-memory store and refreshes on page load.

Accessible at /dashboard: no login required in base configuration

Project evolution & key milestones

The system scope grew significantly from the initial lead scoring proof-of-concept. Key additions and refinements delivered across the project lifecycle:

Core scoring engine

Enrichment layer

Alerting system

Data and integration

Memory layer and analytics

Security and production hardening

Data flow architecture

How data moves through each stage and at what cadence, a key reference for ops teams integrating this system into existing stacks:

StageSourceDestinationTrigger
IntakeForm / API / n8n webhookExpress backendOn submission (real-time)
EnrichmentClearbit API / domain analysisLead record (in memory)Per lead, synchronous
AI ScoringOpenAI GPT-4.1Lead record (in memory)Per lead, synchronous
CRM PushIn-memory lead recordAirtable (18 fields)Per lead, async (non-blocking)
Slack AlertIn-memory lead recordSlack channel (HOT only)Per lead, async (non-blocking)
DashboardIn-memory lead storeBrowser via /dashboardOn page load / manual refresh

Note

The current storage layer uses an in-memory Map for speed and simplicity. For production deployments requiring persistence across restarts or horizontal scaling, this is designed to be swapped for PostgreSQL, Supabase, or MongoDB, the storage service exposes a clean interface with no direct database calls in the route layer.

Lead scoring & classification

The AI scoring engine evaluates every lead across five weighted dimensions and assigns a 0–100 score. Classification thresholds are:

CategoryScore RangeRouting ActionCriteria
HOT80 – 100Immediate Slack alert + rep assignmentClear budget, urgency signal, decision-maker identified, strong ICP match
WARM50 – 79Added to nurture email sequenceSome buying signals, partial ICP match, needs further qualification
COLD0 – 49Archived, no immediate actionNo clear intent, no budget signals, poor ICP fit or generic enquiry

The five scoring dimensions GPT-4.1 evaluates are:

Technology Stack:

TechnologyPurpose
Node.js & ExpressBackend API and lead processing
OpenAI GPT-4.1AI lead scoring and qualification
n8nWorkflow automation and webhook integration
ClearbitCompany data enrichment
SlackReal-time alerts for HOT leads
AirtableLead records and CRM integration
SMTP / EmailLead nurturing and email notifications

Closing Summary

This project combines AI-powered lead scoring, company enrichment, and automated sales routing to help teams prioritize prospects, streamline follow-ups, and manage leads more efficiently through a centralized dashboard.

Page · Plain text

Telegram Thread Builder: From Dropped Screenshots to a Reviewed X Thread

An n8n workflow that turns a source text and screenshots dropped in a Telegram chat into a ready-to-review X thread, with automatic image blurring, AI writing and a card created in Airtable.

Section: n8n Automations

Telegram Thread Builder: From Dropped Screenshots to a Reviewed X Thread

Transform source text, screenshots, and team notes shared in Telegram into AI-generated X threads or single posts, with automatic image blurring and an Airtable review workflow.

Project Overview

The Telegram Thread Builder is an n8n automation designed for content teams that collect ideas, source material, and screenshots in a Telegram group. It turns these inputs into structured X threads or individual posts without requiring the team to leave Telegram during content preparation.

The workflow manages the entire process, from collecting source material and asking setup questions to blurring images, generating content with Claude, applying calls to action, and creating a review card in Airtable.

Each session is tracked in Airtable, allowing the workflow to preserve messages, images, captions, and notes throughout the process. The resulting content is marked Pending Review, giving the team an opportunity to inspect the draft and verify image blurring before approval.

Technology stack: n8n, Telegram, Airtable, Claude, image-blurring service, X content workflow.

01. The Business Problem: Turning Unstructured Ideas into Publishable Content

Content teams often collect information in chat conversations, with source text, screenshots, captions, and notes spread across multiple messages. Turning this material into a coherent X thread requires manual organization, writing, image preparation, formatting, and review.

The process creates several challenges:

The goal was to turn this unstructured collection process into a guided, repeatable workflow with safeguards and a clear human-review stage.

02. The Solution: Telegram-Based Content Generation and Review

The workflow uses Telegram as the team's conversational interface. A user starts a session, submits text and screenshots, answers a small set of configuration questions, and triggers the content-generation process.

n8n stores session materials in Airtable, retrieves the images in order, sends them through an image-blurring service, and verifies that the required blurring has succeeded. Claude then receives the source material, blurred images, captions, notes, and current writing rules from Airtable.

After generation, code nodes clean and validate the draft, enforce the requested post count, check image order, and insert calls to action from the Airtable CTA library.

The workflow creates an Airtable review card containing the draft, hook, and blurred images. Telegram then returns a summary with a preview and a link to the card.

The system also supports single-post requests by routing them through the team's existing content-intake workflow.

03. Project Snapshot

ItemDetail
Platformn8n
Input channelTelegram group chat
Content destinationX
AI writingClaude
Session and content storageAirtable
Image processingExternal image-blurring service
Workflow sizeApproximately 65 nodes
Session duration12 hours
Image capacityUp to 15 images per session
Setup timeout10 minutes before defaults are applied
Output formatsMulti-post X thread or single post
Review statusPending Review
Rule and CTA managementAirtable

04. How the System Works

The workflow follows five main stages, from collecting the source material to delivering a review-ready draft.

Step 1: Start a Session and Collect Materials

A team member replies Go to a submitted text or image. The message can also specify a format, such as thread, image, text, or long.

The bot explains how to provide the source material:

Telegram may split long text into multiple messages. The workflow merges those parts back together in the correct order.

Each image and text item is saved as a separate Airtable row linked to the session. Sessions remain open for 12 hours.

Step 2: Configure the Content

Once the user sends done, the bot asks only the questions that remain unanswered.

These can include:

The questions are numbered so the user can respond with a simple number. Typing go accepts the defaults for any remaining questions, while options supplied with the initial Go command can skip questions entirely.

The bot summarizes the selected configuration. Replying 1 starts the build.

If the user does not respond within 10 minutes, the workflow proceeds automatically using the defaults.

Step 3: Prepare and Blur Images

The workflow retrieves the session's images in their original order, up to a maximum of 15, and downloads them from Telegram.

Each image is sent to an external blurring service designed to hide page names, logos, and faces.

The workflow then checks whether every image has returned successfully blurred. If any image fails, content generation is stopped, the session is reopened, and Telegram identifies the failed images and reasons where available.

The user can correct the issue and send done again rather than restarting the entire session.

If the team explicitly chooses no blur, the workflow follows that configuration instead.

Step 4: Generate the Thread with Claude

Claude receives the source text, team captions and notes, blurred images, and current Post Rules from Airtable.

The writing instructions specify the requested number of posts, preserve the intended image order, and require the writer to use the facts contained in the supplied material, including relevant numbers and labels in screenshots.

The requested writing style includes:

These constraints help turn collected material into a coherent thread rather than a sequence of unrelated summaries.

Step 5: Validate, Add CTAs, and Deliver

After Claude generates the content, a code node cleans the output by removing unwanted links, handles, attribution credits, post numbering, and stock phrases.

It then checks the post count and verifies that each image is used exactly once and in the correct order. If the image sequence is incorrect, the workflow redistributes the images.

Calls to action are selected from the Airtable CTA library. Examples include a newsletter CTA at the end of a thread or a consulting CTA placed at post four.

The workflow creates an Airtable card containing:

Finally, the session is marked complete and Telegram sends a summary containing the post count, image count, selected CTA, a preview of the hook, and a link to the review card.

05. Workflow Architecture

The workflow contains approximately 65 nodes, organized into functional sections.

Additional branches manage configuration timeouts, cancellation, retry handling, and single-post requests.

Image: The Telegram thread session workflow in n8n: messages come in on the left and are routed by what they mean (start, image, note, cancel, done, ask, single post). The long middle row builds the thread, from blurring the images to the Claude writer, the Airtable card and the Telegram summary. The rows below handle the setup questions with the 10-minute timer, and single-post sessions.

06. Single-Post Generation

The workflow also supports individual posts that do not require a multi-post thread.

After the user sends Go, the bot asks the shorter set of configuration questions. The workflow combines the source text, captions, first image, and selected CTA into a single request.

That request is passed to the team's existing content-intake workflow, allowing single posts to reuse the established writing, image-blurring, and Airtable-card creation steps.

This keeps the single-post path aligned with the thread-generation process without duplicating the entire content pipeline.

07. Built-In Safeguards and Validation

The workflow includes several controls designed to prevent incomplete or unusable content from reaching the review stage.

Image-Blurring Validation

The team can explicitly choose not to blur images where appropriate.

AI Output Validation

Failure Recovery

These safeguards are designed to prevent incomplete drafts from being treated as ready for review. They do not replace a human check of image privacy, factual accuracy, and content quality.

08. Airtable as the Content Control Center

Airtable stores the information needed to manage sessions and control the writing process.

Airtable componentPurpose
Session recordsTrack the active content-building session.
Material rowsStore submitted text, captions, notes, and images against the session.
Post RulesProvide the current writing instructions used by Claude.
CTA librarySupply approved calls to action and placement options.
Review cardsStore the generated hook, thread, images, and review status.

Because Post Rules, CTAs, and session materials are stored in Airtable, the team can update writing preferences and content options without changing the n8n workflow itself.

09. Results and Deliverables

The supplied project description documents the workflow's design and capabilities but does not include measured production metrics such as hours saved, generation success rate, content approval rate, or publishing performance.

Delivered Capabilities

Metrics to Track Next

To quantify the business impact, a pilot should measure:

These measurements would help establish whether the automation reduces preparation time while maintaining the team's content and privacy standards.

10. Key Takeaways

The next stage should focus on measuring reliability, improving review visibility, and refining content quality.

11. Future Development

12. Final Outcome

The Telegram Thread Builder converts source text, screenshots, and team notes into structured X threads or single posts through a guided conversational workflow.

By combining n8n, Telegram, Claude, and Airtable, it automates session management, image preparation, AI writing, content validation, CTA insertion, and review-card creation.

The result is a repeatable content-preparation process that keeps source material organized, applies image-blurring safeguards, and gives the team a central place to review generated drafts before publication.

Page · Plain text

End of part 6 of 7. Continue with part 7.