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.
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:
Machine-generated clicks: Automated link scanning can inflate click-through rates.
Inconsistent comparisons: Each newsletter needs to be evaluated against the account's own historical performance.
Limited link-level insights: Product interest and link placement need to be analyzed across campaigns.
Repeated manual reporting: Statistics, comparisons, and recommendations otherwise require separate steps.
Risk of unsupported recommendations: AI must not invent data, treat clicks as sales, or recommend rules already in force.
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
Item
Detail
Platform
n8n
Newsletter service
Kit
Analytics and storage
Airtable
AI analysis
Claude
Team notifications
Telegram
Schedule
Daily at 17:00 South African time, with manual execution available
Issue selection
Newest completed send within the previous 36 hours that has not been logged
Historical context
Last 40 logged issues in Airtable
Click analysis
Machine-click adjustment and link-level attribution
Output
Performance score, AI analysis, recommendations, and run log
Rule activation
Manual 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:
Team reporting: Sends a concise summary to the Telegram feedback group and records the workflow run.
Rule management: Stores proposed rules in Airtable's Newsletter Rules table as inactive entries.
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:
Example
Raw click rate
Adjusted click rate
Historical issue example 1
7.73%
2.63%
Historical issue example 2
6.64%
2.54%
Clean issue
No specific figure supplied
Left 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:
Campaign tag: Identifies the associated product or campaign, with the date suffix removed so results can be compared over time.
Slot tag: Identifies the position where a link appeared in the newsletter.
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:
Missing link-level click data.
Segment sends.
Links without a dated campaign tag.
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
Use adjusted clicks as the primary measure: Raw clicks must not be presented as a performance win when they may contain machine traffic.
Explain discrepancies: If raw and adjusted click rates tell different stories, the analysis must acknowledge the difference.
Do not equate clicks with revenue: Sales cannot be measured by this workflow, so product-link clicks represent interest, not confirmed sales.
Avoid duplicate recommendations: Existing active rules must not be proposed again.
Require evidence: Each proposed rule must state the evidence supporting it.
Allow no recommendation: Zero proposed rules is an acceptable outcome when the evidence is insufficient.
Keep reports concise: The analysis is limited to two paragraphs, with no more than three recommendations. The Telegram summary must remain under 600 characters.
Do not invent data: Claims must be grounded in the supplied statistics and context.
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.
Component
Purpose
Airtable Performance table
Stores issue statistics, score, analysis, and recommendations.
Telegram feedback group
Receives a short summary for the team.
Execution log
Records workflow runs for operational tracking.
Airtable Newsletter Rules table
Stores 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
Daily and manual execution.
Selection of eligible, previously unlogged newsletter issues.
Retrieval of Kit statistics and link-level click data.
Machine-click adjustment and historical baseline scoring.
Product and position-level click attribution.
Data-quality flags passed into the AI analysis.
Structured Claude output and bounded recommendations.
Airtable reporting, Telegram summaries, and execution logging.
Human approval before proposed rules become active.
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:
Time spent producing newsletter reports before and after automation.
Percentage of eligible issues successfully scored.
Frequency of missing or unverified link reports.
Agreement between adjusted click estimates and a trusted validation sample.
Frequency and quality of AI recommendations.
Percentage of proposals approved by a human.
Changes in engagement across subsequent issues, evaluated separately from the workflow's own scoring.
10. Key Takeaways
Correct the data before interpreting it: Machine-generated clicks can make newsletter performance appear stronger than it is.
Use an account-specific baseline: Comparing each issue with historical medians provides context beyond raw statistics.
Keep calculations separate from AI analysis: Deterministic code handles metrics, while Claude interprets the prepared evidence.
Carry uncertainty forward: Missing reports and questionable attribution are flagged rather than silently treated as verified.
Keep recommendations evidence-based: The agent must explain its proposals and can return no recommendations when evidence is insufficient.
Preserve human control: Proposed rules remain inactive until explicitly approved.
Make reporting repeatable: Airtable, Telegram, and execution logs provide structured records for the team.
11. Future Development
The next stage should focus on validating the scoring method and measuring its operational value.
Compare adjusted click rates with a manually reviewed sample to evaluate the machine-click detection method.
Track report completion and data availability across eligible newsletter issues.
Measure the time required to prepare reports manually versus using the workflow.
Track which recommendations are accepted, rejected, or modified by the team.
Evaluate subsequent newsletter engagement to determine whether approved recommendations are associated with meaningful improvements.
Monitor cases where link-level data is missing or campaign and slot tags are incomplete.
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.
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.
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:
Manual revision work: Reviewer feedback must be applied consistently across multiple social platforms.
Content consistency: Existing facts, approved wording, and account-specific voice rules must be preserved.
Platform-specific formatting: X, LinkedIn, and Threads require different content lengths and formatting.
CTA repetition: Frequently used CTAs can become overused if rotation is not managed.
Changing content rules: Writing standards and CTA preferences need to remain editable without modifying workflow logic.
Duplicate processing: A card should not be rewritten or assigned a CTA repeatedly after its task has been completed.
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
Item
Detail
Platform
n8n
Content database
Airtable
AI writing and selection
Claude
Supported platforms
X, LinkedIn, Threads
Main workflows
Redo and CTA Auto-Insert
Shared component
Claude writing sub-workflow
Writing configuration
Post Rules and Craft Playbook in Airtable
CTA configuration
Airtable CTA library
Redo trigger
Dispatcher plus hourly scheduled check
CTA trigger
Every two minutes in the configured workflow
Redo status
Live
CTA Auto-Insert status
Switched off in the current version
Duplicate prevention
Redo 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 original source material.
The previous draft.
The reviewer's feedback.
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:
Platform
Required format
X
Revised X post
LinkedIn
600–1,100 characters
Threads
Approximately 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:
CTA text and link.
Category.
Weight.
Times used.
Conversions.
Weekly usage cap.
A “use when” note describing the appropriate context.
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:
Each CTA's weight counts double.
Each conversion adds half a point.
Each previous use subtracts one point.
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:
Lead post.
Primary CTA as the first reply.
Remaining thread content.
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
Use facts contained in the source material or previous draft.
Never invent numbers, dates, figures, or view counts.
Return the complete revised post rather than a list of suggested changes.
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.
Component
Purpose
Content cards
Store source material and platform-specific drafts.
Redo checkbox
Signals that a reviewer wants the drafts rewritten.
Identifies the CTA assigned to a card and prevents repeated processing.
Times Used counter
Tracks 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
Reviewer-triggered AI rewriting.
Hourly recovery checks for missed Redo requests.
Platform-specific drafts for X, LinkedIn, and Threads.
Centralized writing rules and playbook settings.
Preservation of source facts and reviewer feedback.
Cleanup of unwanted hedging language.
Image-credit formatting rules.
CTA filtering and weighted ranking.
Primary and secondary CTA placement.
Airtable-based usage tracking and duplicate prevention.
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
Average time from reviewer feedback to revised drafts.
Percentage of rewritten drafts approved without another revision.
Frequency of unsupported facts or formatting corrections.
CTA processing volume and execution consumption.
CTA usage distribution and weekly-cap enforcement.
Click-through and conversion performance of approved CTAs.
10. Key Takeaways
Automate targeted revisions: Reviewers can request changes through Airtable without manually rewriting every platform version.
Preserve existing content: Claude receives the source, previous draft, and specific feedback so unrelated content can remain unchanged.
Centralize writing standards: Post Rules and the Craft Playbook are editable in Airtable.
Make CTA rotation data-driven: Ranking uses weight, conversions, and usage history, while Claude considers contextual relevance.
Prevent duplicate processing: Clearing Redo and linking a CTA give each workflow a clear completion condition.
Consider execution costs: Frequent scheduled checks should be balanced against operational needs and n8n execution limits.
Keep human review in the loop: Rewritten drafts return to Pending Review rather than being published automatically.
11. Future Development
Evaluate event-based triggering or a longer polling interval for CTA Auto-Insert.
Measure the quality and approval rate of AI-rewritten drafts.
Track CTA click-through and conversion performance to validate the ranking method.
Add monitoring for cards that remain in Redo status after repeated failures.
Review whether the scoring weights should be adjusted based on actual campaign outcomes.
Add reporting on CTA usage, weekly caps, and the distribution of primary and secondary CTAs.
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.
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:
Inconsistent Lead Scoring: Qualification decisions depend on who reviews the form first, resulting in missed opportunities and wasted sales representative time.
Delayed Response to Hot Leads: High-intent prospects, such as those with approved budgets and urgent timelines, may wait hours before receiving a response.
Manual Company Research: Sales representatives spend valuable time researching companies behind email addresses before deciding whether a lead is worth pursuing.
Lack of Tiered Routing: Without automated escalation, urgent prospects and leads requiring long-term nurturing are handled without clear prioritization.
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
Extracts the company domain from the lead’s email address and enriches it with external company intelligence
With Clearbit: pulls company name, industry, employee count, estimated revenue, tech stack, LinkedIn URL, and headquarters location
Without Clearbit: performs basic domain analysis, infers company name, identifies TLD-based region, and confirms it is a business (not free) email
Free email providers (Gmail, Yahoo, Hotmail, etc.) are skipped for enrichment and flagged accordingly
Alerting and routing
Fires Slack alerts for every HOT lead: rich Block Kit messages, including all 12 analysis fields, AI summary, estimated deal size, and assigned sales team
Routes WARM leads to a nurture queue for email sequence follow-up
Archives COLD leads automatically with no sales action triggered
All notification steps run asynchronously, so they never delay the API response back to the form or caller
CRM integration
Pushes every processed lead to Airtable with 18 mapped fields, including all analysis outputs
Designed to be swapped for HubSpot or any other CRM with a single service file change
Skips gracefully if CRM credentials are not configured: the pipeline continues without interruption
How the System Works
The system processes each incoming lead through a sequence of automated steps:
Lead Intake: Receives lead information from website forms, API submissions, and n8n webhooks.
Data Validation: Validates incoming information, normalizes fields, and checks for duplicate email addresses. Repeat submissions are added to the existing lead history.
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.
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.
Lead Classification: Assigns each lead to a category: HOT (80–100), WARM (50–79), or COLD (0–49).
Automated Routing: Sends HOT leads to Slack for immediate attention, directs WARM leads to nurturing, and archives COLD leads.
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
Hot leads reach a rep in seconds, not hours, the moment a high-intent submission arrives, a Slack alert lands in the right channel with everything the rep needs to act
Consistent, bias-free scoring: every lead is evaluated against the same GPT-4.1 criteria, removing the inconsistency of human triage
Company intelligence without manual research: reps open a Slack alert and already know the company’s industry, size, and tech stack
Zero-downtime resilience: if the AI API goes down, rule-based fallback scoring keeps the pipeline running
Unified lead history: repeat contacts are detected, and interactions are appended to the original record, preserving full context
Clean data from day one: lead sources are tracked, free email submissions are flagged, and all records share a consistent schema
Scalable without config changes: new lead sources plug in via the webhook endpoint; the pipeline handles volume automatically
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
Initial GPT-4 integration replaced with GPT-4.1 for faster, more consistent structured output
AI temperature set to 0.3 after testing: balances consistency with contextual sensitivity
Strict JSON output schema enforced via system prompt to eliminate parsing failures
Rule-based fallback engine added to ensure zero downtime when the OpenAI API is unavailable
Score validation and sanitisation layer added (score clamped 0–100; category constrained to enum)
Enrichment layer
Clearbit integration added as the primary enrichment source for business email domains
Domain-only fallback implemented: company name inference, TLD region mapping, business email detection
Free email provider list maintained to skip enrichment for Gmail, Yahoo, Hotmail, iCloud, ProtonMail, and similar
Alerting system
Slack alerts upgraded from plain text to full Block Kit format with eight labelled fields and section dividers
All notification steps moved to asynchronous execution to keep main API response time under two seconds
CRM push also made non-blocking: Airtable delays no longer affect the caller experience
Data and integration
n8n webhook route added (/api/webhook/n8n) to support visual workflow orchestration
Embedded form endpoint added (/api/webhook/form) for third-party form providers
Importable n8n workflow JSON file shipped with the project for instant setup
Airtable CRM integration added with 18 mapped fields; designed as a swappable service module
Memory layer and analytics
Repeat lead detection added: duplicate email submissions update the existing record rather than creating a new one
Interaction history log added to each lead record for full contact context
Analytics aggregation engine built into the storage service: computes category counts, average score, conversion rate, score distribution, top sources, and temporal metrics on demand
Dashboard feed endpoint added with configurable pagination and category/source filters
Security and production hardening
Helmet HTTP security headers added across all routes
Rate limiter set to 100 requests per 15 minutes per IP on all /api/* routes
Request body size capped at 1 MB to prevent oversized payload attacks
Explicit timeouts set on all external API calls (OpenAI: 30s · Clearbit: 5s · Airtable: 10s · Slack: 5s)
Global error handler middleware added to prevent stack traces leaking to API callers
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:
Stage
Source
Destination
Trigger
Intake
Form / API / n8n webhook
Express backend
On submission (real-time)
Enrichment
Clearbit API / domain analysis
Lead record (in memory)
Per lead, synchronous
AI Scoring
OpenAI GPT-4.1
Lead record (in memory)
Per lead, synchronous
CRM Push
In-memory lead record
Airtable (18 fields)
Per lead, async (non-blocking)
Slack Alert
In-memory lead record
Slack channel (HOT only)
Per lead, async (non-blocking)
Dashboard
In-memory lead store
Browser via /dashboard
On 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:
Category
Score Range
Routing Action
Criteria
HOT
80 – 100
Immediate Slack alert + rep assignment
Clear budget, urgency signal, decision-maker identified, strong ICP match
WARM
50 – 79
Added to nurture email sequence
Some buying signals, partial ICP match, needs further qualification
COLD
0 – 49
Archived, no immediate action
No clear intent, no budget signals, poor ICP fit or generic enquiry
The five scoring dimensions GPT-4.1 evaluates are:
Budget: explicit dollar amounts, investment language, company size inference
Intent: active buying vs. passive browsing language (“want to buy” vs. “just exploring”)
ICP Match: B2B vs. B2C, company size (50–500 employees = Excellent), industry alignment
Email Quality: business domain vs. free provider (Gmail, Yahoo, Hotmail, etc.)
Technology Stack:
Technology
Purpose
Node.js & Express
Backend API and lead processing
OpenAI GPT-4.1
AI lead scoring and qualification
n8n
Workflow automation and webhook integration
Clearbit
Company data enrichment
Slack
Real-time alerts for HOT leads
Airtable
Lead records and CRM integration
SMTP / Email
Lead 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.
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.
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:
Scattered source material: Text, screenshots, and captions may arrive in separate Telegram messages.
Manual content creation: Writers must organize the material into a logical sequence and maintain a consistent voice.
Image privacy: Screenshots may contain page names, logos, or faces that need to be blurred before use.
Inconsistent formatting: Threads must follow an agreed post count, image order, writing style, and call-to-action placement.
Lost context: Without session tracking, it becomes difficult to preserve all the material collected during a conversation.
Review overhead: Drafts, images, and approvals need to be organized in a central location.
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
Item
Detail
Platform
n8n
Input channel
Telegram group chat
Content destination
X
AI writing
Claude
Session and content storage
Airtable
Image processing
External image-blurring service
Workflow size
Approximately 65 nodes
Session duration
12 hours
Image capacity
Up to 15 images per session
Setup timeout
10 minutes before defaults are applied
Output formats
Multi-post X thread or single post
Review status
Pending Review
Rule and CTA management
Airtable
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:
Send screenshots in the required order.
Add captions beneath images when a particular caption should become the text for that post.
Send additional source text or notes.
Send done when the material is ready.
Send cancel to stop the session.
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:
How many posts should the thread contain?
Which call to action should be used, and where should it appear?
Should the images be blurred?
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:
A strong, extended opening hook.
Follow-up posts that each contribute one step to the story.
An analytical post near the end.
Consistent use of the agreed content format.
No naming of pages, people, or brands shown in the source material.
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:
The opening hook.
The complete thread or post.
The selected CTA.
The associated blurred images.
The status Pending Review.
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.
Input and session management: Interprets Telegram messages and manages session state.
Material collection: Stores text, captions, notes, and images in Airtable.
Configuration: Resolves post count, CTA placement, and image-blurring preferences.
Image processing: Downloads, blurs, and validates screenshots.
AI writing: Sends source material and current writing rules to Claude.
Content validation: Cleans the output, checks post count, and verifies image usage.
Delivery and review: Creates the Airtable card, attaches images, and returns the card link through Telegram.
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
Images are processed before they are attached to the generated content.
The workflow checks the returned images for successful blurring.
If a required blur operation fails, thread generation stops.
The session is reopened so the team can retry after addressing the issue.
The team can explicitly choose not to blur images where appropriate.
AI Output Validation
The generated content is cleaned before delivery.
The final post count is checked against the agreed configuration.
Images must be used exactly once and in the correct order.
If the writer returns unusable output, no review card is created.
Failure Recovery
When blurring or writing fails, the session is reopened and the team is notified through Telegram.
The user can retry using done without starting a new session.
Image-upload failures are reported in the final summary.
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 component
Purpose
Session records
Track the active content-building session.
Material rows
Store submitted text, captions, notes, and images against the session.
Post Rules
Provide the current writing instructions used by Claude.
CTA library
Supply approved calls to action and placement options.
Review cards
Store 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
Telegram-based session creation and content collection.
Support for text, screenshots, captions, and notes.
Automatic merging of split Telegram text messages.
Session persistence through Airtable.
Configuration questions with default values and timeout handling.
Image blurring and validation before content generation.
Claude-powered thread and single-post generation.
Automated post-count and image-order checks.
CTA selection from an Airtable library.
Airtable review-card creation with Pending Review status.
Telegram delivery of a summary and review link.
Retry and recovery paths for several processing failures.
Metrics to Track Next
To quantify the business impact, a pilot should measure:
Average time required to produce a thread manually versus using the workflow.
Number of sessions and drafts generated per week.
Percentage of sessions completed successfully.
Image-blurring success and retry rates.
Percentage of generated drafts approved without major edits.
Average number of content revisions per draft.
Time from initial Telegram submission to review-card creation.
These measurements would help establish whether the automation reduces preparation time while maintaining the team's content and privacy standards.
10. Key Takeaways
Use chat as the intake interface: Teams can submit ideas and screenshots where they already collaborate.
Preserve session context: Saving every item in Airtable reduces the risk of losing source material across multiple messages.
Automate repetitive preparation: Image handling, content formatting, CTA insertion, and card creation happen within the same workflow.
Validate before delivery: Image checks and output validation reduce the risk of incomplete drafts reaching review.
Keep writing rules configurable: Airtable allows the team to update Post Rules and CTAs without editing the automation.
Retain human review: The workflow prepares content for approval instead of automatically publishing it to X.
The next stage should focus on measuring reliability, improving review visibility, and refining content quality.
11. Future Development
Track generation success, retry rates, and average processing time.
Record review outcomes and common reasons for content revisions.
Add clear audit information for image-blurring failures and content-validation failures.
Improve visibility into session expiration and abandoned sessions.
Evaluate whether generated threads consistently follow the team's style and factual requirements.
Consider adding a publishing integration only if the team wants to extend the current review-first process.
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.
How Harrington & Cole LLP replaced four disconnected tools with one Airtable workspace, cutting matter-intake time by 68% and automating 1,200+ status touchpoints a month.
Harrington & Cole LLP is a 60-person law firm headquartered in Halifax, Nova Scotia, with three practice groups and a docket of roughly 230 active matters at any given time. By early 2025 the firm was running case intake, conflict checks, scheduling and time capture across four disconnected systems: a legacy practice-management tool, shared Excel files on a network drive, Outlook calendars, and a paper intake form. Status updates lived in attorneys’ heads and email threads.
Over an 11-week engagement we replaced this patchwork with a single Airtable workspace, purpose-built tables, role-specific Interfaces for attorneys and paralegals, and an automation layer that handles the firm’s repetitive coordination work. The implementation was delivered without disruption to billable work and went live with all 60 users on the same day.
Outcomes after 90 days in production
68%: Faster matter intake
1,284: Automated touchpoints / mo.
0: Missed SOL deadlines
$41K: Recovered WIP in Q1
At a glance
Before: 4 systems, ~6 hrs to open a new matter, manual conflict checks, scheduling done by email.
After: 1 Airtable workspace, ~2 hrs to open a matter end-to-end, conflict-check workflow runs in < 60 seconds, hearing prep tasks auto-spawn 14 days out.
Background
The client and the problem
About the firm
Harrington & Cole LLP serves regional commercial clients across Atlantic Canada. Three practice groups (litigation, corporate / transactional, and employment) share a managing partner, a central paralegal pool, and a single billing department. The firm had grown roughly 40% in headcount over five years; its tooling had not kept up.
The pain points that triggered the project
Matter intake took up to six hours. A new lead required duplicate data entry across four systems, with manual conflict checks against an Excel register that one paralegal owned.
Status was invisible. Partners had no reliable view of which matters were stuck in discovery, which were close to trial, or which had open balances over 60 days.
Deadline slips were happening. Two near-misses on statute-of-limitations dates in 2024 prompted the managing partner to require automated alerting as a non-negotiable.
Time capture was lossy. Attorneys logged time at week-end from memory; the firm estimated 6–9% of billable hours were being lost.
Reporting was a fire drill. The monthly management report took the office manager roughly two days to assemble from exports.
Why Airtable
The firm evaluated three traditional practice-management products and Airtable. The decision came down to three factors: (1) the firm wanted a system its own staff could change without a vendor ticket, (2) the data model needed to fit the firm’s terminology rather than force the firm into a vendor’s, and (3) the integration story with Slack, Outlook and DocuSign needed to be straightforward. Airtable’s linked-record model, Interface Designer, and native automation framework made it the right fit.
Approach
How the implementation was run
We delivered the implementation in four phases over eleven weeks. A core working group made up of the managing partner, two senior associates (one per practice area), the office manager, and a paralegal lead met twice a week to validate the data model, review prototypes, and sign off on go-live readiness.
Phase
Weeks
What we did
Output
1. Discovery
1–2
Shadowed intake, conflict-check and billing workflows. Mapped 14 existing data sources. Interviewed 11 attorneys and staff.
Process map, data dictionary, ranked pain-point list.
2. Data model & schema
3–4
Designed 10-table relational schema. Built linked records for Cases ↔ Clients ↔ Hearings ↔ Documents ↔ Tasks ↔ Time entries.
Live Airtable base with sample data; ER diagram.
3. Interfaces & automations
5–8
Built the Attorney Dashboard, the Paralegal Workbench and the Partner Reporting interfaces. Designed and tested 8 automations.
3 production interfaces; automation library.
4. Migration, training, go-live
9–11
Migrated 1,847 historical matters, trained all 60 users in three cohorts, ran a 5-day parallel-run before cutover.
Single-day cutover with zero data loss.
Guiding principles
Match the firm’s vocabulary. Field names mirror how attorneys actually speak (e.g. matter, not project; SOL date, not deadline).
One source of truth. Every piece of data lives in exactly one table; everywhere else uses a linked record, lookup or rollup.
Make the right thing the easy thing. Intake, conflict checks, and time capture were redesigned so the compliant workflow is the fastest workflow.
Internal ownership. The office manager and one senior paralegal were trained as base administrators; they own day-to-day changes.
What Was Built
The Cases table: the heart of the workspace
Every matter the firm works on is a record in the Cases table. From here, attorneys can see the entire docket grouped by practice area, filtered to their own matters, or sliced by stage. The grid below shows the production view used by senior associates each morning to triage their day.
Image: Figure 1: The Cases grid view, grouped by practice area. Coloured stage chips give partners an at-a-glance read on where every matter sits. The footer rolls up open balances and average days-open across the visible records.
Highlights of this view
Grouping by practice area mirrors how the managing partner thinks about workload distribution.
Stage is a single-select with a controlled vocabulary (Intake → Pleadings → Discovery → Negotiation → Trial Prep → Closed). It drives both the kanban view and three automations.
Lead Attorney links to the Staff table, so renaming or reassigning happens in one place.
Open Balance at the bottom is a rollup from the Time entries table, no manual reconciliation needed.
Two more views the firm uses every day
Kanban by stage is how partners review pipeline in their Monday morning meeting. Dragging a card moves the matter through the lifecycle and triggers the corresponding automation chain.
Image: Figure 2: Kanban view of the Cases table, grouped by stage. Card colour and the avatar in the corner make ownership obvious even on a wall display.
The expanded matter record
Clicking any row opens a full-detail view of the matter. This is the single screen attorneys live in when they’re working a case. It consolidates parties, deadlines, team, financials and notes. WIP and Open Balance are rollups from the linked Time entries table; the Statute of Limitations warning is a formula that turns red automatically inside 90 days.
Image: Figure 3: The expanded record view for matter CASE-2024-0142. Rollups, formulas and linked records mean every number on this screen is computed live from the underlying tables: nothing is manually maintained.
The Data Model
Ten tables, one source of truth
The base is built around Cases as the central entity. Everything else (clients, hearings, documents, tasks, time, communications) links to a case. This single design decision is what makes the rollups, formulas and automations possible.
Image: Figure 4: The 10-table schema. Lines indicate linked-record relationships. Cases is the hub; Documents, Tasks, Time entries and Communications all link to a case.
Field-level decisions worth calling out
Stage is a single-select with synced colour. Changes here trigger 3 different automations.
SOL date is paired with a formula days_until_sol; the alert automation reads the formula field, so all date logic lives in one place.
Conflict_clear on Clients is a checkbox controlled by the conflict-check automation, an intake matter is blocked from advancing until this is true.
Time entries rolls up into Cases as WIP and Open Balance, so billing reports build themselves.
Communications is populated by the Gmail and Outlook integrations, every email about a matter is logged automatically.
Interfaces
Three role-based interfaces, one underlying base
Different people in the firm need different things from the same data. We built three Interfaces on top of the base, each tailored to a role. All three read from and write to the same tables. There is no duplication.
The Attorney Dashboard
This is the screen attorneys open when they sit down at their desk. It surfaces the four KPIs that matter to them, the next 30 days of hearings, and their personal task list, all filtered to their own user automatically.
Image: Figure 5: The Attorney Dashboard interface, scoped to the logged-in user. KPI cards on top; upcoming hearings and personal tasks below. Click-through on any matter title opens the full case record in a side panel.
Two other interfaces
Paralegal Workbench: task-centric view. Paralegals can claim open tasks, log time directly against a matter, and upload signed documents which auto-update the matter’s stage.
Partner Reporting: read-only firm-wide view with charts showing matters by stage, WIP trend, top 10 oldest open balances, and attorney utilisation. Replaces what used to be a 2-day monthly reporting exercise.
Automations
Automating the repetitive coordination work
Eight automations remove roughly 1,200 manual touchpoints from the firm’s month. None of them replace an attorney’s judgment: they remove the surrounding paperwork.
Image: Figure 6: The Automations panel. Eight automations, six currently enabled, with run counts visible per automation. The detail pane on the right shows the trigger and three actions of the hearing-reminder workflow.
The automation catalogue
Each automation is owned by a named person on the working group, documented in a Notion runbook, and reviewed quarterly.
#
Automation
Trigger
Actions
Replaces
1
New case → Conflict check workflow
Record created in Cases with stage = Intake
Searches Clients table for matches against parties, opposing counsel and judges. Posts result to Slack and sets conflict_clear if no match.
Manual lookup in Excel register
2
Hearing date approaching (14 d)
days_until formula on Hearings = 14 and status = Scheduled
Slack DM to lead attorney + creates 4 prep tasks (brief, exhibits, witness prep, filings).
Calendar reminders + paralegal phone calls
3
Statute of limitations alert (90/30/7 days)
Cases.days_until_sol formula crosses each threshold
Email to lead attorney; at 30d also CCs managing partner; at 7d escalates to a Slack channel.
Slack DM to managing partner with link to the entry.
End-of-month review (often too late)
6
Client onboarding sequence
Clients.conflict_clear changes to true
Sends client engagement letter via DocuSign, creates Drive folder with templates, books an intake call.
Three separate manual checklists
7
Weekly WIP digest
Schedule: every Monday 7:00 AM
Builds per-attorney summary of WIP, billed and aged AR; emails each lead attorney their digest.
Office manager spending Friday building reports
8
Stale matter (no activity 30 d)
Schedule: nightly scan
Sets a flag field; visible on the Partner Reporting interface for follow-up.
Nothing: these matters used to disappear
Worked example: automation #2 in detail
Trigger: a record in Hearings where the days_until formula evaluates to exactly 14 and status is Scheduled.
Action 1 (Find records): looks up the parent Case via the linked-record field to retrieve the lead attorney and client.
Action 2 (Send Slack): DMs the lead attorney with a deep link back to the case record and a one-line summary of the hearing.
Action 3 (Create tasks): creates four pre-templated prep tasks in the Tasks table, all linked to the same matter, with sensible default due dates working back from the hearing.
Replaced: three different paralegals each maintaining their own version of a hearing-prep checklist, and the senior associate manually pinging attorneys.
Integrations
How the workspace connects to the rest of the stack
Airtable doesn’t replace email, calendars, document storage or e-signature, and shouldn’t. It coordinates them.
System
Direction
What flows
Mechanism
Outlook / Microsoft 365
Two-way
Hearings sync to attorney calendars; calendar invites for new hearings auto-create Hearing records.
Microsoft Graph + Airtable sync
Gmail (firm address)
One-way (in)
Email referencing a matter ID is logged to the Communications table with a link back to the thread.
Native Airtable Gmail integration
DocuSign
Two-way
Engagement letters dispatched from Airtable; signed status triggers automation #4.
Webhooks via Airtable Automations
Slack
One-way (out)
Hearing reminders, SOL alerts, time-entry alerts, weekly WIP digests.
Native Slack action in Airtable Automations
Google Drive
One-way (out)
On client onboarding, a structured matter folder is created with the firm’s standard subfolder template.
Drive API call from Airtable script action
Notion
Reference only
Runbooks for each automation live in Notion; each Automation record has a URL field linking to its runbook.
Manual link
Permissions & data handling
Workspace plan: Airtable Business with SAML SSO via the firm’s identity provider. Two-factor authentication enforced for all 60 users.
Field-level permissions: rate cards, WIP and AR fields are read-only to associates; visible only to partners on the Partner Reporting interface.
Privileged matters: a checkbox on Cases hides a matter from all users not on its team via a row-level filter applied to every view.
Audit: Airtable’s revision history is retained, and a nightly snapshot is exported to the firm’s encrypted backup bucket.
Results
Measurable change after 90 days in production
Metric
Before
After
Change
Matter intake (lead → opened)
≈ 6 hours
≈ 1 hr 55 min
−68%
Conflict check turnaround
Up to 48 hr
< 60 sec (automated)
−99%
Missed SOL deadlines (rolling 12 mo.)
2 near-misses
0
−100%
Monthly management report build time
≈ 14 hours
≈ 25 min (live dashboard)
−97%
Time-entry capture latency
Avg. 4.2 days
Avg. 0.6 days
−86%
WIP recovered Q1 (vs. prior quarter)
n/a
$41,200
+ revenue
Automated touchpoints / month
0
1,284 (across 6 active flows)
n/a
Active users (firm-wide)
n/a
60 / 60
100% adoption
In the words of the firm
The thing that surprised me wasn’t the dashboards: it was the fact that we don’t talk about case status in hallways anymore. Everyone is looking at the same picture, and the system tells us when something needs attention before it becomes a fire. We have not had a near-miss on a deadline since the day we went live.
What we’d do again, and what we’d change
Worked well: embedding the working group from week one. Every design decision had a real attorney’s name attached to it, which made go-live painless.
Worked well: shipping the Attorney Dashboard before the Partner Reporting interface. Adoption is driven by the people doing the work, not the people watching the work.
Would change: we waited until phase 3 to wire up the Outlook two-way sync. In hindsight, that should have been in phase 2, calendars are how attorneys actually work.
Would change: add a fifth interface for the firm’s receptionist. Inbound caller intake is still slightly clunky.