Browse case studies by tool and use case: automations, AI agents, dashboards, and custom platforms.
This is the complete text of the site: a contents list naming every section and case study, then all 109 case studies in full, ordered from shortest to longest. Each section also has its own page at /full/<section>.
If your tool shows only the first part of this page: the page is about 559,000 characters and some tools read only the first 100,000 at a time. The same content is also split into 7 parts that each fit in one read. What you have read so far matches Part 1; continue with the next part:
This Zap connects Skool, Slack, LeadConnector and Close, starting when a member answers the Skool membership questions.
Section: Zapier Automations
Project Overview
This Zap connects Skool, Slack, LeadConnector, and Close. When a member answers the membership questions in Skool, the automation sends a message to a Slack channel, adds or updates the contact in LeadConnector, and looks up the matching contact and lead in Close.
Implemented a robust data pipeline using SyncWith and SQL to extract and sync data from BigQuery to Google Sheets for real-time analytics and reporting.
Section: Google Apps Script
Project Overview
This project uses SyncWith and SQL to extract and synchronize data from BigQuery to Google Sheets, supporting analytics and reporting.
Technology: Google Apps Script, BigQuery, Google Sheets, SQL, SyncWith
01. The Solution
A data pipeline was implemented using SQL queries and SyncWith to retrieve data from BigQuery and sync it into Google Sheets for reporting.
02. How It Works
Query data in BigQuery using SQL.
Join employer and sign-up data by month.
Schedule the query to support regular KPI reporting.
Sync the resulting data to Google Sheets.
03. Workflow
04. Implementation
The SQL query shown in the screenshot groups records by year and month and joins employer and sign-up data for KPI reporting.
Image: A scheduled BigQuery SQL query joining employer and sign-up data by month for the KPI sheet.
05. Outcome
The pipeline supports synchronized data reporting from BigQuery to Google Sheets, helping make KPI data available for analytics.
This Zap automates the process of task creation in ClickUp based on incoming emails from a specified sender in Gmail.
Section: Zapier Automations
Project Overview
This Zap connects Gmail with ClickUp to automate task creation from emails received from a specified sender. When a matching email arrives, the automation creates a new task in ClickUp and uploads any email attachments to that task.
Tools: Zapier, Gmail, ClickUp.
01. How It Works
Incoming Email: Gmail receives an email from the designated sender.
Create Task: Zapier automatically creates a new task in ClickUp based on the email.
Upload Attachments: Any attachments included in the email are uploaded and attached to the newly created task.
Image: Zapier Automation
02. Workflow Overview
03. Key Benefits
Automated task creation: Converts matching incoming emails into ClickUp tasks.
Attachment handling: Keeps email attachments with the corresponding task.
Centralized information: Consolidates task details and documents in ClickUp.
Final Outcome
The Zap streamlines email-based task creation by connecting Gmail and ClickUp, keeping relevant email information and attachments together in one task.
Utilized Google Apps Script to automate the generation and saving of chart images to Google Drive, streamlining the reporting process.
Section: Google Apps Script
Project Overview
This project uses Google Apps Script to automate the generation of chart images and save them to Google Drive, streamlining the reporting process and reducing manual effort.
Technology: Google Apps Script, Google Drive
01. The Challenge
Generating chart images and saving them manually can add repetitive steps to the reporting process and make report preparation less efficient.
02. The Solution
A Google Apps Script automation was implemented to generate chart images and save them directly to Google Drive, simplifying chart management for reporting.
03. How It Works
Generate chart images using Google Apps Script.
Automate the chart image generation process.
Save the generated images to Google Drive.
04. Workflow
05. Technology
Google Apps Script: Automates chart image generation.
Google Drive: Stores the generated chart images.
06. Outcome
The automation streamlines chart image generation and storage, reducing repetitive manual work in the reporting process.
Created Google Apps Script to automatically format data into PDF invoices and send them via email, saving manual effort and enhancing operational efficiency.
Section: Google Apps Script
Project Overview
This project uses Google Apps Script to format data into PDF invoices and send them via email, reducing manual effort and improving operational efficiency.
Technology: Google Apps Script.
01. The Challenge
Preparing invoices manually involves formatting data into invoice documents and sending them to recipients by email. This process requires repetitive manual effort.
02. The Solution
A Google Apps Script solution was developed to automate invoice formatting, PDF generation, and email delivery.
03. How It Works
Format invoice data: Google Apps Script formats the data into an invoice.
Generate PDF: The formatted invoice is produced as a PDF.
Send via email: The PDF invoice is sent through email.
04. Workflow
05. Technology
Google Apps Script: Automates invoice formatting, PDF generation, and email delivery.
06. Outcome
The automation reduces manual invoicing effort by combining PDF invoice creation and email delivery into a scripted process.
This automation is implemented to create a Pinterest pin whenever RSS data is received.
Section: Zapier Automations
Project Overview
This automation uses Zapier to create a Pinterest pin whenever RSS data is received. It extracts the necessary information from the RSS feed and uses it to create the pin, streamlining the process of keeping Pinterest updated.
Tools: Zapier, Pinterest.
01. The Solution
The automation connects RSS data with Pinterest to simplify content distribution.
Creates a Pinterest pin whenever RSS data is received.
Extracts the necessary information from the RSS feed.
Streamlines the process of updating Pinterest with content from the RSS feed.
Reduces manual effort and supports timely pin creation based on new RSS data.
02. Workflow Overview
03. Business Benefits
Reduced manual effort: Automates pin creation from incoming RSS data.
Timely content sharing: Creates pins based on newly received RSS data.
Streamlined workflow: Simplifies the process of keeping Pinterest updated.
04. Final Outcome
The Zapier automation creates Pinterest pins from incoming RSS data, reducing manual effort and streamlining content distribution to Pinterest.
The automation is designed to send daily updates to Slack. The data in Google Sheets is updated daily, and the KPI data is sent to Slack every day using a Make scenario.
Section: Make Automations
Project Overview
This Make scenario sends daily KPI updates to Slack using data from Google Sheets. The spreadsheet data is updated daily, and the scenario delivers the KPI information to Slack.
How It Works
1. Google Sheets Data
The scenario uses data from Google Sheets as the source for daily KPI updates.
2. Router
A Router splits the workflow into two separate branches.
3. Retrieve KPI Values
Each branch uses a Google Sheets module to retrieve the relevant range values.
4. Send Slack Updates
Each branch sends a message to Slack with the corresponding KPI information.
Image: Screenshot of working automation
Workflow Architecture
The workflow contains two branches, each connecting a Google Sheets module to a Slack message module.
Tools and Integrations
Make: Connects the modules and manages the workflow.
Google Sheets: Provides the KPI data.
Slack: Receives the daily updates.
Outcome
The scenario automates the delivery of daily KPI updates from Google Sheets to Slack, reducing the need to share these updates manually.
Created an interactive dashboard within Google Sheets for effective data visualization and tracking, serving as a quick reference tool for stakeholders.
Section: Google Apps Script
Project Overview
This project uses Google Sheets to present CRM data in a dashboard format, giving stakeholders a quick reference for hiring totals, job closures, and feedback scores.
Technology: Google Sheets, Google Apps Script
01. The Solution
An interactive dashboard was created within Google Sheets to organize key metrics and make performance data easier to review.
02. Dashboard Metrics
Total average responses
Total bad responses
Total employers who hired through Taraki
Total jobs of employers who hired through Taraki
Total hired
Total jobs closed
Experience with Taraki
Good feedback
Average feedback
Bad feedback
03. Implementation
The dashboard uses Google Sheets formulas to calculate and display metrics from multiple data tabs, providing a consolidated view of hiring activity and feedback.
Image: A CRM dashboard inside Google Sheets tracking hiring totals, job closures, and feedback scores.
04. Outcome
The dashboard serves as a quick reference for stakeholders to track hiring activity, job closures, and feedback scores in one place.
This automation is implemented to create a Pinterest pin whenever RSS data is received.
Section: Make Automations
Automating Instagram RSS Feed to Pinterest Pin Creation
Automatically create Pinterest pins whenever new RSS feed data is received, using Make and text parsing.
Project Overview
This Make automation creates a Pinterest pin whenever RSS data is received. Multiple text parsers are used to extract and format the relevant information before creating the pin.
The Workflow
1. Receive RSS Data
The automation starts when RSS feed data is received.
2. Extract and Parse Text
Multiple text parsers process the incoming data to ensure the required information is extracted and placed in the relevant format.
3. Prepare Pinterest Content
The parsed data is formatted appropriately for Pinterest pin creation.
4. Create a Pinterest Pin
The automation uses the processed RSS information to create a Pinterest pin.
Platforms Used
Make: Runs the automation and processes the incoming data.
Pinterest: Receives the created pins.
Image: Screenshot of working automation in make.com
Outcome
The automation streamlines RSS-to-Pinterest content creation, reduces manual effort, and helps keep Pinterest updated with content from the RSS feed.
RB2B is a platform that collects website visitor profiles.
Section: Make Automations
Project Overview
This automation connects RB2B, GoHighLevel, and Beehiiv through Make. When RB2B creates a website visitor profile, the profile is added to GoHighLevel as a contact, a deal is created for that contact, and the associated email is added to Beehiiv as a subscriber.
The Workflow
1. Website Visitor Profile
RB2B collects website visitor profiles and triggers the automation when a new profile is created.
2. Create a Contact in GoHighLevel
The visitor profile is added to GoHighLevel as a contact.
3. Create a Deal
A deal is also created in GoHighLevel for the new contact.
4. Add a Beehiiv Subscriber
The associated email address is added to Beehiiv as a subscriber.
Image: Screenshot of working automation in make.com
Platforms Used
Make: Connects the platforms and automates the workflow.
RB2B: Collects website visitor profiles.
GoHighLevel: Stores the contact and its associated deal.
Beehiiv: Receives the email address as a subscriber.
Outcome
The workflow automates the transfer of visitor profile information into GoHighLevel and adds the associated email address to Beehiiv, connecting contact and deal creation with subscriber addition.
The script reads from a spreadsheet cell that lists email addresses authorized for file access.
Section: Google Apps Script
Project Overview
This project uses Google Apps Script and Google Drive to manage file and folder access based on email addresses listed in a spreadsheet.
Technology: Google Apps Script, Google Drive
01. The Challenge
Managing access manually can make it difficult to keep file and folder permissions aligned with the current list of authorized users.
02. The Solution
A Google Apps Script automates access management by granting permissions to email addresses listed in the spreadsheet and removing access for addresses that are no longer listed.
03. How It Works
Read authorized email addresses from a spreadsheet cell.
Update sharing permissions for designated Google Drive files and folders.
Grant access to listed email addresses.
Remove access from addresses not currently listed.
Support different access requirements for team members and clients.
04. Workflow
05. Technology
Google Apps Script: Automates access and permission management.
Google Drive: Stores the files and folders whose access is managed.
06. Outcome
The automation simplifies permission management and helps keep file access aligned with the authorized email list, reducing the risk of unauthorized viewing or editing.
This scenario is implemented so that whenever the status of an opportunity is changed in Go High Level, the associated email is added to Beehiv as a subscriber.
Section: Make Automations
Project Overview
This automation connects GoHighLevel and Beehiiv through Make. When an opportunity’s status changes in GoHighLevel, the associated email address is sent to Beehiiv and added as a subscriber.
The Solution
The Make scenario automates the transfer of contact email information between GoHighLevel and Beehiiv when an opportunity status changes.
How It Works
Opportunity Status Changes: The scenario responds when an opportunity’s status is changed in GoHighLevel.
Process the Contact Information: Make handles the information associated with the opportunity.
Add the Subscriber to Beehiiv: The associated email address is added to Beehiiv as a subscriber.
Image: Screenshot of working automation from make.com
Platforms Used
Make: Connects the two platforms and runs the automation.
GoHighLevel: Provides the opportunity status change that triggers the scenario.
Beehiiv: Receives the associated email address as a subscriber.
Outcome
The integration automates adding email addresses to Beehiiv following opportunity status changes in GoHighLevel, reducing the need to transfer subscriber information manually
Trello Cards to AI Social Captions and Hashtags Zap
This Zap runs every day, goes through the cards on a Trello board, and uses ChatGPT to write a social media caption and hashtags that are saved on each Trello card.
Section: Zapier Automations
Project Overview
This Zap runs daily, retrieves cards from a single Trello pillar, and uses ChatGPT to generate a social media caption and hashtags for each card. The generated content is then saved back to the corresponding Trello card.
Tools: Zapier, Trello, OpenAI (ChatGPT).
01. How It Works
Daily Schedule: Schedule by Zapier starts the workflow once a day.
Retrieve Cards: The Zap gets cards from a single Trello pillar.
Loop Through Cards: Itemizer splits the cards into individual items so the subsequent steps run for each card.
Check Each Card: A webhook GET request, Formatter utility step, and filter determine which cards continue.
Read Attachments: The workflow retrieves the card’s attachments from Trello.
Generate Captions and Hashtags: ChatGPT generates the social media caption and hashtags.
Update Trello: The generated caption and hashtags are saved to the corresponding card.
Image: Zapier workflow pipeline
02. Workflow Overview
03. Final Outcome
The Zap automates caption and hashtag generation for Trello cards, saving the generated content directly to each card and reducing the need to write this content manually.
This Zap facilitates seamless integration between Google Calendar and ClickUp, enhancing task management and operational efficiency.
Section: Zapier Automations
Project Overview
This Zap connects Google Calendar with ClickUp. Whenever a new event is created in Google Calendar, the automation creates a corresponding task in ClickUp and transfers relevant event details, including the date, time, and description.
The Zap also assigns tasks to specific individuals to support task allocation and coordination.
Tools: Zapier, Google Calendar, ClickUp.
01. How It Works
New Calendar Event: A new event is created in Google Calendar.
Create ClickUp Task: Zapier automatically creates a corresponding task in ClickUp.
Transfer Event Details: The task includes the event date, time, and description.
Assign Task: The task is assigned to the specified individual.
02. Key Benefits
Automated task creation: Converts new calendar events into ClickUp tasks.
Information transfer: Carries relevant event details into ClickUp.
Task assignment: Assigns tasks to specific individuals.
Improved coordination: Connects calendar events with task management.
03. Workflow Overview
Final Outcome
The Zap integrates Google Calendar with ClickUp to automate task creation from new calendar events, transfer relevant event information, and assign tasks to the appropriate individuals.
TidyCal Booking to LeadConnector and Google Sheets Zap
This Zap runs when a new booking is made in TidyCal, adds or updates the contact in LeadConnector, and records the booking in Google Sheets.
Section: Zapier Automations
Project Overview
This Zap connects TidyCal, LeadConnector, and Google Sheets. When a new booking is made in TidyCal, the automation adds or updates the contact in LeadConnector and records the booking in Google Sheets.
The workflow includes filtering, text formatting, a spreadsheet lookup, and two paths to update an existing row or create a new one.
Tools: Zapier, TidyCal, LeadConnector, Google Sheets.
01. How It Works
New Booking: A new booking in TidyCal triggers the Zap.
Filter and Format: Filter by Zapier checks conditions, and Formatter processes text.
Update Contact: LeadConnector adds or updates the contact.
Find Spreadsheet Row: Google Sheets looks up the matching row.
Route the Booking: The workflow splits into two paths: one updates the existing row, and the other creates a new row.
Image: The ten-step Zap: a TidyCal booking trigger, filter and text formatting, LeadConnector, a Google Sheets lookup, and two paths that update or create a row.
02. Workflow Overview
03. Final Outcome
The Zap connects booking management, contact updates, and spreadsheet records in one workflow, with separate paths for updating an existing Google Sheets row or creating a new one.
This Zap streamlines the process of appointment cancellations by integrating ClickUp with Calendly.
Section: Zapier Automations
Project Overview
This Zap integrates ClickUp with Calendly to streamline appointment cancellations. When a cancellation is initiated from within ClickUp by pressing the cancel button on a specific task, the corresponding appointment is automatically cancelled in Calendly.
The automation helps manage appointment slots, keep scheduling information updated, and reduce manual oversight.
Tools: Zapier, Calendly, ClickUp.
01. How It Works
Initiate Cancellation: A user presses the cancel button on a specific task in ClickUp.
Trigger the Zap: Zapier processes the cancellation workflow.
Cancel the Appointment: The corresponding appointment is automatically cancelled in Calendly.
Image: Active Zapier Workflows for ClickUp-to-Calendly Cancellation Sync
02. Key Benefits
Automated cancellations: Cancels the relevant Calendly appointment through ClickUp.
Reduced manual work: Minimizes the need to cancel appointments manually in Calendly.
Fewer scheduling conflicts: Helps keep cancellations synchronized between the platforms.
03. Workflow Overview
Image: Active ZapierAutomation
Final Outcome
The Zap connects ClickUp and Calendly to automate appointment cancellations initiated from ClickUp, simplifying scheduling management and reducing manual effort.
A Zap is being built to connect GoHighLevel with Beehiv.
Section: Zapier Automations
Project Overview
This project connects GoHighLevel with Beehiiv using Zapier. When a user submits a form on GoHighLevel, the submitted information is sent to a Zapier webhook and then added to Beehiiv.
The integration uses a GoHighLevel workflow to send the form data to Zapier, which receives the information and forwards it to Beehiiv.
Tools: Zapier, GoHighLevel, Beehiiv.
01. The Business Requirement
The objective is to connect GoHighLevel form submissions with Beehiiv so that submitted user information can be transferred between the two platforms through an automated workflow.
02. The Solution
A Zapier integration is being built to connect GoHighLevel with Beehiiv.
The process consists of the following steps:
A user submits a form on GoHighLevel.
A workflow in GoHighLevel sends the submitted information to a Zapier webhook.
Zapier receives the information from the webhook.
Zapier adds the received information to Beehiiv.
03. Project Snapshot
Item
Detail
Automation platform
Zapier
Source platform
GoHighLevel
Destination platform
Beehiiv
Trigger event
GoHighLevel form submission
Data transfer
GoHighLevel workflow to Zapier webhook
Final action
Add submitted information to Beehiiv
04. Workflow Architecture
05. Final Outcome
The integration is being built to transfer information submitted through GoHighLevel forms into Beehiiv using Zapier as the connection between the platforms.
Monday.com Timeline Stage Alerts to Slack and Close Zap
This Zap watches the timeline stages of Monday.com items and notifies the team in Slack each time an item reaches a new stage.
Section: Zapier Automations
Project Overview
This Zap monitors timeline stages for items in monday.com. When an item reaches a milestone, it updates the item and notifies the team in Slack. At the 45-days-left stage, it also checks Close for the opportunity and updates an existing opportunity or creates a new one when needed.
01. How It Works
Webhook Trigger: Starts when an item reaches a timeline stage.
Find Item: Looks up the item in monday.com.
Determine Stage: Uses Python in Code by Zapier to identify the stage.
Branch by Stage: Paths route the Zap according to the timeline milestone.
Update and Notify: Updates the monday.com item and sends a Slack message.
Close Integration: At 45 days left, checks Close and updates or creates an opportunity.
02. Timeline Milestones
The workflow handles these programme stages:
90 days in
60 days in
45 days in
60 days left
45 days left
1 day left
Image: Steps 1–16 and 31–33: the webhook trigger, the monday.com lookup, the Python step, and the Paths that update items and notify Slack.
03. Workflow Overview
At the 45-days-left stage, the workflow also checks Close and creates or updates an opportunity as needed.
Final Outcome
The Zap automates timeline-stage updates and team notifications, while supporting opportunity management in Close at the 45-days-left stage.
Image: Steps 17–30: the Close branches that find contacts and create leads and opportunities, each ending in a Slack message.
The script initiates by creating a structured main folder in Google Drive.
Section: Google Apps Script
Project Overview
This project uses Google Apps Script to create a structured folder hierarchy in Google Drive, generate spreadsheet files from templates, duplicate Google Docs templates, and record the created files and folders in a master spreadsheet.
Technology: Google Apps Script, Google Drive
01. The Challenge
Creating folders and preparing multiple files manually for each client requires repetitive work and makes file organization more time-consuming.
02. The Solution
A Google Apps Script automates folder creation, spreadsheet generation from templates, and duplication of Google Docs templates. A master spreadsheet records the names, IDs, and direct links of the created items.
03. How It Works
Create a main folder in Google Drive.
Generate predefined subfolders within it.
Create spreadsheet files from templates in the relevant folders.
Duplicate Google Docs templates and place them in their respective folders.
Update the master spreadsheet with file and folder names, IDs, and links.
04. Workflow
05. Technology
Google Apps Script: Automates the batch creation process.
Google Drive: Stores the folders, spreadsheets, and duplicated documents.
06. Outcome
The automation streamlines the creation and organization of client folders and files while maintaining a master spreadsheet for easy navigation.
07. Implementation
Batch-Creation Script: Generates each client's folder structure, contract, and accounting files from templates.
Image: The batch-creation script that generates each client’s folder structure, contract, and accounting files from templates.
Automation of Shopify Orders to Google Sheets for Dropshipping E-commerce Store
The primary goal of this automation is to streamline the process of managing Shopify orders by automatically distributing them to the appropriate fulfillment sheets.
Section: Make Automations
Project Overview
This Make automation streamlines Shopify order management for a dropshipping e-commerce store. It records incoming orders, identifies the relevant products, and distributes order information to the appropriate Google Sheets fulfillment sheets based on supplier requirements.
How It Works
1. Shopify Order Tracking
When a new order is created in Shopify, the automation adds the order to a Make Data Store for tracking.
2. Product Identification
The workflow checks product IDs against a Google Sheets database to determine which supplier's fulfillment sheet should receive the order.
3. Master Sheet Integration
A master sheet consolidates order information. Changes made to the master sheet are reflected in the respective Google Sheets to maintain consistency.
4. Supplier-Based Order Distribution
Order details are routed to the appropriate fulfillment sheets so that each supplier receives the relevant order information.
Workflow Architecture
A master sheet serves as the central location for consolidating and managing order information.
Tools and Integrations
Make: Automates the workflow and coordinates data between applications.
Shopify: Provides order and product information.
Google Sheets: Stores product IDs, consolidates order data, and supports supplier-specific fulfillment tracking.
Outcome
The automation helps organize Shopify orders, distribute them according to supplier requirements, and keep order information consistent across the relevant Google Sheets.
Worked on developing a Project Tracker in Google Sheets to allocate tasks, track project milestones, and monitor team performance, complete with real-time updates and visual dashboards for easy interpretation.
Section: Google Apps Script
Project Overview
This project involved developing a Project Tracker in Google Sheets to help manage tasks, monitor project milestones, and track team performance. The tracker includes real-time updates and visual dashboards for easier interpretation of project schedules and progress.
Tools: Google Apps Script and Google Sheets.
01. Project Objectives
The tracker was developed to support three main activities:
Task Allocation: Organize and allocate project tasks.
Milestone Tracking: Track project milestones and schedules.
Team Performance Monitoring: Monitor team performance through the tracker.
02. The Solution
A project tracking system was developed in Google Sheets, with real-time updates and visual dashboards to make project information easier to understand.
03. Project Schedule Visualization
The tracker includes a Gantt-style project schedule generated directly in Google Sheets. The schedule displays task start and end dates across a timeline, making it easier to view project durations and overlapping activities.
Image: A Gantt-style project schedule generated directly in Google Sheets.
04. Key Features
Task allocation and organization
Project milestone tracking
Team performance monitoring
Real-time updates
Visual dashboards for interpreting project information
Gantt-style schedule visualization in Google Sheets
05. Tools and Technologies
Google Sheets: Provides the project tracking spreadsheet, schedule, and visual dashboard.
Google Apps Script: Listed as a technology used in the project.
06. Outcome
The Project Tracker provides a centralized way to allocate tasks, track milestones, and monitor team performance through Google Sheets, supported by visual scheduling and dashboard features.
This Make scenario is implemented whenever a task gets completed in ClickUp.
Section: Make Automations
Project Overview
This Make automation connects ClickUp with Google Sheets to transfer completed task details into the appropriate spreadsheet. When a task is completed in ClickUp, the scenario processes its information and uses custom fields to determine which Google Sheets file should receive the data.
The Business Need
Task information needs to be recorded in the relevant Google Sheets file when work is completed in ClickUp. This scenario automates that transfer and routes the data according to the task's custom fields.
The Solution
The Make scenario uses a custom webhook, variable configuration, and a router to direct information into Google Sheets.
Webhooks: Receives data through a custom webhook.
Tools: Sets multiple variables used during processing.
Router: Splits the workflow into two branches.
Google Sheets: Each branch adds a row to a spreadsheet.
How It Works
1. Receive the Webhook
The workflow starts when the custom webhook receives the task information.
2. Set Variables
The Tools module sets multiple variables that are used in the subsequent workflow steps.
3. Route the Data
The Router divides the workflow into two branches. The routing logic uses the task's custom fields to determine the appropriate destination.
4. Add a Row to Google Sheets
Each branch connects to a Google Sheets module configured to add a row to its respective spreadsheet.
Image: Screenshot of working automation in make.com
Workflow Architecture
The router splits the workflow into two Google Sheets branches, allowing data to be directed to the relevant destination.
Tools and Integrations
Make: Connects the workflow modules and manages routing.
ClickUp: Provides the completed task information.
Google Sheets: Receives task details as new spreadsheet rows.
Outcome
The scenario automates the transfer of completed task information into Google Sheets and routes the data according to custom fields, reducing the need to enter the same information manually.
Automated PDF Data Extraction from Gmail and Google Sheets Integration
Developed an automated solution for a client who received daily PDFs via email.
Section: Google Apps Script
Project Overview
This solution processes PDF attachments received by email, extracts relevant information, and transfers the data into a designated Google Sheet. It also supports manual PDF uploads and scheduled email fetching.
Technology: Gmail, Google Sheets, Python, FastAPI
01. The Challenge
Processing daily PDF attachments manually requires downloading files, extracting important information, validating data, and entering it into Google Sheets.
02. The Solution
An automated workflow was developed to fetch PDF attachments from Gmail, extract relevant fields, validate the data, and populate Google Sheets. A manual upload interface is also available.
03. Key Features
User Authentication: Provides a login mechanism for users.
PDF Upload: Allows users to upload PDF files manually.
Data Extraction: Extracts fields such as order code, shipping address, and product details.
Google Sheets Integration: Transfers extracted data into a designated spreadsheet.
Scheduled Email Fetching: Retrieves PDF attachments from email at scheduled intervals.
Data Validation: Checks data consistency and accuracy.
04. How It Works
Scheduled workflow
Fetch PDF attachments from Gmail.
Parse the PDF and extract relevant data.
Validate the extracted information.
Transfer the data to Google Sheets.
Manual workflow
User logs in.
User uploads a PDF.
The backend processes the file and sends the extracted data to Google Sheets.
05. Workflow
Manual Upload:
06. Implementation
The FastAPI backend handles file uploads, invoice processing, and spreadsheet integration. The process.py module processes uploaded files, converts extracted invoice data into a dataframe, and passes it to the Google Sheets client.
Image: The FastAPI backend that handles the upload, invoice parsing, and Sheets integration.
07. Outcome
The solution reduces manual PDF processing and data-entry work by combining scheduled email fetching, manual uploads, data extraction, validation, and Google Sheets integration.
Trello to Facebook, LinkedIn and Instagram Social Posting Zap
This Zap runs every day, picks up the Trello cards for that day, and publishes their images and captions to Facebook, LinkedIn and Instagram.
Section: Zapier Automations
Project Overview
This Zap automates social media publishing using Trello and Zapier. It runs daily, retrieves the Trello cards scheduled for that day, and publishes their images and captions to Facebook, LinkedIn and Instagram.
Each Trello card contains the images and platform-specific captions, allowing content to be prepared in Trello before publication.
Daily Schedule: Schedule by Zapier starts the workflow once a day.
Retrieve Trello Cards: The Zap gets cards from a single Trello pillar, splits them into individual items and loops through them.
Check Card Details: Formatter steps convert start and due dates and read the card status. A filter determines which cards continue.
Extract Content: The workflow extracts social media captions and retrieves image attachments from Trello.
Update Trello: The card is updated and moved to another list.
Publish to Social Platforms: Code by Zapier and Paths route the content according to platform and content type.
Image: Steps 1–11: the daily schedule, the Trello card lookup, a loop over each card, and date and status formatting.
Image: Steps 12–48: caption extraction, Trello updates, and the Paths that publish to Facebook Pages, LinkedIn and Instagram for Business.
02. Platform Publishing
Facebook: Publishes posts and videos to Facebook Pages.
LinkedIn: Publishes company updates.
Instagram: Publishes photos and videos to Instagram for Business.
03. Workflow Overview
04. Workflow Screenshots
Steps 1–11: Daily schedule, Trello card lookup, loop over cards, and date and status formatting.
Steps 12–48: Caption extraction, Trello updates, and publishing paths for Facebook Pages, LinkedIn and Instagram for Business.
Final Outcome
The Zap automates daily social media publishing from Trello, using prepared images and platform-specific captions to publish content across Facebook, LinkedIn and Instagram.
Created a script to automate data entry in an inventory sheet from CSV files.
Section: Google Apps Script
Project Overview
This project uses Google Apps Script to automate the import of inventory data from CSV files into an inventory sheet. It also includes a data-cleaning function to help maintain the accuracy and integrity of imported information.
Technology: Google Apps Script.
01. The Challenge
Inventory data from multiple warehouses can contain inconsistencies that need to be identified during processing. The provided inventory sheet shows examples of data-quality issues, including mismatched warehouse locations and unidentified SKUs.
02. The Solution
A Google Apps Script was created to automate CSV-based inventory data entry. The script also includes a data-cleaning function to help ensure that imported data is accurate and consistent.
03. How It Works
Step 1: Import Inventory Data
The script automates data entry into the inventory sheet using CSV files as the data source.
Step 2: Clean the Imported Data
A data-cleaning function processes the imported data to help maintain accuracy and integrity.
Step 3: Identify Inventory Issues
The inventory sheet displays problems such as mismatched locations and unidentified SKUs, helping highlight records that require attention.
04. Google Sheets Custom Menu
The provided screenshot shows a custom menu in Google Sheets with two options:
Update Inventories
Add Leading Zeros
These options provide menu-based access to the inventory-related script functions.
05. Example: Inventory Data Quality
The inventory sheet contains warehouse names, SKUs, locations, updated on-hand quantities, and a Problems column. The displayed examples include mismatched location information and unidentified inventory records.
Image: Multi-warehouse inventory data with flagged data-quality issues the cleaning step catches: mismatched locations and unidentified SKUs.
06. Technology
Google Apps Script: Automates CSV-based inventory data entry and provides a data-cleaning function.
Google Sheets: Holds the inventory data and displays inventory records and flagged issues.
07. Outcome
The solution automates inventory data entry from CSV files and includes data cleaning to support accurate and consistent inventory records.
Daily Ticket-Count Automation: Gmail PDFs to BigQuery and Google Sheets
A Python job that reads daily Ticketmaster audit PDFs from email, stores every figure in BigQuery and publishes a Google Sheet that mirrors the team’s existing workbook.
Section: Python Automation
Project Overview
A Python job reads daily Ticketmaster audit PDFs received by email, stores the extracted figures in BigQuery, and publishes a Google Sheet that mirrors the team's existing workbook.
Technology: Python, Gmail API, BigQuery, Google Sheets API, PDF parsing, pytest
01. The Problem
An events company received daily Ticketmaster audit PDFs by email and manually re-entered the reported figures into a workbook. This repetitive process required daily manual effort.
02. The Solution
A scheduled Python job uses the Gmail API and an OAuth refresh token to retrieve report emails, download and parse PDF attachments, store the figures in BigQuery, and publish the results to Google Sheets.
03. How It Works
Retrieve report emails using the Gmail API.
Download the attached Ticketmaster audit PDFs.
Parse the PDFs and extract ticket-count figures.
Store the extracted figures in BigQuery.
Publish a Google Sheet that mirrors the existing workbook.
Record each job run in the Run Log tab.
04. Workflow
05. Google Sheets Output
The published spreadsheet tracks:
General Admission (GA) tickets
VIP tickets
Total tickets
Tickets sold against capacity
Percentage sold
Image: The Google Sheet the job publishes: tickets sold per day against capacity, split into GA and VIP, with the percentage sold. Event names and some tab names are hidden.
The workbook includes a Top Sheet, Raw Data, and Run Log tabs.
06. Testing and Implementation
The project followed a specification-first process: design specification, implementation plan, tests using fixture PDFs, and then the pipeline implementation.
Image: The project repository, with the ticket-count source code, tests, scripts and design documents.
The repository includes the ticket-count source code, scripts, tests, and design documents.
07. Outcome
The job automates the transfer of ticket figures from daily email attachments into BigQuery and Google Sheets, reducing manual data entry and providing a run log for tracking executions.
Image: The Run Log tab, with one row for each run of the job and its time.
TikTok Video Downloader without watermark: Save Any Reel Directly to Google Drive
To automatically download a TikTok video and store it in Google Drive with a public share link.
Section: AI Agents
TikTok Video Downloader: Save Videos Directly to Google Drive
Automatically download TikTok videos without a watermark and save them to Google Drive with a shareable link.
Category: AI Agents Tools: TikTok, Google Drive
1. Project Overview
This workflow automates the process of fetching a TikTok video, extracting its direct video URL, downloading the video, and uploading it to Google Drive. It simplifies video collection for content management and reposting workflows.
2. The Challenge
Saving videos manually requires opening the video page, locating the downloadable video, downloading the file, and uploading it to cloud storage. These repeated steps take time and make organizing video assets less convenient.
3. The Solution
A workflow connects TikTok video-page processing with automated downloading and Google Drive storage. It extracts the direct video URL, downloads the video file, and uploads it to Drive, where a shareable link can be generated.
4. How the Workflow Works
Image: n8n workflow
Manual Trigger: Start the workflow with a single click.
Fetch Video Page: Retrieve the TikTok page information.
Extract Video URL: Process the page data to identify the direct video link.
Download Video: Use the extracted URL to download the video file.
Upload to Google Drive: Store the downloaded video in Drive.
Generate Shareable Link: Configure the uploaded file for public access and create a link for sharing.
5. Workflow
6. Key Features
One-Click Execution: Start the process manually.
Automated URL Extraction: Identify the direct video link from page data.
Automated Downloading: Retrieve the video file through the extracted URL.
Cloud Storage: Save downloaded videos directly to Google Drive.
Shareable Links: Make the file accessible through a configured sharing link.
7. Business Value
The workflow reduces repetitive downloading and uploading tasks, helping users organize video assets and make them available for sharing from Google Drive.
8. Final Outcome
A streamlined workflow that connects TikTok video retrieval with automated downloading, Google Drive storage, and shareable links—reducing manual effort in video collection and management.
The script is scheduled to run daily to ensure real-time relevancy of its functions.
Section: Google Apps Script
Project Overview
This project uses Google Apps Script to check dates stored in linked spreadsheets and send customized email reminders when tasks or events are due. The scripts support daily reminders, due-diligence checkups, and individual screening workflows.
Technology: Google Apps Script
01. The Challenge
Manually checking multiple spreadsheets for due dates and sending reminders can be time-consuming and may lead to missed tasks or delayed communications.
02. The Solution
Google Apps Script automates the process of locating linked spreadsheets, reading date-specific data, comparing stored dates with the current date, and sending email reminders when the required conditions are met.
03. How It Works
Run the script on a daily schedule.
Extract spreadsheet links from a master file.
Open the relevant spreadsheet and read its date-specific data.
Compare stored dates with the current date.
Send customized email reminders when a matching date is found.
04. Workflow
05. Implementation Examples
Example 1: Extracting Spreadsheet Links
The script checks spreadsheet cells for hyperlinks, extracts the target URL, and locates the appropriate file before processing its data.
Image: Extracting a hyperlink from a spreadsheet cell to locate the right file before checking its dates.
Example 2: Due-Diligence Email Reminders
The due-diligence script compares the current date against spreadsheet data and sends a compliance-related email when the required date conditions are met.
Image: A due-diligence checkup variant: comparing today’s date against the sheet before sending a scheduled compliance email.
Example 3: Individual Screening Automation
The screening script iterates through rows in the master sheet, checks confirmation values, extracts linked spreadsheet URLs, and processes the corresponding files.
Image: The companion screening script that walks each row and extracts the linked spreadsheet before processing it.
06. Technology
Google Apps Script: Automates scheduled execution, spreadsheet link extraction, date comparisons, and email notifications.
07. Outcome
The automation reduces repetitive spreadsheet checks and helps maintain consistent communication by sending reminders when the specified date conditions are satisfied.
Integration of Shopify and ClickUp for Managing Refunded Orders
This scenario is built so that whenever there is a refunded order in Shopify, the order details are added to ClickUp as tasks.
Section: Make Automations
Project Overview
This Make automation connects Shopify with ClickUp to help manage refunded orders. When an order is refunded in Shopify, the scenario retrieves the order details and uses them in the ClickUp task-management workflow.
The integration brings refunded-order information into ClickUp, making it easier for the team to manage refund-related tasks in one place.
The Business Need
Refunded orders need to be identified and their details made available for follow-up. Without an automated connection between Shopify and ClickUp, the team may need to transfer order information manually when managing refunded orders.
The Solution
The Make scenario connects Shopify and ClickUp through an automated workflow.
Shopify trigger: Starts the scenario when a new event is detected.
Get an order: Retrieves the relevant order details from Shopify.
Data Store: Searches for a matching record as part of the workflow.
ClickUp: Updates a task with custom fields using the available information.
Tools: Includes a sleep step before the final Data Store action.
Data Store cleanup: Deletes a record at the end of the scenario.
How It Works
1. Shopify Event
The workflow begins with a Shopify event that triggers the scenario.
2. Retrieve Order Information
The Shopify module retrieves the order details needed for the next steps.
3. Search the Data Store
The scenario searches the Data Store for a relevant record before continuing.
4. Update ClickUp
The ClickUp module edits a task using custom fields, connecting the order information with the task-management process.
5. Execute Follow-up Actions
A Tools sleep step runs before the final Data Store module deletes a record.
Image: Screenshot of working automation from make.com
Workflow Architecture
Tools and Integrations
Make: Connects the applications and runs the scenario.
Shopify: Provides the order event and order details.
ClickUp: Manages tasks using custom fields.
Data Store: Supports record searching and deletion.
Outcome
The scenario connects Shopify order events with ClickUp task updates and Data Store operations. Its purpose is to streamline the handling of refunded-order information by bringing these steps into one automated workflow.
Automatically collect detailed info from YouTube videos of popular creators for content analysis.
Section: AI Agents
YouTube Video Details Scraper Using Automation
Automating YouTube video data collection and storing results in Airtable for content research and analysis.
Category: AI Agents Integrations: YouTube, Airtable, Apify
01. Project Overview
This workflow automates the collection of detailed information from YouTube videos. It retrieves video links from Airtable, sends them to a scraping service, waits for the results, and updates the corresponding Airtable records with the collected data.
02. The Challenge
Collecting video information manually can be time-consuming, especially when researching multiple creators and videos. Titles, channel details, view counts, likes, descriptions, subtitles, and thumbnails must be gathered and organized before they can be analyzed.
03. The Solution
An automated workflow connects Airtable with a video-scraping service. It processes video links, retrieves available video details, and saves the results back to Airtable, reducing repetitive manual data collection.
04. How It Works
Image: n8n working flow screenshot
Step 1 — Manual Trigger: Start the workflow by clicking the test or run button.
Step 2 — Fetch Airtable Records: Search Airtable for records containing YouTube video links ready for processing.
Step 3 — Run the Scraper: Send the video information to the Apify API to start the scraping actor.
Step 4 — Wait for Completion: Allow the scraper to finish collecting the available video details.
Step 5 — Retrieve Results: Fetch the completed scraping results from the actor.
Step 6 — Update Airtable: Write the collected information back to the corresponding Airtable record.
05. Workflow
06. Data Collected
Depending on availability from the scraper, the workflow can collect:
Video title and channel name
Views and likes
Video description and subtitles
Thumbnail information
07. Business Value
Less manual work: Automates repetitive video research.
Organized data: Keeps collected information in Airtable.
Scalable collection: Supports processing multiple video records.
Simplified analysis: Makes video information easier to review and compare.
08. Final Outcome
The workflow connects Airtable and Apify to automate YouTube video data collection, helping organize video information in a structured database for content research and analysis.
A Looker Studio dashboard tracking Google Ads cost, revenue, orders, profit and ROAS for the same multi-channel account.
Section: Looker Studio
Looker Studio: Google Ads Dashboard
A Looker Studio dashboard that brings Google Ads cost, revenue, orders, profit, and ROAS into one reporting view.
Technology: Looker Studio, Google Ads
01. Project Overview
This project adds a dedicated Google Ads dashboard to an existing multi-channel paid media reporting setup. It brings key advertising and financial metrics together so teams can review campaign performance without relying on separate exports.
02. The Challenge
Reviewing Google Ads performance requires monitoring multiple metrics, including advertising spend, revenue, orders, clicks, and conversion rate. When these figures are viewed separately, it becomes harder to assess campaign performance and understand the relationship between advertising costs and revenue.
03. The Solution
A dedicated Google Ads report was created in Looker Studio to consolidate the main performance metrics into one dashboard.
The dashboard includes:
Cost and Revenue: Review advertising spend alongside generated revenue.
Google Ads Revenue: Track revenue attributed to Google Ads.
Orders: Monitor order volume.
Profit and Profit Margin: Review profitability alongside advertising costs.
Clicks and Conversion Rate: Evaluate traffic and conversion performance.
CPP, AOV, and ROAS: Monitor cost per purchase, average order value, and return on ad spend.
Date Filtering: Review results for a selected reporting period.
04. Dashboard Overview
The dashboard presents KPI cards at the top, followed by a time-series chart showing performance over the selected period. This layout makes it easier to scan key figures and compare cost and revenue trends.
Image: Google Ads dashboard for the same account: cost, revenue, orders, profit and ROAS alongside clicks and conversion rate.
The dashboard includes cost, revenue, orders, profit, profit margin, clicks, conversion rate, CPP, AOV, and ROAS.
05. Technology and Integration
Looker Studio: Dashboard creation and performance reporting.
Google Ads: Advertising performance data.
The report provides a consolidated view of paid media metrics within the existing reporting setup.
06. Outcome
The dedicated dashboard gives the team one place to review Google Ads performance across advertising, sales, and profitability metrics. It supports faster performance reviews and reduces the need to navigate separate views for each key indicator.
Smart AI Podcast Audio Script Generator from BBC News
To turn positive and interesting news stories into podcast-style audio scripts using AI.
Section: AI Agents
Project Overview
Category: AI Agents Technologies: n8n, BBC News, Google Gemini
This automation collects news articles from the BBC website, evaluates their suitability for podcast content, extracts the full article text, and uses AI to prepare scripts for audio conversion.
01. The Challenge
Manually finding interesting news, reviewing full articles, and rewriting them into conversational podcast scripts can be time-consuming. Not every news story is appropriate for an engaging podcast, so content must be screened before it moves forward.
02. The Solution
An n8n workflow automates the news-to-script preparation process. It retrieves BBC headlines, classifies stories using Google Gemini, extracts suitable articles, and transforms their content into friendly, podcast-style scripts.
03. How It Works
Step 1 — Fetch BBC News: Retrieve the BBC homepage and extract available news headlines and descriptions.
Step 2 — Process Headlines: Split the extracted articles into individual items and limit processing to 10 headlines.
Step 3 — Classify Stories: Use an AI news classifier to identify articles suitable for podcast content and separate unsuitable stories.
Step 4 — Extract Full Articles: Retrieve the full webpage content for stories that pass classification.
Step 5 — Filter and Generate Scripts: Process the article content and use an AI language model to rewrite suitable news into warm, clear, engaging podcast scripts.
Step 6 — Validate Output: Use structured output parsing and filtering to prepare the generated content for the next stage.
Step 7 — Prepare for Audio: Send suitable scripts to a Hugging Face API endpoint for the subsequent audio-generation stage.
04. Workflow
05. Key Features
Automated BBC news collection
AI-powered article suitability classification
Full-article extraction for selected stories
Conversational podcast script generation
Structured output validation
Integration with a Hugging Face API for the audio stage
06. Business Value
The workflow reduces manual research and rewriting, creates a repeatable news-to-script process, and helps prepare selected news stories for podcast production more efficiently.
07. Final Outcome
A reusable AI-powered pipeline that transforms BBC news articles into podcast-ready scripts, connecting news collection, AI classification, content extraction, script generation, and downstream audio processing in one workflow.
Shopify to Google Sheets Data Transfer with Task Allocation
Leveraged expertise in API integration and Google Sheets to create an automated system that transfers data from Shopify to Google Sheets using the ‘Sync With’ extension.
Section: Google Apps Script
Project Overview
This project uses Google Apps Script and Google Sheets to automate data transfer from Shopify and distribute customer-specific tasks across agents. The system uses the Sync With extension to transfer Shopify data to Google Sheets and integrates the resulting data with Aircall for customer outreach.
The system is configured to update daily.
Tools: Google Apps Script, Shopify, Google Sheets, and Aircall.
01. The Objective
The objective was to automate the transfer of Shopify data into Google Sheets and allocate customer-specific tasks to agents, reducing the need for manual task distribution.
02. The Solution
Google Apps Script functions handle the data processing and task allocation. The system uses the agent roster to distribute unattended calls evenly across available agents and integrates the data with Aircall for customer outreach.
03. How It Works
Step 1: Transfer Shopify Data
Shopify data is transferred to Google Sheets using the Sync With extension.
Step 2: Process the Agent Roster
Google Apps Script reads the agent names from the working sheet.
Step 3: Distribute Tasks
The task-distribution function calculates the allocation of data across the agent roster and assigns tasks evenly.
Step 4: Integrate with Aircall
The resulting data is integrated into Aircall to support customer outreach.
Step 5: Update Daily
The system is configured to update daily.
04. Task Distribution Logic
The Google Apps Script function distributes unattended calls across the agent roster. The provided code checks the agent list, reads the data count, calculates the number of tasks per agent, and assigns the calculated values in the working sheet.
Image: The task-distribution function that splits unattended calls evenly across the agent roster.
05. Workflow Overview
06. Tools and Integrations
Shopify: Source of the data being transferred.
Sync With extension: Supports the transfer of Shopify data to Google Sheets.
Google Sheets: Stores the transferred data and supports task allocation.
Google Apps Script: Processes the data and distributes tasks across the agent roster.
Aircall: Supports customer outreach using the integrated data.
07. Outcome
The solution automates Shopify data transfer, distributes customer-specific tasks across agents, and integrates the data with Aircall. The system is configured for daily updates.
Before, someone had to open Meta Ads Manager and Shopify every morning and compare the numbers by hand. Now an agent does it overnight and posts a short briefing in Slack. It flags problems and suggests changes, and…
Section: Custom SaaS Platforms, AI Agents
Overview
Before, someone had to open Meta Ads Manager and Shopify every morning and compare the numbers by hand. Now an agent does it overnight and posts a short briefing in Slack. It flags problems and suggests changes, and nothing is changed in Meta without approval.
The Problem
An online store owner spends money on Meta ads every day, and the numbers rarely agree with the store. Meta says it drove one amount of sales. Shopify shows what was really ordered. A broken ad can keep spending for days before anyone notices, and each day of that is money gone. Checking every campaign by hand takes hours. So it gets skipped when the week gets busy.
How It Works
Every morning at 8:00 AM, the agent pulls yesterday's ad numbers from Meta: spend, impressions, clicks, purchases and revenue, down to each ad.
It pulls the same days' orders and revenue from Shopify.
It saves both in a database.
It compares the revenue Meta claims with the orders Shopify recorded, and flags any day where Meta claims more.
It calculates ROAS, cost per purchase, CPM, CTR, frequency, and conversion rate, and checks the rules: wasted spend, weak ad sets, tired creative, and room to scale.
Claude writes the briefing in plain English from those calculated numbers. Claude doesn't do the math.
It posts a short digest in Slack with a link to the full report page.
Every hour it checks the alert limits and messages Slack only when one is crossed.
Suggested changes, such as pausing an ad set or changing a budget, wait for a person to approve them.
Approved changes run within set limits: a maximum budget change, a daily action cap, and a cooldown. Each one is logged with its before and after state. A kill switch stops everything.
Tech Stack
Tool
Job in this workflow
Meta Marketing API
Supplies ad numbers and carries out approved pauses and budget changes
Shopify Admin API
Supplies orders and revenue, the actual sales
PostgreSQL
Stores daily snapshots and the full action history
Python (FastAPI)
Runs the schedule, the rules, the report page and the control panel
Claude API
Writes the daily briefing from the calculated numbers
Slack
Delivers the daily digest and alerts
Railway
Keeps the agent running around the clock
GitHub
Holds the full source code
The team keeps using Ads Manager and Shopify exactly as before. The only new thing to read is one Slack message each morning.
A Looker Studio dashboard tracking Meta ad spend, clicks, impressions and campaign-level ROAS in one live view.
Section: Looker Studio
01. Project Overview
This dashboard provides a consolidated overview of Meta Ads performance, combining campaign metrics with a detailed breakdown of individual ads. It helps users review traffic, advertising spend, impressions, and return on ad spend within a single reporting interface.
Paid Media Reporting
Built in Looker Studio to track Meta ad spend, clicks and campaign performance in one place, replacing manual exports from Meta Ads Manager.
21,767: Clicks
627,879: Impressions
$35.2K: Spend
3.47%: CTR (all)
02. The Challenge
Reviewing advertising performance across multiple campaigns and ads can require switching between different views and manually comparing metrics. Without a consolidated report, it can be harder to identify how individual campaigns are performing and how advertising spend is distributed.
03. The Solution
A Looker Studio dashboard was created with two main reporting views:
Performance Overview: Displays high-level metrics such as clicks, link clicks, impressions, ROAS, spend, and CTR.
Campaign-Level Breakdown: Presents campaign and ad-level data, including ROAS, clicks, amount spent, impressions, and CPM.
Date Range Selection: Allows users to review performance for a selected reporting period.
Campaign Filtering: Supports filtering the detailed table by campaign name.
04. Dashboard One: Performance Overview
The overview page brings key advertising metrics together for a quick assessment of campaign activity.
Metrics shown in the supplied screenshot:
These values reflect the dashboard screenshot and should be interpreted according to the report's metric definitions and selected date range.
Image: Meta Ads dashboard overview: clicks, link clicks, impressions, ROAS and spend for a single brand’s campaigns.
05. Dashboard Two: Campaign-Level Analysis
The detailed reporting table provides a closer look at individual campaigns and ads. Users can compare performance indicators across rows and filter the table by campaign name.
The table includes:
Image: Campaign-level breakdown: ROAS, clicks, spend, impressions and CPM for every ad and campaign, filterable by name.
This view complements the overview by making individual campaign and ad performance easier to inspect.
06. Technology and Integration
Looker Studio: Reporting, visualisation, and interactive filtering.
Meta Ads: Advertising performance data.
07. Outcome
The dashboard consolidates Meta advertising metrics into a single reporting interface. The overview supports quick performance reviews, while the detailed table enables campaign-level comparisons without relying solely on separate manual exports.
This Make scenario is implemented so that whenever an order is fulfilled in Shopify, the order details are added to ClickUp.
Section: Make Automations
Project Overview
This Make automation connects Shopify with ClickUp, Google Sheets, and Slack to process fulfilled orders and update the relevant records.
When an order is fulfilled in Shopify, the scenario retrieves the order details, searches for a matching record in the Data Store, adds a row to Google Sheets, and updates a ClickUp task with custom fields. The workflow also includes Data Store and Slack actions after the ClickUp update.
The Solution
The Make scenario automates the order-fulfilment process by connecting the relevant applications in a single workflow.
Shopify: Triggers the scenario when a new order is fulfilled and retrieves the order details.
Data Store: Searches for a matching record using the available order information.
Google Sheets: Adds a row containing the order information.
ClickUp: Updates a task with custom fields using the processed order details.
Data Store: Performs a follow-up action to delete a record.
Slack: Creates a message as part of the workflow.
How It Works
1. Shopify Order Trigger
The workflow starts when Shopify detects a newly fulfilled order. This event initiates the scenario and provides the order information for subsequent steps.
2. Retrieve Order Details
The scenario retrieves the corresponding order details from Shopify so they can be used by the following modules.
3. Search the Data Store
The workflow searches the Data Store for a record associated with the order. This step helps the scenario use the available stored information before continuing.
4. Add a Row to Google Sheets
The order information is added to Google Sheets, creating a record of the fulfilled order in the spreadsheet.
5. Update the ClickUp Task
The scenario updates a ClickUp task using custom fields. This connects the order-processing workflow with task management.
6. Perform Follow-up Actions
After the ClickUp update, the scenario branches into two actions: deleting a record from the Data Store and creating a message in Slack.
Image: Screenshot of working automation of make.com
Workflow Architecture
Tools and Integrations
Make: Connects the applications and orchestrates the automation.
Shopify: Supplies the order event and order details.
Data Store: Searches and deletes records.
Google Sheets: Stores order information in a spreadsheet.
ClickUp: Updates tasks with custom fields.
Slack: Creates a message through the workflow.
Outcome
The scenario connects Shopify order fulfilment with spreadsheet recordkeeping, ClickUp task updates, Data Store operations, and Slack messaging. It brings these actions together in one Make automation, reducing the need to perform each connected step manually.
Python MCP Server Connecting Claude to a Field-Service CRM
A hosted, OAuth-protected MCP server in Python that lets a home-services business ask Claude about customers, jobs, invoices and leads, with write actions hidden unless allowed.
Section: Python Automation
Project Overview
This project connects Claude to Housecall Pro, enabling a home-services business to ask questions about customers, jobs, invoices, and leads through an MCP server built with Python and FastMCP.
Technology: Python, FastMCP, OAuth 2.0, REST API, Railway, Claude
01. The Problem
The business wanted to interact with its field-service data through Claude and perform permitted actions without giving the AI direct access to the raw database.
02. The Solution
A Python MCP server was developed to expose the Housecall Pro REST API through approximately 20 domain modules, covering customers, jobs, estimates, invoices, leads, employees, scheduling, webhooks, and more.
The server is hosted on Railway and connects to claude.ai.
03. Key Features
OAuth 2.0 Authentication: Uses GitHub as the OAuth provider, with authentication redirecting back to claude.ai.
Domain-Specific Tools: Organizes tools into namespaces such as customers_*, jobs_*, and invoices_*.
Read-Only Enforcement: Middleware hides tools containing create, update, delete, send, void, or dispatch in their names unless explicitly allowed.
REST API Integration: Exposes field-service functionality through a unified FastMCP application.
Hosted Deployment: Runs on Railway for connection to Claude.
04. How It Works
The user authenticates through the OAuth login flow.
Claude connects to the hosted MCP server.
FastMCP exposes the available CRM tools through domain-specific modules.
Permission middleware determines which tools are visible to the agent.
Claude uses the available tools to interact with the field-service CRM API.
Image: The server entry point: GitHub OAuth in front, one FastMCP app, and each domain module (customers, jobs, estimates, invoices, leads, employees) mounted under its own namespace.
05. Workflow
06. Implementation
The server entry point mounts the CRM domain modules under one FastMCP application. Each module handles a specific area of the field-service API, while OAuth authentication and permission middleware control access to the available tools.
Image: The repository: one Python module for each area of the field-service API, plus a Procfile for deployment on Railway. The commit messages are blurred.
The repository contains separate Python modules for the different API domains and a Procfile for Railway deployment.
07. Outcome
The solution provides Claude with a structured interface to field-service CRM data, with OAuth authentication, domain-specific tool namespaces, and protocol-level controls over which actions are exposed to each agent.
Developed an app script to automatically update columns in an inventory sheet based on values in another sheet, enabling seamless data synchronization within Google Sheets.
Section: Google Apps Script
Automated Column Management in Inventory Sheet
Automating inventory column updates and synchronizing information between Google Sheets using Google Apps Script.
Project Overview
This project uses Google Apps Script to update columns in an inventory sheet based on values in another spreadsheet. It also provides custom menu options for updating inventory values and adding leading zeros.
Tools: Google Apps Script, Google Sheets.
01. The Challenge
Maintaining inventory information across linked spreadsheets requires consistent updates. Manual changes can leave records out of sync, while inventory values such as SKU and location codes may require leading zeros to be preserved.
02. The Solution
A Google Apps Script solution was developed to automate inventory updates and synchronize relevant column values between spreadsheets.
The scripts provide custom menu actions to run inventory updates and normalize leading zeros when needed.
03. How It Works
Read spreadsheet data: The script accesses the main spreadsheet and relevant inventory sheets.
Compare records: It reads client information and account status values to identify the records that need processing.
Update inventory columns: The script updates inventory-related values based on the information in the linked spreadsheet.
Run custom actions: Users can select options from the Google Sheets custom menu to update inventories or add leading zeros.
04. Workflow Architecture
The workflow connects the main spreadsheet, Google Apps Script, and the linked inventory spreadsheet.
Custom Menu Actions
The provided Apps Script screenshots show these menu options:
Update Inventories — runs the inventory update function.
Add Leading Zeros — runs the function for adding leading zeros.
05. Implementation Screenshots
Inventory synchronization
The first screenshot shows the Apps Script function for checking account status and synchronizing information between the main sheet and a linked inventory spreadsheet.
Image: Syncing active/inactive status between a main sheet and a linked inventory spreadsheet.
Custom inventory menu
The second screenshot shows the custom menu available in Google Sheets for running inventory updates and adding leading zeros.
Image: A custom menu for updating inventory values and normalizing leading zeros on demand.
06. Tools and Integrations
Google Apps Script: Executes the inventory update and leading-zero functions.
Google Sheets: Stores inventory records and provides the interface for running custom menu actions.
07. Outcome
The solution automates inventory column updates between linked spreadsheets and provides on-demand menu actions for inventory updates and leading-zero normalization.
AI-Powered Social Post Generator: From Spreadsheet to Socials in Seconds!
Automatically create short, engaging, and fact-based posts (with emojis!) based on your content ideas, and publish them to the right platform.
Section: AI Agents
AI-Powered Social Post Generator
Automatically turn content ideas in Google Sheets into engaging, platform-specific social media posts using Google Gemini, with publishing routed to LinkedIn or X.
Category: AI Agents Tools: Google Sheets, Google Gemini, LinkedIn, X (Twitter)
1. Project Overview
This workflow automates social media content creation and publishing. It reads content ideas and the selected platform from Google Sheets, uses Google Gemini to generate a short, fact-based post, and routes the result to the appropriate social network.
2. The Challenge
Creating and publishing social media content manually involves several repetitive steps:
Reviewing content ideas in a spreadsheet.
Writing posts suitable for each social platform.
Checking which ideas have already been published.
Copying and pasting content into the correct platform.
Keeping track of publishing status.
These tasks can slow down content production and create unnecessary manual work.
3. The Solution
An AI-powered workflow connects Google Sheets with Google Gemini and social media publishing tools.
The workflow starts manually when the user clicks Test workflow. It reads the spreadsheet, checks publication status, generates content with Gemini, and uses conditional logic to route the post to LinkedIn or X according to the selected platform.
4. How the Workflow Works
Image: n8n workflow
Manual Trigger: The user starts the workflow with a click.
Read Google Sheets: Retrieve content ideas and their target platforms.
Check Publishing Status: Select ideas marked 0, indicating they have not yet been published.
Generate Social Content: Google Gemini creates a concise, fact-based post with suitable emojis.
Route by Platform: Conditional branches determine whether the post should go to LinkedIn or X.
Publish the Post: The appropriate platform integration handles publishing.
5. Workflow
6. Key Features
Spreadsheet-Driven Content: Manage content ideas and platform choices in one place.
AI-Assisted Writing: Generate concise, engaging posts with Google Gemini.
Publication Status Filtering: Avoid selecting ideas already marked as published.
Platform-Based Routing: Send content to LinkedIn or X based on the selected destination.
One-Click Execution: Start the workflow manually when content is ready.
7. Business Value
The workflow reduces repetitive writing and publishing tasks, makes content production more organized, and simplifies the process of turning spreadsheet ideas into social media posts.
8. Final Outcome
A streamlined content workflow that connects Google Sheets, Google Gemini, and social media publishing integrations—helping users move from a content idea to a platform-specific post with less manual effort.
A centralized dashboard for managing one-way and two-way synchronization across Monday.com boards
Section: Python Automation
Overview
The platform synchronizes project and deal information from the PM board to Media Buyer and Account Strategist boards, while keeping the Master CRM and individual closer boards aligned through separate two-way workflows. Each workflow maintains its own configuration, field mappings, and execution logs.
The Problem
Teams working across multiple Monday.com boards may need to repeat updates manually. This can leave records inconsistent and makes it harder to manage changes from both sides, prevent repeated updates, and identify synchronization errors or skipped records.
How It Works
Identify records: The workflow checks configured Monday.com boards through automatic polling or a supported manual run.
Match destination items: Board relationships, role mappings, and linked item identifiers are used to find the corresponding record.
Apply field mappings: Configured rules determine which fields are synchronized and in which direction.
Create or update records: Missing items are created where configured; existing matching items are updated.
Apply safeguards: Two-way workflows use conflict policies and loop-prevention rules to avoid repeatedly processing their own updates.
Record the outcome: Each workflow logs successful updates, skipped records, errors, and execution detail.
The Result
The platform brings multiple board synchronization workflows into one dashboard. Teams can keep configured records aligned, manage one-way and two-way updates separately, and review execution logs to understand what was synchronized, skipped, or unsuccessful.
Results & Performance Metrics
Metric
Observed Result
Records synchronized
295
Errors encountered
4
Records skipped
2
Records dropped
0
Monitoring availability
24/7
Synchronization interval
18 seconds
Tech Stack
Python: Core application and synchronization logic.
Flask: Web application and dashboard backend.
SQLite: Stores synchronization state and execution records.
Monday.com API / Monday SDK: Accesses board data and applies updates.
HTML, CSS and JavaScript: Provide the dashboard interface and frontend interactions.
Where This Pattern Applies
This solution helps businesses keep information consistent across multiple Monday.com boards and teams.
The same approach can be used in:
Sales & CRM: Synchronize client records, deals, and ownership.
Project Management: Keep project details, deadlines, and statuses aligned.
Media Buying: Share campaign and client information across teams.
Account Management: Maintain consistent client records and responsibilities.
Marketing: Coordinate campaigns and team activities.
Business Operations: Synchronize operational records across departments.
The underlying pattern remains the same: identify matching records, apply configured field mappings, create or update items, handle conflicting changes, and log synchronization results.
A Looker Studio dashboard rolling up Facebook ad spend, revenue, ROAS and profit margin across a 9-month window.
Section: Looker Studio
01. Project Overview
This dashboard is part of a larger multi-channel paid media reporting setup. It provides a dedicated view of Facebook advertising performance, allowing marketing and finance teams to review campaign-related spending, revenue, and performance indicators in one place.
Paid Media Reporting
Part of a larger multi-channel Looker Studio report, this page rolls up spend, revenue and profit for Facebook campaigns specifically, alongside a daily revenue-vs-spend trend.
$3.94M: Facebook spend (9 mo.)
$3.99M: Facebook revenue
1.01: Facebook ROAS
27,184: Orders
The dashboard runs on Looker Studio so paid media and finance read from the same live numbers instead of a separate export from Meta.
02. The Challenge
Facebook advertising performance involves several interconnected metrics. Reviewing spend, revenue, purchases, orders, ROAS, and profit margin separately makes it harder to understand overall performance across a reporting period.
A consolidated dashboard helps make these indicators easier to review and compare.
03. The Solution
A dedicated Facebook Ads overview was created in Looker Studio, combining key financial and performance metrics with a revenue-versus-spend trend chart.
The dashboard includes:
Spend and Revenue: Compare advertising costs with reported revenue.
Profit and Profit Margin: Review the displayed profitability metrics.
ROAS: Monitor return on advertising spend.
Purchases and Orders: Track the conversion and order-volume figures shown in the report.
CPP: Review cost per purchase.
Hook Rate: Monitor the displayed creative-engagement indicator.
Date Filtering: Review performance across a selected period.
04. Dashboard Overview
The dashboard presents high-level KPIs at the top and a revenue-versus-spend chart below. This makes it easier to scan the main figures and observe how spending and revenue move over time.
Image: Facebook performance overview across a 9-month window: spend, revenue, ROAS and profit margin alongside a daily revenue-vs-spend trend.
Dashboard highlights:
Facebook spend: $3.94M
Facebook revenue: $3.99M
ROAS: 1.01
Orders: 27,184
Profit: -$1.03M
Profit margin: 1.21%
These figures are reproduced from the supplied dashboard screenshot. The displayed profit and profit-margin figures may require reconciliation before being used for financial decisions.
05. Technology and Integration
Looker Studio: Dashboard visualisation and reporting.
Meta Ads: Facebook advertising performance data.
The report provides a dedicated Facebook performance view within the wider multi-channel reporting environment.
06. Outcome
The dashboard brings Facebook advertising and financial indicators into one reporting interface. It supports performance reviews by making spend, revenue, order volume, and ROAS easier to compare without relying solely on separate platform views or manual exports.
Reports that used to take days across sites now land by 6am, and we act on them the same morning.
The network ran on four disconnected systems: scheduling, the EHR, billing/claims and finance. Leadership could never see patient flow, provider utilisation and revenue-cycle health in the same place, and each site’s monthly report was rebuilt by hand. I consolidated all four into one governed Power BI model behind two role-based dashboards, refreshed automatically every morning, turning days of manual reporting into a screen the team reads with their coffee.
What Was Leaking
Siloed systems: Scheduling, EHR, billing and finance never lined up, so no-shows, utilisation and collections couldn’t be seen together.
Manual per-site reporting: Every site’s pack was rebuilt by hand (weeks behind by the time it landed, and easy to get wrong).
Invisible revenue leakage: Denials, AR aging and slow collections weren’t tracked in one place, so cash slipped through unnoticed.
Dashboard One: Patient Flow & Utilisation
Appointments vs utilisation, department mix, top sites, a day-by-hour utilisation heat map and capacity gauge.
Utilisation heatmap: Spots under-used clinic slots by day and hour at a glance.
Sites & departments: Ranks volume and no-shows together, site by site.
Volume vs utilisation: Pairs appointment growth with the utilisation trend.
Capacity gauge: Tracks attainment against the plan, currently 96%.
Dashboard Two: Revenue Cycle & Claims
Billed vs collection rate, a claims funnel, AR aging buckets and net revenue by payer.
Image: Revenue Cycle & Claims
Claims funnel: Shows where submissions fall out before they’re paid.
AR aging: Flags the £84K stuck in 90+ days for chase-up.
Billed vs collected: Tracks the collection rate month over month.
Payer mix: Splits net revenue across NHS, insurers and self-pay.
How It’s Built
Stage
What We Built
Tools
Sources
4 systems: Scheduling · EHR · Billing · GL
REST / API / file connectors
Clean
Key standardisation
Power Query
Model
Star schema, shared date table, DAX
Power BI model + DAX
Secure
RLS by site, per-site access
RLS roles
Deliver
06:00 refresh via gateway & service
Power BI Service + gateway
The Impact
After six weeks
+5.0pts: Provider utilisation
−2.1pts: No-show rate
−6 days: Days in AR
3 days → 0: Manual reporting
With utilisation and no-shows visible by site and hour, the network reallocated clinic slots and tightened reminders, lifting utilisation five points while trimming no-shows, and replacing days of manual work with an automatic 6am refresh reconciled to the ledger.
LoanPro MCP Server: AI-Powered Financial Data Access & Account Analysis
Connecting AI assistants to LoanPro through a secure Model Context Protocol server for customer lookups, loan data retrieval, and past-due account triage.
Section: AI Agents
Overview
Accessing customer and loan information in LoanPro previously required users to search records and review account details manually. A custom MCP server now connects AI assistants such as Claude with LoanPro, allowing users to retrieve financial information and review accounts through conversational requests.
The Problem
Loan and customer information is stored inside LoanPro, while users want to access and understand it through conversational AI. Manually searching for customers, opening loan profiles, and reviewing transactions and balances makes account reviews repetitive. Identifying past-due accounts that meet specific balance thresholds also requires retrieving and filtering records. An integration layer was needed to connect AI assistants with LoanPro through controlled API operations.
How It Works
Submit a Request: A user asks Claude to find a customer or review a loan account.
Connect Through MCP: The AI client connects to the Go-based MCP server using SSE or stdio.
Select a Tool: The assistant selects an available tool, such as search_customers, and provides the required arguments.
Process the Request: The server prepares the corresponding LoanPro API operation.
Retrieve Financial Data: The server requests customer, loan, transaction, or balance information from LoanPro.
Normalize the Response: Go processes the returned JSON data and handles inconsistent identifier formats.
Apply Review Logic: Available tools and predefined prompts support customer reviews and past-due account filtering.
Return Results: The processed information is sent back to the AI assistant for a readable response or account summary.
Architecture flow:
Tech Stack
Tool
Purpose
Go
MCP server and request processing.
MCP
Connects AI assistants with LoanPro tools.
LoanPro API
Retrieves customer and financial records.
Claude
Conversational AI interface.
Docker
Containerized deployment.
The team can continue using LoanPro while accessing its selected capabilities through a compatible AI assistant.
Where This Pattern Applies
This solution is not limited to loan management. The same approach can connect AI assistants with business platforms through APIs.
Example — Insurance: An AI assistant can retrieve policyholder records, access claim information, and prepare summaries for review.
Other applications include:
Banking: Customer accounts and transaction reviews.
Healthcare: Authorized patient record retrieval.
Legal Services: Client and case information searches.
Property Management: Tenant records and payment reviews.
Customer Support: Customer profiles and support history.
The general pattern is to connect an AI assistant to a business API through a dedicated server, expose specific tools, retrieve relevant data, and return structured results. The API, available tools, and business rules change according to the platform.
An automated content generation system that transforms viral social media posts into original, branded creatives for more than 100 Facebook pages using n8n, Airtable, and AI agents.
Section: n8n Automations
Overview
This solution makes it easier to create and manage content for more than 100 Facebook pages. Airtable is used as the main workspace, while n8n handles the automation. The system collects source content, rewrites captions, recreates images, and adds branding for each page. Virtual assistants can then review the content and schedule it through Post Planner.
The Problem
Managing content for many Facebook pages takes a lot of time and effort. Virtual assistants have to find trending posts, rewrite captions, recreate images, and add the correct branding for each page. Doing all of this manually makes the process slow and difficult to manage. A single system was needed to bring these tasks together and make content creation easier.
How It Works
Submit Source Content: Virtual assistants add a link to a trending post, meme, or news item in Airtable.
Collect Source Content: n8n retrieves the content and related information from the submitted link.
Rewrite Captions: AI agents rewrite the original captions to create fresh versions.
Recreate Images: AI tools process the original images and create new versions.
Add Page Branding: The system applies the correct templates, logos, and branding for each Facebook page.
Save the Final Content: The generated captions and images are saved in Airtable for review.
Schedule Posts: Virtual assistants review the completed content and schedule it through Post Planner.
Result
The system brings content collection, AI content creation, and page branding together in one workflow.
Supports content management for more than 100 Facebook pages.
Reduces the manual work involved in writing captions and creating images.
Produces branded content ready for review and scheduling.
Gives virtual assistants one place to manage their daily content tasks.
Uses separate n8n workflows to handle different content-generation tasks.
Tech Stack
n8n: Automates the workflow and manages content processing.
Airtable: Provides a workspace for submitting source links and reviewing generated content.
AI Agents: Rewrite captions and help create new images.
Post Planner: Used to schedule completed posts.
Facebook Pages: The platforms where the content is published.
Where This Pattern Applies
This approach can help any organization that manages content for multiple social media accounts.
Digital Marketing Agencies: Create and manage content for different clients.
Media Companies: Turn trending topics into new social media content.
Social Media Teams: Make daily content creation faster and easier.
Content Publishers: Manage content production across multiple pages.
Brand Networks: Keep branding consistent across different social media accounts.
The same approach can be used to collect content, create new versions with AI, add the right branding, and prepare posts for publishing from one central workspace.
A Google Sheets weekly tracker that brings Google Analytics traffic and Klaviyo email and SMS performance into one view.
Section: Dashboards & Reporting
1. Project Overview
This project brings acquisition and retention metrics together in a centralized Google Sheets tracker. Marketing teams can review website traffic, customer acquisition, email and SMS sales, and subscriber growth without switching between separate platforms.
Category: Dashboards & Reporting
Tools: Google Sheets, Google Analytics, Klaviyo
2. The Challenge
Marketing performance data was spread across different platforms, making it harder to compare acquisition and retention results in one place.
Fragmented reporting: Website traffic and email/SMS performance were tracked separately.
Limited visibility: Reviewing performance across channels required switching between tools.
Manual comparison: Comparing results across weeks and months required a consolidated reporting view.
3. The Solution
A centralized Google Sheets tracker organizes Google Analytics and Klaviyo metrics into weekly and monthly dashboards.
The tracker includes:
Website traffic: Total traffic, new users, new customers, and engagement time.
Acquisition channels: Organic search, organic social, paid search, paid social, direct, and other traffic sources.
SMS performance: SMS sales, subscriber totals, and new subscribers.
Historical comparison: Weekly and monthly views for comparing performance over time.
4. How It Works
The tracker brings data from both platforms into one reporting view, where the team can compare acquisition and retention metrics over time.
Workflow
Google Analytics + Klaviyo → Consolidated Google Sheets Tracker → Weekly & Monthly Dashboards → Marketing Performance Review
5. Dashboard Highlights
Weekly Dashboard
The weekly dashboard displays traffic sources alongside Klaviyo email and SMS performance. Teams can review weekly changes in website acquisition, sales, and subscriber growth.
Monthly Dashboard
The monthly dashboard provides a broader reporting view for reviewing performance trends over a longer period.
Image: Weekly dashboard tracking Google Analytics traffic by source alongside Klaviyo email and SMS sales and subscriber counts.
6. Business Value
Centralized reporting: Acquisition and retention metrics are available in one spreadsheet.
Cross-channel visibility: Website traffic can be reviewed alongside email and SMS results.
Historical comparison: Weekly and monthly views support trend analysis.
Simplified reporting: Teams can review key marketing metrics without manually assembling separate platform reports.
7. Final Outcome
The Weekly Marketing Performance Tracker provides a single reporting view for Google Analytics traffic and Klaviyo email and SMS performance. By organizing these metrics into weekly and monthly dashboards, it makes cross-channel performance easier to review and compare.
Technology Stack: Google Sheets, Google Analytics, Klaviyo
Automating the conversion of Slack requests into structured and assigned Monday.com tasks.
Section: Make Automations
1. Overview
This automation connects Slack with Monday.com to convert qualifying messages into structured tasks. An AI agent extracts task details from the original Slack message, while configured mappings determine the appropriate Monday.com board and task owner. The workflow also creates explicitly listed subtasks and sends a confirmation back to Slack.
2. The Problem
Teams often share work requests through Slack, but important action items can get buried in conversations. Manually converting these requests into Monday.com tasks requires reviewing messages, extracting details, selecting the correct board, and assigning owners. This repetitive process takes time and can result in inconsistent task information or missed action items.
3. How It Works
Capture Slack Event: The workflow detects qualifying Slack messages or reactions through a configured event trigger.
Retrieve Original Message: It retrieves the complete Slack message to provide context for AI processing.
Extract Task Information: The AI agent generates a task title and description and identifies mentioned Slack user IDs and explicitly listed subtasks.
Retrieve User Details: The workflow uses extracted Slack IDs to retrieve the corresponding user information where required.
Determine Board and Owner: Configured user and channel mappings identify the appropriate Monday.com board, group where applicable, and task owner.
Create Monday.com Task: The workflow creates the main task using the extracted title and adds its description and original Slack message context.
Create Subtasks: If the request contains explicitly listed subtasks, the workflow iterates through them and creates them under the main task.
Send Slack Confirmation: After task creation, the workflow sends a confirmation in the original Slack conversation with a link to the Monday.com task.
4. The Result
The automation connects Slack requests directly with Monday.com task management. It reduces manual task entry, structures incoming requests, applies configured board and owner mappings, and preserves the original conversation context. It also supports automatic subtask creation and sends confirmation through Slack.
Execution Metrics
Metric
Result
Total Executions
4,856
Successful Executions
4,826
Failed Executions
16
Success Rate
99.4%
Average Execution Time
0.63 seconds
Metrics are based on the available execution logs and may vary depending on message volume, task complexity, and the number of subtasks processed.
5. Tech Stack
Make: Coordinates the automation, processes Slack events, manages AI extraction, handles routing, and creates Monday.com tasks and subtasks.
Slack: Provides the triggering messages or reactions, original conversation context, user information, and task confirmations.
OpenAI: Uses GPT-4.1 mini and GPT-4.1 nano to extract and structure task information from Slack messages.
Monday.com: Receives the structured tasks, mapped owners, and explicitly listed subtasks.
6. Where This Pattern Applies
This automation pattern can be applied wherever teams receive work requests through communication platforms and need to organize them in task-management systems. Examples include internal operations, customer support, marketing coordination, project management, and administrative task tracking.
AI-Powered Contract Validation, Human Review, Automated Google Drive Filing, Folder Organization, Missing-Term Detection & Document Tracking.
Section: Custom SaaS Platforms
Overview
The Contract Intake Tool is a web app that uses Claude AI to extract key terms from supplier contracts, flags missing information for human review, and automatically files approved contracts into the correct Google Drive folders. It also maintains a record of all filing activities..
Business Problem
Supplier contracts such as hotel, venue, and bus services) Were reviewed and filed manually, making the process time-consuming. Important terms like cancellation clauses, fees, and tax rates could be missed, and contracts sometimes ended up in the wrong Google Drive folders, making them difficult to find later for billing or disputes.
Proposed Solution
Supplier contracts (hotel, venue, bus) were being reviewed and filed by hand. That was slow, and important terms (cancellation clauses, fees, tax rates) could get missed, and contracts sometimes ended up in the wrong Drive folder, making them hard to find later for billing or disputes.
Goal
ut the manual review time per contract
Make sure required terms are never silently missed
File every contract into the exact right folder, every time, with no human guesswork
Keep a record of who filed what, and when
How It Works
1. Scan
User uploads the PDF and picks a category (Hotel / Venue / Buses / Other). The text is extracted from the PDF and sent to Claude (Anthropic’s AI), which pulls out the specific terms that category requires, e.g. for Hotel: room rate, attrition clause, cancellation terms, tax rate. Each term comes back marked Found or Not Found.
2. Review
Anything Not Found must be manually checked and ticked off by a person before the contract can be filed. The tool never files something incomplete without a human saying it’s okay.
Image: The review screen after a scan: each key term (group name, number of rooms, rate, attrition, cancellation, additional fees and tax rate) with the text found in the contract and a Found status, plus a File button. The group name and company name are blurred.
3. File
Using the contract’s group name (e.g. “State University - Alpha Chapter”) and date, the tool works out the correct folder path, Year → Season → University → Chapter → Category, and uploads the PDF there automatically. It only creates the last two folder levels itself; everything above that must already exist in Drive. Every filing is logged (who, what, where).
Image: The Google Drive folder tree the contracts are filed into: Formal Contracts, then the year, then (inside 2027) a season folder, Spring 2027, and a group folder. One folder name and its owner are blurred.
Key Features
AI-Powered Term Extraction: Extracts required contract terms using Claude AI.
Missing Term Review: Flags missing information (Not Found) for manual review before filing.
Automated Google Drive Filing: Files contracts into the correct folder based on group name, date, and category.
Filing Activity Log: Records who filed the contract, what was filed, where it was stored, and when.
Category-Based Checks: Checks contract terms according to the selected category (Hotel / Venue / Buses / Other).
What It’s Built With
Next.js (web framework) + TypeScript, Google Drive API, Claude for the AI extraction, Postgres for the log. PDF text extraction is done with a JavaScript library.
An AI reporting system that pulls Meta Ads data, flags underperforming ads in real time, and recommends budget and creative changes.
Section: AI Agents, AI Agents for Ecommerce
AI-Powered Meta Ads Reporting
Automating Meta Ads performance reporting, identifying underperforming campaigns, and generating AI-driven optimization recommendations.
Project Overview
This system is designed to collect Facebook and Instagram campaign data, analyze performance using AI, and recommend changes to budgets, targeting, and creatives. It aims to help marketers make faster, data-driven decisions while reducing manual reporting work.
Platforms: Meta Ads, Instagram
01. The Problem
Manual campaign analysis required marketers to collect data across campaigns and ad sets, identify underperforming ads, and decide when to adjust budgets or creatives. This process was time-consuming and made timely optimization difficult as campaigns scaled.
02. The Solution
An AI-powered reporting system designed to automate data collection, analyze campaign performance, flag potential issues, and provide actionable recommendations for improving campaign results.
03. Key Features
Automated Data Collection: Collect campaign-, ad set-, and ad-level metrics.
AI Performance Analysis: Identify trends, anomalies, and underperforming ads.
Budget Recommendations: Suggest budget reallocations based on performance.
Real-Time Alerts: Flag deviations from defined performance benchmarks.
Natural Language Interaction: Allow users to request campaign insights and changes using natural language.
Performance Tracking: Monitor metrics such as CTR, CPA, ROAS, conversions, spend, and impressions.
04. System Workflow
05. System Architecture
Phase 1 — Data Collection and Normalization
Collect campaign metrics, including impressions, clicks, CTR, conversions, ROAS, CPA, spend, and budget utilization, then prepare the data for analysis.
Phase 2 — AI-Powered Analysis
Analyze performance data to detect trends, anomalies, low ROAS, and CTR below defined benchmarks.
Phase 3 — Optimization Recommendations
Generate suggestions for budget allocation, audience targeting, and creative improvements, prioritized by their potential impact on KPIs.
Phase 4 — Reporting and Alerts
Present performance metrics in dashboards and notify users when defined KPI thresholds are breached.
Phase 5 — AI-Assisted Campaign Management
Allow users to request campaign changes through natural language, with validation and tracking of adjustments and their subsequent KPI impact.
06. Reported Results
The original case study reports the following outcomes after automation:
Reporting time reduced from 6–8 hours to under 1 hour per week.
90% of underperforming ads flagged in real time.
Campaign response time reduced from 1–2 days to under 1 hour.
Reported ROAS improvement of 15–25%.
Approximately 7 hours saved per marketer each week.
Campaign management scaled from 10 to 50+ ad sets without additional staff.
Human errors in campaign adjustments reduced by approximately 90%.
These figures are reported in the supplied case study and have not been independently verified.
07. Final Outcome
The system aims to replace repetitive manual analysis with automated reporting, AI-generated insights, performance alerts, and optimization recommendations, allowing marketers to focus more on campaign strategy and testing.
A centralized analytics dashboard for monitoring orders, inventory levels, shipping performance, unit economics, and stock alerts.
Section: Looker Studio
Overview
Managing supplement operations requires visibility into orders, inventory, shipping, product costs, and stock alerts. This project brings these areas together in an interactive Google Looker Studio dashboard, allowing users to review operational information, apply filters, and monitor different business activities from one interface.
The Problem
Operational information is often spread across separate reports and spreadsheets. Reviewing order statuses, checking stock availability, comparing regional shipping costs, and identifying inventory warnings can require repeated manual filtering and switching between data views.
A centralized dashboard was needed to organize these areas and make operational information easier to access, compare, and review.
How It Works
Access the Dashboard: Users open the dashboard and navigate through the sidebar to the required operational section.
Review Orders: The Order Management section displays product details, quantities, order statuses, expected delivery dates, and tracking information.
Monitor Inventory: Users review available stock, days and weeks of supply, regions, and critical or warning indicators.
Check Inventory Forecasts: The forecasting view presents current stock alongside average demand over 14 and 30 days and replenishment recommendation fields.
Analyze Shipping: The Shipping Analytics section compares regional shipping costs and average bottles per order.
Review Unit Economics: Users examine product prices, stock in hand, expiry dates, and cost of goods sold (COGS).
Monitor Alerts: The Alerts section presents alert distribution and recent shipment-related notifications.
Filter and Investigate: Available search fields, product filters, region selectors, and status filters help users narrow the information and identify records requiring attention.
Result
The dashboard provides a single interface for reviewing six operational areas: Overview, Order Management, Inventory, Shipping Analytics, Unit Economics, and Alerts.Users can move between dedicated reporting views, compare regional and product-level information, review inventory conditions, and identify shipment-related alerts without switching between separate reporting interfaces.
Metric
Observed Output
Items tracked daily
170
Alert channels
2 (Email + Slack)
Source platforms
3 (Amazon, Shopify + Google Sheets)
Alert levels
2
Tech Stack
Google Looker Studio: Dashboard interface, interactive filters, data tables, charts, and operational reporting.
Where This Pattern Applies
The same dashboard approach can be used by businesses that need to monitor several operational areas through one reporting interface.
E-commerce: Track orders, inventory, shipping, and product performance.
Retail: Monitor stock availability, replenishment needs, and sales operations.
Warehousing: Review inventory levels, stock movements, and fulfillment activity.
Logistics: Compare regional shipping costs and delivery performance.
Manufacturing: Monitor material availability, product costs, and operational indicators.
Distribution: Review order status, regional inventory, and shipment alerts.
The general pattern is to organize information from different operational areas into dedicated dashboard views, provide relevant filters and indicators, and make important records easier to review.
Production Linux Server Audit and Repair for a Data Subscription Site
An audit of the single Ubuntu server behind a financial-data subscription site, a fix for its silently failed social-posting pipeline, and a documented setup so it can be maintained safely.
Section: Python Automation
Project Overview
A financial-data subscription site ran its Python backend, data pipelines, scheduled jobs, publishing automation, and social-posting pipeline on a single Ubuntu VPS. The project focused on auditing the server, repairing a silently failed social-posting pipeline, and documenting the setup for safer maintenance.
The server supported several interconnected services and automated workflows. The social-posting pipeline had silently stopped working, and the client needed a server audit, a repair, and a clear maintenance roadmap.
02. What Was Done
Audited systemd units, cron jobs, logs, Nginx, Gunicorn, the SQLite database, and the backup job.
Prepared a plain-English client report with a health score and prioritized fixes.
Repaired the social-posting pipeline with two targeted changes and stabilized its scheduling.
Set up a Git mirror of /opt and added a CLAUDE.md file documenting the architecture to support safer maintenance with Claude Code.
03. How the System Runs
Nightly pipeline — 20:00 ET: Ingests OHLC data, runs scanners, builds JSON outputs, backs up the database to Google Drive using rclone, builds the newsletter and blog post, publishes through the WordPress REST API, and sends the daily email through Brevo.
Live pipeline — 15:45 ET: Runs live_pipeline.py for real-time signals and options pricing.
Always-on API: Runs the Gunicorn-hosted Flask API on port 5500 behind Nginx and Cloudflare Tunnel.
Content engine: Scheduled through cron at 08:15, 08:45, every 15 minutes during market hours, and 21:00 to render PNG/MP4 content cards and post to Instagram, X, and TikTok.
04. Workflow
Nightly Data Pipeline
Scheduled systemd Timer → nightly_pipeline.sh → Ingest OHLC Data → Run Scanners → Build JSON → Back Up Database to Google Drive → Build Newsletter and Blog Post → Publish via WordPress REST API → Send Daily Email via Brevo
Flask API → Gunicorn on Port 5500 → Nginx → Cloudflare Tunnel
Social Content Pipeline
Cron Schedule → Content Engine → Render PNG/MP4 Cards → Publish to Instagram, X, and TikTok
20:00 ET systemd timer → nightly_pipeline.sh
ingest OHLC → run scanners → build JSON → DB backup to Drive (rclone)
→ build newsletter + blog post (publish via WP REST API)
→ send daily email (Brevo)
15:45 ET systemd timer → live_pipeline.py (real-time signals + options pricing)
always systemd service → gunicorn Flask API :5500 behind nginx + Cloudflare Tunnel
cron 08:15 / 08:45 / every 15 min market hours / 21:00 → content engine renders PNG/MP4 cards and posts to IG / X / TikTok
05. Technology and Integrations
Python, Flask, SQLite, systemd, cron, Bash, Nginx, Gunicorn, Cloudflare Tunnel, rclone, JWT authentication, Stripe, WordPress REST API, Brevo, and the Post for Me API.
06. Outcome
The server was audited, the failed social-posting pipeline was repaired, scheduling was stabilized, and the architecture was documented to support safer ongoing maintenance.
Automated Meeting Transcription and Case Management
Automating Webex meeting transcript retrieval, case matching, document storage, and record tracking using Zapier.
Section: Zapier Automations
Overview
Meeting transcripts previously required manual handling, from retrieving recordings and identifying the correct client case to storing documents and updating tracking records. The Zapier automation connects these steps, using Calendly matching or AI-assisted case identification to route transcripts into the appropriate Box folders and update Google Sheets.
The Problem
Teams handling Webex meetings need to retrieve transcripts, identify the correct client or case, and store documents in the right folders. When these tasks are handled manually, transcripts can be difficult to match with the correct records, and tracking sheets may not stay up to date. Managing different meeting sources also adds repetitive work and increases the chance of misplaced or untracked documents.
How It Works
Capture Meeting Information: A webhook starts the workflow when meeting-related data is received.
Retrieve Meeting Details: Webex provides meeting information and participant details.
Check Transcript Availability: Filters check whether the meeting meets the required transcription conditions.
Format Meeting Data: Meeting dates and times are prepared for further processing.
Match the Meeting: Zapier routes the meeting through either Calendly matching or AI-assisted case identification.
Identify the Case Folder: The workflow locates the corresponding folder in Box.
Process the Transcript: The transcript is retrieved and uploaded to the appropriate Box folder.
Update Records: Google Sheets records the meeting and processing information.
Results
The automation brings transcript retrieval, case matching, document storage, and tracking into one coordinated workflow. It provides two matching paths for handling meetings and helps keep transcript files and associated case records organized across connected applications.
Tech Stack
Tool
Role in the Workflow
Zapier
Connects applications and manages filters, loops, and workflow paths.
Webex
Provides meeting details, participant information, and transcript access.
Calendly
Supplies event information for meeting matching.
AI by Zapier
Assists in identifying case numbers from client records.
Microsoft Excel
Provides case-related information through CSV data.
Box
Stores transcripts in the relevant folders.
Google Sheets
Maintains meeting and processing records.
The team can continue using its existing applications without needing to move its meeting records or document storage to a new platform.
Where This Pattern Applies
This solution is not limited to meeting management. The same approach can help any team that needs to match incoming documents or records with existing client information.
Example – Insurance: An incoming claim document can be matched with a customer record, stored in the correct claim folder, and logged in a tracking sheet.
Other applications include:
Legal: Match client documents with case files.
Healthcare: Organize consultation records and related documents.
Recruitment: Match candidate documents with applications.
Financial Services: Route transaction documents to customer records.
Customer Support: Attach incoming correspondence to support cases.
The general pattern is to capture incoming information, identify its matching record, store the associated document, and update the tracking system. The matching rules and connected applications change according to the business process.
AI-Powered RAG Chatbot for The Fast Bite: Seamless Ordering and Query Handling
Create an AI-powered chatbot that helps The Fast Bite( a fast food restaurant) customers with menu queries, placing orders, and providing restaurant details in a fast and friendly manner.
Section: AI Agents
AI-Powered RAG Chatbot for The Fast Bite
An AI-powered chatbot that answers customer questions about menu items, restaurant information, and opening hours using an automatically updated knowledge base.
Project Overview
The Fast Bite chatbot uses Google Gemini and Pinecone to retrieve relevant information and generate helpful responses. Restaurant information is processed from files stored in Google Drive, allowing the chatbot’s knowledge base to be updated when new information is added.
Technology Stack: Google Drive, Google Gemini, Pinecone Vector Store
01. The Challenge
Customers need quick answers about menu items, food options, restaurant hours, and other frequently asked questions. Keeping this information current and responding consistently can require manual effort, especially when menu details or restaurant information change.
02. The Solution
An AI-powered Retrieval-Augmented Generation (RAG) chatbot was developed to process restaurant information, store it in a searchable vector database, and use that knowledge to answer customer questions.
The solution combines:
Google Drive: Source for menu and restaurant information.
Google Gemini: Processes information and generates natural-language responses.
Pinecone: Stores searchable vector representations of the processed content.
AI Chatbot: Retrieves relevant information and responds to customer queries.
03. How the System Works
Knowledge Base Preparation
When a new file is added to the designated Google Drive folder, the workflow detects the file and downloads it for processing.
Information Processing
Google Gemini helps process the content into information suitable for retrieval. The processed information is then prepared for storage in the vector database.
Vector Storage
Pinecone stores the processed knowledge so the chatbot can search for relevant information when a customer asks a question.
Customer Query Handling
When a customer submits a question, the chatbot retrieves relevant knowledge and uses an AI model to generate a helpful response based on the available information.
Detailed working Flow:
DEMO
04. Workflow
Image: Simple analogy
05. Key Features
Knowledge Updates: New files can trigger the knowledge-processing workflow.
Context-Aware Answers: Responses use relevant information retrieved from the knowledge base.
Menu Assistance: Helps customers find menu details and food options.
Restaurant Information: Answers common questions, including opening hours, based on available information.
Centralized Knowledge: Keeps restaurant information available through a searchable vector store.
06. Technology Stack
Technology
Purpose
Google Drive
Stores source documents and restaurant information
Google Gemini
Processes content and generates responses
Pinecone Vector Store
Stores and retrieves relevant knowledge
AI Chat Interface
Receives customer questions and displays answers
07. Outcome
The result is a reusable RAG workflow for restaurant customer support that can be maintained by updating the underlying source information.
The Fast Bite chatbot provides a convenient way for customers to ask questions about restaurant information and receive AI-generated answers. By combining Google Drive, Gemini, and Pinecone, the solution connects document updates with knowledge retrieval and conversational responses.
Cold Email Copy Generation with Automatic Quality Checks
An AI tool that writes five cold email sequences in spintax format in minutes and checks each one against eight quality rules, rewriting any that fail.
Section: Python Automation
Overview
Cold email copy generation and quality control. Instead of spending hours writing email variations by hand in spintax format and checking each line against banned phrases and formatting rules, teams now get five production-ready email sequences in minutes.
The Problem
Creating cold email variations meant hours of manual work. Writers had to draft email sequences by hand, then apply spintax format line by line, a tedious process where every variation had to be written and formatted separately. Quality control was completely manual: each line had to be checked against banned phrases and banned words, word counts verified, spintax coverage confirmed, and offer rotation rules checked. With no automated checklist, mistakes slipped through before emails went into the sending tool. Creating five email sequences took 5 to 10 hours of work, was error-prone, and depended entirely on someone being available to do it correctly.
What the Automation Does
Image: The team interface: a chat assistant on the left, a button to generate the week’s strategy, and Copy Variations and History at the top.
Step 1: Email sequences are generated
The automation takes the email parameters and requirements, then uses AI to generate five complete cold email sequences in full spintax format, with multiple variations per email step (A/B variants) so testing options are built in.
Step 2: Automatic quality checks run
Every generated copy is automatically checked against eight quality rules: word count, spintax coverage on every line, banned phrases, banned words, offer accuracy, hook uniqueness, offer rotation compliance, and more. If a copy passes all checks, it is flagged as production-ready. If it fails, the system automatically rewrites it (up to three retries) to meet the requirements.
Step 3: Ready-to-send copies are delivered
The team receives five email sequences with a pass or fail verdict on each. Every copy is either production-ready or clearly flagged as needing manual revision, so there are no surprises or quality issues after the copy goes into the sending tool.
Main Work Flow
Tools and Integrations Used
Custom code automation (AI-powered email generation and quality control)
Anthropic Claude (copywriting and analysis)
Python and FastAPI (backend automation)
TypeScript, React and Next.js (team interface)
The Result
Teams no longer spend 5 to 10 hours writing and quality-checking email sequences by hand. Five production-ready sequences now generate automatically in minutes. Quality control shifted from a manual checklist to an automated pipeline that catches banned phrases, spintax gaps, word count violations and formatting mistakes instantly. Every copy follows the same proven structure with consistent formatting. What used to take hours of manual writing and QA now happens automatically, freeing the team to focus on strategy and testing instead of production work.
Summary
The tool automates the full cycle from email copy generation to quality-checked delivery. Teams provide their email requirements, the automation generates five complete sequences in spintax format, automatic quality checks verify everything, and production-ready emails are delivered in minutes instead of hours. The team stays in control, since they review and approve the output, while the repetitive writing and quality-checking work is handled automatically.
An AI-powered WhatsApp assistant that understands voice notes, text messages, and photos, then answers customer questions using product information stored in Supabase.
Section: n8n Automations, AI Agents for WhatsApp
Overview
This project is a WhatsApp business assistant for an online store. Customers can send a voice note, text message, or product photo and receive an answer based on the store’s product database. The system uses n8n to process incoming messages, OpenAI to understand different input types, and Supabase to retrieve product information. When a customer sends a voice note, the assistant can respond with a voice message. Conversation memory also helps maintain context across messages from the same customer.
The business problem
Online stores receive repeated questions about product availability, prices, and delivery. Customers may ask these questions through text, voice notes, or photos, making them difficult for simple chatbots to handle. Manual replies take time, while inaccurate answers about prices or stock can reduce customer trust.
How It Works
Receive WhatsApp Messages: The WhatsApp Business Cloud API receives customer messages, including text, voice notes, and photos.
Identify Message Type: n8n checks the incoming message and routes it to the correct processing path.
Process Voice and Images: OpenAI transcribes voice notes and analyzes product photos. Text messages are passed through directly.
Prepare the Message: n8n converts each input into a common text format and associates it with the customer's phone number.
Retrieve Product Information: The AI agent uses the Supabase product database to find relevant information before preparing an answer. Conversation memory helps it maintain context.
Send the Response: Text messages receive text replies. When the customer sends a voice note, the answer is converted into speech and returned as a WhatsApp voice message.
The Result
The completed workflow brings voice, text, and image-based customer enquiries into one WhatsApp assistant. It retrieves product information from Supabase before answering, supports both text and voice replies, and maintains conversation context for each customer.
Workflow Delivery Metrics
Metric
Result
n8n nodes after cleanup
21
Supported input types
3
Reply formats
2
AI models used
4
Main agent workflows
1
Workflow defects fixed
2
Note: These figures describe the delivered workflow. Live customer response time, answer accuracy, and sales conversion have not yet been measured.
Tech Stack
n8n: Connects the services and manages the message-processing workflow.
WhatsApp Business Cloud API: Receives customer messages, downloads media, and sends replies.
OpenAI: Transcribes voice notes, analyzes images, generates answers, and converts replies into speech.
Supabase: Stores product information and provides a searchable knowledge source for the AI agent.
Shopify: Relevant to the planned extension for product and order-related functionality; order lookup and replacement-order creation are not part of the current workflow.
Where This Pattern Applies
E-commerce Stores: Answer product questions about prices, availability, and product details.
Retail Businesses: Help customers identify products through photos and ask questions through voice or text.
Customer Support Teams: Handle common enquiries and pass complex issues to human support.
Online Service Providers: Provide customers with a WhatsApp-based assistant for frequently asked questions.
This pattern is useful for businesses that receive customer enquiries through WhatsApp and want to automate responses while keeping answers connected to reliable business data.
AI Calling Agent with Human Handover and Automatic AI Fallback
An AI-powered phone calling workflow using ElevenLabs and Twilio that allows callers to request a human representative and automatically return to the AI agent when the human does not answer.
Section: AI Agents
Overview
This solution is designed to connect an ElevenLabs AI voice agent with Twilio to manage incoming calls and human handovers. When a caller requests to speak with a person, the AI agent initiates a transfer to a designated human number. If the human answers, the caller is connected. If the call is not answered within the configured timeout, Twilio returns the caller to the AI agent so the conversation can continue.
The Problem
An AI calling agent needs to support more than automated conversations. Callers may sometimes need assistance from a human representative, and the transfer process should not leave them disconnected if the representative is unavailable.
A reliable call-handling workflow was needed to support incoming calls, human transfers, and automatic fallback to the AI agent without interrupting the caller's experience.
How It Works
Receive Incoming Call: The caller dials the designated Twilio phone number, which routes the call through the inbound Twilio Function.
Connect to ElevenLabs: The inbound function registers the call with ElevenLabs and connects the caller to the AI voice agent.
Handle the Conversation: The ElevenLabs agent communicates with the caller and handles their request.
Request Human Assistance: When the caller asks for a human representative, the AI agent invokes the connect_to_human webhook tool.
Transfer the Call: The /connect-human Twilio Function initiates the transfer to the designated human phone number.
Handle the Human Answer: If the human answers, Twilio connects the caller and the human representative.
Return to AI When Unanswered: If the human does not answer before the timeout, the /after-dial function redirects the caller back to the AI agent.
Continue the Conversation: The AI agent apologizes for the unavailable representative and continues assisting the caller.
Result
The proposed workflow brings AI call handling, human assistance, and automatic fallback into one connected calling experience.
It is designed to support:
Incoming calls routed to the ElevenLabs AI agent.
On-demand transfers to a human representative.
Automatic return to the AI agent when the human does not answer.
Continued conversations without requiring the caller to restart the call.
The workflow will be validated against three scenarios: a normal AI call, a successful human transfer, and an unanswered human transfer followed by an AI fallback.
Tech Stack
ElevenLabs: Provides the AI voice agent, conversation instructions, and connect_to_human webhook tool.
Twilio: Handles incoming calls, call transfers, and the return-to-AI process.
Call.com: Provides the caller number used for testing.
GHL: Retains the existing calendar functionality without changes.
Where This Pattern Applies
The same approach can be used in voice automation systems where callers need access to both AI assistance and human support.
Customer Support: Transfer complex customer queries to human agents.
Sales: Connect interested prospects with sales representatives.
Appointment Management: Escalate scheduling requests that require human assistance.
Service Businesses: Route customer calls to available staff while maintaining AI support when they are unavailable.
Call Centers: Combine automated call handling with human escalation and fallback.
The general pattern is to let AI handle routine conversations, transfer callers when human assistance is requested, and restore AI support when the human representative is unavailable.
From a Signed DocuSign Contract to a Master Sheet Row and an Itinerary Slide
Turning a signed DocuSign travel contract into a master sheet row, a filed contract and an itinerary slide, automatically.
Section: Make Automations
Project Overview
This Make automation supports operations for a group travel company that manages college formal events.
When a group signs a travel contract in DocuSign, the workflow processes the completed contract and supports three follow-up tasks: recording trip details in the master operations spreadsheet, filing the signed contract in the group's Google Drive folder, and producing a Friday, Saturday, and Sunday itinerary slide.
Tools: Make, DocuSign, Google Apps Script, Anthropic Claude (claude-sonnet-4-6), Google Sheets, Google Slides, and Google Drive.
01. The Challenge
Signed travel contracts contain information that must be transferred into several operational resources, including:
Hotel names and room counts
Check-in ages
Buses and venues
Event times
Food and bar packages
Payment and task due dates
Manually transferring these details into the master sheet, filing the contract, and building a customer-facing itinerary is repetitive and can lead to errors.
02. The Solution
A Make scenario automates the process after a DocuSign envelope is completed. It downloads the signed document, obtains structured contract data through a Google Apps Script web app, and uses Claude to generate the three-day itinerary text.
The workflow then routes the results into three paths: a new-contract path, an addendum path, and an archive path.
03. How It Works
Step 1: Detect the Signed Contract
The workflow starts when a DocuSign envelope is completed.
Step 2: Download the Document
Make downloads the signed contract for further processing.
Step 3: Extract Contract Information
An HTTP request sends the document to a Google Apps Script web app, which returns the contract fields as structured data.
Step 4: Generate Itinerary Text
Claude uses the structured fields to write the itinerary content for Friday, Saturday, and Sunday.
Step 5: Route the Results
A router directs the workflow into three paths:
New Contract: Handles the new-contract path.
Addendum: Handles the addendum path.
Archive: Handles the archive path.
The scenario connects with Google Sheets, Google Slides, and Google Drive as part of the downstream processing.
Image: Part of the Make scenario: the DocuSign trigger and download, the HTTP call to the Apps Script web app, Claude, and a router that splits into Google Sheets, Slides and Drive paths.
04. Workflow Architecture
The workflow uses a router to separate the processing paths after the contract information and itinerary text have been prepared.
05. Example Output: Three-Day Itinerary
The example itinerary slide presents a group's Friday, Saturday, and Sunday schedule. The supplied screenshot has group, date, hotel, and company details blurred for privacy.
Suggested placement: Include the itinerary screenshot here, after the workflow architecture section, to show an example of the generated output.
Image: An example three-day itinerary slide (group, dates, hotel and company details blurred for privacy).
06. Tools and Integrations
Make: Coordinates the automation and routes the workflow.
DocuSign: Triggers the process when a contract envelope is completed and provides the signed document.
Google Apps Script: Returns contract fields as structured data.
Anthropic Claude: Generates the three-day itinerary text.
Google Sheets: Supports master operations data.
Google Slides: Supports the itinerary slide.
Google Drive: Supports contract filing.
07. Outcome
The workflow automates key steps following contract completion, connecting signed-document processing with structured trip data, itinerary text generation, and downstream document handling.
Automated pipeline that pulls fresh leads from a CRM every morning, sends a personalized heads-up email, and loads a ready-to-dial Aircall campaign before the sales rep even logs in.
Section: n8n Automations
Overview
This project automates daily warm-lead outreach using n8n, HubSpot, Gmail, and Aircall. Every weekday, it selects up to 30 eligible contacts, sends personalized emails, and adds successfully emailed contacts to a new Aircall campaign. It also updates HubSpot and maintains a backup log to prevent duplicate outreach.
The Problem
The sales team previously spent time every morning collecting warm leads from HubSpot, sending introductory emails, and manually adding contacts to Aircall campaigns.This repetitive process reduced selling time and created risks such as duplicate outreach, incorrect phone numbers, and calls being made to contacts who had not received the introductory email.
How It Works
Scheduled Execution: n8n starts the workflow every weekday at 6:00 AM EST, before the sales team begins its day.
Retrieve HubSpot Contacts: The workflow collects eligible contacts from a designated HubSpot segment, retrieving up to 500 contact IDs before applying the daily selection limit.
Validate and Select Leads: It retrieves contact details, normalizes phone numbers into E.164 format, skips contacts already contacted that day, and selects up to 30 contacts.
Prevent Duplicate Outreach: Selected contacts are marked in HubSpot with the current date. Their details are also saved in a backup data table for auditing.
Send Personalized Emails: The workflow builds personalized HTML emails using the contact's first name and the sales representative's signature, then sends them through the representative's Gmail account.
Create the Aircall Campaign: n8n duplicates a master Aircall campaign, adds the current date to its name, and prepares it for the selected contacts.
Synchronize Email and Calls: Only contacts whose emails were successfully sent are added to the Aircall campaign. Their email activity is also logged on their HubSpot timeline.
Launch the Campaign: The workflow launches the campaign so the sales representative can open Aircall and start calling without preparing the list manually.
The Result
The automation connects lead selection, personalized email outreach, and Aircall campaign preparation in one workflow. It removes the need to manually build daily call lists, keeps email and calling activities synchronized, and prevents contacts from being selected repeatedly on the same day.
Automation Testing Results
Metric
Result
Contacts processed per test run
30
Email delivery success rate
100% (30/30)
Aircall contact loading success
Approximately 93%
Duplicate contacts observed
None
Daily list and campaign preparation
Automated
Note: Results are based on structured testing and dry runs. The remaining Aircall loading failures were linked to malformed phone numbers in legacy CRM records. Call connection rates, email replies, and sales impact have not yet been measured.
Tech Stack
n8n: Manages the scheduled workflow, contact selection, email delivery, and campaign creation.
HubSpot: Provides contact records, lead segments, daily outreach flags, and activity logging.
Aircall: Creates and launches daily outbound calling campaigns.
Gmail / Google Workspace: Sends personalized emails from the sales representative's mailbox.
Backup Data Table: Maintains an independent record of selected contacts for auditing and troubleshooting.
Where This Pattern Applies
Sales Teams: Prepare daily calling lists and coordinate email and phone outreach.
B2B Companies: Follow up with warm leads collected through CRM segments.
Lead Generation Agencies: Automate outreach preparation for multiple sales representatives.
Customer Acquisition Teams: Keep email introductions and follow-up calls organized in one process.
Webex Recording Transcription and Case File Automation
Automating meeting transcription storage, case identification, and record tracking using Zapier, Webex, Box, Calendly, Microsoft Excel, AI, and Google Sheets.
Section: Zapier Automations
Overview
This solution automates the process of retrieving Webex meeting transcripts, matching meetings with client cases, storing documents in Box, and tracking records in Google Sheets. It uses Calendly matching for direct case identification and AI-assisted matching when a usable case number is not available.
The Problem
Meeting transcripts need to be associated with the correct client and case before they can be stored and tracked. Handling this manually requires staff to review meeting details, identify the relevant case, download transcripts, locate the correct Box folder, upload files, and update tracking records.
The process becomes more difficult when meeting information does not contain a usable case number. An automated approach was needed to support both direct case matching and matching through existing client records.
How It Works
Receive Meeting Data: A Webhook triggers the automation when meeting-related information is received.
Retrieve Webex Details: The workflow fetches meeting information and checks whether a transcription is available.
Collect Participants: It retrieves participant details and formats meeting start and end times.
Match Calendly Events: JavaScript compares meeting information with scheduled Calendly events and retrieves the corresponding invitee details.
Identify the Case: The workflow checks whether a valid case number is available through the Calendly match.
Use AI When Needed: If direct matching does not provide a usable case number, the workflow downloads client records from Excel as CSV and uses AI by Zapier to identify a matching client and case number.
Find the Box Folder: The identified case number is used to search for the corresponding folder in Box.
Download and Store the Transcript: The Webex transcription is retrieved and uploaded to the relevant Box folder.
Update Tracking Records: Google Sheets logs the participant name, available case number, and Zapier run reference.
Result
The automation brings meeting retrieval, case identification, transcript storage, and record tracking into one connected process. It supports both direct Calendly-based matching and AI-assisted client matching, allowing transcripts to be routed according to the information available.Box maintains the associated transcript documents, while Google Sheets provides a record of the processed meetings and their related references.
Daily Processing Metrics
Metric
Daily Volume
Meetings processed
5
Meetings with available transcripts
3
Transcripts uploaded to client folders in Box
3
Tech Stack
Zapier: Connects applications and manages automation, filters, loops, and conditional paths.
Webex: Provides meeting information and transcription access.
Calendly: Supplies scheduled meeting and invitee information.
JavaScript: Handles meeting matching and data processing.
Box: Stores transcripts in the corresponding case folders.
Google Sheets: Maintains meeting and case tracking records.
Where This Pattern Applies
The same approach can be used wherever incoming documents or recordings need to be matched with existing client records and stored in the correct location.
Legal Services: Match meeting recordings and transcripts with case files.
Healthcare: Organize consultation recordings and related documents.
Insurance: Associate recorded client statements with claim records.
Recruitment: Match interview recordings with candidate profiles.
Customer Support: Attach call transcripts to customer and support records.
The general pattern is to retrieve incoming information, identify its matching record, store the associated document, and update the tracking system. The matching logic and connected applications can be adapted to different business processes.
A Slack Bot That Answers Trip Questions from an Ops Master Sheet
A Make scenario that lets a team member ask a plain-English trip question in Slack and get an answer drawn only from the ops master sheet.
Section: Make Automations
Project Overview
This internal operations tool helps a group travel team find trip information using plain-English questions in Slack, without manually searching through a large Google Sheets workbook.
The team stores trip information in the MASTER tab of the Master Ops Fall 26/Spring27 workbook. Each row represents a group trip and contains information about dates, destinations, operations coordinators, sales representatives, contracts, hotels and rooming, transport, events, task due dates, and payment status.
Tools: Make, Slack, Google Sheets, and Anthropic Claude (claude-sonnet-4-6).
01. The Problem
The operations master sheet contains more than 55 labelled fields per trip, spanning columns A to BH.
Finding a specific detail—such as a group's hotel information or room counts—requires locating the correct trip row and navigating to the relevant column. This makes answering everyday operational questions more time-consuming.
02. The Solution
A six-module Make scenario connects Slack with Google Sheets and Claude to process questions and return relevant trip information.
The workflow:
Receives the question and Slack channel through a webhook.
Uses Claude to convert the question into structured search terms.
Searches the master sheet for matching trips.
Combines the matching rows into readable text.
Uses Claude again to generate an answer based only on the retrieved information.
Posts the answer back to the same Slack channel.
03. How It Works
Step 1: Receive the Question
A custom webhook receives the incoming question and the Slack channel information.
Step 2: Identify the Search Terms
Claude interprets the plain-English question and converts it into structured search terms that can be used to find relevant trips.
Step 3: Search Google Sheets
The scenario searches the operations master sheet for trips matching the extracted criteria.
Step 4: Format the Matching Results
The matching spreadsheet rows are combined into readable text using a text aggregator.
Step 5: Generate the Answer
Claude uses the retrieved text to answer the original question. The answer is restricted to the information provided by the matching spreadsheet results.
Step 6: Reply in Slack
The final answer is posted back to the same Slack channel where the question originated.
Image: The Make scenario: a custom webhook, Claude turning the question into search terms, a Google Sheets search, a text aggregator, Claude answering from the results, and a Slack message.
04. Workflow Architecture
The scenario separates question interpretation, data retrieval, result formatting, and answer generation into distinct steps.
05. Example Use Case
A team member asks:
“How many groups do we have in Nashville from April 9–11, 2027?”
The bot searches for trips matching the destination and dates, then returns the matching groups with their trip dates and destinations in Slack. The example screenshot shows group names blurred for privacy.
Image: An example answer in Slack: the question, the search terms Claude worked out, and the matching groups with their dates and destination (group names blurred for privacy).
06. Tools and Integrations
Make: Connects the workflow modules and coordinates processing.
Slack: Provides the interface for asking questions and receiving answers.
Google Sheets: Stores the operations master data used to answer questions.
Anthropic Claude: Converts questions into search terms and generates answers from the retrieved results.
07. Outcome
The scenario gives the operations team a conversational way to retrieve trip information from a large master sheet. Team members can ask questions in Slack and receive structured answers based on matching spreadsheet records, without manually searching across the workbook.
An automated workflow that classifies HubSpot companies into industry groups using Google Gemini and sends uncertain records for human review.
Section: n8n Automations, AI Agents
Overview
This project uses n8n and Google Gemini Flash to automatically classify company records in HubSpot. The workflow runs every hour, retrieves companies from a designated HubSpot list, and checks whether their industry group is already assigned. Gemini analyzes company information and suggests an industry based on the categories available in HubSpot.
To maintain CRM data quality, the workflow validates every suggested category and checks its confidence score before updating a record. Companies that cannot be classified reliably are marked as Needs R&D for human review. A dry-run mode also allows the team to test the workflow without changing live CRM records.
The Problem
Many HubSpot company records may have missing or inconsistent industry classifications. Updating these records manually takes time and can lead to inconsistent categories.
Using AI without proper checks also creates risks, such as invented industry groups, unreliable classifications, and repeated processing of companies that have already been classified.
How It Works
Scheduled Execution: n8n starts the workflow every hour and loads its configuration, including the company limit, confidence threshold, and dry-run setting.
Retrieve Company Records: The workflow retrieves companies from a designated HubSpot list, collecting up to 100 records per run.
Check Company Information: It retrieves each company's name, domain, website, and existing industry group. Already classified companies and records without usable information are skipped.
AI Classification: Google Gemini Flash analyzes the available company information and returns a suggested industry group, confidence score, exclusion flag, and reasoning.
Validate the Result: n8n checks whether the suggested industry exists in HubSpot's allowed options. It also applies a minimum confidence threshold of 0.6 and limits confidence to 0.65 for companies without a domain.
Update or Flag Records: Valid classifications are written to HubSpot with relevant classification details. Uncertain or excluded companies are marked as Needs R&D for human review.
Control Updates: Dry-run mode prevents changes to live records during testing. A Wait node also separates updates to help manage HubSpot API rate limits.
The Result
The workflow provides an automated and controlled process for classifying HubSpot company records. It uses Gemini to suggest categories while HubSpot provides the approved industry options. Validation rules, confidence checks, and human-review routing help prevent unreliable classifications from being accepted automatically.
Workflow Configuration Metrics
Metric
Result
n8n workflow nodes
22
Execution schedule
Every hour
Maximum companies per run
100
Confidence threshold
0.6
No-domain confidence cap
0.65
AI model
Google Gemini Flash
Note: These figures describe the workflow configuration. Actual companies processed, classification accuracy, human-review rate, and time saved have not yet been measured.
Tech Stack
n8n: Runs the scheduled automation and manages the classification process.
HubSpot: Provides company records, approved industry groups, and the destination for validated updates.
Google Gemini Flash: Analyzes company information and suggests industry classifications with confidence scores and reasoning.
Where This Pattern Applies
CRM Management Teams: Keep company industry fields consistent across large CRM databases.
Sales Teams: Organize company records for better segmentation and reporting.
Marketing Teams: Group companies into relevant industries for targeted campaigns.
Business Data Teams: Automate data enrichment while routing uncertain records for manual review.
This pattern is useful for businesses that need to enrich large datasets with AI while maintaining control over data quality and ensuring uncertain results receive human review.
An automated reporting system that collects ticket sales data from multiple vendors, calculates festival revenue and attendance, and updates a central dashboard using Python and Google Cloud.
Section: Python Automation
Overview
Palm Tree Crew, a live music festival organizer, needed a reliable way to track ticket sales, revenue, and attendance across multiple festival locations. We developed a Python-based automation pipeline on Google Cloud that collects daily reports from Ticketmaster, Front Gate Tickets, and Posh through Gmail. The system processes the reports, applies the required business rules, stores the results in BigQuery, and updates a Google Sheets dashboard for the management team.
The Problem
The operations team had to download daily ticket reports from different vendors, extract the information from PDFs and emails, and manually enter the numbers into Google Sheets. They also had to calculate multi-day attendance and track revenue from separate VIP and sponsorship spreadsheets. This process took hours, increased the risk of errors, and made it difficult for management to view total revenue and remaining ticket capacity in one place.
How It Works
Start the Automation: Google Cloud Scheduler triggers the Python service on Cloud Run at the scheduled reporting time.
Collect Vendor Reports: The system uses the Gmail API to retrieve daily audit emails from Ticketmaster, Front Gate Tickets, and Posh.
Extract Ticket Data: Custom Python parsers process Ticketmaster PDF reports and Front Gate HTML email tables to extract ticket sales information.
Apply Business Rules: The system calculates daily attendance, 24-hour sales rates, and remaining capacity. It also splits two-day passes across the correct festival days.
Store Data in BigQuery: Processed information is saved in three tables: raw reports, parsed report lines, and daily snapshots.
Update the Dashboard: The Google Sheets API rebuilds the executive dashboard with ticket sales, revenue, attendance, sales rates, and remaining capacity.
Include Offline Revenue: VIP table and sponsorship data from external spreadsheets is connected through Google Sheets IMPORTRANGE, bringing online and offline revenue into one view.
Result
The system brings ticket sales collection, revenue calculations, and reporting into one automated pipeline.
Replaces hours of manual report collection and data entry with scheduled automation.
Combines ticket sales data from multiple vendors in one dashboard.
Reduces manual calculation errors and duplicate ticket counting.
Provides a combined view of online ticket sales, VIP tables, and sponsorship revenue.
Displays daily attendance, sales rates, and remaining ticket capacity.
Allows new festival shows and ticketing platforms to be added through a standard onboarding template.
Tech Stack
Python: Handles report extraction, data processing, and business calculations.
Google Cloud Run: Hosts and runs the Python automation service.
Google Cloud Scheduler: Triggers the pipeline at scheduled intervals.
BigQuery: Stores original reports, parsed ticket data, and calculated daily snapshots.
Gmail API: Retrieves daily ticketing reports from vendors.
Google Sheets API: Builds and updates the executive dashboard.
IMPORTRANGE: Connects external VIP table and sponsorship revenue spreadsheets.
Where This Pattern Applies
The same approach can help organizations that collect operational and financial data from multiple external sources.
Event Organizers: Combine ticket sales and attendance data across different events.
Music Festivals: Track revenue, ticket sales, and venue capacity across multiple locations.
Ticketing Companies: Process reports from different ticketing platforms.
Hospitality Businesses: Combine revenue and booking data from multiple systems.
Finance Teams: Automate daily reporting and bring information from separate spreadsheets into one dashboard.
The general approach is to collect reports from different sources, extract and process the data, apply business rules, and deliver updated results through a centralized dashboard.
An automated outbound sales system for discovering target companies, enriching decision-maker profiles, evaluating lead quality, and generating personalized email outreach.
Section: n8n Automations
Overview
Salesbeast is a three-layer AI-powered outbound sales system designed to automate company discovery, decision-maker identification, lead qualification, and personalized email generation.The system collects business information from multiple sources, evaluates potential leads using qualification rules, and uses AI to research decision-makers and prepare tailored email variations.
The Problem
Finding suitable companies and identifying the right people to contact requires searching multiple platforms, reviewing company websites, checking business information, and researching individual profiles.
After collecting this information, sales teams must manually assess lead quality and write personalized outreach messages. This process can become time-consuming and difficult to manage across large prospect lists.
How It Works
Collect Company Data: D7 Networks identifies companies based on industry, location, and company size criteria.
Enrich Business Information: Google Maps API retrieves ratings, reviews, phone numbers, and business hours. Website scraping collects company information, services, and blog content.
Identify Decision-Makers: Apollo.io searches for employees based on job titles and retrieves contact details, LinkedIn profiles, and professional background information.
Store Enriched Records: Company information, decision-maker profiles, and enrichment logs are organized in PostgreSQL.
Qualify Leads: The qualification layer evaluates company size, Google ratings, review counts, industry, and business activity.
Score and Segment: Leads receive a score out of 100 and are assigned categories such as Reputation Recovery, Moderate Reputation, High Authority, or industry-specific segments.
Research Decision-Makers: AI analyzes company information and professional profiles to identify relevant pain points, opportunities, and talking points.
Generate Personalized Emails: The system creates three email variations for each decision-maker: pain-focused, growth-focused, and authority-focused.
Review Email Quality: Generated emails are scored, and only emails scoring above 75 are approved. Lower-scoring emails are rejected for regeneration.
Result
The system connects company discovery, contact enrichment, lead qualification, and personalized email generation into one automated process.
It provides:
Enriched company and decision-maker records.
Structured lead scoring and segmentation.
Industry-specific targeting.
Research-based personalization.
Three email variations per qualified decision-maker.
Quality-scored email drafts stored for further use.
The documented design specifies an average email quality score of 88/100. This is a design-document figure, not an independently verified production performance metric.
Image: Figure 1. Company Data Collection & Enrichment
Image: Figure 2. Decision-Maker Identification
Image: Figure 3. AI Lead Qualification & Email Generation
Tech Stack
n8n: Workflow automation and coordination across the three processing layers.
D7 Networks: Company discovery based on search criteria.
Google Maps API: Business details, ratings, reviews, and contact information.
Apollo.io: Decision-maker identification and professional profile enrichment.
AI Models: Lead research, qualification support, and personalized email generation.
PostgreSQL: Structured storage for leads, decision-makers, qualification results, and email variants.
Where This Pattern Applies
B2B Sales: Identify target companies and relevant decision-makers.
Marketing Agencies: Build enriched prospect lists for outreach campaigns.
Recruitment: Research organizations and identify relevant hiring contacts.
Business Development: Discover companies matching specific market criteria.
Lead Generation Agencies: Qualify and segment prospects before outreach.
SaaS Companies: Build targeted outreach campaigns using company and professional profile information.
The general pattern is to combine business data collection, contact enrichment, qualification rules, and AI-assisted personalization into a connected outbound sales workflow.
Newsletter Generator: From a Google Sheets Row to a Draft Campaign
A Make scenario that turns one row of a Google Sheets newsletter planner into a finished draft campaign in Campaign Monitor, in one of three layouts chosen by the editor.
Section: Make Automations
Project Overview
This Make scenario automates the creation of newsletter draft campaigns using content stored in Google Sheets. Editors prepare the newsletter information in a spreadsheet, select one of three templates, and mark the row for creation. Make then builds the newsletter and creates a draft campaign in Campaign Monitor.
01. The Challenge
Creating a newsletter manually requires editors to copy titles, images, excerpts, links, and category labels into an email template. This process must be repeated for news articles, sponsored posts, a destination report, and a podcast episode.
02. The Solution
The Make scenario connects Google Sheets with Campaign Monitor to generate a newsletter draft from a single spreadsheet row. It uses the selected template to build the campaign content and updates the row when the process is complete.
03. How It Works
Step 1: Prepare the Newsletter
The editor fills in a Google Sheets row with the content for three news posts, three sponsored posts, a destination report, and a podcast episode.
Step 2: Select a Template
The editor chooses template 1, 2, or 3 and sets the Create Newsletter cell to Create.
Step 3: Find the Requested Row
Make searches the sheet on its schedule for a row marked Create and processes one row at a time.
Step 4: Route to the Selected Layout
A router directs the row to one of three routes based on the selected template number.
Step 5: Build the Newsletter
A code step assembles the newsletter content, including banners, images, category labels, titles, excerpts, links, and buttons. The layout varies according to the selected template.
Step 6: Create the Draft Campaign
An HTTP request sends the generated content to the Campaign Monitor API, which creates a draft campaign using the selected template.
Step 7: Update the Spreadsheet
After the campaign is created, Google Sheets is updated with the status Done.
Image: The Make scenario: Google Sheets searches for a row marked Create, a router picks one of three templates, a code step builds the newsletter content, an HTTP call creates the campaign from the template, and Google Sheets updates the row. A Skip step on each route handles errors.
04. Newsletter Content Structure
The generated newsletter includes:
A top banner
Three news posts
A banner separating content sections
Three sponsored posts
A destination report
A podcast episode
An additional banner
News and sponsored posts include images, category labels, titles, excerpts, and links. The destination report includes a destination name and description, while the podcast section includes its date, title, description, and listening link.
05. Template Options
The scenario supports three newsletter layouts:
Template 1: A three-row layout.
Templates 2 and 3: Mixed layouts with two posts side by side and one centred below, using their respective templates.
06. Content Handling
The code includes defaults for missing content. Missing news or sponsored-post images use a default image, missing links point to the main website, and each campaign receives a unique name with a timestamp. The subject line and header date default to the current month and year. Sender details and the subscriber list are also set in the code step.
07. Workflow Architecture
Each template route builds the campaign content and sends it to Campaign Monitor. A Skip step on each route handles errors.
08. Tools and Integrations
Make: Coordinates the workflow, routing, and newsletter generation.
Google Sheets: Stores newsletter content, template selection, and processing status.
Campaign Monitor: Creates the newsletter as a draft campaign.
09. Review and Error Handling
The campaign is created as a draft in Campaign Monitor so the team can review it before sending. If Campaign Monitor returns an error, the scenario skips that run instead of stopping with an error.
10. Outcome
The scenario allows editors to prepare newsletter content in Google Sheets and generate a corresponding Campaign Monitor draft without manually copying each content block into the email editor. The team can review the generated draft in Campaign Monitor before sending it.
Automated Transcription Workflow Between Box and Rev.com
Automating audio and video transcription submissions, transcript delivery, and file tracking using Zapier.
Section: Zapier Automations
Overview
Audio and video files stored in Box previously required manual retrieval, transcription submission, order tracking, and document storage. Two connected Zapier workflows now submit eligible files to Rev.com, track pending orders, and deliver completed transcripts back to their corresponding Box folders.
The Problem
Teams handling recordings in Box need to submit files for transcription and keep track of each request until the transcript is ready. Manually retrieving files, creating transcription orders, checking their status, and uploading completed documents involves repetitive work. It can also become difficult to keep the original recording, transcription order, and completed document connected to the correct client folder.
How It Works
Detect New Files: A Box webhook triggers the workflow when a new file is received.
Filter Media Files: Zapier checks the file extension and allows supported formats such as WAV, MP4, MP3, OGG, and M4A.
Retrieve the File: Webhooks obtain Box API access, and Code by Zapier generates the source file's download link.
Submit for Transcription: The download link is sent to Rev.com to create an automated transcription order.
Save Order Details: Zapier Tables stores the order ID, client reference, pending status, and folder information.
Log Source Information: Google Sheets records the original filename, Box file ID, parent folder ID, and download link.
Check Pending Orders: A second workflow runs daily at 9 PM and retrieves pending records from Zapier Tables.
Verify Transcription Status: The workflow checks each order through the Rev.com API and identifies orders marked Complete or Delivered.
Retrieve the Transcript: The automation locates the transcript attachment and prepares a Word document filename.
Deliver the Document: The completed transcript is uploaded to its associated Box folder. Conditional paths handle orders that are not ready or have been canceled.
Results & Metrics
The two workflows separate transcription submission from transcript delivery, so the initial file-processing workflow does not need to wait for Rev.com to finish the transcription.Pending orders are tracked in Zapier Tables, while Google Sheets maintains source-file details. Once a transcript is marked Complete or Delivered, the automation retrieves the Word document and places it in the associated Box folder.
Tech Stack
Tool
Role in the Workflow
Zapier
Coordinates both automations, scheduling, filters, loops, and conditional paths.
Box
Stores the original media files and receives completed transcripts.
Rev.com API
Handles transcription submissions, order-status checks, and transcript retrieval.
Webhooks
Communicate with the Box API for authentication and file access.
Code by Zapier
Generates download links, extracts order IDs, checks status, and prepares filenames.
Zapier Tables
Stores pending transcription orders and related references.
Google Sheets
Maintains source-file details and download-link records.
The team can continue using its existing Box, Rev.com, and Google Sheets setup without moving to a new document-management platform.
Where This Pattern Applies
This solution is not limited to transcription services. The same approach can be used wherever incoming files need to be processed by an external service and returned to the correct record or folder.
Example — Legal Services: Audio recordings of client interviews can be submitted for transcription, tracked until completion, and returned to the relevant case folder in document storage.
Other applications include:
Healthcare: Process consultation recordings and store completed transcripts.
Recruitment: Transcribe interviews and attach documents to candidate records.
Insurance: Process recorded client statements and organize transcripts with claim files.
Education: Transcribe lectures and store documents by course or session.
Customer Support: Process recorded calls and attach transcripts to support records.
The general pattern is to detect an incoming file, submit it for processing, track its status, retrieve the completed output, and return it to the correct destination. The external service, matching rules, and storage platform change according to the business process.
Automating weekly client forecasting and overdue-account reporting with Zapier, LoanPro, Calendly, and Microsoft Outlook.
Section: Zapier Automations
Overview
Preparing weekly client forecasts and monitoring overdue loan accounts previously required information to be collected and reviewed across multiple systems. The solution uses Zapier to retrieve calendar and LoanPro data, apply business rules, calculate relevant figures, and deliver structured reports through Microsoft Outlook.
The Problem
Financial reporting requires teams to review calendar events, match clients with loan records, and identify overdue balances. These details are spread across different systems, making manual reporting repetitive and difficult to maintain. Smaller outstanding balances can also be overlooked when accounts are reviewed individually. A consistent process was needed to organize client forecasts and highlight qualifying overdue accounts.
How It Works
Start Scheduled Reporting: Zapier triggers the reporting automations according to their weekly schedules.
Retrieve Calendar Information: Microsoft Outlook provides calendar events, while Calendly supplies additional scheduled event information.
Process Meeting Details: JavaScript extracts client information, processes event dates, and prepares records for matching.
Match Client Records: The workflow searches LoanPro for corresponding customer records using available names and email addresses.
Retrieve Loan Information: The LoanPro API provides customer, loan, and account details, including outstanding balances and days past due.
Apply Reporting Rules: JavaScript evaluates client and loan information against configured qualification conditions.
Group Smaller Balances: Individual amounts below $500 are combined by client, and clients reaching the $500 threshold are included in the report.
Calculate Report Figures: The automation calculates flagged entries, total amounts due, and principal balances, and sorts the results by days past due.
Generate Reports: The processed information is formatted into structured HTML reports containing summary figures and relevant account details.
Deliver Reports: Microsoft Outlook sends the generated reports to the configured recipients.
Results & Metrics
The reporting solution provides visibility into upcoming client engagements and overdue loan accounts through structured email reports.
The available report show:
Metric
Observed Result
Upcoming items in firm forecast
4
Active loan accounts reviewed
280
Flagged receivable entries
151
Total amount due
$352,715.29
Total principal balance
$220,674.10
Note: These figures reflect the current report data and may change from day to day as new calendar events and loan account information are updated.
Tech Stack
Tool
Role in the Workflow
Zapier
Coordinates scheduled automation and connects the different processing steps.
LoanPro API
Retrieves customer, loan, and account information.
Calendly API
Provides scheduled event information for client forecasting.
Microsoft Outlook
Retrieves calendar events and delivers generated reports by email.
JavaScript
Processes API responses, matches records, calculates balances, applies reporting rules, and generates HTML reports.
The team can continue using its existing calendar, loan-management, and email applications without changing its day-to-day tools.
Where This Pattern Applies
This solution is not limited to financial reporting. The same approach can help businesses collect information from different systems, match records, apply business rules, and deliver scheduled reports.
Example — Insurance: An automation can retrieve policy and claims data, identify overdue payments, group balances by customer, and prepare a weekly outstanding-payment report.
Other applications include:
Banking: Monitor overdue loan payments and customer balances.
Healthcare: Prepare scheduled patient-account and payment reports.
Legal Services: Match client appointments with case records and generate summaries.
Property Management: Identify overdue rent and prepare tenant payment reports.
Sales Operations: Combine scheduled meetings with customer records and prepare pipeline reports.
The general pattern is to retrieve information from connected systems, match records, apply qualification rules, calculate relevant figures, and deliver structured reports. The data sources, business rules, and reporting format change according to the business process.
Automated NetSuite to ShipStation Order Processing
Automation that sends eligible NetSuite sales orders to ShipStation, prepares shipping details, and updates order status automatically.
Section: Make Automations
Overview
This solution connects NetSuite with ShipStation through Make. It identifies eligible sales orders, prepares their customer, address, item, and shipping details, creates the corresponding orders in ShipStation, and updates NetSuite to record processing.
The Problem
Sales orders are managed in NetSuite, while shipment preparation takes place in ShipStation. Transferring order details between the two systems requires staff to enter customer information, billing and shipping addresses, line items, quantities, prices, and shipping services.
This repetitive work takes time and creates opportunities for incorrect item details, shipping selections, or incomplete order records. Teams also need a reliable way to identify which orders and line items have already been processed.
How It Works
The solution uses a Make scenario to handle the order-processing workflow.
Monitor sales orders. Make watches a configured NetSuite saved search for sales orders that have been modified.
Check order eligibility. The workflow checks whether the order is marked to be sent to ShipStation and has not already been marked as created there.
Retrieve order details. It fetches the complete sales order, including customer information, billing and shipping addresses, dates, totals, and line items.
Prepare order information. The workflow collects the order details and processes its line items, including item names, descriptions, quantities, and prices.
Format item data. OpenAI converts the NetSuite line-item data into the structure required by the ShipStation API.
Identify the shipping service. The workflow reads the shipping method from the order items and maps it to the corresponding ShipStation service code. If no method is available, it uses the configured Ground default.
Create the ShipStation order. An HTTP request sends the prepared customer, address, item, payment, tax, and shipping information to ShipStation.
Update NetSuite records. After the order-creation step succeeds, the workflow updates the NetSuite sales order and marks the relevant line items as processed.
The Result
The automation connects order entry with shipment preparation, reducing the need to manually transfer sales order information between NetSuite and ShipStation. It prepares item and shipping details, creates ShipStation orders, and records processing status back in NetSuite. This helps reduce repetitive data entry and keeps order-processing records aligned across both systems.
Daily Automation
Metric
Observed Output
Emails processed
7/day (average)
Successful runs
96/day
Run frequency
15 minutes
Success rate
100%
Execution time
1.5 seconds
Note:Metrics are based on the observed execution history and may vary depending on order activity and processing time.
Tech Stack
Make: Runs the automation and coordinates order processing, routing, data preparation, and conditional operations.
ShipStation: Receives and manages sales orders for shipment processing.
The solution works with the existing NetSuite and ShipStation setup, without requiring teams to replace their systems or learn a new order-management platform.
Where This Pattern Applies
This approach connects order records with downstream fulfilment activities, ensuring that information is transferred, processed, and tracked automatically.
Imagine a wholesale business receiving customer orders through its ERP system. The automation collects the order details, formats product and shipping information, sends the order to its fulfilment platform, and updates the original record once processing is complete.
The same pattern can be adapted to:
E-commerce: Transfer online orders into shipping and fulfilment platforms.
Wholesale: Process bulk customer orders and prepare shipment records.
Manufacturing: Send production orders to operational and dispatch systems.
Retail: Coordinate store orders with warehouse fulfilment.
Logistics: Transfer shipment details between order and transport systems.
Healthcare Supply: Coordinate medical supply orders with distribution systems.
The reusable pattern remains the same: monitor incoming orders, validate eligibility, prepare structured data, send it to the fulfilment platform, and update the original system to reflect processing.
Automation that turns incoming documents into filed, logged, and findable records, without anyone watching an inbox.
Section: Zapier Automations
Overview
Documents used to arrive, sit in an inbox, and wait for someone to notice them, open them, and put them where they belonged. Now they file themselves correctly, every time, with a record left behind.
The Problem
A document lands in someone’s inbox, and for a while, nobody knows it is there. Maybe it is the filing that should have gone out yesterday. Maybe it is the one that got missed last month, found only after a client called asking where it went. Every day comes down to one person checking an inbox, guessing what matters, and hoping nothing slips through. One missed email is the difference between on time and in real trouble.
How It Works
The automation sits where the person used to sit, watching the inbox, and runs through the same checks in the same order, without getting tired or distracted partway through:
Watch for the right emails. It recognizes incoming filings by sender and subject, and ignores everything else.
Confirm there’s actually something attached. No attachment, no work to do. It moves on instead of acting on an empty notification.
Pull out what matters. The case number, the subject, and the attachment itself are lifted out of the email automatically.
Log it immediately. Before anything else happens, the document is recorded in a running sheet, so there’s a timestamped record that it arrived, even before it’s filed.
Check for duplicates. It looks up whether this exact document has already been filed, so the same thing doesn’t get added twice.
Find the right home. It looks up the matching folder by case number. If that folder doesn’t exist, nothing gets misfiled into the wrong place.
File it, and say so. The document is uploaded, and the log is updated to say whether it was newly added or already existed.
Catch failures out loud. If any step fails, that failure is written into the log instead of disappearing silently, so nothing goes missing without someone knowing.
The Result
Nobody checks the inbox to find out whether a new filing came in. It is simply already in the right folder by the time anyone looks. The running log answers “did we get this?” on sight instead of requiring a search. Duplicate filings are caught automatically rather than relying on someone to notice a repeat. And when something does fail, it shows up in the log as a visible flag instead of quietly vanishing.
Tech Stack
Microsoft Outlook: where the pleading emails arrive, sorted into a dedicated folder the automation watches.
Zapier: runs the whole process in the background, handling each attachment separately when several pleadings come in one email.
Google Sheets: the running log, with a row for every pleading showing its case number, file name, time received, and whether it was filed.
Box.com: where each pleading lands, inside the folder that matches its case number.
Where This Pattern Applies
This isn’t really a story about legal filings. Picture the same automation watching a different inbox for a different business.
A supplier emails an order confirmation. The automation checks it has an attachment, pulls out the purchase order number instead of a case number, logs the confirmation the moment it lands, checks whether it’s already been recorded, finds the folder for that purchase order, and files it, flagging anything that doesn’t match a known order instead of losing track of it.
Swap “purchase order number” for whatever identifier matters in your world, and the same shape shows up everywhere:
Government & permitting: applications, licenses, inspection filings
Education: student applications, transcripts, enrollment forms
The shape never changes: watch, verify, extract, log, match the destination, file, confirm. What changes is only which number you’re matching against. Whatever industry it sits in, the win is the same. Nobody has to be the one remembering to check.
An automated support workflow that turns incoming customer emails into correctly routed ClickUp tickets, adds replies to existing tickets, and prevents duplicate tickets using n8n.
Section: n8n Automations, AI Agents for Ecommerce, ClickUp Setups
Overview
This solution automates support email handling for RefureTech. When a customer sends an email to the shared Gmail inbox, n8n reads the message, identifies the client using their email domain, and sends it to the correct ClickUp support list. If the client is unknown, the email goes to a default triage list. If the conversation already has a ticket, the new email is added as a comment instead. Attachments and previous messages are also included, giving the support team the full conversation in one place.
The business problem
Support requests arrived through a shared email inbox and had to be added to ClickUp manually. This took time and created a risk of assigning emails to the wrong client, missing attachments, or creating duplicate tickets. ClickUp also has its own email feature that handles customer replies, so a basic email-to-ticket automation could create duplicate tickets or process its own confirmation emails repeatedly.
The solution
A single n8n workflow polls the support inbox every minute. It looks up the client list stored in ClickUp, matches the sender by domain, checks four different ways whether the conversation already has a ticket or is already managed by ClickUp, and only then creates a ticket or comment. It uses plain, explainable rules in code nodes rather than an AI model, so every decision can be traced to a header, a subject line or a ClickUp field. Wherever a step could fail, the workflow prefers a duplicate ticket over a lost customer email.
How It Works
Receive Support Emails: The Gmail Trigger checks the shared inbox every minute and retrieves new messages, including their attachments.
Identify the Client: n8n checks the sender's email domain against the client information stored in ClickUp. Each client has a domain, folder ID, and support list ID.
Check for Existing Tickets: The workflow searches for existing tickets using Gmail thread IDs and ClickUp email thread IDs. It also checks the full email conversation to identify related messages.
Decide Where the Email Goes: The workflow uses routing rules to determine whether the email is a new request, a reply to an existing ticket, an unknown client request, or a message that should be skipped.
Create a Ticket or Add a Comment: New requests are added to the correct client's support list. Emails from unknown clients go to the default triage list, while replies to existing tickets are added as comments.
Upload Attachments: Email attachments are downloaded and uploaded to the related ClickUp ticket. Earlier messages in the conversation are also included where available.
Prevent Duplicate Processing: The workflow skips ClickUp confirmation emails, messages already managed by ClickUp, and automatic replies such as out-of-office messages.
Mark Emails as Processed: Successfully handled emails receive a Ticketed label in Gmail. For new tickets, the workflow also waits two minutes and saves ClickUp's confirmation email thread ID for future matching.
The Result
The automation successfully manages incoming support emails, creates and routes ClickUp tickets, and adds replies to existing tickets. It also preserves attachments and email history while preventing duplicate tickets and unnecessary processing.
Automation Performance
Metric
Result
Successful workflow executions
11
Successful execution rate
100%
Failed executions
0
Total n8n nodes
38
Tech Stack
n8n: Manages the automation, email processing, routing rules, and duplicate checks.
Gmail: Receives support emails, retrieves message threads and attachments, and labels processed messages.
ClickUp: Stores client information, creates support tickets, adds comments, and manages attachments.
ClickUp API: Supports searches and operations that connect the workflow with ClickUp records.
Where This Pattern Applies
The same approach can be used by organizations that manage customer requests through shared email inboxes.
IT Support Teams: Convert incoming technical support emails into tickets.
Customer Service Teams: Route customer requests to the correct team or department.
Managed Service Providers: Organize support requests across multiple clients.
SaaS Companies: Track customer issues and follow-up conversations in one system.
Operations Teams: Turn shared inbox requests into assigned and trackable tasks.
The general approach is to monitor a shared inbox, identify the customer, check for existing conversations, and automatically create or update the right ticket while keeping the full email history and attachments.
Automated NetSuite Billing and Shipment Processing
Automation that extracts invoice and shipment details from incoming emails, matches them with NetSuite records, and prepares shipment notifications.
Section: Make Automations
Overview
This solution connects Microsoft Outlook, OCR.space, OpenAI, and NetSuite through Make. It processes incoming billing emails and PDF attachments, extracts purchase order numbers, tracking IDs, and vendor information, matches the information with NetSuite transactions, and prepares shipment-related email notifications. It also sends an alert when OCR processing encounters an error.
The Problem
Billing teams manually review incoming emails, download invoices and shipment documents, extract key details, and match them with NetSuite records. This repetitive process takes time and increases the risk of missing information or incorrect transaction matching.
How It Works
The solution uses a Make scenario to process incoming billing emails and their attachments.
Monitor Billing Emails. Microsoft Outlook watches the configured billing inbox for incoming messages.
Apply Email Conditions. The workflow checks sender and subject details to determine which messages should proceed.
Retrieve Attachments. It lists the available attachments and downloads the relevant files.
Filter PDF Documents. PDF attachments proceed through the document-processing route, with a short delay before extraction.
Extract Document Text. OCR.space processes the PDF and returns its extracted text.
Handle OCR Errors. If the OCR request encounters an error, the workflow sends an email alert to the configured recipient.
Prepare Extraction Inputs. The email preview and extracted PDF text are stored for further processing.
Extract Purchase Order and Tracking Details. OpenAI identifies purchase order numbers and tracking IDs from the available email and document content.
Identify Vendor Information. A separate OpenAI step extracts vendor details, and the returned information is parsed into structured fields.
Search NetSuite Transactions. The workflow searches NetSuite for records matching the extracted information and retrieves the relevant transaction details.
Prepare Item Information. Related transaction items are collected and processed into a structured list for the notification.
Prepare Shipment Emails. The workflow combines the retrieved transaction, item, and shipment information to prepare the relevant email.
Send Notifications. Microsoft Outlook sends the shipment-related email using the prepared information.
The Result
The automation connects incoming billing documents with the corresponding NetSuite records and shipment notifications. Instead of manually reviewing every email, downloading documents, extracting details, and searching transactions, the workflow handles these steps automatically. It also provides an email alert when OCR processing fails, helping the team identify document-processing issues.
Execution Metrics
Metric
Result
Total executions
164
Successful executions
158
Success rate
~95%
Average execution time
17.15 seconds
Note:Metrics are based on the available execution logs and may vary depending on email volume, attachment processing, and document complexity.
Tech Stack
Make: Coordinates the complete workflow, including email routing, attachment processing, data extraction, transaction matching, and error handling.
Microsoft Outlook: Monitors the billing inbox, retrieves email attachments, and sends shipment notifications and OCR error alerts.
OCR.space API: Extracts readable text from PDF attachments for further processing.
OpenAI: Extracts purchase order numbers, tracking IDs, and vendor information from email and document content.
NetSuite: Provides transaction and item records used to match extracted billing and shipment information.
JavaScript: Supports custom data processing and prepares structured item information for email notifications.
The team can continue using Outlook and NetSuite without replacing its existing email or business management systems.
Where This Pattern Applies
This is not limited to billing and shipment processing. Imagine an e-commerce business receiving supplier invoices, delivery documents, and tracking information through email. The automation extracts the relevant details, finds matching order records, and prepares the next notification without requiring someone to process every document manually.
The same approach can be adapted to:
E-commerce: Order and shipment document processing
Logistics: Delivery documents and tracking details
Finance: Invoice and purchase order processing
Procurement: Supplier document management
Distribution: Shipment records and customer notifications
Healthcare Supply: Medical supply invoices and delivery documentation
The reusable pattern remains the same: receive documents, extract information, identify relevant details, match existing records, and trigger the next action. What changes is the document type, the system being searched, and the action that follows.
Power BI: Turning Five Booking Systems Into One Revenue Engine
A governed Power BI model and two dashboards that replaced three days of manual owner-statement assembly with an automated daily refresh for a short-term rental portfolio.
BnB Heaven manages a portfolio of short-term rentals and boutique B&Bs across the UK. Bookings arrived from Airbnb, Booking.com, Vrbo and their own direct site; cleaning and turnovers lived in the ops tool; finance sat in the accounting system. Owner statements and the monthly board pack took three days to assemble by hand. This case study shows how we consolidated everything into one governed Power BI model with two dashboards, cutting reporting effort by roughly 90% and giving the team occupancy, rate and channel-profitability numbers they finally trust.
The Challenge
Before the project, 'how are we doing?' was a surprisingly hard question to answer. Three problems came up in every conversation with the team.
Bookings scattered across platforms: Revenue lived in Airbnb, Booking.com, Vrbo and the direct site, with turnovers in the PMS and money in accounting. Nobody could see occupancy, nightly rate and net revenue in one place without exporting several files first.
Owner statements ate three days a month: A manager rebuilt every owner statement and the board pack by hand (copy, paste, reconcile, repeat). By the time they were ready the numbers were weeks old, and one slip meant redoing the lot.
No shared version of the truth: Channel profitability after platform fees was invisible. It wasn’t clear which channels actually paid off once commissions were taken out, so pricing and listing decisions were made on gut feel.
The Approach
Rather than bolt a chart onto each platform, we built one properly modelled layer underneath a small number of focused dashboards. Four phases over six weeks:
Discovery & metric definitions (week 1): Workshops to agree exactly what occupancy, ADR, RevPAR and net-of-fees revenue mean (one signed-off definition each, so the model has a single source of truth).
Connect & clean with Power Query (weeks 2–3): ETL into all five sources, standardised property and channel keys, and consistent handling of platform fees, refunds and cancellations so figures reconcile to the accounts.
Star-schema model & DAX (weeks 3–4): A clean fact-and-dimension model with a shared date table, reusable DAX measures (occupancy, ADR, RevPAR, YoY, target) and row-level security so each owner sees only their own properties.
Dashboards, refresh & handover (weeks 5–6): Two role-based dashboards, an on-premises gateway for the automated 06:00 refresh, plus training and a short written guide so the team can extend the model themselves.
The Solution
Executive overview
The board-level view answers leadership’s core questions on one screen: where revenue comes from, how occupancy and rate are trending, which properties and channels pull their weight, and whether the year is on target.
Image: Revenue & Occupancy: the executive overview page, live in Power BI Desktop, with KPIs, revenue trend, channel mix, property and location breakdowns and target attainment.
Operations & guests
The operations view is a daily working screen for the wider team: booking volume against occupancy, manager contribution, the direct-site booking funnel and guest satisfaction by location.
Image: Operations & Guest Experience: bookings vs occupancy, manager revenue, booking funnel and 5-star reviews by location.
Cumulative revenue vs operating cost shows the margin gap at a glance.
Channel donut exposes reliance on commission-heavy platforms vs direct.
Top-property table ranks by revenue with live YoY growth flags.
Gauge tracks progress against the £4.55M annual target (106%).
Under the Hood
Layer
What We Built
Tools
Sources
Airbnb, Booking.com, Vrbo, direct site, PMS / channel manager, accounting
Row-level security by owner / manager, documented definitions
RLS roles
Delivery
Two role-based dashboards, automated daily refresh
Power BI Service + gateway
The Results
+5.6pts: Occupancy rate
+0.14: Guest rating
3 days → 0: Manual reporting
106%: Of annual target
Measure
Before
After
Owner statements & board pack
~3 days, manual
Automatic, ready by 06:00
Data freshness
~3 weeks old
Refreshed daily
Channel profit (net of fees)
Invisible
Live, per channel
Sources reconciled
Manually, error-prone
Reconciled to accounts automatically
With channel profitability visible net of platform fees, BnB Heaven leaned into direct bookings and trimmed commission-heavy inventory, finishing the year 6% ahead of target.
Automated P&L & Sales Tracker for Ecommerce (Google Sheets)
A single Google Sheets template that turns raw sales, COGS and marketing cost data into live real-vs-estimated profit numbers for any date range.
Section: Dashboards & Reporting
Project Overview
This project delivers an automated profit and loss (P&L) tracking solution for an ecommerce business. It consolidates sales, real COGS, marketing costs, and other expenses into a single spreadsheet-based reporting system.
The tracker calculates real and estimated profit automatically, allowing the team to review financial performance across different date ranges without rebuilding reports manually.
The Challenge
Ecommerce financial data can be spread across sales records, product costs, marketing expenses, and other operational costs. Combining these figures manually makes it harder to maintain an up-to-date view of profitability.
The main challenges included:
Fragmented financial data: Sales, COGS, marketing spend, and other expenses needed to be considered together.
Manual reporting: Profit and loss figures required repetitive calculations and reporting work.
Limited visibility: Understanding real profit, estimated profit, and profit margins across different periods required a consolidated view.
A reusable Google Sheets template was developed to bring the relevant financial figures into one reporting system and calculate profitability automatically.
The solution provides:
Automated P&L calculations: Combines sales, COGS, marketing costs, and other expenses to calculate profit metrics.
Real vs. estimated profit: Makes both measures available for financial review.
Flexible date-range reporting: Allows the team to review performance for selected periods.
Daily performance tracking: Presents sales, profit, and expense metrics for day-to-day monitoring.
Monthly and rolling analysis: Supports longer-term performance reviews and expense breakdowns.
Reusable template: The same template can be applied to different brands, with totals recalculated for the relevant data.
Key Dashboard Features
Finance & Sales Reporting
An automated profit & loss tracker built in Google Sheets for an ecommerce business. Pulling sales, real COGS, marketing spend and other expenses into one model, it calculates real vs. estimated profit automatically for any date range instead of being rebuilt by hand every month.
$1.18M: Total sales (period)
$54.6K: Total real profit
4.61%: Real profit margin
$587K: Total marketing cost
Image: Monthly sales and profit dashboard: total sales, real/estimated profit, margins and marketing cost calculated automatically from raw order data.
Image: The same template applied to a different brand: totals, COGS and marketing cost recalculated instantly for any date range.
Daily and 30-day views
A daily dashboard view surfaces total and trailing-30-day sales, profit and expense metrics side by side, so the team can catch a bad week before it becomes a bad month.
Image: Daily dashboard: total and last-30-days sales, profit and expense metrics side by side for fast day-to-day monitoring.
Rolling breakdowns
A rolling 12-month view breaks total profit down into COGS, marketing cost, other expenses and disputes won, so the team can see exactly where margin is being gained or lost.
Image: Last-12-months pie chart breaking total profit down into COGS, marketing cost, other expenses and disputes won.
Built as a single Google Sheets template so finance reads live profit numbers for any date range without exporting from five different tools first.
Workflow
The workflow consolidates the available financial inputs, calculates the relevant profit and margin metrics, and presents the results through reporting views for different periods.
Technology Used
Google Sheets is the core platform used to organize the financial data, calculate P&L metrics, and display the dashboards.
The solution uses a reusable spreadsheet structure to support financial reporting across date ranges and brands.
Results and Business Value
The tracker brings key ecommerce financial metrics into one place and reduces the need to rebuild reports manually.
Centralized financial visibility: Sales, profit, margins, COGS, and marketing costs can be reviewed together.
Reduced manual reporting: Calculations and dashboard views are organized within a reusable template.
Flexible analysis: The team can review performance across daily, monthly, and rolling periods.
Consistent reporting: Different brands can use the same reporting structure.
Improved financial oversight: Real and estimated profit figures help the team review financial performance.
Final Outcome
The Automated P&L & Sales Tracker provides an organized, reusable Google Sheets solution for ecommerce financial reporting. By bringing sales, costs, and profitability metrics into one place, it makes financial performance easier to review across selected date ranges and supports more consistent reporting for ecommerce operations.
AI Voice Agents for Lead Qualification and Customer Support
An AI voice automation system for Pine Street Code that instantly qualifies new leads, handles customer calls, and connects callers with human representatives when needed.
Section: n8n Automations, AI Agents
Overview
Pine Street Code wanted to improve lead response times and ensure customer calls were handled even when the team was unavailable. We developed two AI voice agents using ElevenLabs and n8n. Hazel automatically contacts new Meta leads within seconds, asks qualifying questions, and gathers project details. The second agent handles incoming customer calls when the team cannot answer. Both agents integrate with Thrive CRM and Slack for lead tracking and team notifications. A customer-facing application also allows the client to review call recordings and request improvements.
The Problem
Pine Street Code needed a way to respond to new Meta leads immediately and avoid losing potential customers to competitors. It also needed reliable coverage for incoming calls when staff were unavailable, without changing its existing business phone numbers.
How It Works
Capture New Leads: When a prospect submits a Meta lead form, the n8n workflow receives the lead information and initiates the automated calling process.
Immediate AI Follow-Up: Hazel, the AI lead qualification agent, contacts the prospect within approximately 5–10 seconds of form submission.
Qualify Prospects: Hazel asks predefined qualifying questions, gathers project requirements, and captures relevant lead details using configured conditions and conversation instructions.
Apply Conversation Guardrails: Hazel avoids making pricing commitments, disclosing sensitive business information, or making decisions reserved for human representatives.
Notify the Team: Lead qualification details are sent to Slack so the team can review new opportunities and follow up when human involvement is needed.
Track Leads in the CRM: The n8n workflows connect with the client's Thrive CRM, maintaining lead information and tracking progress through the pipeline until the opportunity is closed.
Route Existing Business Calls: The second AI voice agent handles incoming calls through the business's existing phone numbers, allowing Pine Street Code to retain its established numbers.
Activate Customer Support Agent: When an incoming call rings three times without being answered by the team, the call is routed to the AI customer support agent.
Handle Customer Inquiries: The support agent responds to customer questions while following strict instructions that prevent unauthorized pricing commitments, disclosure of internal processes, or sharing sensitive business information.
Provide Call Review: A customer-facing application allows the business to listen to recorded conversations and flag specific calls or interactions for changes and improvements.
Result
The solution connects lead acquisition, AI-powered qualification, customer support, and CRM tracking into one automated system.
Faster lead response: Hazel initiates calls approximately 5–10 seconds after form submission.
Automated qualification: Prospects are contacted and asked predefined questions to capture project requirements.
Human-controlled decisions: Pricing and other sensitive commitments remain under human control.
Improved call coverage: Incoming calls can be handled by the support agent when the business team does not answer after three rings.
Centralized lead tracking: Lead progress is maintained in Thrive CRM through the final pipeline stage.
Client visibility: The customer-facing application provides access to call recordings and a way to flag interactions for review.
Tech Stack
ElevenLabs: Powers the AI voice agents, conversation handling, and voice interactions.
n8n: Orchestrates lead processing, calling workflows, conditional logic, CRM updates, and notifications.
Meta Lead Forms: Provides incoming prospect information from advertising campaigns.
Thrive CRM: Tracks leads and their progress through the sales pipeline.
Slack: Delivers lead qualification notifications to the business team.
Customer-Facing Application: Allows clients to listen to calls and flag interactions for changes.
Telephony Integration: Routes incoming business calls to the AI customer support agent while retaining existing phone numbers.
Where This Pattern Applies
The same approach can be adapted for businesses that need faster lead response and reliable phone support.
Home Services: Contact new inquiries immediately and qualify project requirements.
Real Estate: Follow up with property inquiries and identify serious prospects.
Marketing Agencies: Qualify advertising leads and notify sales teams about opportunities.
Healthcare: Handle routine appointment inquiries and route calls when staff are unavailable.
Professional Services: Capture new client requirements and manage incoming service inquiries.
Customer Support Teams: Provide automated call coverage outside busy periods.
The general pattern combines immediate AI-powered lead follow-up, structured qualification, automated customer call handling, and human oversight to help businesses respond faster and manage more conversations efficiently.
A self-hosted AI research platform that searches a trader's private documents and videos, provides source citations, reads chart information, and runs trading strategy backtests.
Section: Custom SaaS Platforms
Overview
This project delivers a private AI assistant for an active trader working with ICT trading concepts. It combines document and video search, AI-powered answers, chart analysis, and a Python backtesting engine in one platform. The system runs on the client's own VPS, keeping their data, infrastructure, and operating costs under their control.
The Problem
The client's trading knowledge was spread across hundreds of hours of mentorship videos, PDFs, Pine Script references, and price-data spreadsheets. Finding specific explanations required manually searching through documents and videos, while testing strategies meant writing code from scratch.
General-purpose AI assistants were not reliable enough because they could mix outside information with the client's material or provide incorrect chart prices with confidence. The client needed a private system that could provide source-backed answers and perform real backtests using their own data.
How It Works
Private AI Chat: Open WebUI provides a secure chat interface, with Caddy handling HTTPS and LiteLLM connecting the AI models.
Document Processing: The FastAPI and Haystack services extract content from uploaded documents, divide it into searchable sections, generate embeddings, and store them in Qdrant.
Video Processing: Videos are downloaded, transcribed, and analyzed using keyframes, OCR, and visual descriptions. The extracted information is indexed so users can search for specific explanations and chart moments.
Intelligent Retrieval: The platform combines keyword and semantic search, reranks results, and filters out low-confidence matches. A query planner also rewrites natural-language questions into clearer search queries.
Source-Based Answers: The AI answers using retrieved client materials and provides document-page or video-timestamp citations. Uncertain chart prices are marked rather than presented as confirmed values.
Trading Backtesting: An isolated Python environment runs strategy backtests, parameter sweeps, indicators, ICT pattern detection, performance metrics, and chart exports.
Administration and Monitoring: A Streamlit dashboard manages uploads, video processing, storage, costs, and restoration. Phoenix tracing and encrypted backups support monitoring and recovery.
The Result
The platform provides the client with a private workspace to search trading knowledge, review source materials, and test strategies. It also supports a shared knowledge base across different user accounts, allowing authorized users to access relevant documents and videos. By connecting AI-powered research with an isolated backtesting environment, the system keeps the client's data and infrastructure under their control.
Tech Stack
Open WebUI: Provides the private AI chat interface.
LiteLLM: Connects and manages AI models, including Gemini Flash.
FastAPI and Haystack: Handle document processing, retrieval, and RAG services.
Qdrant: Stores document and video embeddings for search.
PostgreSQL: Stores application state and related data.
Apache Tika: Extracts content from documents.
Voyage AI: Provides embeddings and reranking.
Groq ASR: Supports speech-to-text processing.
OCR and Vision Models: Extract and describe information from video frames and charts.
Python: Runs the trading backtesting engine and analysis tools.
Streamlit: Provides the administration dashboard.
Docker Compose and Caddy: Manage self-hosted services and HTTPS.
Phoenix / OpenTelemetry: Support tracing and monitoring.
restic and rclone: Handle encrypted backups and storage transfers.
Investment Research Teams: Retrieve information from private reports, documents, and recorded discussions.
Financial Educators: Make large libraries of training videos and learning materials searchable.
Quantitative Analysts: Combine AI-assisted research with automated backtesting and strategy evaluation.
Agriculture: Help farmers and agricultural organizations search farming guides, crop research, soil reports, weather records, and agricultural training materials.
Healthcare: Help medical research teams retrieve information from clinical studies, medical documents, and educational resources.
Education: Make institutional learning materials, lectures, research papers, and training content searchable.
Manufacturing: Provide AI-powered access to equipment manuals, maintenance records, technical documentation, and operational procedures.
Research Organizations: Build private AI assistants grounded in internal documents and datasets.
This pattern can be applied across industries wherever organizations have large collections of private information. By combining a shared knowledge base, AI-powered search, source-backed answers, and specialized analysis tools, organizations can turn their existing data into a searchable and useful research assistant while keeping control of their infrastructure.
Detailed ClickUp workspace structure for a staffing company’s operations.
Section: ClickUp Setups
01. Project Overview
This project organizes Taraki Staffing Company's operations into a structured ClickUp workspace. The workspace centralizes recruitment activities, client accounts, staffing requests, compliance tracking, onboarding, and performance reviews.
The setup uses dedicated folders, lists, custom fields, and automation rules to help teams manage tasks consistently and track work throughout the staffing lifecycle.
02. The Challenge
Staffing companies coordinate multiple interconnected processes, from publishing job openings and screening candidates to managing client requirements and onboarding placements.
Without a structured workspace, teams can face challenges such as:
Client Feedback: Records feedback dates, satisfaction levels, comments, and follow-up actions.
05. Automation and Workflow Rules
ClickUp automation rules support the processes defined within each list.
Recruitment: Notify the team when jobs are posted, send alerts when statuses change, remind recruiters about overdue vacancies, and initiate onboarding tasks after offer acceptance.
Client Management: Schedule quarterly account reviews, remind account managers about contract renewals, and flag urgent staffing requests.
Compliance and Onboarding: Create compliance tasks for new placements, flag unresolved issues, and notify teams when onboarding remains incomplete.
Performance Management: Remind reviewers about pending assessments, schedule future reviews, and create follow-up tasks based on employee or client feedback.
These rules are designed to reduce repetitive coordination and make task ownership and progress easier to track.
06. End-to-End Workflow
This workflow connects the major stages of staffing operations, from the initial client requirement through placement, onboarding, and ongoing performance management.
07. Key ClickUp Features
Custom Fields: Capture structured information specific to each operational process.
Dedicated Lists: Separate recruitment, client management, compliance, onboarding, and performance activities.
Status Tracking: Make task progress and outstanding work visible.
Automation Rules: Trigger reminders, notifications, and follow-up tasks based on configured conditions.
Centralized Workspace: Keep staffing operations organized within one ClickUp structure.
08. Expected Business Value
The workspace is designed to support:
Better visibility into recruitment and staffing requests.
More consistent candidate and placement tracking.
Improved coordination between recruitment and account management.
Clearer oversight of compliance and onboarding requirements.
More organized employee reviews and client feedback.
Less repetitive manual follow-up through configured automation rules.
09. Conclusion
The Taraki Staffing Company ClickUp setup provides a structured foundation for managing staffing operations in one workspace. By combining dedicated lists, custom fields, status tracking, and automation rules, the system helps teams coordinate recruitment, client relationships, compliance, onboarding, and performance management more consistently.
Compare payment and rooming records, identify discrepancies, and keep group travel organized with confidence through faster, smarter, and more accurate data reconciliation.
Section: Custom SaaS Platforms
Project Overview
The Paid List vs. Rooming List is a web application designed for a group travel company to compare payment records with room assignments. It identifies missing guests, unpaid balances, and similar-looking names, helping staff detect discrepancies quickly and maintain accurate travel records. Users can upload CSV files exported from Google Sheets and receive categorized comparison results without manually checking hundreds of rows.
Business Problem
The group travel company managed payment records and room assignments in separate Google Sheets, making it difficult to keep both lists consistent. Staff had to manually check hundreds of rows to identify guests who had paid but were missing from the rooming list, guests assigned to rooms without payment records, and names with slight spelling differences. This process was time-consuming, error-prone, and made it harder to identify discrepancies quickly.
Proposed Solution
The solution is a web application that compares the Paid List and Rooming List using uploaded CSV files exported from Google Sheets. It automatically matches guest names, verifies payment status, and categorizes results into three groups: Matched, Paid List Issues, and Rooming List Issues. It also highlights similar-looking names to help staff identify possible spelling differences and avoid overlooking guests. Each results table can be sorted and downloaded separately as a CSV file, making the reconciliation process faster and more reliable.
End-to-End Workflow
Image: Figure: Workflow Overview
How It Works
1. CSV Upload and Parsing: Staff upload the Paid List and Rooming List as CSV files exported from Google Sheets. The system handles differences in file formats, including header rows, optional row-number columns, and variations in payment column names.
2. Rooming List Processing: Rooming List rows are converted into individual guest records, including multiple occupants assigned to the same room.
3. Guest Name Matching: The system compares names using case-insensitive exact matching. If an exact match is not found, it checks for similar names based on shared surnames, minor spelling differences, or possible nicknames.
4. Discrepancy Detection: The application identifies guests missing from either list, flags payment statuses that are not marked “Paid in Full,” and highlights potential name matches for further review.
5. Categorized Results: Results are displayed in three separate tables: Matched, Paid List Issues, and Rooming List Issues. Red highlights indicate discrepancies, while yellow highlights indicate possible similar-name matches.
6. Review and Export: Staff can sort the results and download each table as a separate CSV file for further review and record-keeping.
Results Categories
Product Experience
The application provides a simple, browser-based interface that allows staff to upload CSV files, compare guest records, and review discrepancies in organized tables. Results are separated into three categories
Matched
Paid List Issues
Rooming List Issues
so users can quickly identify records that need attention. The tables support sorting and individual CSV downloads, making it easier to investigate issues and share results with the team.
Image: The upload screen: a staff member adds the Rooming List and Paid List CSVs exported from the group’s Google Sheet and clicks Compare.
Image: The results summary and the Paid List issues. Red rows are real discrepancies and yellow rows are similar-name warnings. Names, amounts, room and confirmation numbers are blurred for privacy.
Image: The Rooming List issues: people on the rooming list who are not on the paid list. Names and booking numbers are blurred for privacy.
Image: The matched list: people who paid in full and are on the rooming list, with no action needed. Names, amounts and booking numbers are blurred for privacy.
Technology Stack
Technology
Purpose
TypeScript
Core application logic and type-safe data processing
Node.js
Runs the backend using a plain HTTP server without a web framework
HTML, CSS & Vanilla JavaScript
Provides the browser interface, interactive result tables, sorting, and CSV downloads
Google Sheets & CSV
Source of the Paid List and Rooming List data, uploaded as CSV files
Railway
Cloud deployment and application hosting
Data Handling & Limitations
The application processes uploaded CSV files in real time and returns comparison results directly in the browser. It is stateless, meaning uploaded data is not saved to disk. Each comparison runs independently, and users can download the Matched, Paid List Issues, and Rooming List Issues tables as separate CSV files.
Limitations: The accuracy of the results depends on the quality and consistency of the uploaded data. Similar-name detection helps identify potential matches but may require manual verification. Staff should review flagged discrepancies before making changes to payment records or room assignments.
Closing Summary
The Paid List vs. Rooming List application simplifies group travel reconciliation by automatically comparing payment records with room assignments. Through exact name matching, similar-name detection, payment status validation, and categorized discrepancy reports, it helps staff identify issues faster and reduce manual checking. Built with TypeScript, Node.js, and a lightweight web interface, the tool provides a practical and efficient way to maintain accurate guest records and support smoother group travel operations.
Automated Order-to-Task Management and Asana Synchronization
Automation that turns sales orders into Asana tasks, with deadlines and project updates handled automatically.
Section: Make Automations
Overview
This solution connects NetSuite sales orders with Asana, automating task creation, deadline tracking, and project organization. It keeps order information and operational tasks aligned, reduces repetitive manual updates, and helps teams stay organized.
The Problem
Sales orders live in NetSuite, but the work needed to fulfil them is managed in Asana. Moving information between the two systems means manually creating tasks, transferring order details, checking deadlines, and keeping project sections organized.
Tasks can be duplicated, important order details can be missed, and statuses can fall out of date. When several projects are involved, keeping everything aligned becomes another job in itself.
How It Works
The solution uses three connected Make scenarios, each handling a different part of the operational workflow.
Receive sales order information. A custom webhook receives sales order data originating from NetSuite and starts the automation.
Process the order items. The workflow iterates through the line items and separates regular Asana items from TM Engraving items, sending each through its configured processing route.
Prepare structured task details. It combines item names, descriptions, quantities, engraving notes, and shipping methods where available.
Check for existing tasks. Before creating anything, the automation searches Asana using the sales order number and purchase order number.
Create or update the task. If no matching task exists, a new one is created. If a matching task already exists, its notes are updated instead of creating a duplicate.
Monitor deadlines and statuses. A second scenario retrieves active tasks from two configured Asana projects and evaluates their due dates, current sections, and existing status fields.
Update only when necessary. Conditional rules calculate the appropriate status based on configured date and section conditions. The automation updates the custom field only when a change is required and skips unnecessary updates
Organize tasks through events. A third scenario listens for Asana webhook events, identifies the associated task and project, determines the appropriate destination section, and moves the task using the Asana API..
The Result
The integrated automation manages the complete workflow between NetSuite, Asana, and Ashore. It automatically creates and updates Asana tasks from eligible sales orders, checks deadlines, updates task statuses, and organizes tasks into the appropriate project sections based on Ashore updates. This reduces manual task management, improves project organization, and keeps information synchronized across all three platforms.
Daily Automation Output
Metric
Combined Result
Successful workflow executions
65 per day
Successful execution rate
100% of displayed runs
Average execution time
1.66 seconds
Tasks created
4
Existing tasks updated
2
Scheduled deadline checks
24 per day
Note:Metrics are based on the observed day and may vary depending on daily sales order volume, task updates, and incoming Ashore events.
Daily Automation Activity
Tech Stack
Make: Runs all three automation scenarios and coordinates the workflow logic, routers, filters, iterators, and conditional operations.
NetSuite: Supplies sales order information, customer details, and order line items.
Asana: Manages operational tasks, project sections, due dates, notes, and custom status fields.
Asana API: Handles task searches, creation, updates, status changes, and section assignments.
Webhooks: Trigger the scenarios when sales order information or supported Asana task events are received.
Routers, Filters, Iterators, and Variables: Control processing paths, handle line items, evaluate conditions, and determine the appropriate task updates.
Where This Pattern Applies
This solution goes beyond task creation. It keeps sales orders, deadlines, task statuses, and project activities connected, helping teams stay organized across their daily operations.
Imagine a business receiving a new customer order through its CRM. The automation takes the order information, identifies the required work, checks whether a corresponding project task already exists, creates or updates it, assigns the relevant deadline, and keeps its status aligned as work progresses.
The same approach can be adapted to different business operations:
Sales: Convert new opportunities and closed deals into structured tasks and follow-up activities.
Manufacturing: Turn production orders into operational tasks with deadlines and progress tracking.
E-commerce: Coordinate order fulfilment, packaging, and shipping activities.
Insurance: Convert new claims into investigation and documentation tasks.
HR & Recruiting: Organize candidate onboarding, interview activities, and employee documentation.
Finance: Coordinate invoice approvals, payment processing, and reconciliation tasks.
Logistics: Manage shipment preparation, delivery coordination, and dispatch activities.
Customer Support: Convert incoming requests into trackable support tasks.
Project Management: Keep tasks, deadlines, statuses, and project sections synchronized across teams.
Professional Services: Coordinate client projects, deliverables, and internal assignments.
The underlying pattern remains the same: receive information, process it, check for existing records, create or update tasks, evaluate deadlines, synchronize statuses, and organize work based on events.
Whatever systems a business uses, the objective is the same: keep operational information connected and let automation handle the repetitive coordination.
An n8n workflow that turns one product photo into AI-generated model images plus eCommerce and lifestyle campaign shots, saved to Google Drive.
Section: n8n Automations, AI Agents, AI Agents for Ecommerce
Project Overview
The AI-Powered Fashion Campaign Image Generation system automates fashion visual production using n8n, Google Gemini, image generation APIs, and Google Drive. Starting with a single uploaded clothing image, the workflow analyzes the garment, develops creative prompts, generates a model image, and uses the original product and generated model as references for additional campaign visuals.
The final images are automatically uploaded to Google Drive, creating a streamlined process for producing consistent fashion and eCommerce assets without manually managing each stage of the creative workflow.
Technologies: n8n · Google Gemini · AI Image Generation APIs · Google Drive
01. The Problem: Manual Image Creation for Fashion Campaigns
Before automation, fashion campaign production required manual coordination across photography, creative direction, and AI image generation.
Common challenges included:
Time-consuming image conceptualization and generation.
Specialist prompt engineering for different image types.
Fragmented workflows for managing product images.
Delays and inconsistencies across campaign visuals.
Core challenge: Integrate the entire creative production pipeline into one automated system that generates high-quality, consistent fashion campaign images efficiently.
02. The Goal: A Fully Automated Fashion Photoshoot
The goal was to transform a single product photo into a complete set of AI-generated campaign assets through one workflow.
The system:
Accepts a clothing image through a simple form.
Analyzes the product and generates a suitable creative prompt.
Creates a photorealistic model image featuring the product.
Generates eCommerce studio shots and lifestyle campaign visuals.
Uses the original clothing and generated model images as references.
Uploads the resulting assets to Google Drive automatically.
This reduces manual coordination and streamlines creative production from input to final output.
03. The Solution: AI-Powered Fashion Image Generation
The workflow combines n8n automation with AI-powered image analysis, prompt generation, and image creation.
It uses internal workflow logic to develop creative directions, generates a model image from the original product photo, and then creates additional product and lifestyle visuals using both images as references.
All generated assets are organized in Google Drive, making them easier to access and manage.
04. How the System Works
Phase 1: Image Input and Model Creation
A form trigger receives the uploaded clothing image.
The image is converted to Base64 for API processing.
Workflow logic analyzes the garment and develops a creative prompt, including the intended model persona.
An AI image generation API using Google Gemini creates the fashion model image.
The generated model image is uploaded to Google Drive.
Phase 2: Prompt Generation and Campaign Image Creation
The original clothing image and generated model image are used as visual references.
The workflow creates prompts for eCommerce studio shots and lifestyle scenes.
AI image generation APIs produce the corresponding campaign visuals.
Generation results are checked for success.
Final images are uploaded to Google Drive.
05. Real-World Impact
Reduced Manual Prompting: Creative direction and prompt generation are handled by the workflow.
Faster Production: Multiple stages that previously required manual coordination run automatically.
Scalable Content Creation: The same workflow can be reused across a product catalog.
Organized Assets: Generated images are stored in Google Drive with predictable naming conventions.
06. Expected Impact
Time Savings
The workflow is designed to reduce manual creative and prompt-writing time by an estimated 70–90%, depending on the production process and level of review required.
Consistency and Coverage
Standardized prompts help reduce missing image angles, incomplete product coverage, and inconsistent lifestyle visuals.
Faster Content Production
Campaign visuals can potentially be generated on the same day products arrive, helping teams prepare new collections more quickly.
Asset Organization
Generated images are uploaded to Google Drive using predictable naming conventions, such as AI Model and Result #X, making image sets easier to browse.
Creative Efficiency
Reusable creative logic allows teams to produce more variations while reducing dependence on external photoshoots for every campaign asset.
07. Workflow Architecture
Product Image Upload: Receives the original clothing image.
Garment Analysis: Extracts visual details to guide image generation.
Creative Prompt Generation: Defines the model and visual direction.
AI Model Image: Creates the initial model image using the product reference.
Campaign Image Generation: Produces studio and lifestyle variations.
Google Drive: Stores the generated assets for later use.
Image: Fig:n8n automation workflow
08. Final Outcome
The workflow transforms a single clothing image into a collection of AI-generated fashion campaign visuals through an automated process.
Creative prompting is handled within the workflow.
Model, eCommerce, and lifestyle images are generated from visual references.
Multiple stages of image production run automatically.
Campaign assets are organized in Google Drive.
Reusable automation supports production across larger product catalogs.
The result: A streamlined fashion content production pipeline that helps brands create campaign-ready visuals faster, with more consistent creative direction and less repetitive manual work.
AI-Driven Instagram Video Breakdown: Decode What Makes Viral Content Tick
Automatically fetch and analyze top-performing Instagram videos from popular creators to uncover what makes them stand out.
Section: AI Agents
Project Overview
Understanding why an Instagram Reel performs well requires more than looking at its view count. The opening hook, visual presentation, setting, storytelling, and memorable moments can all provide useful insights for content planning.
This project automates the process of identifying high-performing videos from selected Instagram creators and analyzing their creative elements. The workflow retrieves creator usernames from Airtable, identifies each creator’s most-viewed Reel, collects its details, downloads the video for analysis, and uses AI to generate a structured breakdown.
The resulting insights are saved back to Airtable, creating a searchable reference for reviewing successful content and informing future creative decisions.
01. The Challenge
Content research can become repetitive when teams manually review creators, compare video performance, and document what makes individual Reels engaging.
The main challenges include:
Finding High-Performing Content: Identifying the strongest-performing Reel for each creator requires reviewing video performance data.
Manual Video Research: Collecting links, captions, creator names, and view counts takes time when handled individually.
Understanding Creative Techniques: View counts alone do not explain how a video attracts attention or maintains viewer interest.
Inconsistent Analysis: Without a consistent framework, different videos may be reviewed using different criteria.
Scattered Research Notes: Video observations can be difficult to organize and revisit when they are not stored in a structured database.
02. Project Objectives
The workflow was designed to automate video discovery and provide a consistent framework for analyzing creative content.
Its objectives are to:
Retrieve Instagram creator usernames from Airtable.
Identify the highest-viewed Reel available for each creator.
Capture essential video information, including the link, caption, creator name, and view count.
Download the selected video for closer analysis.
Use AI to examine the opening hook, overall mood, visual style, and standout moments.
Store the resulting analysis in Airtable for future reference.
03. The Solution
The solution combines Airtable-based creator tracking, automated video discovery, video downloading, and AI-assisted content analysis in a single workflow.
Rather than requiring a person to research and document every video manually, the workflow processes creator records, selects a top-performing Reel, and organizes its information for analysis.
The AI analysis focuses on four core areas:
Opening Hook
Examines how the video captures attention in its opening seconds, including the opening scene, action, or message that encourages viewers to keep watching.
Mood and Setting
Reviews the atmosphere of the video, including its background, environment, lighting, and overall energy.
Visual Style
Examines presentation elements such as on-screen text, clothing, framing, and other visible creative choices that contribute to the video's appearance.
Standout Moments
Identifies memorable or attention-grabbing moments that may help explain why viewers continue watching the video.
These observations are organized into a structured output and saved to Airtable alongside the relevant video information.
04. How It Works
Retrieve Creators: Read Instagram usernames from Airtable.
Find the Top Reel: Identify the most-viewed available Reel for each creator.
Collect Video Details: Capture the video link, caption, creator name, and view count.
Download the Video: Prepare the selected Reel for closer analysis.
Analyze with AI: Examine the hook, mood, visual style, and standout moments.
Save the Insights: Write the structured analysis back to Airtable.
Demo:
05. Workflow
06. Key Features
Automated Creator Research: Uses Airtable as the source for Instagram creator usernames.
Performance-Based Selection: Focuses on the most-viewed available Reel for each creator.
Video Metadata Collection: Organizes essential information about each selected video.
AI-Assisted Creative Analysis: Applies consistent analysis criteria to the selected content.
Structured Content Breakdown: Separates observations into hook, mood, visual style, and standout moments.
Centralized Results: Stores video information and analysis in Airtable.
Scheduled Execution: Supports daily, weekly, or monthly scheduling when configured in the automation platform.
07. Technology Stack
Technology
Purpose
Instagram
Source of creator videos and Reel content
Airtable
Stores creator records, video details, and analysis results
Automation Workflow
Coordinates video discovery, downloading, analysis, and data storage
AI Analysis
Examines the video's creative and storytelling elements
Note: The exact AI provider and video-downloading service are not specified in the supplied case study details.
08. Business Benefits
Faster Content Research
Automates repetitive steps involved in finding videos and collecting their key information.
More Consistent Analysis
Uses a common set of creative criteria to review videos, making observations easier to compare.
Organized Creative Intelligence
Keeps video metadata and analysis together in Airtable rather than scattered across separate notes.
Better-Informed Content Planning
Provides a structured reference for exploring hooks, visual presentation, storytelling, and other creative techniques used in high-performing videos.
09. Conclusion
The AI-Driven Instagram Video Breakdown workflow turns video research into a more organized and repeatable process. By combining creator tracking, Reel selection, video downloading, AI-assisted analysis, and Airtable storage, it helps transform individual videos into structured creative insights.
The result is a centralized content research process that makes it easier to review successful Reels, compare creative approaches, and use documented observations to guide future content planning.
An always-on automation that detects abandoned Shopify carts and sends personalized, AI-written recovery emails.
Section: n8n Automations, Make Automations, AI Agents, AI Agents for Ecommerce
01. The Problem: Abandoned Carts Were Leaving Revenue on the Table
Before automation, abandoned carts were often handled manually or received no follow-up at all.
Teams had to check Shopify manually for abandoned checkouts.
Writing reminder emails took time and effort.
Follow-ups were inconsistent, and many carts were never contacted.
Generic emails lacked personalization.
Delayed reminders reduced the chance of customers completing their purchases.
The Cost of Manual Follow-Ups
For stores handling 40–60 abandoned carts per day:
Each follow-up took approximately 5–7 minutes.
Manual work could consume 3–5 hours daily.
Some stores followed up only once a day or skipped follow-ups entirely.
Without timely reminders, potential sales were lost.
02. Results After Automation
The automated workflow ensures abandoned checkouts receive timely, personalized recovery emails with minimal human intervention.
100% recovery-attempt coverage: Every detected abandoned cart receives a recovery attempt.
90–95% less manual work: Repetitive follow-up tasks are automated.
Faster communication: Recovery emails are sent within the configured time window.
AI personalization: Each email is generated to provide a relevant, friendly reminder.
Time Savings
Metric
Before Automation
After Automation
Follow-up process
Manual
Automated
Time per cart
Approximately 6 minutes
Minimal manual effort
Daily workload
Around 3–5 hours
Near-zero routine effort
Monthly time savings
—
Approximately 100–120 hours
Potential Revenue Impact
Using a conservative example of 50 abandoned carts per day, a $50 average cart value, and a 5–8% recovery rate:
Potential recovered sales: $125–$200 per day.
Potential recovered sales: Approximately $3,750–$6,000 per 30-day month.
These figures are illustrative estimates, not guaranteed results. Actual performance depends on store traffic, customer behavior, email deliverability, and conversion rates.
03. The Solution: AI-Powered Abandoned Cart Recovery
The system works as an always-on sales assistant that follows up with customers automatically.
It:
Detects abandoned Shopify checkouts.
Waits for a configured period before sending a reminder.
Verifies that the checkout is still abandoned and has not been completed.
Uses AI to generate a personalized recovery email.
Sends the email automatically through Gmail or a configured email service.
The workflow operates in the background, reducing repetitive work while keeping follow-ups consistent.
04. How the Automation Works
The workflow connects Shopify, an automation platform, AI, and email delivery.
Smart Amazon Product Tracker for Price Drop Alerts
To fetch product details from Amazon and alert you if the price drops, because who doesn’t love a good deal? 💸
Section: AI Agents
Project Overview
This project automates the process of monitoring Amazon product prices. Product links are stored in Airtable, where the workflow retrieves the records and sends product URLs to Apify for scraping. Once the scraping process is complete, the workflow retrieves the latest product information, updates the corresponding Airtable records, and checks whether the price has decreased.
When a price drop is detected, an email notification is sent to alert the user. The latest price is saved so it can be used for future comparisons.
01. The Challenge
Monitoring multiple Amazon products manually can be time-consuming and inconsistent. Prices may change between checks, making it difficult to identify savings opportunities quickly.
The main challenges included:
Manual Price Monitoring: Users must repeatedly visit product pages to check for price changes.
Scattered Product Information: Tracked products and their previous prices need to be organized in a central location.
Delayed Price-Drop Detection: Without automated comparisons, a lower price may go unnoticed.
Repetitive Data Updates: Product details and prices must be refreshed regularly to keep tracking records current.
Lack of Timely Notifications: Users need a convenient way to learn when a tracked product becomes cheaper.
02. The Solution
An automated workflow connects Airtable, Apify, AI-assisted URL processing, and Gmail to handle product monitoring from beginning to end.
The workflow retrieves tracked products from Airtable, processes each product URL, launches an Apify scraping task, and waits for the results. It then updates the product record with the latest information and compares the new price against the previously stored price.
If the price has decreased, the workflow sends an email notification. If no price drop is detected, it updates the record without sending a price-drop alert.
03. How the Automation Works
Image: n8n working flow
Step 1 — Retrieve Products from Airtable
The workflow begins by retrieving product records from Airtable. These records contain the product information and links needed for price monitoring.
Airtable acts as the central tracking database, allowing the workflow to process multiple products without requiring each product to be entered manually into the scraping process.
Step 2 — Process Product URLs
The workflow loops through the retrieved product records and processes each product URL individually.
A Google Gemini-powered AI component helps format URLs when necessary, including handling quotation marks or other formatting issues that could interfere with the scraping request.
Step 3 — Launch the Apify Scraper
The processed product URL is submitted to Apify through an API request. Apify performs the scraping operation to retrieve available product details from Amazon.
This separates the scraping task from the rest of the workflow and allows the automation to process the results once the scraping operation has finished.
Step 4 — Wait for the Scraping Process
After launching the scraper, the workflow waits for the task to complete. It then requests the results from Apify.
This step ensures that the workflow retrieves the scraping output before attempting to update the product record or compare prices.
Step 5 — Update Product Information
The retrieved product details are written back to the corresponding Airtable record.
Keeping the product data in Airtable provides a centralized view of the tracked products and their latest recorded prices.
Step 6 — Check for a Price Drop
The workflow evaluates whether the latest product price is lower than the previously stored price.
Price decreased: The workflow follows the notification branch.
No price decrease: The workflow follows the alternative branch and updates the latest price for future comparisons.
This conditional step ensures that price-drop emails are sent only when the configured comparison identifies a decrease.
Step 7 — Send an Email Alert
When a price drop is detected, the workflow uses Gmail to send an email notification.
The alert informs the user that the tracked product has become cheaper, allowing them to revisit the product and decide whether to purchase it.
Step 8 — Maintain Updated Records
The workflow saves the latest price regardless of whether a price drop is detected. This keeps the stored information current and provides a reference point for subsequent monitoring runs.
04. Workflow
05. Technology Stack
Technology
Role
Airtable
Stores product records and updated price information
Apify
Scrapes available Amazon product details
Google Gemini
Assists with product URL formatting
Gmail
Sends email notifications when a price drop is detected
API Requests
Connect the workflow to the scraping service
06. Key Features
Automated Product Tracking: Retrieves tracked products from Airtable.
Batch Processing: Processes product records through a loop.
AI-Assisted URL Formatting: Helps prepare product URLs for scraping.
Automated Data Collection: Retrieves available product details through Apify.
Conditional Price Comparison: Determines whether the latest price is lower than the stored price.
Email Notifications: Sends alerts when a price decrease is detected.
Centralized Record Management: Updates product information in Airtable.
Recurring Monitoring Support: The workflow can be configured to run on a schedule, subject to its scheduling configuration.
07. Business Benefits
Less Manual Work
Automates repetitive product-page checks, data collection, and record updates.
Faster Price-Drop Awareness
Email notifications help users discover price decreases without continually checking Amazon manually.
Better Data Organization
Airtable provides a central place to maintain tracked product records and current prices.
Consistent Monitoring
The workflow follows the same scraping, comparison, and update process for each product it processes.
08. Conclusion
The Smart Amazon Product Tracker demonstrates how API-based scraping, AI-assisted processing, conditional logic, and automated notifications can work together in a single workflow.
By connecting Airtable, Apify, Google Gemini, and Gmail, the solution automates product data collection, maintains updated price records, and notifies users when a tracked product becomes cheaper.
A scheduled workflow that tracks product prices, logs history to Google Sheets, and alerts you only on meaningful price drops.
Section: n8n Automations, AI Agents, AI Agents for Ecommerce
Project Overview
The AI-Powered E-Commerce Product Price Monitoring system automates product price tracking, historical data collection, and intelligent price-drop alerts. Built with n8n, Google Sheets, Slack, OpenAI, and Gemini, it regularly collects product prices, compares them with historical records, and identifies meaningful changes.
By automating repetitive price checks and notifying users only when relevant opportunities arise, the system helps users make informed purchasing decisions while saving time and avoiding unnecessary alerts.
01. The Problem: Manual Price Checking Wastes Time
Before automation, tracking product prices across online stores was slow, repetitive, and error-prone.
Users had to manually:
Open multiple product pages.
Check prices repeatedly.
Record or remember previous prices.
This often resulted in missed price drops, limited-time deals, and a lack of historical visibility into price trends. Buying decisions were frequently based on incomplete information rather than reliable data.
Impact per user
30–60 minutes per day spent manually checking prices.
Missed savings on deals and discounts.
Decisions based on incomplete price information.
Core challenge: Users want to buy at the right time without constantly monitoring product prices themselves.
02. Results After Automation
After implementation, the system automatically monitors prices, records historical data, and sends alerts when meaningful changes occur.
Key improvements
Automated daily price monitoring.
Notifications triggered by meaningful price changes.
Historical price trends available in Google Sheets.
Data-driven purchasing decisions.
Minimal human involvement in routine monitoring.
Time and effort savings
Before
Approximately 45 minutes per day.
Around 22.5 hours per month spent checking prices manually.
After
Price checks and comparisons run automatically.
Human effort for routine monitoring is close to zero.
Approximately 20–25 hours saved per user each month.
Accuracy and opportunity gains
Consistent recording of monitored prices.
Timely alerts for price drops and limited-time deals.
Better comparisons based on historical data and AI analysis.
03. The Solution: AI-Powered Price Monitoring
The system acts as a virtual price tracker and analyst by combining scheduled data collection, historical tracking, AI analysis, and automated notifications.
It:
Collects product prices on a defined schedule.
Logs historical prices in Google Sheets.
Evaluates price changes and potential value opportunities using AI.
Sends notifications through Slack or other configured channels.
Reduces notification noise by alerting users only when meaningful changes occur.
04. How the System Works
Phase 1: Scheduled Price Collection
The workflow runs automatically on a daily or custom schedule.
It visits configured product pages and extracts:
Product name.
Current price.
Incomplete or erroneous entries are skipped.
Phase 2: Price Comparison and History Logging
Current prices are compared across monitoring runs.
Each successful run adds a new row to Google Sheets.
Historical records build a timeline of price changes.
Phase 3: AI-Driven Analysis
OpenAI or Gemini evaluates the collected information to help identify:
Current prices compared with historical prices.
Products offering better value.
Significant changes that may justify a notification.
Phase 4: Smart Notifications
Notifications are sent when configured conditions are met, such as a significant price drop or a better deal becoming available.
Alerts can be delivered through Slack, email, or other configured channels.
No alert is sent when there is no meaningful change.
05. Business Value
Zero Manual Monitoring: Routine price checks run automatically.
Never Miss a Deal: Timely alerts highlight potential savings.
Data-Driven Decisions: AI analysis supports product comparisons.
Historical Visibility: Price records reveal trends over time.
A Python pipeline (Prefect, Skyvern and GPT-4.1) that quotes all 22 approved suppliers for every ingredient reorder and delivers a ranked comparison in about four hours instead of 3.5 days.
Section: Python Automation
At a glance
Mid-size generic drug manufacturer, ~40 SKUs in production. Five weeks. Python 3.12, Prefect, Skyvern Cloud, OpenAI GPT-4.1, Postgres, S3, Slack. Went from quoting a fifth of their supplier base per order to quoting all of it.
The 6% nobody could see
Production planning flags a reorder for an active ingredient. A procurement officer opens a portal, searches the CAS number, pulls a price, downloads the spec sheet, pastes it into Excel. Then the next portal. Then the next.
Twenty-two suppliers were on the approved list. In practice the officer got through five or six before the purchase order had to go out, and the same five or six every time, the ones with the least annoying logins.
The waste wasn't the officer's afternoon. It was the sixteen vendors nobody had time to ask. When the full list was finally quoted, the cheapest compliant supplier turned out not to be one of the usual five surprisingly often.
Why this wasn't a scraping job
Three things ruled out the obvious approach, and a hand-written Playwright suite had already been abandoned for exactly these reasons.
Vendors don't agree on what anything is called. Metformin HCl USP, metformin hydrochloride BP/EP, or a bare product code, same molecule, three listings, no shared key except the CAS number buried somewhere on the page.
Quotes don't arrive in one shape. Some portals render a price table. Some hand back a PDF. Some won't tell you anything until you've submitted an RFQ form and waited for an email.
And it's a regulated purchase. Pharmacopoeia grade, GMP status, and whether the supplier holds a DMF or CEP are pass/fail gates, not preferences. A cheap quote from a vendor without the right filing isn't a cheap quote. It's not a quote at all. Every choice has to survive an audit two years later.
Following one RFQ through
Image: Multi-vendor ingredient quoting pipeline: RFQ intake (CAS number, grade, quantity), a Skyvern browser handles login, 2FA and CAPTCHA, prices come from an in-page table or from a downloaded and parsed PDF or emailed quote, GPT-4.1 normalises and validates them, and the ranked comparison goes to a Slack thread with an audit log.
A reorder request arrives as a CAS number, a grade, and a quantity. Before anything opens a browser, that gets resolved against an internal ingredient register, deterministically, on the CAS number, never on the product name.
Prefect then fans the request out to twenty-two isolated subflows, one per vendor. Each launches its own Skyvern cloud browser and logs in. Nine of these portals want 2FA and two sit behind CAPTCHAs; that's handled inside the login step rather than being a per-vendor engineering problem.
From there the paths diverge by portal. Where the price sits in the page, it's read straight off the page against a schema. Where it only exists as a PDF or an emailed quote sheet, the file is downloaded and parsed separately.
Everything then funnels back into a single normalisation pass, one model call, one strict schema, twenty-two vendors reduced to comparable rows: unit price, currency, unit of measure, MOQ, lead time, incoterm, grade, GMP status, DMF reference.
The ranked comparison lands in Slack about four hours later, with every row linking to the evidence behind it.
Four forks in the road
Skyvern rather than raw Playwright
The rejected option was writing and maintaining twenty-two scripts. That's what had already failed. At this many portals somebody is always redesigning something, and the maintenance load quietly exceeded the hours the automation was saving. Buying the resilience rather than building it was the entire reason the project was viable a second time.
1Password rather than a second vault
Skyvern can read credentials from several providers, and the client was already on 1Password. The alternative, standing up a dedicated secrets store, would have meant twenty-two sets of credentials living in two places, which is worse security dressed up as better engineering.
Selectors first, model second
Every stable element on a page gets a selector and a prompt. The selector runs, costs nothing, and usually works; the model only engages when it misses. Going model-first on everything would have been simpler to write and roughly ten times the running cost.
The model never decides what an ingredient is
It was tempting to let a model reconcile vendor product names. It isn't allowed to. Where a listing has no CAS field, the model may suggest a match, and that suggestion goes to a human. Misidentifying an ingredient in this industry isn't a data quality issue, and no accuracy figure would have made that trade acceptable.
When it breaks
Image: Route Memorization in practice: a memorized route replays deterministically. If the replay works the quote is captured with its evidence hash; if the route breaks it is regenerated by AI with a diff alert; if it keeps failing it goes to a review queue with the session recording attached.
Skyvern's Route Memorization compiles a successful run into a deterministic script and replays it. When a portal changes and the replay fails, it re-plans with AI, finds the new path, and regenerates the script. That mechanism does the heavy lifting here.
What it doesn't do is announce itself. A regenerated route is a silent event, and silent events don't belong in a regulated purchasing process.
So the wrapper watches for it. Each subflow records its action count and wall-clock duration; a memorised replay sits in a tight, predictable band, and an AI re-plan blows straight through it. That signal tags the run as a regeneration, diffs the new route against the old one, and drops a summary into Slack so someone can see what the portal changed before the next cycle.
If a regenerated route produces a quote that can't be evidence-checked, that vendor goes to a review queue with its session recording attached instead of into the comparison. About 4% of quotes land there, mostly from two portals that render prices as images.
The result is that failure is local. One portal breaking means twenty-one quotes still land and the RFQ is still useful.
Monday.com board setup built for Veterinary Specialist Partners’ operations.
Section: Monday.com Setups
Project Overview
Veterinary Specialist Partners (VSP) operates specialized veterinary hospitals in Louisville and Evansville, providing care for pets with complex medical conditions.
Before the implementation, appointment scheduling, patient records, follow-up communications, and referrals relied heavily on manual processes. VSP partnered with our team to configure monday.com as a centralized operational workspace and automate key processes from appointment booking through patient follow-ups and referral management.
01. The Challenge
Manual Appointment Scheduling
Appointments were managed through phone calls and in-person scheduling, creating administrative bottlenecks and additional workload.
Fragmented Patient Records
Patient histories, treatment records, and supporting documents were spread across different platforms, making information harder to retrieve and manage.
Inconsistent Follow-Up Communications
Manual follow-up scheduling and patient reminders were prone to delays and errors.
Referral Coordination
Managing referrals between specialists required better tracking and coordination to ensure patients were not overlooked.
02. Project Objectives
The implementation focused on three primary objectives:
Automate Appointment Management: Streamline appointment booking, updates, and cancellations.
Centralize Patient Information: Organize patient histories, treatment records, and supporting documents in monday.com.
Improve Communication: Automate appointment reminders, follow-up tasks, and referral-related workflows.
03. Solutions Implemented
A. Automated Appointment Management
New appointments booked through the configured process are captured in a dedicated monday.com appointments board.
Separate groups organize appointments by type and location.
Appointment entries provide a central place to track scheduling information.
Automated registration and check-in processes capture required patient information.
Patient information is linked to the corresponding appointment entry.
B. Calendly Integration
Calendly is integrated with monday.com to synchronize appointment bookings and cancellations.
New bookings are reflected in the relevant monday.com board.
Appointment cancellations update the corresponding records.
The integration helps maintain consistent scheduling information across both platforms.
C. Email and SMS Reminders
Automated reminders notify patients about upcoming appointments.
SMS reminders provide an additional communication channel.
Automated notifications reduce reliance on manual reminder messages.
D. Centralized Patient Records
monday.com serves as the central workspace for organizing patient-related information.
Custom forms collect patient histories and treatment information.
Relevant documents can be uploaded directly into the system.
Records are linked to the appropriate patient or appointment entries.
Access levels are configured for different team members to help protect sensitive information.
E. Follow-Up Task Automation
Follow-up tasks are created and linked to specific appointments.
Post-appointment follow-ups can be tracked centrally.
Team members can monitor outstanding tasks.
Automated task creation helps reduce the chance of missed follow-ups.
F. Referral Management
A dedicated monday.com board manages referrals to and from other specialists.
Referrals are recorded in a centralized workspace.
Specific workflows are triggered for referral-related activities.
Relevant records can be coordinated with the appropriate parties.
Referral status can be tracked to help ensure each case receives attention.
04. System Workflow
This workflow brings appointment scheduling, patient information, communication, and ongoing care coordination into one operational process.
05. Outcomes and Business Value
Improved Operational Efficiency
Automating appointment handling reduces repetitive administrative work and helps minimize errors associated with manual scheduling.
Centralized Data Management
Organizing patient histories, treatment records, and appointment information in monday.com makes records easier to access and supports more informed operational decisions.
More Reliable Patient Communication
Automated email and SMS reminders reduce dependence on manual messaging and help patients stay informed about upcoming appointments.
Better Follow-Up Coordination
Linked follow-up tasks provide a structured way to track post-appointment activities and outstanding work.
Improved Referral Management
A dedicated referral board and associated workflows help organize referrals and coordinate activities between specialists.
The original case study describes these qualitative outcomes but does not provide numerical measurements for time saved, no-show reduction, or error reduction.
06. Technical Highlights
monday.com Customization
Custom boards and fields tailored to appointment and patient workflows.
Automation rules for appointment handling, reminders, follow-ups, and referrals.
Separate board groups to organize appointments by type and location.
Linked records to connect patient information with appointments and tasks.
Configured access levels for team members.
Integrations
monday.com: Central operational workspace.
Calendly: Appointment booking and cancellation synchronization.
Email platforms: Automated patient reminders.
SMS gateways: Appointment notification messages.
Medical record software: Listed as part of the integration suite in the original case study.
The exact configuration of each external integration depends on the connected services and deployed automation rules.
07. Future Improvements
Ongoing Optimization
Continue refining boards and automation rules based on team feedback and changing operational requirements.
Expanded Automation
Identify additional manual processes across hospital operations that could benefit from automation.
Workflow Refinement
Review appointment, follow-up, and referral workflows regularly to ensure they remain aligned with the hospital's operational needs.
08. Final Outcome
The monday.com setup provides Veterinary Specialist Partners with a more structured way to manage appointments, patient information, reminders, follow-ups, and referrals.
By centralizing operational records and automating repetitive coordination tasks, the solution helps reduce manual administrative effort and supports more consistent communication across the veterinary care process.
An automation that generates LinkedIn captions and images, sends them for approval, and publishes only approved posts.
Section: n8n Automations, AI Agents, AI Agents for Ecommerce
Project Overview
The AI-Powered Social Media Content Creation system automates the process of generating, reviewing, and publishing LinkedIn content. Built with n8n, LinkedIn, Google Sheets, and Google Drive, it uses AI to create captions and matching post images while maintaining a centralized record of content and approval status.
By introducing an approval step before publishing, the system helps teams maintain consistent brand messaging, reduce repetitive work, and manage their social media content through a single workflow.
Technologies: n8n · LinkedIn · Google Sheets · Google Drive · AI Content Generation
01. The Problem: Social Media Management Is Inconsistent
Before automation, creating and publishing social media content required multiple tools and manual steps.
Teams had to:
Write captions repeatedly.
Design post images manually.
Maintain content variety and avoid duplication.
Track approvals through email or chat.
Publish posts manually on LinkedIn.
Keep track of drafts, approvals, and published content.
Impact per team
2–4 hours per day spent creating, approving, and publishing posts.
Risk of duplicate, missed, or unapproved posts.
Inconsistent brand messaging across channels.
Core challenge: Teams needed a reliable system to create, review, approve, and publish content at scale without unnecessary operational complexity.
02. Results After Automation
After implementation, content creation and publishing became a structured, automated process.
Key improvements
Captions and images are generated automatically.
Posts are published only after approval.
Google Sheets provides a centralized content control panel.
Manual content creation and publishing effort is significantly reduced.
Time and effort savings
Before
Approximately 3 hours per day.
Around 60 hours per month, based on 20 working days.
After
Automated content generation and publishing.
Human involvement mainly required for approvals, estimated at 5–10 minutes.
Monthly impact
Approximately 50–55 hours saved per team per month.
More time available for planning, strategy, and other creative work.
Consistency and tracking improvements
Approved posts follow the configured brand tone and guidelines.
Approval controls help prevent unauthorized publishing.
Content status and live post URLs are recorded centrally.
03. The Solution: AI-Powered Social Media Automation
The system acts as a virtual social media assistant that manages content from creation to publication.
It:
Generates LinkedIn captions based on topics, brand tone, and content goals.
Creates post images aligned with the generated captions.
Uses Google Sheets to manage content and approval status.
Sends posts for approval before publishing.
Publishes approved posts to LinkedIn.
Records publishing status and live URLs for tracking and reporting.
04. How the System Works
Phase 1: AI Caption Generation
The workflow starts when a new row is added to Google Sheets.
AI generates captions based on:
Topic.
Brand context.
Content objective.
The captions are formatted for LinkedIn and saved in Google Sheets for review and approval.
Phase 2: Image and Post Creation
The generated caption is used to create a matching AI-generated image.
The image is uploaded to Google Drive.
The image URL is stored in Google Sheets.
Caption, image URL, and status are maintained in the control panel.
Content remains visible for review and approval.
Phase 3: Approval and Publishing
Approval emails are sent automatically.
Posts remain blocked until approval is received.
Only approved posts are published on LinkedIn.
Google Sheets is updated with:
Publishing status.
Live post URL.
This provides a centralized record of the content lifecycle and helps prevent missed or duplicate publishing.
05. Business Value
End-to-End Automation: Manages content generation through publishing in one workflow.
Centralized Control Panel: Tracks drafts, approvals, and published posts.
Consistent Brand Voice: Applies configured tone and style guidelines.
Approval-Safe Publishing: Prevents publishing before explicit approval.
Full Tracking and Reporting: Maintains content statuses and live URLs.
Time and Cost Savings: Saves an estimated 50+ hours per team each month.
06. Workflow Architecture
Each component has a defined role:
Google Sheets: Triggers content creation and tracks captions, image URLs, and statuses.
AI Caption Generation: Creates captions from the topic and brand context.
Image Generation: Produces visuals aligned with the captions.
Google Drive: Stores generated images.
Approval: Ensures posts are reviewed before publishing.
LinkedIn Publishing: Publishes approved content.
Status Update: Records publication status and the live post URL.
07. How to Replicate the System
Step 1: Import the Workflow
Open the attached Social Media Automation Workflow.json file.
Copy the complete JSON content.
Open your n8n cloud or self-hosted instance.
Create a new workflow and paste or import the JSON.
Save and rename it to Social Media Content Automation.
Step 2: Configure Connections
Google Sheets: Connect your account and configure columns for Topic, Caption, Image URL, Status, and Post URL.
AI Caption Generation: Add the required AI credentials and verify the brand context and prompts.
Image Generation: Confirm that image prompts are derived from captions and images are saved to Google Drive.
Approval: Configure email credentials and verify the approval logic.
LinkedIn: Connect the appropriate account and configure publishing permissions.
Step 3: Test the Workflow
Run the workflow manually and verify that:
Captions and images appear in Google Sheets.
Approval logic blocks unapproved posts.
Approved posts publish correctly.
Publishing statuses and live URLs update accurately.
Step 4: Activate the Automation
Once testing is complete, activate the workflow and verify its trigger settings.
Content generation, approval, and publishing can then run automatically with minimal manual involvement.
08. Final Outcome
The AI-powered workflow transforms social media management into a consistent and trackable process.
Content creation becomes faster and more repeatable.
Publishing follows an approval-based process.
Teams manage content through a centralized control panel.
Publishing activity and live URLs remain available for tracking.
An estimated 50+ hours of manual work can be saved per team each month.
The result: A more efficient, approval-controlled social media workflow that allows teams to scale content production without proportionally increasing manual effort.
An AI-powered WhatsApp assistant that automates customer support through text, voice, and image understanding, delivering instant, knowledge-based responses 24/7.
Section: n8n Automations, AI Agents, AI Agents for WhatsApp, AI Agents for Ecommerce
01.Project Overview
The AI-Powered WhatsApp Message Assistant is an intelligent customer support solution built with n8n, OpenAI, WhatsApp, and Supabase. It automates customer conversations by understanding text, voice messages, and images, then generating relevant responses based on business knowledge.
Using AI-powered processing and semantic search, the assistant delivers consistent, context-aware support around the clock, reducing repetitive manual work and allowing human agents to focus on more complex customer inquiries.
02. The Problem: WhatsApp Customer Support Didn’t Scale
Before automation, customer support over WhatsApp was entirely manual and increasingly difficult to manage.
Staff had to respond to every message individually, including repetitive questions about products, prices, availability, and store policies. Voice messages required manual listening and interpretation, while image-based questions, such as product photos, needed human review. Responses varied depending on the staff member, and support was unavailable outside business hours.
For a small business receiving 80–120 WhatsApp messages per day, this resulted in:
High Manual Workload: 4–6 hours per day spent answering routine questions.
Delayed Responses: Longer waiting times during peak hours.
Missed Inquiries: Customer messages going unanswered outside working hours.
Staff Dependency: Heavy reliance on trained employees with product knowledge.
Inconsistent Support: Different responses depending on who handled the conversation.
Core Challenge: WhatsApp was the main customer communication channel, but human-only support could not keep up with demand without increasing headcount.
03. Results After Automation
After deploying the WhatsApp AI Business Assistant:
70–85% of incoming queries were handled automatically.
Customers received instant replies, including outside business hours.
Voice messages were transcribed and answered automatically.
AI understood image-based queries involving products and issues.
Responses became more consistent, accurate, and aligned with business policies.
Human agents focused on complex or exceptional conversations.
Time and Workload Impact
Before Automation
Approximately 3–4 minutes per WhatsApp message.
Around 100 messages per day required approximately 5–6 hours of support time.
After Automation
Human involvement was limited to approximately 15–30 messages per day.
Manual support time decreased to around 1–1.5 hours per day.
Estimated Time Savings
3–4 hours saved per day.
90–120 hours saved per month.
This allowed the business to scale WhatsApp support without hiring additional staff.
04. The Solution: An AI Assistant Inside WhatsApp
The system acts as a virtual support agent directly within WhatsApp.
Understands text, voice messages, and images.
Maintains conversation context.
Retrieves relevant business knowledge instantly.
Generates natural, context-aware responses.
Supports text or voice replies when appropriate.
Customers receive fast, helpful support without needing to change how they communicate with the business.
05. How the System Works
Customer Message: Customers contact the business through WhatsApp.
Message Understanding: AI identifies the message type and intent.
Knowledge Retrieval: Relevant business information is retrieved using semantic search.
Response Generation: AI generates a context-aware answer based on the available information.
WhatsApp Reply: The response is delivered automatically to the customer.
The workflow processes messages automatically within seconds.
06. Business Value
Reduced Manual Workload: Automates repetitive customer support tasks.
A structured ClickUp workspace designed to manage ecommerce dropshipping operations, including order fulfillment, customer service, product management, marketing, website maintenance, and branding.
The Boots & Bags E-Commerce Operations workspace organizes the store’s major business processes within ClickUp. Dedicated folders, lists, custom fields, templates, and automation rules help teams manage orders, resolve customer issues, coordinate product listings, monitor marketing activities, and maintain website quality.
02. The Business Challenge
Ecommerce dropshipping operations involve several connected activities that need to be coordinated efficiently.
Order fulfillment: Tracking orders, inventory shortages, disputes, and reshipments.
Customer service: Managing customer inquiries and approved reshipment requests.
Product management: Organizing product research and preparing product pages for publication.
Marketing coordination: Tracking advertising campaigns and coordinating promotional communications.
Website maintenance: Monitoring website performance, SEO, user experience, and branding consistency.
Without a structured workspace, these activities can become difficult to track and coordinate across teams.
03. The Solution
A dedicated ClickUp workspace was organized under the main folder Boots & Bags E-Commerce Operations, with five operational areas:
Fulfillment
Customer Service
Collection and Product Pages
Marketing
Website and Branding
Each area contains purpose-specific lists, relevant custom fields, and automation rules to support task tracking and follow-up.
04. Workspace Structure
A. Fulfillment
Manages order processing, stock shortages, disputes, and reshipment activities.
Orders Management
Tracks order ID, customer name, order date, status, product SKU, quantity, and shipping address.
Imports orders from Shopify.
Notifies the fulfillment team when a new order is entered and flags urgent orders based on delivery dates.
Out of Stock
Tracks product ID, last available date, expected restock date, and supplier contact.
Alerts the purchasing manager when inventory falls below a predefined threshold.
Disputed Orders
Records the order ID, dispute reason, resolution status, customer contact, and resolution date.
Escalates unresolved disputes older than five days to senior management.
Order Reshipment
Tracks the original order ID, reshipment reason, new tracking number, and reshipment status.
Creates reshipment tasks after customer service approval and notifies logistics.
Templates
Order Processing Checklist
Dispute Resolution Guide
B. Customer Service
Organizes customer requests and coordinates approved reshipments with the fulfillment team.
Creates a linked task in the Order Reshipment list when a request is approved.
Notifies the customer when the request has been processed.
Template
Customer Inquiry Response Template for common customer questions and issues.
C. Collection and Product Pages
Coordinates product discovery, approval, and preparation for Shopify publication.
Product Research
Tracks product ID, research date, approval status, market analysis, and supplier details.
Moves approved products to the Product Upload list and notifies the upload team.
Product Upload
Tracks product ID, upload date, SEO keywords, price, and image URLs.
Notifies marketing when a product is live and ready for promotion.
Templates
Product Proposal Template
Product Upload Checklist
D. Marketing
Organizes paid advertising and direct marketing campaigns across multiple channels.
Facebook Marketing
Tracks campaign ID, start and end dates, target audience, budget, actual spend, and ROI.
Supports weekly performance reporting and budget adjustments based on performance metrics.
Google Ads and Bing Marketing
Organizes PPC campaign activities across advertising platforms.
Email, SMS, WhatsApp, and Push Notifications
Coordinates direct marketing campaigns.
Tracks campaign type, content schedule, engagement rate, and conversion rate.
Supports campaign scheduling based on customer interaction history and A/B testing of messaging.
E. Website and Branding
Supports website health, brand consistency, and ongoing user experience improvements.
Website Health Checks
Custom fields:
Check Date
Performance Score
SEO Score
Issues Identified
Urgency Level
Resolution Status
Automation rules:
Create an immediate review task for high-urgency technical issues.
Schedule subsequent checks based on performance scores, with more frequent checks for lower scores.
Branding Consistency Reviews
Custom fields:
Review Date
Inconsistencies Found
Corrected
Responsible Team Member
Automation rules:
Notify the marketing manager when inconsistencies are identified.
Schedule follow-up checks one week after the initial review.
User Experience Optimization
Custom fields:
Task ID
Initiation Date
Expected Impact
Completion Date
Impact Review
Automation rules:
Create a follow-up task 30 days after an optimization task is completed to review its impact.
Prioritize tasks according to their expected impact on user engagement.
05. End-to-End Workflow
This workflow represents the overall operational structure. Individual automation rules handle specific events, such as low inventory, approved reshipments, urgent website issues, and follow-up reviews.
06. Key ClickUp Capabilities
Custom Fields: Capture order, customer, product, campaign, and website information.
Task Organization: Separate activities into dedicated lists and operational areas.
Workflow Automation: Trigger notifications, escalations, task creation, and follow-ups.
Reusable Templates: Standardize order processing, dispute handling, product proposals, and product uploads.
Better visibility into order and fulfillment status.
More consistent handling of disputes and reshipment requests.
Organized product research and publication workflows.
Centralized tracking of advertising and promotional activities.
Earlier identification of website performance and branding issues.
More reliable task ownership, notifications, and follow-ups.
08. Conclusion
The Boots & Bags ClickUp workspace provides a structured foundation for managing ecommerce dropshipping operations. By bringing fulfillment, customer service, product management, marketing, and website maintenance into one organized environment, it helps teams coordinate work, track responsibilities, and apply repeatable processes across the business.
An event-driven Python service (FastAPI, Celery, Playwright and Claude) that answers load quote requests from a shared inbox with three ranked carriers. Median first reply: 48 seconds, down from 7 minutes 40.
Section: Python Automation
Overview
This case study focuses on an event-driven Python automation system that processes freight quote requests from a shared Gmail inbox. It checks carrier availability through browser automation, compares rates using Airtable data, and uses Claude to rank the top three carriers before sending a response through Gmail and Slack.
The system uses FastAPI, Celery, Redis, PostgreSQL, Browserbase, Playwright, and Claude. It replaces slow, unreliable polling with Gmail push notifications, uses database-based deduplication to prevent duplicate replies, and includes retries, recovery checks, and Slack alerts for failures.
Key results reported in the case study:
Median first reply reduced from 7 minutes 40 seconds to 48 seconds.
Cost per request reduced from $0.42 to $0.06.
Reported success rate increased from 71% to 98.6%.
Duplicate replies reduced from 4–6 per week to zero.
The problem
Load quote requests landed in a shared quotes@ inbox, around 40 a day. A dispatcher would read the request, log into the carrier portal (no public API for what they needed), check which trucks were available on that lane, cross-reference an internal rate sheet, and reply with three carriers and a price. Six to nine minutes each, every time.
Their first automation attempt was a Python script on a five-minute cron driving a hosted agent platform. It worked about 70% of the time, cost roughly $0.42 per request, and failed silently. They usually found out from a customer, not a log.
Three root causes, and all three shaped the rebuild:
Polling. A 0–5 minute delay before anything started, and the cron had no idea what the previous run had done.
Re-planning on every run. The agent asked an LLM to navigate the portal from scratch each time, so any UI jitter became a fresh failure mode, and every run paid full navigation token cost.
No durable state. Nothing recorded which requests had been handled, so retries either duplicated replies or never happened.
The architecture
Everything runs as a small Python service on a single Fly.io machine, a FastAPI app that receives Gmail push notifications, and a Celery worker pool that does the actual work.
Image: Event-driven quote triage pipeline: a FastAPI webhook verifies and acknowledges the push, the request is de-duplicated and queued (Postgres key, Redis queue), Browserbase and Playwright check portal availability while an Airtable rate sheet supplies lanes, margins and exclusions, Claude ranks the top 3 carriers, and a threaded reply goes out on Gmail and Slack.
Key engineering decisions
Real-time trigger, not a cron. Gmail's users.watch publishes to a Google Pub/Sub topic, which pushes to a FastAPI endpoint. The handler does three things and nothing else: verify the JWT on the push request, write the message ID to Postgres, and return 204. Pub/Sub redelivers anything not acked within 10 seconds, so all real work is handed to Celery and the endpoint stays under 50 ms.
@app.post("/gmail/push")
async def gmail_push(req: Request, claims=Depends(verify_pubsub_jwt)):
envelope = await req.json()
history_id = decode_message(envelope["message"])["historyId"]
for msg in gmail.list_since(history_id):
if requests_repo.claim(msg.thread_id): # INSERT ... ON CONFLICT DO NOTHING
process_quote.delay(msg.thread_id)
return Response(status_code=204)
Idempotency lives in the database, not in memory. claim() is an INSERT ... ON CONFLICT DO NOTHING on the Gmail thread ID. If Pub/Sub redelivers, or the safety net and a live webhook race each other, exactly one worker wins the row. This is the piece that eliminated duplicate replies outright.
Cached navigation instead of per-run LLM planning. Playwright drives a Browserbase session with stored credentials and a persistent context. The first time the portal layout is seen, an LLM produces a navigation plan, a sequence of selectors and actions, which is hashed against the page structure and cached in Postgres. Every subsequent run replays the cached plan with plain Playwright calls: no LLM, no tokens, sub-second steps. Only when a replay step fails does the code fall back to re-planning, write the new plan, and post a Slack notice that the portal changed. That's the same idea as Skyvern's Route Memorization, built explicitly so the failure path is visible rather than silent.
Prompt caching on the ranking call. The system prompt, the scoring rubric, and the serialised carrier roster are static across requests and sit in a cached block; only the parsed request and the fresh availability data go in the user turn. Roughly 11k stable input tokens moved to cache reads.
Concurrency capped deliberately. The Celery pool runs three workers. The portal rate-limits aggressively and had previously locked the shared account twice, so throughput was traded for account safety.
State machine and the safety net
Every request row moves through an explicit status column. The hourly sweep is the belt-and-braces layer for the rare case where a Pub/Sub push is lost or a worker dies mid-run.
Image: Request states and recovery: a request is processing (row claimed, timestamp set), then done (reply sent, thread id) on success or failed (alert posted to Slack) on error. An hourly sweep re-runs rows stuck for more than 15 minutes.
The sweep is a Celery Beat task, about 30 lines: select rows in processing with claimed_at < now() - interval '15 minutes', reset the attempt counter, re-enqueue. After three attempts it moves to failed and posts a Slack alert with the thread link and the last exception, so a dispatcher can handle it manually and an engineer can see exactly where it broke.
Errors are handled in three tiers rather than one generic retry: transient network and portal timeouts retry with exponential backoff inside the task; a failed selector replay triggers re-planning and a "portal layout changed" notice; anything else fails the row loudly.
Results
Before
After
Time to first reply (median)
7 min 40 s
48 s
Cost per request
$0.42
$0.06
Success rate (30-day)
71%
98.6%
Duplicate replies / week
4–6
0
Silent failures
routine
none, every failure alerts
The cost drop came from two places roughly equally: cached navigation removed the per-run planning tokens, and prompt caching cut input cost on the ranking call.
Delivered
Dockerised FastAPI + Celery service with a one-command deploy; Postgres schema and migrations; the Browserbase automation module with cached-plan replay and fallback; the Claude ranking module with the rubric prompt; Slack alerting; a runbook covering the four common failure modes and how to re-run a request by thread ID; and a 45-minute handoff call testing a live request end to end.
One click after the consultation creates a ready-to-work matter
CASE STUDY · BREWSTER LAW FIRM
Section: n8n Automations
Over View
This project automates Brewster Law Firm’s client intake process using Clio and n8n. When an attorney marks a consultation as Ready to Engage, the system automatically creates the matter, assigns the attorney, and sends the client a branded questionnaire with a secure link.
~1 min
3
1 click
10
from Ready to Engage to
practice-area groups,
by the attorney;
connected workflows with
a created matter
each with its own starting stage
everything after it is automatic
automatic failure alerts
Once submitted, responses are saved directly in Clio, matter stages are updated, and relevant notifications are sent automatically. The solution reduces manual work, streamlines client onboarding, and keeps matter records organized.
THE PLAN OF ACTION
We started from a written plan, then built it part by part
Brewster Law Firm's clients arrive through Google and AI search, the website form, the booking page and the phone. Our Plan of Action found that what happened after a lead arrived depended on two people remembering every step. It set out a client journey in five parts, from inquiry to closing, with Clio as the single place where every lead, client and matter lives. Below is each problem the plan found and what we built for it.
Problem in the plan
What we built
Status
Form submissions (Part 1)
An instant, branded thank-you with the next step and
Delivered
Leads reach Clio Grow, but the lead
booking link, then timed nudges that stop the moment
gets no thank-you email or next
the lead books.
step.
Consultation bookings (Part 2)
Confirmation and follow-up emails driven from Clio
Delivered
No automatic confirmation email
Grow, alongside Clio's own appointment reminders.
after a booking.
After the consultation (Parts 2–3)
One click sets the outcome to Ready to Engage. The
Delivered
Intake depends on someone
matter is created in the right practice area and first
remembering each step: convert the
stage, the attorney is assigned and the questionnaire
lead, create the matter, pick the
goes out.
stage, send the questionnaire.
Client questionnaires (Part 3)
A branded questionnaire on the firm's own address, with
Delivered
Intake forms are collected by hand.
a one-time private link per matter. Answers are saved as a note on the matter.
Client updates (Part 4)
A plain-language email on every stage change, a "still
Delivered
Some clients have to ask for a status
working on it" note when a matter sits too long, and
update.
reminders when the client owes something.
Info inbox (Part 1)
Reply tracking pauses automated reminders the moment
Delivered /
Replies are manual, usually the next
a client writes back. Reply drafting is the next phase.
next phase
morning.
Problem in the plan
What we built
Status
Ownership and control (Part 0)
Clio stays the single place for leads and matters.
Delivered
Tools are only partly set up and
Automations run on a firm-owned, self-hosted n8n
spread across chat and email.
server, with a daily health report and instant failure alerts.
Agreements and payments (Part
Kept manual in Clio by the firm's own choice. Billing and
By design
3)
agreements are deliberately not automated.
Approvals travel by chat;
agreements are hard to track.
Phone, documents, closing (Parts
Voice intake, OneDrive sync and closing and review
Next phase
1, 4, 5)
emails are scoped in the plan for the next phase.
Smith.ai re-entry, OneDrive folders,
and no closing or review request.
One click by the attorney after the consultation. Everything after it happens on its own.
THE JOURNEY AT A GLANCE
The plan, drawn out
The five-part client journey. Green is built; dashed grey is planned for the next phase.
From consultation to questionnaire. One click, then the checks, matter, email and stage update happen on their own.
How the pieces connect. Clio stays the system of record; n8n runs on a firm-owned server.
HOW IT WORKS
From consultation to questionnaire
The outcome is set to Ready to Engage The only manual step. It happens in Clio Grow, where the team already works.
The matter is created automatically Formation matters start at "Questionnaire Sent", compliance matters at "Information Gathering", contract matters at "Documents Received". Before it creates anything, the system confirms the client has an email address, matches exactly one contact, and has no open matter. If anything looks unusual, it hands the case to a person instead of guessing.
The client receives their questionnaire The email carries a private link tied to that one matter.
The client submits it The answers are saved as a note on the matter in Clio, the link closes, and the matter moves to its next stage.
Everyone is kept informed The client receives the update for the new stage. The firm receives a short "questionnaire received" notice.
WHAT IT LOOKS LIKE
Inside Clio and n8n
The matter-creation workflow. It reads leads from Clio Grow, applies the safety checks, creates the matter, and sends the two emails.
The client questionnaire. Hosted on the firm's own address, in Brewster's branding. Only the description of the matter is required.
The matter after the client submitted the questionnaire. It started in the compliance group's first stage and moved to Assessment in Progress on its own. Client details are blurred.
The answers land on the matter. The note is saved where the attorney will look for it.
WHAT THE CLIENT RECEIVES
Emails that read like the firm wrote them
Every email uses the firm's branding and Elissa Brewster Langston's own signature. These are real messages captured from the firm's mailbox during the verification run.
The questionnaire email. Sent the moment the matter is created, with a private link for that one matter.
The signature and confidentiality notice match the attorney's own email signature.
The stage update. When the questionnaire was submitted and the matter moved, the client received this note on its own. The [TEST] tag marks messages sent during verification.
BUILT TO BE TRUSTED
Guardrails a law firm needs
The firm's own voice
Every client email is written in the firm's tone and carries the attorney's own
Per-matter control
signature and confidentiality notice. A single Clio field turns automatic emails on or off for any matter.
Private by design
Each questionnaire link works once, for one matter. A reused or invalid link is refused and recorded.
Your data stays yours
The workflows run on a dedicated self-hosted server, not a shared automation service. Client records stay in Clio.
THE RESULT
The whole journey runs without hand-offs
Run end to end in Brewster's own Clio account, across all three practice-area groups, the system did what the team used to do by hand:
Matter created
In about a minute, in the correct practice area and first stage, with the attorney
Questionnaire sent
assigned. A private link arrived in the client's inbox at the same moment, in the firm's branding.
Stage moved
Formation, compliance and contract matters each advanced to their next stage when the form came back.
Answers on the matter
Saved as a note in Clio, with the team notified, and no one retyping anything.
RUN YOUR INTAKE THE SAME WAY If your firm uses Clio and still triggers intake by hand, we can map your stages, practice areas and client emails into a workflow like this one. Talk to Growlyze about a free intake review.
A health and wellbeing company sells a biological ageing assessment. It does not give one “body age”. It shows how each of 16 body systems, from heart and brain to sleep, digestion and skin, seems to be ageing…
Section: n8n Automations, Python Automation
Overview
A health and wellbeing company sells a biological ageing assessment. It does not give one “body age”. It shows how each of 16 body systems, from heart and brain to sleep, digestion and skin, seems to be ageing compared with the person’s real age, and what is driving each one.
Each client answers a 150-question form in JotForm and takes a short camera face scan in Upvio. The company had a locked scoring method written up as a specification, but nothing to run it: no way to join each form to its scan, turn the answers into system ages, or produce the personal report it promises.
Now an engine built by Growlyze, with three n8n workflows around it, matches each form to its scan, scores both in code exactly as the specification says, has AI write the report around those numbers, checks every part, and emails the client a private link to their PDF.
The Problem
Clients pay for a detailed, personal picture of their health. A wrong number or a careless sentence about their body would cost the company their trust.
Two tools, no shared ID. The form and the scan arrive separately, at different times and in either order, and the form carries no assessment number. Someone would have to pair every form with its scan by hand.
The maths has to be exact. The 150 answers feed 16 body systems, 58 clusters, 28 interaction rules and several indices, with weights that shift when a layer is missing. The same answers must always give the same ages, which an AI model cannot guarantee on its own.
The scan has to be handled honestly. A camera reading from one sitting is an estimate. Impossible readings must be left out, not scored, and the report must never name a medical condition.
The words have to be safe, and every client needs a report. The text must be in plain British English, must never change or invent a number, and must never make a diagnosis. A weak AI draft cannot be allowed to leave a paying client with nothing.
How It Works
The form comes in. An n8n workflow maps the JotForm fields to the engine’s format and sends them on. Each answer must match one of the question’s exact options; an unknown answer stops that assessment and raises an alert instead of guessing. Repeats of the same submission are ignored.
The scan comes in. A second n8n workflow keeps only completed scans from this assessment’s Upvio link, looks up the client’s email through Upvio’s patient API, and sends the scan to the engine.
Form and scan are matched by email. Whichever arrives first is stored and waits for the other. When both exist, the engine links them under one assessment ID and queues the report. A scan is never reused for a second report.
Code does the scoring. The answers and the usable scan readings (blood pressure, resting heart rate, breathing rate and waist-to-height ratio) are scored by the locked method into 16 system ages, burdens and directions. Missing answers are left out, never counted against the client, and readings outside what is physically possible are listed and excluded.
AI writes the words. The AI gets a pseudonymised summary with no name or contact details and writes the report in parts. It never calculates: the tables and charts are filled by code, and any figure the AI mentions must be one the code already worked out.
Every part is checked. Checks look for structure, changed or invented numbers, diagnosis claims and hard-to-read sentences. A failing part goes back for repair; minor issues that remain become internal warnings, and any unsafe sentence still there is removed by code, with an alert.
The PDF is built. The engine adds the client’s first name, builds a branded report of around 45 pages, stores it and creates a private, unguessable link.
The client is emailed. The engine tells n8n the report is ready, and a third workflow emails the client their link through Gmail, checking first that the event has not already been handled.
All of this runs as its own service, with its own database and four workers, beside the company’s live ADHD assessment without touching it. If the AI service fails, the job is retried and finished parts are kept. The scoring method and the scan mapping are fixed, fingerprinted files, so any change is a new, recorded version rather than a quiet edit.
Results & Metrics
A form and a scan now find each other by email and become a scored, written, checked report without anyone stepping in. The numbers come only from code, so the same answers always give the same ages, and every accepted assessment ends in a report.
Metric
Observed Output
Test reports with the live AI model
19
Processing time per report (current version)
3 to 3½ minutes (5 of 5 runs)
Report length
16 body systems, about 45 pages
AI drafts checked before publishing
293
Reports sent with banned or unsafe wording
0
Deliberate wrong answer and repeated webhook
Stopped with an alert; ignored, no second report
Automated tests
887 passing (100%)
💡
Metrics come from development and test runs on made-up participants, timed from scored answers to stored PDF. Runs that were restarted after a fix are left out of the timing. Figures from live client traffic may vary.
Image: Workflow: the form intake in n8n.
Image: Workflow: the scan intake in n8n, with the email lookup in Upvio.
Image: Output: the job log of one test assessment with the live AI model, from form to notification in 3½ minutes. IDs shortened.
Image: Workflow: the report email in n8n, sent once per client.
Image: End result: two pages of the PDF report for a made-up test participant. Company name blurred.
Tech Stack
Technology
Role in the solution
JotForm
The 150-question assessment form clients fill in
Upvio
The camera face scan, and the patient lookup that supplies the email
n8n
Three workflows: form intake, scan intake, and the report email
Python engine (FastAPI)
Matching, scoring, AI calls, checks, the job queue and the private report links
MySQL / MariaDB
Its own database for assessments, scans, scores and the job queue
OpenAI
Writes the report text around numbers set by code
WeasyPrint
Turns the finished report into a branded PDF
Gmail
Sends the client their report link
The engine runs on the company’s own server, next to its existing ADHD assessment but fully separate from it. Clients use the same kind of form and scan they already know.
Where This Pattern Applies
This isn’t really about ageing.
Worked example: a corporate wellness provider. Employees answer a lifestyle questionnaire and wear a fitness tracker for a week. The two are matched by email, a fixed scoring model turns them into risk areas in code, AI writes each person’s summary around those scores, the text is checked for medical claims, and a private report goes to each employee.
Clinics: intake form plus device readings
Insurance: health questionnaire plus checks
Fitness coaching: check-in plus wearable data
Property: survey answers plus inspection data
Education: assessment plus coursework
Engineering: equipment log plus sensor data
The shape: separate inputs are matched to one person, a fixed method scores them in code, AI writes within strict limits, and checks decide what gets sent. What changes from case to case is the questions, the scoring method, the second data source and the list of claims that must never appear.
A health and wellbeing company sells an ADHD profile assessment. It is not a diagnosis and not a single “mild to severe” score. It shows how a person’s attention, drive, ideas, order, recovery and body work together,…
Section: n8n Automations, Python Automation
Overview
A health and wellbeing company sells an ADHD profile assessment. It is not a diagnosis and not a single “mild to severe” score. It shows how a person’s attention, drive, ideas, order, recovery and body work together, and it gives strengths and difficulties equal weight.
Each client completes a 72-question form in JotForm and a short camera body scan in Upvio. Before, the answers and the scan sat in those two tools with nothing joining them and nothing turning them into the personal report the company promises.
Now an assessment engine built by Growlyze, with three n8n workflows around it, matches each form to its scan, scores the answers in code, has AI write the report within strict limits, checks every part before publishing, and emails the client a private link to their PDF.
The Problem
People taking an ADHD assessment are often anxious about what it will say. They have paid for something personal, and a careless report can hurt them.
Two tools, no shared ID. The form and the scan arrive separately, at different times and in either order. Upvio’s scan notification does not even include the client’s email, so someone would have to pair every form with its scan by hand.
The scoring has to be exact. The 72 answers feed 11 dimensions, scoring bands, nine operating profiles, a seven-day experiment and product-suitability rules. The same answers must always give the same result, which an AI model cannot guarantee on its own.
The words have to be safe. The report must use the client’s own words in British English, but never claim a diagnosis or a cause, never mention brain chemicals or medication changes, and never show raw scores or question numbers. A short scan shows how the body was working at that moment; it must not be read as “how much ADHD” someone has.
Nothing can be lost or mixed up. Webhooks get sent twice, the AI service can be slow or down, and many clients can finish at once. Every accepted assessment still has to end in one report, sent once, to the right person.
How It Works
The form comes in. When a client submits the form, an n8n workflow maps the JotForm fields to the engine’s format, checks it is complete and sends it to the engine. Repeats of the same submission are ignored, and unusable ones (missing answers, no consent) are rejected.
The scan comes in. A second n8n workflow keeps only completed remote scans, looks up the client’s email through Upvio’s patient API, and sends the scan to the engine.
Form and scan are matched by email. The engine stores whichever arrives first and waits for the other, with no time limit. When both exist, it links them and queues the report. If someone submits twice, the newest wins, and a scan is never reused for a second report.
Code does the scoring. The answers are scored against the company’s rules into dimensions, bands, profiles, an experiment and suitability flags. Each scan reading (heart rate variability, recovery, stress, breathing, heart rate, blood pressure and a wellness score) becomes a plain finding and is compared with the questionnaire.
AI writes the words. The AI gets a pseudonymised summary, with no name or contact details, and is told exactly which findings and which of the client’s own reflections it may use. It writes the questionnaire sections first and the scan section last.
Every part is checked. The checks look for correct structure, evidence that points to real findings, use of the client’s words, and anything banned: question numbers, raw values, diagnosis or cause claims, medication advice, hype or US spelling. A failing part gets up to two targeted repairs; if it still fails, safe text built from the scores is used, so every client gets a report.
The PDF is built. The engine adds the client’s name, builds a branded PDF, stores it and creates a private, unguessable link.
The client is emailed. The engine tells n8n the report is ready, and a third workflow emails the client their link through Gmail, checking first that they have not already been sent it.
All of this runs in a database-backed job queue with several workers. If the AI service fails, the job is retried, and parts that already passed are kept, not written again. The questions, scoring rules and scan ranges live in one versioned configuration file, so a method change, or a whole new assessment, is a configuration edit rather than new code.
Results & Metrics
The team no longer pairs forms and scans by hand. Each client’s form and scan find each other by email, and a report is scored, written, checked and emailed without anyone stepping in. Nothing reaches a client until it passes the checks, and a temporary AI failure no longer means a missing report.
Metric
Observed Output
Test runs with the live AI model
14
Typical processing time per report
About 1 minute (median)
Processing time range
39 seconds to just over 2 minutes (13 of 14 runs)
AI drafts checked before publishing
66
Reports sent with banned or unsafe wording
0
Load test
1,000 submissions, none lost, duplicated or mixed up
Automated tests
110 passing (100%)
💡
Metrics come from development and test runs, measured from validated input to stored PDF. The one run outside the range waited on automatic retries. Figures from live client traffic may vary.
Image: Workflow: the form intake in n8n.
Image: Workflow: the scan intake in n8n, with the email lookup in Upvio.
Image: Output: one engine run for a test participant, from matched form and scan to “ready”.
Image: Workflow: the report email in n8n, sent once per client.
Image: End result: two pages of the PDF report for a fictional test participant. Logo and company name blurred.
Tech Stack
Technology
Role in the solution
JotForm
The 72-question assessment form clients fill in
Upvio
The camera-based body scan, and the patient lookup that supplies the email
n8n
Three workflows: form intake, scan intake, and the report email
Python engine (FastAPI)
Matching, scoring, AI calls, checks, the job queue and the private report links
MySQL / MariaDB
Stores assessments, scans, results and the job queue
OpenAI
Writes the report narrative from pre-selected findings
WeasyPrint
Turns the finished report into a branded PDF
Gmail
Sends the client their report link
The engine runs on the company’s own server next to its database. Clients keep using the same form and scan, and the team keeps working in the tools it already has.
Where This Pattern Applies
This isn’t really about ADHD.
Worked example: a recruitment firm. A candidate fills in a skills questionnaire and records a task on another platform. The two are matched by email, the questionnaire is scored against the firm’s rubric in code, AI writes a candidate summary from the scores only, the summary is checked for banned claims, and a PDF goes to the hiring manager.
Clinics: intake form plus test results
Fitness coaching: check-in plus wearable data
Education: assessment plus coursework
Insurance: application plus documents
HR: engagement survey to team report
Financial advice: fact-find to review pack
The shape: separate inputs are matched to one person, code scores them, AI writes within fixed limits, and checks decide what gets sent. What changes from case to case is the questions, the scoring rules, the second data source and the list of claims that must never appear.
Salesforce Marketing Cloud to GoHighLevel Migration & Two-Way CRM Sync
Automated CRM migration, customer journey rebuilding, and real-time two-way data synchronization.
Section: n8n Automations
1. Overview
My Digital Money runs Cash and IRA investment accounts and grows its list with a free crypto guide. Its customer journeys ran in Salesforce Marketing Cloud, driven by Salesforce leads, accounts and opportunities.
The journeys and contact history were moved into GoHighLevel, and n8n now keeps leads, guide requests and opportunities in step between the two CRMs.
18,480 contacts imported in the main migration with 0 errors.
3 n8n sync workflows in production.
2. The Problem
The objective was to move customer journeys and contact history out of Marketing Cloud and keep Salesforce and GoHighLevel in sync without manual data entry.
The migration involved six main challenges:
A hard cut-off: The Marketing Cloud subscription was ending, so journeys, email history and unsubscribes had to be exported before access closed.
Journeys wired to Salesforce data: Entry rules and splits read Salesforce fields such as account type (Cash or IRA), funding type and opportunity stage.
Two CRMs, no connection: Salesforce stayed the system of record, but GoHighLevel couldn't tell when a lead arrived, asked for the guide or moved through a deal.
Silent sync failures: Salesforce outbound messages first hit a test webhook URL, then kept retrying because the reply wasn't in the SOAP format Salesforce expects.
Records that had to match: An opportunity could arrive before its contact existed in GoHighLevel, and repeated updates risked creating duplicates.
A brand-new sending domain: mail.mydigitalmoney.com had no sending history, so volume had to start at around 1,000 contacts and grow in stages.
3. How It Works
The implementation consists of six connected components, covering journey migration, data migration, CRM synchronization and email sending.
Step 1 — Journey Audit and Rebuild
Each Marketing Cloud journey was mapped, including its entry source, criteria, splits, emails and waits. It was then rebuilt as a GoHighLevel workflow with the same branches.
Splits by account type and funding type carried over as workflow conditions.
Approval, application, abandonment and first-trade journeys each became their own workflow.
The lead nurture runs as a multi-day email and SMS sequence after the guide is sent.
Application submitted, IRA
Image: Marketing Cloud: New IRA applications split by initial funding type into two application emails.
Image: GoHighLevel: Contact-created trigger with the same funding-type condition, emails and waits.
Application submitted — Cash
Image: Marketing Cloud: One path: application-received email, a one-day wait, then exit.
Image: GoHighLevel: Contact-created trigger for unapproved individual (Cash) accounts, then the same email and wait.
Step 2 — Data Migration
Contacts, Marketing Cloud email tracking and unsubscribe data were exported, merged and imported into GoHighLevel.
Separate imports for unconverted prospects, Cash and IRA account holders, and matched unsubscribes.
Contact fields created to carry Salesforce data such as account approval, funding type, lead source and guide status.
The main import processed 18,480 records with no errors.
Image: Contact fields: Salesforce data such as approval, funding type and guide status.
Step 3 — Lead Synchronization
A Salesforce flow sends an outbound message to n8n whenever a lead is saved. n8n reads the full lead and creates or updates the contact in GoHighLevel.
n8n replies with the SOAP acknowledgement Salesforce requires, so messages aren't retried.
GoHighLevel custom fields are looked up and mapped before each write.
A Salesforce "lead created" trigger runs alongside the webhook.
Image: Workflow: webhook or lead trigger → full lead → field mapping → create or update.
Image: Executions: recent runs succeeded in about a second.
Step 4 — Guide Requests
When a lead asks for the crypto guide, n8n waits a minute for Salesforce to finish saving, re-reads the lead, sets Send Guide in GoHighLevel and resets it in Salesforce.
Resetting the flag means a returning lead can request the guide again.
In GoHighLevel, the Send Guide field starts the guide email and then the nurture sequence.
Image: Marketing Cloud: Splits new leads by campaign before sending the guide emails.
Image: GoHighLevel: Send Guide set to true starts the guide email, then the nurture sequence.
Image: GoHighLevel: MDM – Lead Nurture Sequence, shown in three parts
Image: Workflow: wait → re-read lead → set in GoHighLevel → reset in Salesforce.
Image: Executions: each run includes the one-minute wait
Step 5 — Two-Way Opportunity Synchronization
Opportunity changes in Salesforce create or update the matching opportunity in GoHighLevel, and the GoHighLevel ID is written back to Salesforce.
n8n pulls the opportunity and its account, finds the contact in GoHighLevel and creates it if it's missing.
Matching uses the Salesforce Opportunity ID stored on the GoHighLevel record, so updates don't create duplicates.
Salesforce stages map to GoHighLevel pipeline stages, such as Trade – Completed.
Image: Workflow: update or create in GoHighLevel, then write the ID back to Salesforce.
Image: Executions: successful runs, including batches of updates.
Step 6 — Sending Domain and Warmup
mail.mydigitalmoney.com was authenticated and set as the sending domain for every email type in GoHighLevel.
SPF, DKIM, DMARC and MX records verified before sending.
A contact property controlled who received newsletters during warmup, starting around 1,000 contacts and expanding at each stage.
Test contacts were removed from production sends so they didn't drag down engagement.
Image: Synced opportunity: stage mapped from Salesforce, with the Salesforce IDs stored (blurred)
Image: Sending domain: mail.mydigitalmoney.com handles all seven email types.
4. The Result
The migration moved the customer journeys and contact history into GoHighLevel while establishing synchronization between Salesforce and GoHighLevel through n8n.
Seven GoHighLevel workflows now cover the guide, nurture, application, approval, abandonment and first-trade journeys. The main contact import processed 18,480 records with 100% success and no errors.
Leads, guide requests and opportunities now sync through n8n. Recent lead sync runs shown in the dashboards completed in about a second, and opportunity records are linked between both systems using their respective IDs.
The new sending domain was authenticated and used for all seven email types, with a staged warmup process.
5. Results & Metrics
The following figures are taken from the GoHighLevel and n8n dashboards. They represent the documented implementation results, not independent performance audits.
Metric
Documented result
Marketing Cloud journeys documented
9
GoHighLevel workflows covering customer journeys
7
Contacts in the main import
18,480
Main import success rate
100%
Import errors
0
n8n sync workflows in production
3
Emails delivered in the last 30 days
120,362
Email bounce rate
1.2%
Spam complaints
8
Recent lead sync execution time
About 1 second
6. Tech Stack
Technology
Purpose
Salesforce Sales Cloud
System of record for leads, accounts and opportunities.
Salesforce Marketing Cloud
Original customer journeys and email history.
n8n
Self-hosted synchronization between the two CRMs.
GoHighLevel
Rebuilt workflows, email, SMS and pipeline management.
LeadConnector API
Reads and writes GoHighLevel records.
7. Where This Pattern Applies
Financial Services: Migrate customer journeys and synchronize investment account information between CRM platforms.
Insurance Companies: Connect customer records, policy enquiries and application workflows across systems.
Real Estate Businesses: Synchronize leads, property enquiries and sales opportunities between CRM platforms.
Marketing Agencies: Migrate email journeys, contact history and nurture sequences while maintaining CRM synchronization.
Sales Organizations: Keep leads, contacts, opportunities and pipeline stages aligned across multiple CRM systems.
This pattern is useful for organizations moving from one CRM or marketing automation platform to another while maintaining customer history, automated journeys and reliable synchronization between their systems.
AI-Powered Construction Report SaaS (MeinBüromeister)
Turning construction-site voice notes, photos, and messages into structured reports through an automated AI-powered backend for German trade companies.
Section: Custom SaaS Platforms
Overview
MeinBüromeister is a B2B SaaS platform for German construction and trade companies. It allows workers to submit job updates through WhatsApp instead of preparing every report manually. The backend organizes incoming information, generates structured reports, and asks workers to review them before submission.
The Business Problem
Construction workers often send separate voice notes, photos, and text corrections from job sites. Office staff must identify the correct customer and project, organize materials and working hours, and format the information into professional reports. This creates repetitive administrative work and makes report preparation more time-consuming. The goal was to reduce this manual effort while keeping workers involved in reviewing and approving their reports.
The Solution
An n8n-based backend receives WhatsApp messages and groups related inputs into a single session. OpenAI Whisper transcribes voice recordings, while Claude AI extracts relevant report information into structured data. After the worker reviews and approves the report, the backend stores it in Supabase for delivery to the office dashboard. Supporting workflows automate customer onboarding, subscription management, team access, and error handling.
Project Snapshot
A production backend connecting WhatsApp messaging, AI-powered report extraction, worker approval, report storage, customer onboarding, and subscription lifecycle management.
How the System Works
System Architecture
The backend is organized around an n8n automation layer that sits between WhatsApp, the AI services used for transcription and extraction, and the Supabase/Stripe infrastructure that powers the office dashboard.
Supporting Integrations
Stripe: Checkout, subscription lifecycle events, plan changes, and subscription-based access rules.
Supabase Auth: Authentication support for the application.
Supabase Storage: Storage for uploaded photos and other media.
Docker: Supports the self-hosted deployment environment.
Core Automation Workflows
The backend is built around interconnected n8n workflows that automate WhatsApp message handling, AI-powered report generation, customer onboarding, and subscription management. Each workflow handles a specific responsibility and integrates with the relevant APIs and backend services to support the complete reporting lifecycle. Some main automation workflows are shown below.
1. Core Onboarding & Workflow Management
This workflow handles company onboarding, setup-code verification, worker registration, subscription checks, report approval, project management, and notifications through interconnected n8n automation nodes.
Image: Core onboarding and workflow management: company setup, worker registration, subscription checks, report approval, project handling, and notifications across 15 interconnected automation groups.
2. AI-Powered Report Processing Workflow
This workflow processes WhatsApp messages using Whisper and Claude AI to extract structured report data, enrich customer and project details, validate reports, and handle database updates and notifications.
Image: AI-powered report processing: message intake, voice transcription, Claude-based data extraction, report generation, and save/notification handling.
Product Experience
Report inbox
Image: The office inbox organizes incoming reports by date, technician, customer/project, category, and status.
Customers and projects
Image: The project view groups customers and highlights open-report counts and recent work.
WhatsApp work history
Image: Workers review and approve each AI-generated report directly in WhatsApp before it goes to the office.
<30s: Voice note to structured report
Image: Once approved, the report is saved, confirmed back to the worker on WhatsApp, and delivered to the office as a PDF.
Core Backend Capabilities
AI Report Extraction: Supports four report categories (Rapport, Aufmaß, Neues Angebot, and Notiz). The AI extracts work descriptions, materials, dimensions, and working hours while using prompt guardrails to reduce invented details.
Multi-Input Session Handling: Groups related voice notes, photos, captions, and corrections into a single processing session instead of treating every incoming message as a separate report.
Project Matching and Clarification: Uses available employee and project records to associate reports with the correct destination. When a match is ambiguous, the workflow can request clarification.
Onboarding and Access Management: Supports company setup, worker invitations, registration tracking, and access checks to ensure incoming messages are routed correctly.
Subscription Lifecycle Management: Handles relevant Stripe events and subscription states, including active, canceling, and canceled subscriptions. It also manages plan mapping and seat limits.
Failure Handling and Validation: Validates incoming data and AI-generated output, handles incomplete sessions and invalid actions, and provides controlled paths for processing failures.
Results & Metrics
5: Production workflows
5: Testing rounds
30+: Test scenarios per round
25+: Bugs found & fixed
The project delivered five production workflows connecting WhatsApp, AI-powered report extraction, Supabase, and Stripe. Across five rounds of end-to-end testing, more than 25 bugs were identified and fixed, with over 30 test scenarios executed per round.
Technical Challenges & Solutions
During development and end-to-end testing, several integration and AI reliability issues required targeted solutions.
1. Stripe Subscription Data Handling
Challenge
The Stripe checkout event did not always contain all the subscription information required by the workflow.
Solution
Retrieved the complete subscription details directly through the Stripe API before continuing with subscription processing.
Outcome
Improved the reliability of subscription data handling.
2. Subscription Plan Mapping
Challenge
Mapping subscription plans based on payment amounts could lead to incorrect plan identification.
Solution
Used Stripe product IDs to identify plans instead of relying on monetary amounts.
Outcome
Made plan identification more consistent across subscription events.
3. AI Hallucination Control
Challenge
Claude AI could occasionally introduce materials or details that were not present in the worker’s input.
Solution
Refined the AI prompt with guardrails to discourage unsupported details and keep extraction grounded in the supplied information.
Outcome
Improved the consistency of structured report generation.
4. Supabase PATCH Response Handling
Challenge
Some Supabase PATCH operations returned empty responses, creating difficulties for downstream workflow nodes.
Solution
Explicitly referenced upstream node outputs where required instead of relying on the PATCH response to provide all subsequent data.
Outcome
Made downstream data handling more reliable.
5. End-to-End Integration Testing
Challenge
The system depended on multiple connected services, including WhatsApp, AI models, Supabase, and Stripe, making integration failures difficult to isolate.
Solution
Conducted five rounds of end-to-end testing, covering more than 30 scenarios per round, and fixed over 25 identified bugs.
Outcome
Improved integration reliability across the production workflows.
Key Takeaways & Future Development
Key Takeaways
Workflow automation: Built and integrated five production n8n workflows connecting WhatsApp, AI services, Supabase, and Stripe.
AI reliability: Improved structured report extraction through prompt engineering, validation, and guardrails against unsupported details.
Integration engineering: Resolved issues involving Stripe subscription events, plan mapping, and Supabase response handling.
End-to-end testing: Completed five testing rounds, identifying and fixing more than 25 bugs across the integrated system.
Cross-functional collaboration: Coordinated with the frontend engineer on database requirements and data contracts to connect backend workflows with the React dashboard.
Closing Summary
MeinBüromeister demonstrates how workflow automation, AI-powered information extraction, and integrated SaaS infrastructure can simplify construction reporting. The primary contribution was engineering the backend workflows and integrations that connect field communication with structured reports, subscription management, and the office dashboard.
AI-Powered 24/7 Voice Support Agent for eCommerce Stores
A 24/7 AI voice agent that answers store calls using your product and policy data, escalating only complex calls to humans.
Section: n8n Automations, AI Agents, AI Agents for Ecommerce
Project Overview
The AI-Powered 24/7 Voice Support Agent automates customer support calls for eCommerce stores using conversational AI and a centralized knowledge base. Built around VAPI, n8n, Slack, and Google Sheets, it can answer common questions about products, pricing, shipping, returns, and store policies through natural voice conversations.
The system understands customer intent, retrieves relevant store information, responds in real time, and supports optional escalation for complex or high-risk issues. This reduces repetitive work for support teams while providing customers with access to assistance around the clock.
Technologies: VAPI · n8n · Slack · Google Sheets · AI Voice Agent
01. The Problem: Support Calls Don’t Scale
Before automation, customer support teams handled incoming calls manually.
Common challenges included:
Repeating answers about products, sizes, shipping, returns, and order status.
Switching between store systems and knowledge documents during calls.
Missing calls during peak hours or outside business hours.
Providing inconsistent answers depending on the agent handling the call.
Impact per team
Long wait times and dropped calls.
Frustrated customers seeking answers to basic questions.
Inconsistent use of product and policy information.
High dependency on human agents for repetitive FAQs.
Core challenge: Build a 24/7 support system that can resolve common customer queries using the store’s own knowledge while escalating issues that require human attention.
02. Results After Automation
After implementation, the voice agent can answer calls around the clock and handle common customer questions automatically.
Key improvements
Calls answered without waiting for a human agent.
Common FAQs handled through conversational AI.
Complex or high-risk issues escalated when required.
Responses grounded in available store product and policy information.
Human agents able to focus on more complex customer needs.
Time and effort savings
Before
Approximately 100–200 repetitive calls per week.
Around 2–3 hours per day spent answering FAQs.
After
Routine call handling automated.
Human involvement primarily reserved for escalations and exceptions.
Estimated monthly impact
Approximately 40–60 hours saved per support team.
More time available for complex and high-value support cases.
Consistency improvements
Responses use the configured product and policy knowledge base.
Reduced reliance on improvised answers.
Easier alignment with updated store information when the knowledge base is maintained.
03. The Solution: AI-Powered Voice Agent
The system acts as a virtual customer support representative capable of handling common eCommerce questions independently.
Uses store knowledge covering products, pricing, inventory, policies, and FAQs.
Answers common questions without requiring a human agent.
Maintains conversational context across follow-up questions.
Supports optional escalation for complex or high-risk calls.
Can send call summaries and capture relevant information through n8n, Slack, and Google Sheets.
04. How the System Works
Phase 1: Knowledge Base and Store Data
Relevant store information is collected and organized for retrieval during calls.
This may include:
Product details, sizes, colors, and availability.
Pricing and promotions.
Shipping fees and delivery times.
Return, refund, and exchange policies.
Frequently asked questions.
The knowledge base should be kept up to date to reduce the risk of outdated responses.
Phase 2: Incoming Call and Intent Detection
A customer calls the support number.
VAPI answers with a configured greeting and voice.
The customer's speech is converted into text.
AI identifies the intent, such as a product question, order inquiry, or policy clarification.
Phase 3: Knowledge Base Lookup
The system retrieves relevant information to answer the customer's question.
For example:
Product specifications and availability.
Delivery timelines and shipping costs.
Return and refund conditions.
Promotions and bundles.
Order details for authenticated users, where the required integration is configured.
Phase 4: Voice Response Generation
AI prepares a relevant, conversational answer.
Text-to-speech generates the spoken response.
The answer is played to the customer in real time.
Phase 5: Multi-Turn Conversation
The agent maintains context throughout the call, allowing customers to ask follow-up questions about products, orders, and policies without restarting the conversation.
Phase 6: Human Escalation and Call Summary
When configured, complex or high-risk calls can be forwarded to a human agent. The workflow may also support callback requests or ticket creation.
After the call:
VAPI sends call-end information to an n8n webhook.
n8n processes the call summary and relevant details.
Slack receives the summary.
Google Sheets records applicable information.
05. Business Value
24/7 Availability: Customers can receive assistance outside normal business hours.
Reduced Support Workload: AI handles repetitive FAQs automatically.
Consistent Answers: Responses are based on configured store knowledge.
Faster Resolution: Common questions can be answered in a short conversation.
Better Knowledge Utilization: Product and policy information supports customer interactions.
Human Escalation: Complex cases can be routed to people when required.
Call Visibility: Summaries and captured details can be recorded for follow-up.
06. Expected Impact
Time Savings
Automating repetitive calls reduces the time support agents spend answering routine questions, allowing them to focus on complex issues.
Error Reduction
Using maintained product and policy data helps reduce inconsistent or improvised answers.
Call Handling Speed
Common questions can potentially be resolved in one or two exchanges, depending on their complexity.
Knowledge Utilization
Centralized store information can be reused across voice interactions, improving consistency and accessibility.
Estimated time savings: Approximately 40–60 hours per month per support team, depending on call volume and automation coverage.
07. Workflow Architecture
The main components work together as follows:
VAPI: Handles voice interactions and call management.
Knowledge Base: Supplies relevant product and policy information.
AI Processing: Understands customer questions and prepares responses.
n8n: Processes call-end events and coordinates follow-up actions.
Slack: Delivers call summaries to the support team.
Google Sheets: Stores applicable call records and captured information.
08. How to Replicate the System
Step 1: Configure the VAPI Voice Agent
Create the voice agent and configure its greeting and voice tone.
Connect the store knowledge base.
Test its ability to answer FAQs and product or policy questions.
Step 2: Configure the Call-End Webhook
Create a webhook node in n8n.
Configure VAPI to send call-end information to the webhook.
Verify that the webhook receives the expected call details.
Step 3: Import the n8n Workflow
Open ShopTalk AI – Call Summary & Lead Capture (1).json.
Import the workflow into n8n.
Connect the VAPI webhook to the workflow.
Configure Slack and select the appropriate summary channel.
Connect Google Sheets and select the spreadsheet and required columns.
Step 4: Test the Flow
Make a test call.
Ask product or policy questions.
Test a follow-up question.
End the call.
Verify that the call summary appears in Slack.
Confirm that a row is added to Google Sheets when applicable.
Step 5: Activate the Workflow
Once testing is complete, activate the n8n workflow and verify that the VAPI webhook is configured correctly.
The voice agent can then handle customer calls continuously, while n8n processes call summaries and related follow-up actions.
09. Final Outcome
The AI-powered voice support system transforms repetitive customer support calls into a more consistent and scalable operation.
Customers can receive answers at any time.
Human agents spend less time handling repetitive FAQs.
Product and policy information supports consistent responses.
Complex issues can be escalated when necessary.
Call summaries and relevant records improve follow-up visibility.
Support teams can handle routine demand without relying exclusively on additional staff.
The result: A scalable, 24/7 voice support experience that reduces repetitive work while keeping human agents available for the issues that need them most.
Veterinary Specialist Partners (VSP) operates veterinary facilities in Louisville and Evansville, providing specialized care for pets with complex medical conditions. Managing appointments, patient information, lab communications, and follow-ups manually created administrative overhead and made coordination across locations more difficult.
The solution used ClickUp as a central operations workspace, connecting scheduling and communication tools through automated workflows. Appointments, related information, reminders, cancellations, and follow-up activities could be managed with greater consistency.
2. The Challenge
Before the implementation, several operational processes depended on manual work.
Fragmented Appointment Management
Appointments were booked through external scheduling tools and needed to be organized across different locations and appointment types. Staff had to maintain accurate records and keep appointment statuses up to date.
Incomplete Patient Information
Required forms, medical details, and laboratory results could arrive through separate systems and email communications. Locating the relevant information alongside an appointment required additional coordination.
Manual Reminders and Follow-Ups
Patient reminders, form-completion checks, and post-appointment follow-ups required staff attention. Inconsistent follow-up processes could result in missed administrative steps.
Cancellation and Record Synchronization
When appointments changed or were cancelled, the corresponding records and lists needed to remain consistent across the scheduling system and ClickUp.
3. Project Objectives
The project focused on the following objectives:
Centralize appointment management: Maintain a unified view of appointments across Louisville and Evansville.
Automate scheduling workflows: Synchronize new bookings and cancellations from Calendly.
Connect patient information: Link Jotform submissions and relevant medical information to appointment records.
Improve communication: Automate appointment reminders using email and RingCentral SMS.
Organize laboratory communications: Attach incoming lab emails and documents to the relevant ClickUp tasks.
Maintain accurate records: Synchronize custom fields and clean up past appointments across lists.
Improve operational visibility: Give staff a more consistent way to track appointments, referrals, and follow-up activities.
4. The Solution
4.1 Calendly to ClickUp Integration
Calendly bookings are captured and converted into ClickUp tasks.
New appointments are added to the appropriate ClickUp lists.
Appointment types and locations are organized separately.
Tasks use relevant tags and custom fields for easier identification.
A centralized Appointments list consolidates bookings from both locations for teams that need an organization-wide view.
Image: Calendly-to-ClickUp appointment automation screenshot from Make.com
This setup reduces the need to manually transfer appointment information between systems.
4.2 Jotform Integration and Patient Information
The workflow monitors required Jotform submissions associated with scheduled appointments.
Patient form submissions are tracked.
Relevant medical information is connected to the corresponding ClickUp appointment record.
Missing forms can trigger email and SMS reminders two days before the appointment.
Staff can access the relevant information from the associated task.
This helps staff identify outstanding administrative requirements before appointments take place.
4.3 Laboratory Email and Attachment Management
Gmail integration brings relevant laboratory communications into ClickUp.
Incoming lab emails and attachments are added to the corresponding patient or appointment task, making related information easier to locate without manually searching through email conversations.
4.4 Appointment Cancellations
Cancellation handling keeps appointment records aligned between Calendly and ClickUp.
Cancelled appointments are removed from active appointment lists.
Cancelled records are moved to a dedicated Cancelled Appointments list.
Staff can also initiate cancellations through a ClickUp dropdown field, with the change reflected in the scheduling workflow.
This provides a clearer distinction between upcoming and cancelled appointments.
4.5 Centralized Appointment Lists and Synchronization
A master Appointments list provides a consolidated view of bookings from Louisville and Evansville.
Custom-field changes are synchronized across the relevant location-specific and central lists, helping maintain consistent appointment information for teams working across departments.
4.6 Automated Appointment Reminders
RingCentral is integrated to send SMS reminders for upcoming appointments.
Image: Ring Central SMS reminder workflow screenshot.
Automated reminders help patients prepare for scheduled visits and reduce the amount of manual communication required from administrative staff.
4.7 Past Appointment Cleanup
Appointments whose dates have passed are automatically removed from the relevant active lists.
This keeps the operational workspace focused on upcoming appointments and outstanding tasks rather than outdated records.
5. Workflow
This workflow connects scheduling, information management, communication, and appointment status updates within the ClickUp operations workspace.
Image: The broader Louisville and Evansville recheck workflow screenshot.
6. Tools and Integrations
Tool
Purpose
ClickUp
Central appointment lists, tasks, custom fields, and workflow automation
Calendly
Appointment booking and cancellation events
Jotform
Patient forms and medical information collection
Gmail
Laboratory communications and attachments
RingCentral
Automated SMS appointment reminders
Slack
Supporting team communication and coordination
7. Outcomes and Business Value
Improved Operational Efficiency
Appointment creation, cancellation handling, record synchronization, and past-appointment cleanup reduce repetitive administrative work.
Better Information Organization
Centralized appointment lists connect scheduling records with relevant patient information and laboratory communications, making information easier for staff to find.
More Consistent Patient Communication
Automated reminders and form-completion notifications support more consistent communication before scheduled visits.
Improved Cross-Location Visibility
The central Appointments list provides a consolidated view of bookings across Louisville and Evansville, supporting teams that need visibility across both facilities.
More Maintainable Operations
Custom fields, dedicated lists, and defined automation rules provide a structured foundation that can be refined as operational requirements change.
8. Technical Highlights
Event-driven automation: Appointment creation and cancellation events initiate the relevant workflows.
Structured task management: ClickUp lists, tags, and custom fields organize appointments by location and type.
Cross-list synchronization: Relevant field updates are reflected across centralized and location-specific lists.
Integrated communications: Calendly, Jotform, Gmail, and RingCentral support scheduling, information collection, laboratory communications, and reminders.
Automated record maintenance: Past appointments are removed from active lists to keep the workspace current.
9. Future Improvements
Potential next steps include refining automation rules based on staff feedback, expanding reporting on appointment statuses and follow-up completion, and reviewing notification workflows to ensure they continue to meet the needs of both locations.
10. Conclusion
The ClickUp implementation brings key operational processes for Veterinary Specialist Partners into a more connected system. By integrating appointment scheduling, patient forms, laboratory communications, SMS reminders, cancellations, and centralized tracking, the solution reduces repetitive administrative work and helps teams maintain more consistent records across Louisville and Evansville.
The result is a structured operations workspace designed to support appointment coordination, information accessibility, and ongoing workflow improvement.
Two n8n workflows that find athlete news, draft the post, and publish it to Instagram once a person approves.
Section: n8n Automations
Project Overview
PeakNIL connects college athletes with brands for Name, Image, and Likeness (NIL) opportunities. To attract brand partnerships and maintain a consistent social media presence, the team needs a steady stream of posts highlighting athlete achievements across 28 sports.
This project uses two connected n8n workflows to automate the process. The first monitors athlete news, evaluates stories, drafts captions, and sends content for review. The second detects the manager’s email response, generates a branded graphic, and publishes the post to Instagram after approval.
Human approval remains part of the publishing process, helping ensure that the final content aligns with PeakNIL’s brand and content standards.
Technology stack: n8n, Claude, Google Sheets, Gmail, Placid, Instagram.
The Business Problem: Scaling Athlete Coverage
PeakNIL manages hundreds of athletes across 28 sports. Finding relevant stories and turning them into social media content requires ongoing research, writing, image selection, graphic design, and publishing.
The main challenges include:
Time-consuming research: Staff must regularly check news about a large athlete roster.
Manual content production: Captions, headlines, photos, and branded graphics require several separate steps.
Inconsistent coverage: Manual processes make it difficult to maintain a regular posting schedule across all athletes.
Incomplete athlete records: Missing information can make it harder to identify and track athletes.
Brand safety: Posts must focus on positive, relevant achievements and avoid injuries, losses, and controversies.
Publishing control: Content must be reviewed and approved before it appears on Instagram.
The objective was to reduce repetitive work while improving consistency and retaining human control over publication.
The Solution
Two connected automations handle the work, and a person approves the result.
Workflow 1: Athlete Monitor (finds and drafts)
Runs every weekday and picks athletes from the roster sheet. It skips anyone with missing data or scanned in the last 3 days.
Searches for recent news (last 3 days) from trusted sports sources.
Claude decides whether the story is worth posting, assigns a content category, and writes the caption and a short headline.
Finds a clean photo of the athlete and emails the draft to the content manager for review.
Image: Workflow 1, Athlete Monitor: a schedule trigger reads the roster from Google Sheets, searches for news, has Claude draft the post, and emails it to the content manager through Gmail.
Workflow 2: Reply Detection (approves and publishes)
The manager replies to the email with an image number or “approve”.
The workflow reads the reply, builds a branded graphic with the chosen photo and headline, and sends it back for a final check.
Once approved, it publishes the post to Instagram and updates the tracking sheet.
Image: Workflow 2, Reply Detection: a Gmail trigger reads the manager’s reply, then one branch builds the graphic with Placid and another publishes to Instagram after approval
How the System Works
Step 1: Read the Athlete Roster
The Athlete Monitor workflow retrieves athlete records from Google Sheets and checks whether each record contains the information needed for monitoring.
Athletes with incomplete data or who were scanned within the previous three days are skipped.
Step 2: Discover Recent News
For eligible athletes, the workflow searches trusted sports sources for relevant news published within the last three days.
This creates a pool of recent stories that can be evaluated for potential social media content.
Step 3: Evaluate and Draft Content
Claude evaluates each story for suitability, assigns a content category, and generates a short headline and caption.
The content must follow PeakNIL’s positive, brand-safe approach, avoiding injuries, losses, and controversies.
Step 4: Send the Draft for Review
The workflow finds a suitable athlete photo and sends the proposed content to the content manager by email.
The manager can review the story and select an image or provide an approval response.
Step 5: Generate the Branded Graphic
The Reply Detection workflow reads the manager’s response and uses Placid to create a branded graphic from the selected photo and headline.
The graphic is sent back for a final check before publishing proceeds.
Step 6: Publish and Update Tracking
After approval, the workflow publishes the post to Instagram and updates the athlete content tracking sheet in Google Sheets.
This closes the loop between discovery, content creation, review, and publication.
05. Workflow Architecture
Workflow 1: Athlete Monitor
Weekday schedule → Google Sheets athlete roster → Eligibility checks → Recent news search → Claude story evaluation and caption writing → Athlete photo selection → Gmail review email
Workflow 2: Reply Detection
The first workflow prepares content for review. The second uses the manager’s response to continue the process and publish only after approval.
Content Rules and Human Approval
The automation is designed to maintain a positive and brand-safe social media presence.
Story Selection
Claude evaluates whether a news story is worth posting and assigns it a content category before generating the draft.
Brand Safety
The content rules exclude stories focused on injuries, losses, or controversies. This helps keep the proposed content aligned with the project's positive athlete-celebration approach.
Human Review
The content manager receives the draft by email and provides a response. The workflow then generates the branded graphic and sends it for a final check.
Publishing remains approval-gated: the workflow is designed to publish to Instagram only after the required human approval.
07. Integrations and Their Roles
Integration
Responsibility
n8n
Orchestrates both workflows and connects the services.
Google Sheets
Stores the athlete roster and tracks content activity.
Claude
Evaluates news stories and drafts headlines and captions.
Gmail
Delivers draft emails and detects manager responses.
Placid
Generates branded social media graphics.
Instagram
Receives approved social media posts.
Each service has a defined role, allowing the workflow to move content between research, writing, review, design, and publishing.
08. Results and Business Value
The project is designed to reduce the manual effort required to create athlete-focused social media content while improving consistency across the roster.
Delivered Capabilities
Automated weekday monitoring of athlete records.
Recent-news discovery using a three-day lookback.
AI-assisted story evaluation, categorization, and caption writing.
Photo selection and email-based content review.
Automated branded graphic generation.
Reply-driven approval processing.
Instagram publishing after approval.
Google Sheets tracking updates.
Checks for incomplete athlete records and recently scanned athletes.
Expected Business Value
Less manual time spent researching athletes and drafting posts.
More consistent coverage across sports and athletes.
Faster preparation of social media content.
A repeatable review and publishing process.
Better visibility into athlete records that need attention.
The project description does not provide measured time savings, publishing volume, engagement improvements, or brand-partnership conversion figures. These should be added after reviewing actual workflow and Instagram performance data.
Key Takeaways
Separate discovery from publishing: The two-workflow design keeps research and drafting distinct from approval and publication.
Use AI to reduce repetitive work: Claude handles story evaluation, categorization, headlines, and captions.
Keep people in control: Human review remains part of the publishing process.
Standardize visual content: Placid generates branded graphics from the selected photo and headline.
Maintain centralized tracking: Google Sheets supports athlete records and content tracking.
Improve coverage consistency: Automated monitoring provides a repeatable process for discovering stories across a large roster.
Future Development
Measure time spent per post before and after automation.
Track the number of stories discovered, drafts reviewed, and posts published.
Measure engagement by sport, athlete, and content category.
Add monitoring for failed news searches, missing photos, and incomplete athlete records.
Evaluate the quality of AI story selection and caption drafts through reviewer feedback.
Add reporting on publishing frequency and approval turnaround time.
Final Outcome
PeakNIL Athlete Content Automation connects athlete news discovery, AI-assisted drafting, email-based review, branded graphic creation, and Instagram publishing in two n8n workflows.
The system is designed to help PeakNIL maintain a consistent flow of athlete-focused content while reducing repetitive production work. By keeping human approval in the publishing process, it balances automation with editorial oversight and brand safety.
WidowWise Platform Automation, Data Integrity & Dashboard Modernization
Repairing and expanding a connected learning platform with automated enrollment synchronization, accurate reporting, and certificate delivery.
Section: Make Automations
1. Overview
Wings for Widows is a Minnesota-based nonprofit that provides free one-to-one financial coaching to widows through a network of approximately 150–170 volunteer CFP advisors. Its digital learning operations run through two distinct programs: WidowWise University (WWU), which provides free and scholarship-funded courses, and Advising Through Widowhood (ATW), a separate paid financial advisor certificate program.
The platform uses Teachable for course delivery, Airtable for operational data and dashboards, Make.com for email and certificate workflows, and Mailchimp for student and advisor communications.
The engagement focused on reverse-engineering and repairing an existing automation system, resolving recurring data and dashboard problems, improving enrollment synchronization, and expanding reporting and certificate automation.
Client: Wings for Widows Platform: WidowWise / WidowWise University Additional Program: Advising Through Widowhood (ATW) Industry: Nonprofit · Financial Education · Professional Training
2. The Problem
The existing system had recurring synchronization and reporting problems that affected enrollment records, dashboard accuracy, and student completion workflows.
The main challenges included:
Inaccurate dashboards: Engagement status fields were sometimes blank, causing totals and charts to show incorrect figures.
Duplicate enrollment records: The original synchronization logic could overwrite previous enrollment history when a student enrolled in the same course more than once.
Unreliable data synchronization: Teachable enrollment data was not consistently matched to the correct Airtable records.
Manual certificate issuance: Completed students required a manual certificate process, creating delays and additional administrative work.
Data quality issues: Duplicate registrations, unmatched enrollment records, and incorrectly classified records affected reporting accuracy.
Automation ownership risk: The primary Teachable API secret belonged to the previous developer, creating a dependency for maintaining the synchronization system.
3. How It Works
The solution connects the learning platform, operational database, automation workflows, and communication system.
Step 1 — Teachable to Airtable Synchronization
Teachable provides the course, student, enrollment, completion, and transaction information used by the operational system.
Airtable serves as the central data layer, containing 20 tables covering people, enrollments, completions, products, lessons, modules, transactions, prices, coupons, graduates, and automation errors.
Scheduled JavaScript automations synchronize Teachable information into Airtable.
Step 2 — Enrollment Matching and Data Integrity
The original enrollment-matching logic used a combination of course and user identifiers. This could cause a new enrollment cycle to overwrite an earlier record.
The matching logic was rebuilt around each enrollment's actual Person and Product relationships.
Existing records for the same person and course are identified.
The record with the highest completion percentage is treated as the current enrollment cycle.
A new record is created only when progress has moved backwards, indicating a genuine restart.
Historical enrollment information is preserved instead of being overwritten by a duplicate synchronization event.
Additional JavaScript and Airtable field-formatting issues were identified during testing and corrected before production.
Screenshot to add: Teachable enrollment records alongside their corresponding Airtable enrollment records. Highlight the Person and Product relationships and the corrected matching logic.
Step 3 — Engagement Status and Dashboard Accuracy
Dashboard totals were not reconciling because some incoming Teachable records had blank Engagement Status fields.
The synchronization process was updated so Engagement Status is automatically derived from Percent Complete on every sync run.
Existing records with blank statuses were backfilled using actual completion data.
The recurring synchronization logic was corrected so new records receive the appropriate status automatically.
A separate In Progress metric was fixed after identifying an incorrect filter and inconsistent Percent Complete data.
This removed the need for repeated manual corrections to dashboard records.
Screenshot to add: Airtable dashboard showing Total, Completed, In Progress, and Not Started, alongside the Engagement Status and Percent Complete fields.
Step 4 — Graduation and Certificate Automation
A certificate automation pipeline was built around the student's completion status.
When Engagement Status changes to Completed:
A sequential Certificate ID is generated.
Certificate and mailing details are sent to C&M Printing.
Chris receives the CFP continuing-education filing information.
The process is gated to prevent certificates from being issued when registration data is incomplete or mismatched.
The workflow also addressed real completion-record issues, including students stuck at 99% and certificate records requiring manual intervention.
Screenshot to add: Make.com certificate automation scenario, the generated Certificate ID in Airtable, and an example of the certificate notification workflow.
Step 5 — Dashboard Expansion
Several dashboards were built or improved to provide more reliable operational reporting.
ATW Enrollments: Corrected metric-card calculations so dashboard figures reconcile.
All Courses (Select to Filter): Created a unified dashboard with a live course-selection dropdown.
ATW Progression (Pace & Stuck Points): Rebuilt based on detailed client feedback, including a clearer advisor grid, normalized completion percentages, and enrollment information.
Percent Complete (Normalized): Added a safety-net formula to protect against incorrectly scaled Teachable values.
Screenshot to add: The ATW Enrollments dashboard, All Courses dashboard with its course selector, and ATW Progression dashboard.
Step 6 — Automation Ownership and Reliability
The Teachable API credential previously belonged to the original developer, creating an operational dependency.
A new independently owned API secret was created, and the synchronization automation was repointed to use it.
This restored the client's control over the integration and reduced dependency on the previous developer.
Screenshot to add: Teachable API integration configuration and the relevant Make.com or Airtable automation scenario. Do not expose API keys or credentials.
4. The Result
The engagement transformed a recurring maintenance problem into a more reliable learning and reporting system.
Enrollment synchronization was rebuilt around actual student and course relationships, preserving enrollment history and reducing the risk of duplicate records. Dashboard calculations were corrected, and Engagement Status is now automatically derived from completion data during synchronization.
Certificate issuance was automated through sequential Certificate IDs, print-partner notifications, and completion checks. Additional dashboards improved visibility into course enrollment, advisor progression, and student completion.
The platform's API ownership was also transferred away from the previous developer, giving the client independent control over the integration.
5. Results & Metrics
The source documents specific implementation outcomes rather than a complete before-and-after performance study.
Area
Documented outcome
Airtable operational database
20 tables
Enrollment synchronization
Rebuilt around Person and Product relationships
Engagement Status
Automatically derived on every sync
Dashboard accuracy
Metric-card calculations corrected
Certificate workflow
Sequential Certificate ID and automated notifications
Dashboard expansion
ATW Enrollments, All Courses, and ATW Progression
API ownership
New independently owned Teachable API secret
6. Tech Stack
Teachable: Learning management system hosting courses and enrollment information.
Airtable: Central operational database, enrollment records, completion tracking, and dashboards.
Airtable Automations: JavaScript-based scheduled synchronization and data processing.
Make.com: Outbound email automation and graduation/certificate workflows.
Mailchimp: Student and advisor communications, including welcome, reminder, continuation, completion, and access-related emails.
Professional Certification Providers: Automate eligibility checks, completion tracking, certificate generation, and continuing-education records.
Online Learning Platforms: Maintain accurate student histories across repeat enrollments, course restarts, and completion cycles.
Coaching Organizations: Track client and advisor progress, program participation, and follow-up workflows.
Training and Development Teams: Combine learning platforms with operational databases to monitor employee training and certification.
This pattern is useful for organizations that rely on multiple connected platforms to manage people, enrollments, learning progress, and communications. By improving synchronization, data integrity, and workflow automation, they can build a more dependable operational system around their existing tools.
From Manual Calendar Checking to Automatic Tutor Matching
Finding the right tutor for a family used to mean checking the tutor sheet and then each tutor's calendar, one by one. Now a staff member posts the request in Slack, and a ranked list of tutors who are really free arrives in the same thread within minutes.
Section: n8n Automations
From Manual Calendar Checking to Automatic Tutor Matching
Browser automation
n8n automations
AI agents
Works with: n8n, Slack, Skyvern, Google Sheets, TutorBird, Claude
Before A tutor sheet and 56 separate calendars to check for every request
Now One ranked report in Slack, in about 2 to 4 minutes
Project overview
A tutoring company places children with tutors. For every family request, one question matters most: which tutors are free at the times this family needs, and right for this child?
Answering it means combining two sources: a tutor sheet (who is available now, where they work, which grades, what experience, how many students) and a separate calendar in TutorBird for each of 56 tutors.
Growlyze built a Slack bot that does this check. A staff member posts the request in a fixed numbered format. The bot shortlists the right tutors from the sheet, has a browser automation read their live TutorBird calendars, matches their free time to the family’s windows and session length, and replies in the same thread with a ranked report.
The bot also handles the family’s time zone, applies the company’s rule for how many sessions a week a tutor must cover, and says why a tutor is only a partial match.
Key results at a glance
Metric
Before
After
Time to a match report
6–8 minutes
2–4 minutes
Calendars read per request
All 56 tutors
Only the shortlisted tutors (24 in the first live test)
Tutor information
A sheet plus 56 separate calendars
One ranked report in Slack
Name matching
Two name formats: “First Last” in the sheet, “Last, First” in TutorBird
All 34 tutors marked available matched to their TutorBird names
Temporary page errors
Re-run by hand
Retried automatically, up to 3 attempts
Report times come from measured live runs (2:00 and 3:54). The calendar figure comes from the first live test, a remote request with 24 shortlisted tutors. No other numbers are claimed.
01. The business challenge
When a family asks for a tutor, speed and accuracy both matter. A family left waiting, or promised a time that can’t be kept, can lose trust quickly. Matching a request to the right tutor involves several connected problems.
1.1 Every request has many conditions
A match has to fit the child’s grade, any experience the family needs (such as ADHD or autism), a city or online, the session length (for example 45 or 60 minutes), how many sessions a week, and the family’s free windows in their own time zone. All of these have to be true at once.
1.2 The answers live in two places
The tutor sheet says who is available now, where they work, which grades they teach, what experience they have and how many students they already have. Their actual free time sits in a separate TutorBird calendar for each of 56 tutors, which has to be opened through the website.
Image: The TutorBird calendar, where each tutor’s lessons and free time live. Student and tutor names are blurred.
1.3 Time zones and names don’t line up
Families write their free times in their own zone (ET, MT, PT and others), while TutorBird shows times in Eastern. The sheet writes names as “First Last”, while TutorBird writes “Last, First”, and some names have a middle name or a two-word surname.
1.4 Free time isn’t always usable time
A tutor can be free for 30 minutes inside a family’s window when the session needs 45 or 60. A request for two sessions a week also needs two separate days, not one long gap.
1.5 A wrong match is costly
If a tutor looks free and isn’t, the family is promised a time that can’t be kept. A child waits longer for help, and the team has to start the search again.
02. The solution: a Slack tutor-matching bot
Growlyze built the bot around the company’s own tutor sheet, TutorBird calendars and Slack channel. It replaces none of them. It connects them, so one Slack message sets the whole check in motion.
2.1 A request in Slack
A staff member posts the request as eight numbered lines: student, remote or address, backup option, session length, how often, the family’s free times, grade, and any experience needed. The bot adds a “working on it” reaction and checks every line; if one is missing, it replies in the thread and says which. AI turns the days named in the request, even a range like Monday to Friday, into real dates for the upcoming Sunday-to-Saturday week.
Image: An example request posted in Slack. The sender, student name and address are blurred.
2.2 A shortlist from the tutor sheet
The bot reads the tutor sheet and keeps tutors who are marked available now, work in the right city or remote, and teach the child’s grade. AI then checks which of them have the experience the family asked for, matching on meaning (“Autism” and “Autism Spectrum Disorder” count as the same condition) and requiring every condition named. For in-person requests, the bot also works out how far each tutor is from the family.
2.3 A live calendar read with Skyvern
The bot sends the dates and the shortlisted tutors, written the way TutorBird writes names, to Skyvern. Skyvern logs into TutorBird, selects those tutors and reads each tutor’s free times for the requested days from that tutor’s own calendar column. The workflow checks every 30 seconds until the read is done, and if TutorBird has a temporary page problem it retries up to two more times.
2.4 Matching free time to the family
AI turns the family’s free-text availability into clear day and time windows, including “either day” options. The bot matches sheet names to TutorBird names, converts times from TutorBird’s Eastern time into the family’s time zone, and keeps only the free time that fits a window and is long enough for the session length.
2.5 A ranked report in the same thread
The bot then checks how many sessions a week each tutor can cover. Tutors who cover every requested session are full matches; those who cover fewer are partial matches, with the reason and any too-short slots listed; the rest are named as having no availability. The top pick is chosen from the full matches (closest for in-person requests, then fewest students), and remote backups are added when too few in-person tutors fit. The report is posted as a reply to the original message, with a check-mark reaction.
Image: An example report. Student and tutor names, and the logo, are blurred.
2.6 Clear failure messages
If a step fails, the bot replies in the thread with “Match failed for this request” and the reason, and marks the message with an X. Temporary calendar errors are retried first, so the team only sees an error when every attempt has failed.
03. End-to-end workflow
The whole process runs as one n8n workflow, started by the Slack message.
Image: The n8n workflow, from the Slack message to the posted report.
Request posted in Slack
Dates and fields read from the request
Shortlist built from the tutor sheet
Calendars read by Skyvern, with automatic retry
Free time matched to the family’s windows and session length
Weekly frequency checked and tutors sorted
Top pick chosen
Report posted in the same thread
There is one path from the Slack message to the posted report, and any failure is reported back to the same thread.
04. What makes this solution different?
Built around the company’s own rules
The bot uses the company’s grade bands, experience matching and student counts. When a family accepts “1x or 2x a week”, a full match must cover the higher number, so tutors who can only do one session show as partial.
Reads only the tutors who could match
The sheet filters run first, and only the shortlisted tutors’ calendars are read. In the first live test that was 24 tutors instead of all 56.
AI where judgment is needed, fixed rules where precision is needed
AI reads the family’s free-text availability and matches experience and names. Time-zone conversion, overlap, session-length checks and sorting follow fixed rules.
Partial matches explain themselves
Every partial match says why it falls short (for example, one session of two) and lists any slots that were too short for the session.
Each tutor is read from their own column
Skyvern takes each tutor’s availability from that tutor’s own calendar column, and the read is set up to check that the number of tutors matches the number of columns.
Temporary errors fix themselves
If TutorBird has a temporary page problem, the bot retries up to two more times before showing an error.
05. Business impact
Match reports in 2–4 minutes
Measured live runs finished in 2:00 and 3:54. Before tuning, matches had slowed to 6–8 minutes; removing an unused calendar-read step and checking for results every 30 seconds instead of every 2 minutes brought them back down.
Fewer calendars to read
Only the shortlisted tutors’ calendars are read. In the first live test, that was 24 tutors instead of all 56.
Less manual re-running
Temporary TutorBird page errors used to mean re-running the request by hand. The bot now retries up to two more times on its own. This has been tested with simulated failures, and the first live retries are still to be observed.
Clearer shortlists
Each report names the full matches, the partial matches with the reason, and the tutors with no availability, so the team can see why someone was or wasn’t suggested.
Accuracy checked by hand
In two test requests, all 21 and all 24 tutors in the reports were checked against the raw calendar data and the tutor sheet, and every time range and experience label matched. All 34 tutors marked available in the sheet matched their TutorBird names.
06. Technology stack
Technology
Role in the solution
n8n
Workflow automation: runs every step, from request to report
Slack
Where requests are posted and where the report is replied
Skyvern
Browser automation: logs into TutorBird and reads the tutors’ free times
TutorBird
The calendar system the team already uses
Google Sheets
The tutor roster: availability, location, grades, experience, student count
Claude (Anthropic)
AI for dates, free-text availability, experience matching, name matching and ZIP estimates
Zippopotam.us
Turns ZIP codes into locations for distance checks
The technologies support the bot’s main functions: request intake, shortlisting, calendar reading, matching and reporting. The team keeps working in Slack, TutorBird and their own tutor sheet.
07. Future enhancements
The following items were identified as future improvements rather than completed capabilities.
Warn when a tutor can’t be found in TutorBird
Today a tutor the calendar reader can’t find shows up as having no availability. The report should say “not found” instead.
Refresh and retry inside the calendar reader
Retrying inside the Skyvern run itself would let a temporary page error recover in seconds, instead of starting the whole read again.
An error message for every failed step
Some steps, such as the AI steps, don’t report a failure to Slack. Adding that would make sure no request is ever left without a reply.
08. Where this pattern applies
This isn’t really about tutoring.
Worked example: a home care agency. A family asks for a caregiver who speaks Spanish, lives nearby, and is free Tuesday and Thursday afternoons. The sheet shortlists caregivers who are active, certified and in the right area. A browser bot reads only those caregivers’ schedules in the scheduling system, keeps the ones free at the family’s times, and posts a ranked list in Slack.
Where else it fits:
Salons and spas: stylist to appointment
Field service: technician to job
Clinics: provider to patient visit
Fitness and coaching: trainer to member
Language services: interpreter to event
Legal and accounting: advisor to client intake
The shape: a request comes in, a sheet shortlists who qualifies, a browser bot reads the live calendars, and a ranked answer lands where the team already works.
What changes from case to case: the filters in the sheet, the calendar system being read, and the rules for what counts as a match.
Conclusion
Matching a family to a tutor depends on a tutor sheet and 56 separate TutorBird calendars, each with its own times, time zones and name formats.
Growlyze connected them with a Slack bot that shortlists tutors from the sheet, reads the shortlisted tutors’ live calendars, converts times to the family’s zone, and replies with a ranked report that explains every partial match.
Measured reports arrive in 2–4 minutes, and temporary calendar errors are retried automatically. The team keeps using Slack, TutorBird and their own tutor sheet.
Automatic Cleanup of Scheduled Posts When a Card Is Unapproved
An n8n workflow that checks every 15 minutes for cards that are no longer approved and removes their still-scheduled posts from Metricool, without touching anything already published or about to go out.
Section: n8n Automations
Project Overview
This project automates the cleanup of scheduled social media posts using n8n, Airtable, and Metricool. When a content card is denied, returned to review, or has a scheduling failure, its previously scheduled posts may still be waiting to publish.
The workflow checks Airtable every 15 minutes for cards with statuses such as Pending Review, Denied, Schedule Failed, or a blank status. It retrieves the associated Metricool post IDs, checks each post's current state, and applies safety rules to determine whether it should be deleted, retained, cleared from the card, or checked again later.
The workflow also updates Airtable with the results, clears obsolete post IDs, records timestamped audit entries, and removes the scheduled time when a post is deleted so the content can be scheduled again after approval.
01. The Business Problem: Unapproved Content Can Still Be Published
A content team manages social media scheduling through Airtable cards and Metricool. Each card stores the Metricool post IDs for its scheduled posts across supported social platforms.
If a card's approval status changes after scheduling, the posts already queued in Metricool may still be published. Without an automated cleanup process, the team must manually locate and unschedule each post.
The main challenges include:
Approval changes after scheduling: Posts can remain queued even after a card is denied or returned for review.
Multiple social platforms: A single card can contain separate Metricool post IDs for X, Facebook, LinkedIn, and Threads.
Publishing safety: Deleting a post that is already published or about to go live can create unnecessary disruption.
Repeated processing: Previously handled post IDs should not be checked repeatedly on every scheduled run.
Auditability: The team needs a record of which posts were deleted, retained, or cleared, and when.
Temporary API failures: A failed lookup or deletion should not prevent the workflow from processing other posts.
The goal was to make scheduled-post cleanup automatic while maintaining strict safeguards around publishing status and timing.
02. The Solution: Automated Unscheduling with Safety Checks
A single n8n workflow runs every 15 minutes and searches Airtable for cards that may require cleanup.
The workflow separates each eligible card into individual Metricool post IDs and checks each post sequentially, with a short pause between API calls. A decision step determines whether each post should be deleted, kept, cleared, or retried during a later run.
Only future, unpublished posts that meet the deletion criteria are sent to Metricool's delete endpoint. Published posts and posts due within the next five minutes are protected. Posts that are already overdue but are not marked as published are also left untouched for manual checking.
After processing, n8n updates the corresponding Airtable card, clears IDs for deleted or already-missing posts, records timestamped decisions in the Unschedule Log, and clears the Scheduled Time when a post is deleted.
If a lookup or deletion fails, the workflow leaves the relevant record untouched so that a later run can retry it.
03. Project Snapshot
Item
Detail
Platform
n8n
Schedule
Every 15 minutes
Source of approval status
Airtable
Social scheduling platform
Metricool
Supported networks
X, Facebook, LinkedIn, Threads
Input
Airtable cards and Metricool post IDs
Decision logic
Status, publishing state, and scheduled time
Processing method
One post ID at a time
Audit trail
Timestamped Unschedule Log in Airtable
Error handling
Failed lookups and deletions remain available for retry
Status
Live and running on an automatic schedule
04. How the System Works
Step 1: Find Cards Requiring Cleanup
Every 15 minutes, the workflow searches Airtable for cards with a status of Pending Review, Denied, Schedule Failed, or blank, provided they still contain a Metricool post ID.
This identifies content that may no longer be eligible for publication but still has scheduled posts associated with it.
Step 2: Split Cards into Individual Posts
A code node converts each eligible card into one item per Metricool post ID.
The workflow checks its processing log and skips IDs that have already been handled and recorded. This reduces unnecessary repeated processing of settled posts.
Step 3: Retrieve Each Post from Metricool
The workflow requests the current details of each post from Metricool, processing one post at a time with a short pause between requests.
If an API lookup fails, the error does not stop the entire workflow. The affected post is left untouched so the workflow can try again during a subsequent run.
Step 4: Apply the Safety Rules
A decision step evaluates the retrieved post information and assigns an action:
Delete: The post is unpublished and scheduled sufficiently far in the future.
Keep: The post is already published or is due within the next five minutes.
Clear: Metricool no longer has the post, so the stale ID can be removed from Airtable.
Retry later: A lookup or deletion fails, leaving the relevant record unchanged for another attempt.
An overdue post that is not marked as published is not automatically deleted. Instead, the workflow records that someone should check its status in Metricool.
Step 5: Delete Eligible Posts
The Delete? branch sends a deletion request to Metricool only for posts marked for deletion.
Posts assigned any other action bypass the deletion request and continue through the merge step. This keeps the delete operation separate from the logic that decides whether deletion is safe.
Step 6: Update Airtable and Record the Outcome
After the deletion and non-deletion branches merge, a code node prepares one update per Airtable card.
The workflow:
Clears IDs for posts that were deleted or were already missing from Metricool.
Adds a timestamped entry to the card's Unschedule Log for each handled post.
Clears the Scheduled Time when a post is deleted, allowing the content to be scheduled afresh after approval.
Leaves failed lookup or deletion records unchanged so they can be retried.
Airtable stores the resulting updates, giving the team a record of the cleanup decisions.
05. Workflow Architecture
The workflow has four main functional layers:
Discovery: Finds Airtable cards that may have obsolete scheduled posts.
Post-level processing: Handles each Metricool post ID separately.
Safety and action routing: Determines whether a post should be deleted, kept, cleared, or retried.
Record synchronization: Updates Airtable IDs, scheduled times, and the audit log.
This separation helps ensure that a post is not deleted simply because its Airtable card has an unsuitable status. Its individual publishing state and scheduled time must also satisfy the safety rules.
n8n Workflow
Image: The workflow is live and includes protections for published content, posts about to go out, and operations that fail. Its next improvement opportunity is to measure cleanup performance and monitor unresolved cases over time.
06. Safety Rules and Deletion Logic
The workflow applies the following rules before deleting a scheduled post.
Post condition
Action
Reason
Future post, not published, and more than five minutes from its scheduled time
Delete
Eligible for automatic cleanup.
Already published
Keep
Published content must not be deleted by this workflow.
Scheduled within the next five minutes
Keep
Avoid interfering with content about to go live.
Past its scheduled time but not marked as published
Keep and flag for manual checking
Avoid making an unsafe assumption about its status.
Metricool no longer has the post
Clear the stale post ID
The post is already gone, so the ID no longer needs to remain on the card.
Lookup or deletion request fails
Leave unchanged and retry later
Preserve the record for a subsequent attempt.
The same safety rules apply across all supported networks, including X.
07. Airtable Synchronization and Audit Logging
Airtable remains the central record of approval status and scheduled-post identifiers.
After processing, the workflow synchronizes the card with the actual cleanup outcome.
Airtable field or record
Purpose
Card status
Identifies content that may require unscheduling.
Metricool post IDs
Tracks the scheduled posts associated with the card.
Unschedule Log
Records timestamped actions and decisions.
Scheduled Time
Cleared when a post is deleted so it can be scheduled afresh.
The log provides visibility into what was deleted, retained, or cleared, along with the time of the action. Failed operations remain available for retry rather than being treated as successful cleanup.
08. Reliability and Error Handling
The workflow is designed to continue processing other posts when an individual operation encounters an error.
Sequential API Requests
Metricool is called one post at a time, with a short pause between requests. This reduces the risk of overwhelming the service when many cards require cleanup.
Failure Isolation
A failed lookup or deletion does not stop the entire workflow. The affected post is left untouched, allowing a later run to retry it.
Previously Handled IDs
IDs that have already been handled and logged are skipped, reducing repeated checks of settled posts.
Separate Decision and Deletion Paths
The workflow sends only posts explicitly marked for deletion to Metricool's delete operation. All other decisions bypass the delete request and continue through the merge path.
These controls reduce unnecessary API calls and help protect posts that should remain scheduled. They do not imply that API failures or every possible scheduling edge case are eliminated.
09. Results and Operational Capabilities
The project description confirms that the workflow is live and runs automatically. It does not provide measured figures for the number of posts cleaned up, API success rate, time saved, or prevented accidental publications.
Implemented Capabilities
Automatic checks every 15 minutes.
Identification of Airtable cards requiring scheduling cleanup.
Individual processing of Metricool post IDs.
Skipping of previously handled and logged IDs.
Protection for published posts and posts due within five minutes.
Manual-review handling for overdue posts not marked as published.
Removal of eligible future, unpublished posts.
Cleanup of stale post IDs when posts are already missing.
Timestamped Unschedule Log entries.
Scheduled Time clearing after deletion.
Retry behavior for failed lookups and deletion requests.
Metrics to Measure Next
A measured production review could track:
Number of cards and posts evaluated per run.
Number of posts deleted, retained, cleared, and retried.
Average time between an approval-status change and cleanup.
Number of failed Metricool requests.
Number of posts that require manual status checks.
Number of duplicate or unnecessary cleanup attempts.
Any cases where an unapproved post remained scheduled or a valid post was incorrectly targeted.
These figures would help quantify the operational value and verify the effectiveness of the safety rules.
10. Key Takeaways
Approval status must remain synchronized with scheduling: Changing an Airtable card does not automatically remove a post already queued in Metricool.
Evaluate individual posts before deletion: A card's status alone is not enough to determine whether every associated post can safely be removed.
Protect publishing boundaries: Published posts, posts due within five minutes, and ambiguous overdue posts receive special handling.
Keep an audit trail: Timestamped Unschedule Log entries make cleanup decisions visible to the team.
Handle failures without losing state: Failed operations remain available for a later retry.
Use sequential API calls: Processing posts one at a time helps control the request rate.
11. Future Development
The next stage should focus on measuring reliability and improving operational visibility.
Add a periodic summary of deleted, retained, cleared, and retried posts.
Track repeated failures and alert the team when a post remains unresolved across multiple runs.
Measure the time between card-status changes and successful cleanup.
Review manual-check cases to determine whether additional Metricool status signals could safely resolve them.
Test the workflow against edge cases involving multiple networks, missing post IDs, schedule changes, and posts close to their publication time.
Maintain an audit of cleanup outcomes to support ongoing verification of the deletion safeguards.
12. Final Outcome
The Automatic Cleanup of Scheduled Posts workflow provides an automated safeguard between Airtable approval decisions and Metricool's publishing queue.
By checking cards every 15 minutes, evaluating each associated post, applying time- and status-based deletion rules, and recording the outcome in Airtable, it helps prevent obsolete scheduled content from being left in the publishing queue.
An AI agent that reads support tickets, applies your SOPs and product manuals, and drafts accurate replies in the customer’s language.
Section: AI Agents, AI Agents for Ecommerce
AI-Powered Customer Support Agent
An AI agent that reads support tickets, applies company SOPs and product manuals, and drafts accurate responses in the customer's language.
Technologies: n8n, Zapier, PostgreSQL, Supabase, Google Sheets, OpenAI
Project Overview
Customer support teams often spend significant time reading long ticket conversations, searching through standard operating procedures (SOPs), reviewing product manuals, and preparing responses to routine customer questions.
This project introduces an AI-powered customer support agent designed to automate these repetitive tasks. It classifies incoming tickets, retrieves relevant policies and product information, applies business rules, and generates customer-ready response drafts alongside internal support notes.
The system also supports ongoing knowledge synchronization so that responses can reference current SOPs and product documentation. Complex or exceptional cases can be escalated for human review.
01. The Problem: Manual Customer Support Doesn't Scale
Before automation, support teams faced several operational challenges.
Time-consuming manual research
Agents had to read lengthy tickets and conversation threads, then switch between multiple sources to find the information needed to respond correctly.
SOP documents and internal policy guides
Product manuals and troubleshooting instructions
Order details and purchase information
Warranty, return, and refund conditions
Inconsistent decision-making
Different agents could interpret the same policy differently, particularly when handling returns, refunds, warranty claims, missing items, defective products, and payment issues.
Outdated knowledge
When product manuals or SOPs changed, agents could unknowingly rely on outdated information, increasing the risk of incorrect responses.
Operational impact
These challenges resulted in:
High manual workload for support agents.
Inconsistent, non-standard customer responses.
Longer response and resolution times.
More effort required to onboard new agents.
Difficulty scaling support as ticket volumes increased.
Core challenge: The business already had the necessary knowledge, but needed a system to retrieve, apply, and use it consistently across support tickets.
02. The Solution: AI-Powered Customer Support Agent
The solution acts as a virtual senior support agent that combines ticket understanding, policy-based decision-making, product knowledge retrieval, and response drafting.
What the system does
Reads incoming tickets and their conversation history.
Understands customer intent and identifies the ticket category.
Detects the customer's language and relevant case details.
Retrieves applicable SOPs and product manuals.
Applies configured business rules for returns, refunds, warranties, and other support cases.
Drafts customer replies in a clear, friendly tone.
Generates internal support notes explaining the relevant policy or manual and suggested next steps.
Escalates complex or exceptional cases for human review.
Supports synchronization of updated SOPs and product documentation.
The objective is to automate routine research and drafting while preserving human oversight where needed.
03. How the System Works: Six-Phase Workflow
Phase 1 — Ticket Intake and Understanding
The process begins when a new customer support ticket arrives.
The AI system:
Reads the full conversation and available ticket context.
Identifies the customer's intent and primary concern.
Detects the language used by the customer.
Checks whether the ticket appears valid or is potentially spam.
Records incoming ticket information temporarily so that it can be processed without being lost.
Output: A ticket prepared for classification, with its conversation context available for subsequent processing.
Phase 2 — Smart Ticket Classification
The system identifies the type of support request and extracts relevant details.
Ticket categories include:
Product usage and troubleshooting
Warranty claims
Return requests
Refund requests
Missing or defective items
Order-status questions
Payment issues
Relevant details may include:
Order ID
Product SKU
Purchase date
Ticket urgency
Customer's specific question or reported problem
Based on the identified category and available details, the workflow determines which SOP or product manual is relevant.
Output: A categorized ticket with extracted information and a defined knowledge-retrieval path.
Phase 3 — SOP-Driven Decision-Making
The system applies the company's documented procedures and configured business rules to the ticket.
Rules may cover:
Warranty eligibility and conditions
Return eligibility
Refund conditions
Price-based thresholds
Other configured support policies
Instead of generating decisions solely from general AI knowledge, the workflow uses the relevant company rules to guide its response.
For example, a refund-related ticket can be evaluated against the applicable refund conditions before a response draft is generated.
Output: A proposed support decision grounded in the applicable SOPs and business rules.
Phase 4 — Product Manual Intelligence (RAG)
For product-specific questions, the system retrieves relevant information from product manuals and the knowledge base using retrieval-augmented generation (RAG).
The retrieval process supports questions involving:
Product instructions and usage
Product specifications
Troubleshooting steps
Product-specific guidance
The retrieved information provides context for the AI response, helping it address the customer's actual question rather than relying only on a general model response.
The knowledge-update component is intended to keep product information and SOPs synchronized as documentation changes.
Output: Relevant product information and policy references for the response-generation stage.
Phase 5 — Response Drafting
After the ticket has been classified and the relevant policies and product information have been retrieved, the AI generates two outputs.
A. Customer reply draft
Friendly, professional tone
Clear explanation of the proposed answer or next steps
Written in the customer's detected language
Based on the applicable SOPs and retrieved product information
Ready for support-agent review or sending according to the configured workflow
B. Internal support notes
Explanation of the proposed response
Relevant SOP or product manual used
Key information considered during processing
Suggested next steps for the support team
These two outputs serve different purposes: the customer receives a clear response, while the support team receives context to help review the proposed answer.
Phase 6 — Continuous Knowledge Updates
The system includes a knowledge-maintenance component designed to keep support information current.
The intended process includes:
Monitoring product manuals for updates.
Synchronizing SOP changes.
Removing or replacing outdated information.
Keeping the knowledge base aligned with current documentation.
This helps reduce the risk of responses relying on obsolete policies or product instructions.
Output: A knowledge base that can be maintained as product documentation and company procedures evolve.
Image: Main workflow from n8n
04. Complete System Workflow
Main ticket-processing workflow
Knowledge retrieval workflow
Exception-handling workflow
Knowledge maintenance workflow
05. Business Value
Reduced manual research
Agents spend less time searching through lengthy SOPs, manuals, and conversation histories to prepare routine responses.
Consistent policy application
Configured business rules and relevant SOPs guide responses across return, refund, warranty, and other support categories.
Faster response preparation
The system automates ticket understanding, knowledge retrieval, and initial response drafting, helping support teams prepare replies more quickly.
Multilingual support
Customer response drafts can be generated in the language detected in the incoming ticket.
Better knowledge reuse
Existing product documentation and company procedures become reusable sources of context for support requests rather than requiring agents to locate and interpret the same information repeatedly.
Improved agent confidence
Internal support notes explain the basis of a proposed response and identify the relevant policy or manual, giving agents useful context for review.
Support scalability
Automating repetitive work can help teams handle larger volumes of routine requests without increasing manual research effort at the same rate.
06. Results and Expected Impact
The original case study reports the following figures and expected benefits.
Time and effort savings
Metric
Reported figure
Routine tickets handled before automation
50–100 per day
Time spent reading manuals and drafting replies before automation
Approximately 2–4 hours per day
Human time required after automation
Approximately 10–15 minutes
Monthly time saved per team
Approximately 50–60 hours
Equivalent support capacity freed
Approximately 1–1.5 full-time support agents
Accuracy and consistency goals
The case study describes the intended benefits as:
Consistent application of configured SOP rules.
More relevant answers to product-specific questions.
Reduced human error and knowledge drift.
Fewer manual policy lookups.
More consistent response preparation.
Cost efficiency
The original case study estimates AI costs at approximately $30–40 per month per agent workflow. Actual costs depend on model usage, ticket volume, retrieval infrastructure, and the deployed integrations.
Important: These metrics are reported in the supplied project description and have not been independently verified. The expected benefits should not be interpreted as guaranteed outcomes for every deployment.
07. How to Replicate This System
The supplied case study describes a workflow-based implementation using an automation platform, an AI model, and a knowledge source.
Step 1 — Prepare the workflow
Open the workflow automation platform used for the project, such as n8n or Zapier.
Create a new workflow.
Import the supplied Customer support Agent.json workflow file, if available and compatible with the platform.
Review the imported nodes, connections, and configuration.
Save the workflow with a suitable name.
Step 2 — Connect the ticket platform
Configure the relevant ticket-platform integration.
Enable the appropriate new-ticket event or webhook.
Configure the endpoint that forwards new ticket information to the workflow.
Ensure the workflow receives the ticket content and any required metadata.
Test that incoming tickets reach the correct workflow entry point.
The exact configuration depends on the ticket platform and the available API or webhook integration.
Step 3 — Configure the knowledge base
Choose the knowledge source used for SOPs, product manuals, and supporting documents.
The original case study lists:
Google Sheets
PostgreSQL
Supabase
Configure the required connection and organize the relevant support documentation. If the implementation uses RAG, ensure the retrieval and indexing components are configured for the selected knowledge source.
Step 4 — Connect the AI model
Configure the OpenAI model credentials and the workflow components responsible for:
Ticket classification
Intent and detail extraction
SOP-based reasoning
Product information retrieval and response generation
Customer reply drafting
Internal support notes
Use clear instructions that require responses to follow the retrieved information and configured business rules.
Step 5 — Configure business rules and escalation
Define the policies that determine how common support categories should be handled.
Examples include:
Return eligibility
Refund conditions
Warranty requirements
Price-based thresholds
Conditions requiring human review
Confirm that exceptional cases are routed appropriately rather than being treated as routine requests.
Step 6 — Test the workflow
Submit test tickets covering different scenarios.
Verify that:
Ticket ingestion works correctly.
Classification and detail extraction produce the expected results.
The appropriate SOPs and product manuals are retrieved.
Business rules are applied as configured.
Customer reply drafts appear in the expected format and language.
Internal support notes contain useful context.
Ticket data and processing results are logged correctly.
Errors, missing information, and exceptional cases are handled appropriately.
Test return, refund, warranty, product troubleshooting, and other relevant scenarios before enabling live processing.
Step 7 — Activate and monitor the workflow
Once the workflow has passed testing:
Enable the workflow.
Monitor its initial runs.
Review generated drafts and escalation behavior.
Check that knowledge updates are reflected in subsequent processing.
Investigate failed runs and adjust the configuration as needed.
From that point, supported tickets can be processed automatically according to the configured workflow, with human review or sending behavior determined by the deployment.
08. Final Outcome
The AI-Powered Customer Support Agent brings ticket understanding, policy retrieval, business-rule evaluation, product knowledge, and response drafting into a unified workflow.
By automating routine research and preparing customer-ready drafts, the system is designed to reduce repetitive work, improve consistency, and help support teams respond more efficiently. Its knowledge-maintenance and escalation components also support ongoing documentation updates and human handling of complex cases.
The result is a more structured approach to customer support in which AI handles repetitive processing while the support team retains visibility into the policies, information, and next steps behind each proposed response.
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.
How Loomstack Inc. consolidated its customer-success stack into a single Airtable workspace, surfacing at-risk accounts 47 days earlier and lifting net revenue retention from 102% to 114%.
Loomstack Inc. is a Series B B2B SaaS company providing workflow automation tooling to mid-market and enterprise customers, with roughly $24M ARR across 280 paying accounts. By Q4 2025 the customer success team was operating across five disconnected tools: HubSpot for CRM data, Zendesk for support tickets, Stripe for subscriptions, a homegrown product-usage dashboard, and a sprawl of Google Sheets for everything that didn’t fit elsewhere. Health scoring was a quarterly spreadsheet exercise, and renewal forecasts were assembled by hand the week before each board meeting.
Over a 9-week engagement we replaced this stack’s coordination layer with a single Airtable workspace, a unified accounts table, computed health scores updated nightly, role-specific Interfaces for CSMs and the VP, and an automation suite that triggers playbooks before churn risk turns into a churn ticket. HubSpot, Zendesk and Stripe still own their primary data; Airtable is the operating surface on top.
Outcomes after 90 days in production
114%: Net revenue retention
47 d: Earlier risk detection
3,742: Automated runs / mo.
$1.2M: Saved ARR (Q1)
At a glance
Before: 5 disconnected tools, quarterly health scoring done in a spreadsheet, renewal forecast assembled by hand, average risk detection lag of 51 days.
After: 1 Airtable workspace as the CS operating layer, health scores recomputed nightly, live forecast on the VP dashboard, average risk detection lag of 4 days.
Background
The client and the problem
About Loomstack
Loomstack sells a workflow automation platform to mid-market and enterprise operations teams across North America and EMEA. Headcount is 180; the customer-facing org is split into 14 CSMs (segmented by Enterprise / Mid-Market), 6 support engineers, and 4 account executives covering expansion. The CS leadership reports to a VP of Customer Success who in turn reports to the COO.
The pain points that triggered the project
Churn was being detected too late. The first signal an account was in trouble was usually a renewal coming up in 30 days and a CSM scrambling. Two enterprise logos worth $640K combined churned in Q3 2025 with effectively no warning.
Health scoring was theatre. A quarterly spreadsheet exercise produced colour-coded statuses that nobody trusted, by the time it shipped, the underlying data was already 4–6 weeks stale.
CSMs lived in eight tabs. A typical customer review meant opening HubSpot, Zendesk, Stripe, Mixpanel, the usage dashboard, the renewal sheet, the QBR notes doc, and the Slack channel, for every account.
Forecasts were unreliable. The VP’s renewal forecast was built in a spreadsheet from CSM-submitted estimates; variance against actuals was running ±22% per quarter.
Playbooks didn’t run. The CS playbook library lived in Notion but was almost never triggered, because nothing automatically noticed when a playbook should fire.
Why Airtable
Loomstack evaluated three category-leading customer success platforms and Airtable. The decision came down to four factors: (1) Loomstack already had clean data sitting in HubSpot, Zendesk and Stripe, what they needed wasn’t another database, but a coordination layer on top, (2) the CS ops team wanted to own the system and iterate on it weekly without a vendor implementation queue, (3) the health-score formula needed to be theirs, not a vendor’s black box, and (4) integration with Slack was non-negotiable. Airtable’s linked-record model, sync sources, and native Slack actions made it the right fit.
Approach
How the implementation was run
We delivered the implementation in four phases over nine weeks. A core working group made up of the VP of Customer Success, two senior CSMs (one per segment), the head of CS Ops, and a RevOps analyst met twice a week to validate the data model, review prototypes, and approve each automation before it went live.
Phase
Weeks
What we did
Output
1. Discovery
1–2
Shadowed CSMs through 5 customer reviews. Audited HubSpot, Zendesk, Stripe and the usage dashboard. Workshopped the health-score formula with leadership.
Process map, data dictionary, agreed health-score definition.
2. Data model & sync
3–4
Designed 11-table relational schema. Configured one-way syncs from HubSpot (accounts/contacts), Stripe (subscriptions) and Zendesk (tickets).
Live Airtable base with synced data; ER diagram.
3. Interfaces & automations
5–7
Built the CSM Command Center, the Account Detail Workspace and the VP Forecast Room. Designed and tested 9 automations.
3 production interfaces; automation library.
4. Pilot, training, go-live
8–9
Piloted with 4 CSMs for one week, trained all 14 CSMs and the VP team, ran a 3-day shadow-mode period before full cutover.
Single-day cutover; 14 / 14 CSMs active on day 1.
Guiding principles
Don’t replace systems of record. HubSpot, Zendesk and Stripe stay as systems of record. Airtable is the system of action on top: pulling from each, surfacing what matters, and writing back where appropriate.
One health score, one definition. Health is a single formula owned by CS leadership, not three competing scores. Every place it appears in the workspace is the same calculation.
Surface signals, don’t bury them. An at-risk account should be impossible to miss. Risk surfaces on the CSM dashboard, the VP forecast, and as a Slack alert, within 24 hours of the signal.
CS Ops owns the base. The head of CS Ops and a RevOps analyst were trained as base administrators and now ship changes weekly without engineering or vendor involvement.
What Was Built
The Accounts table: the heart of the workspace
Every paying customer is a record in the Accounts table. From here, CSMs can see their book of business at a glance, sliced by segment, plan, health band, or renewal window. The grid below shows the production view used by the VP each Monday to triage the team’s at-risk accounts.
Image: Figure 1: The Accounts grid view, grouped by segment and coloured by health band. The footer rolls up total ARR and counts at-risk / critical accounts across the visible records.
Highlights of this view
Health is a coloured chip driven by a formula on the record. It’s the same calculation everywhere it’s shown.
ARR is a rollup from the linked Subscriptions table, which is one-way synced from Stripe, no double-entry, no drift.
CSM is a linked record to the Staff table, so rebalancing books happens in one place and propagates everywhere.
NPS (last) is a lookup from the most recent record in the NPS Responses table, refreshed automatically.
Two more views the team uses every day
Kanban by health band is the view the VP uses on Monday morning. Cards are stack-ordered by ARR, so the largest at-risk accounts always sit at the top. The colour bar on the left of each card encodes the band; the avatar in the corner is the CSM.
Image: Figure 2: Kanban view of the Accounts table, grouped by health band. Healthy / At risk / Critical / Onboarding / Churned columns make book composition obvious in one glance.
The expanded account record
Clicking any row opens the full account detail. This is the screen a CSM lives in during a customer review, every field a CSM might want is on one page, computed live from the underlying tables. The Health Score, Usage Trend, Open Tickets and Days to Renewal all turn red automatically when they cross their respective thresholds.
Image: Figure 3: The expanded record view for ENT-00142 (Halcyon Robotics). Notice that the timeline at the bottom shows the champion-change event detected on Apr 18 that automatically triggered a save playbook.
The Data Model
Eleven tables, one source of truth
The base is built around Accounts as the central entity. Everything else (contacts, subscriptions, tickets, health scores, renewals, playbooks, NPS responses) links back to an account. This single design decision is what makes the rollups, formulas and automations possible.
Image: Figure 4: The 11-table schema. Accounts is the hub; Subscriptions and Tickets are synced from Stripe and Zendesk respectively; the rest is native to Airtable.
Field-level decisions worth calling out
health_score is a single formula combining four sub-scores: usage (40%), support (25%), NPS (20%), commercial signals (15%). Weights live in a Settings table so leadership can tune them without code changes.
health_band is a derived formula (Healthy / At risk / Critical) with bands at 80 and 60, the only place the thresholds are defined in the entire workspace.
days_to_renewal is a formula reading from renewal_date; the renewal automations all read this field, so date arithmetic lives in one place.
Subscriptions is one-way synced from Stripe: Airtable doesn’t write back. ARR is rolled up from synced rows.
Tickets is one-way synced from Zendesk every 15 minutes, open_tickets on the Account is a count rollup.
Interfaces
Three role-based interfaces, one underlying base
Different people on the CS org 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 CSM Command Center
This is the screen a CSM opens when they sit down at their desk. It surfaces the four KPIs that matter to them, the live health distribution of their book, a renewal forecast for the next six months, and a prioritised list of accounts that need attention today, all filtered to their book automatically.
Image: Figure 5: The CSM Command Center, scoped to the logged-in CSM. KPI cards on top; health distribution and renewal forecast charts below; on the right, the accounts that need attention today, sorted by ARR × risk.
Two other interfaces
Account Detail Workspace: the single screen a CSM uses during a customer review. Live health timeline, ticket history, usage chart, contacts directory, active playbooks, and a notes stream, all on one scrollable page.
VP Forecast Room: read-only org-wide view for CS leadership. Net revenue retention trend, weighted renewal forecast by quarter, churn-risk dollar amount, and CSM utilisation. Replaces what used to be a manual Friday afternoon spreadsheet exercise.
Automations
Automating the work that catches churn early
Nine automations remove roughly 3,700 manual touchpoints from the team’s month, but more importantly, they catch churn signals while there’s still time to act. None of them replace a CSM’s judgment; they make sure no signal slips through.
Image: Figure 6: The Automations panel. Nine automations, eight currently enabled, with run counts visible per automation. The detail pane on the right shows the trigger and three actions of the renewal-playbook workflow.
The automation catalogue
Each automation is owned by a named person on the CS Ops team, documented in a Notion runbook, and reviewed monthly.
#
Automation
Trigger
Actions
Replaces
1
Health score recompute (nightly)
Schedule: 2:00 AM, every night
Runs the health-score formula across all accounts; writes a row into Health Scores; updates health_band.
Quarterly spreadsheet exercise
2
Score drop > 15 pts → Alert CSM
Health Scores.delta_30d < −15
Slack DM to CSM + tags account as ‘momentum loss’; logs into the activity timeline.
Nothing: drops were missed
3
Renewal in 90/60/30 days → Playbook
Accounts.days_to_renewal IN (90, 60, 30)
Branches on plan + health to pick playbook (e.g. Enterprise + <80 → exec save). Spawns 5 linked tasks.
Manual playbook lookup in Notion
4
Trial ending in 7 days → Sales handoff
Subscriptions.status = trial AND term_end in 7 days
Creates handoff record; assigns AE; Slack DM to AE with usage summary; books a calendar slot.
CSM-to-AE handoff via email
5
New ticket P1 → Slack war room
Tickets.priority = P1 (synced from Zendesk)
Posts to #cs-warroom; tags CSM, AE, support engineer; creates a Linear issue if flagged.
Manual Slack post by support
6
NPS detractor → Recovery sequence
NPS Responses.score ≤ 6
Sets account flag; emails CSM with NPS comment; creates a follow-up task due in 48 hours.
NPS responses going unread
7
Usage anomaly → Tag account
Usage signal: WAU drop > 25% w/w
Sets a ‘usage_drop’ tag; surfaces it on CSM dashboard ‘Needs attention’ panel.
Caught (sometimes) at quarter-end
8
Onboarding day 14/30/60 check-ins
Schedule: nightly scan of accounts in Onboarding
Spawns the right check-in task at each milestone; emails customer with the day-30 product-tour link.
Three different CSM templates
9
Champion change detected → Playbook
Contacts.is_primary changes OR HubSpot role-change signal
Creates ‘Champion change’ playbook record; spawns a 5-step exec-meeting save plan.
Nothing: usually noticed too late
Worked example: automation #3 in detail
Trigger: nightly check on every Account where days_to_renewal equals exactly 90, 60, or 30 and status = Active.
Action 1 (Conditional branch): evaluates plan + health. Enterprise + health < 80 routes to Playbook A: Executive Save; everything else routes to Playbook B: Standard Renewal.
Action 2 (Create Playbook + tasks): writes a row in the Playbooks table linked to the account, then spawns 5 tasks with due dates working back from the renewal date.
Action 3 (Notify): Slack DM to the CSM with a deep link to the account; appends the record to the VP’s weekly forecast view.
Replaced: CSMs manually checking renewal calendars and looking up playbooks in Notion (frequently the wrong playbook, frequently too late).
Integrations
How the workspace connects to the SaaS stack
Airtable doesn’t replace HubSpot, Zendesk, Stripe, or the product analytics warehouse. It coordinates them.
System
Direction
What flows
Mechanism
HubSpot
One-way (in)
Accounts and Contacts sync nightly. Field-level mapping for industry, employee count, lifecycle stage and owner.
Airtable HubSpot sync source
Stripe
One-way (in)
Subscription rows sync every 4 hours. ARR rolls up from subscription records to the account.
Stripe → Airtable via Zapier
Zendesk
One-way (in)
Tickets sync every 15 minutes. Priority, status, assignee, and time-open are all rollup-able.
Native Zendesk sync
Slack
One-way (out)
Health drops, P1 tickets, renewal-playbook triggers, NPS detractor alerts.
Native Slack action in Automations
Mixpanel / Snowflake
One-way (in)
Daily WAU and feature-adoption metrics per account, used as inputs to the health score.
Snowflake → Airtable via reverse-ETL
Linear
One-way (out)
P1 tickets that need engineering escalation create a Linear issue with customer context attached.
Linear API call from script action
Gmail / Outlook
One-way (out)
Customer-facing emails (NPS follow-ups, day-30 onboarding tour) sent from automation actions.
Native email actions
Permissions & data handling
Workspace plan: Airtable Business with SAML SSO via the company’s identity provider. Two-factor authentication enforced for all users.
Field-level permissions: ARR and renewal amounts are read-only for CSMs and hidden from support engineers; visible to AEs and the VP.
Book-level filtering: CSMs see only their own accounts by default on every interface; the VP sees the full org. No CSM can edit another CSM’s accounts.
Audit: Airtable’s revision history is retained, and a nightly backup is exported to the company’s S3 bucket via the Airtable API.
Results
Measurable change after 90 days in production
Metric
Before
After
Change
Net revenue retention (NRR)
102%
114%
+12 pts
Average risk-detection lag
51 days
4 days
−92%
Renewal forecast variance
± 22%
± 6%
−73%
At-risk ARR identified earlier
n/a
$1.2M (Q1)
+ saved revenue
CSM time spent on reporting
≈ 6 hr / week
≈ 45 min / week
−87%
Playbook trigger rate
≈ 14% of cases
100% of cases
+ coverage
Automated touchpoints / month
0
3,742 across 8 active flows
n/a
CSM adoption (firm-wide)
n/a
14 / 14 active on day 1
100%
In the words of the team
The thing that changed isn’t really the dashboard: it’s that the team has time. My CSMs aren’t building reports any more, they’re actually talking to customers. And when an account starts going sideways, we know about it the next morning, not three weeks later when the renewal blows up. We saved $1.2M of ARR last quarter that would otherwise have walked out the door.
What we’d do again, and what we’d change
Worked well: co-designing the health-score formula with leadership in week 1. Because they owned it from day one, nobody argued with the scores once they started shipping.
Worked well: shipping the CSM Command Center first and the VP Forecast Room last. Adoption follows the front line.
Would change: we underestimated the data-cleanup burden in HubSpot during phase 2. About 11% of accounts had missing or stale ownership; cleaning that up consumed three days we hadn’t planned for.
Would change: add an in-product feedback widget that writes directly to the NPS Responses table. The current Typeform-based flow has a higher drop-off than we’d like.
Section: Custom SaaS Platforms, n8n Automations, AI Agents
Project Overview
Pure NSM manufactures capsule supplements for brands that need their own formulas produced at commercial scale. For every prospective customer, one of the most important questions is straightforward: How much will this formula cost to manufacture?
Answering that question, however, involved a complicated process. Quotes were prepared in a large Excel workbook, pricing information was spread across QuickBooks exports and supplier websites, and the manufacturing calculations required detailed knowledge of the business. Only a few experienced team members knew how to complete the workbook correctly.
The result was a quoting process that typically took two to three weeks.
Growlyze replaced this spreadsheet-dependent process with a custom quoting platform that centralizes ingredient and packaging costs, automates manufacturing calculations, supports AI-assisted quote editing, identifies missing supplier prices, and checks formulas for known production risks.
The platform also extends the quoting process to Pure NSM’s website, where prospective customers can receive a ballpark estimate without waiting for a sales call.
Key Results at a Glance
Metric
Before
After
Quote turnaround
2–3 weeks
24–48 hours
Raw material records
Distributed across data sources
7,800+ items in one searchable database
Packaging components
Maintained across separate sources
460+ items centralized
Quote preparation
Complex Excel workbook
Guided four-step quote builder
Public pricing
Enquiry and waiting process
Three-step ballpark estimator
The reported improvement reduced quote turnaround from several weeks to one or two days. The centralized database and automated calculations also made pricing information easier to access and the quoting process less dependent on a small number of spreadsheet specialists.
01. The Business Challenge
In supplement contract manufacturing, responding quickly with an accurate quote can influence whether a prospective customer chooses a manufacturer. A brand developing a new formula may approach several manufacturers at once. When one manufacturer takes weeks to respond, the opportunity to engage that customer can be lost.
Pure NSM’s previous process created several connected problems.
1.1 A Complex Spreadsheet Was the Bottleneck
Every quote depended on a large, multi-tab Excel workbook. Preparing a quote required the user to enter the correct information, follow the existing calculations, and ensure that the different cost components were handled properly.
A mistake in a single cell could affect the final price. Because of this complexity, only a few experienced team members could confidently prepare quotes.
When those team members were busy, other quotes had to wait. The process therefore depended not only on the complexity of the workbook but also on the availability of people who understood how to use it correctly.
1.2 Pricing Information Was Scattered Across Multiple Sources
The cost of manufacturing a supplement depends on more than its ingredient quantities. The team also needs current prices for raw materials, packaging, labour, and other relevant production inputs.
Before the new platform, this information was spread across:
QuickBooks exports.
Existing ingredient and packaging price lists.
Historical pricing records.
External supplier websites.
When an ingredient price was missing, someone had to search supplier websites, compare different package sizes, and manually convert the results into a comparable price per kilogram.
This repetitive research added time to quote preparation and made it harder to maintain a consistent view of costs.
A supplement quote cannot be calculated through simple multiplication alone. The pricing process must account for how ingredients are used and how manufacturing costs change with formula composition and order size.
The calculations included:
Ingredient potency: Low-potency ingredients can require more raw material to achieve the intended amount in the finished product.
Overage adjustments: Vitamins and minerals may require additional quantities to account for manufacturing requirements.
Packaging quantities: Bottle sizes and order volumes affect the quantities and costs of packaging components.
Production labour: Labour costs vary across 15 different manufacturing steps.
Margins and volume tiers: The final price must reflect the business’s margins and the requested order quantity.
Performing these calculations manually made quote preparation slower and left more room for errors in pricing and margins.
1.4 Formula and Production Risks Could Be Identified Too Late
Certain ingredient combinations can create formulation challenges or production difficulties. A formula may also present problems when processed through manufacturing equipment.
When these issues are not identified during quote preparation, the team may discover them only after the quote has already been sent.
Pure NSM therefore needed a way to flag known ingredient and production risks earlier, while the formula was still being reviewed.
1.5 Prospective Customers Could Not Get an Immediate Estimate
The existing process required prospective customers to submit an enquiry and wait for the sales team to prepare a quote.
This introduced friction at the beginning of the customer journey. Interested brands could not quickly assess whether a formula was likely to fit their budget, and the sales team spent time responding to enquiries that might not become viable opportunities.
The challenge was to make pricing more accessible without removing the detailed calculations required for manufacturing-specific quotes.
02. The Solution: A Custom Manufacturing Quoting Platform
Growlyze built a quoting platform around Pure NSM’s existing pricing logic, data, and operational requirements.
Rather than simply transferring the spreadsheet into another interface, the platform separates the process into connected components: centralized cost management, guided formula entry, automated calculations, AI-assisted changes, supplier price discovery, formula checks, quote generation, and public price estimation.
Each component addresses a specific weakness in the original process.
2.1 Centralized Database for Costs and Materials
The first step was to bring the information required for quoting into one searchable database.
The platform consolidates:
More than 7,800 raw material records.
More than 460 packaging components.
Labour rates.
Supplier contacts.
QuickBooks pricing information.
The team can search for items, edit records, and perform bulk price updates rather than repeatedly consulting different files and websites.
Each price also records its source, such as the internal database, QuickBooks, a supplier website, or a manual entry. This helps the team understand where a cost originated when reviewing a quote.
The centralized database provides the foundation for the platform’s other features: calculations can use the available cost data, while missing prices can be identified for further research instead of being treated as known values.
2.2 Guided Quote Builder With Automated Calculations
The quote builder organizes the preparation process into four steps: Formula, Packaging, Labour, and Summary.
This structure makes the workflow easier to follow and separates the main areas that contribute to the final price.
Step 1 — Formula
The team enters the ingredients and quantities required for the proposed supplement formula. The platform applies the relevant potency and overage adjustments as part of its calculation process.
Step 2 — Packaging
The packaging step accounts for the selected bottle sizes and the required packaging quantities, allowing packaging costs to be incorporated into the quote.
Step 3 — Labour
The platform estimates labour hours and costs across 15 production steps. This allows the labour component to be included in the overall calculation rather than handled separately through manual spreadsheet work.
Step 4 — Summary
The system combines the calculated costs, applies Pure NSM’s margins, and produces six price tiers. These cover two bottle sizes at three different order volumes.
The calculation logic was checked against a real historical quote, and the resulting price matched to within ten cents. This provided a practical validation point against the company’s existing quoting process.
2.3 AI Assistant for Natural-Language Quote Editing
The platform includes an AI assistant that allows team members to request quote changes in plain English.
Instead of manually locating every relevant field, a user can enter an instruction such as:
“Add 200mg magnesium glycinate.”
“Set bottle cost to 75 cents.”
The assistant interprets the instruction and proposes the requested changes. The changes are not applied automatically: a team member must approve them first.
This approval step keeps the user involved in pricing decisions and reduces the risk of unintended changes to a quote.
The assistant also follows an important pricing safeguard: it is not allowed to guess missing prices.
If a required cost is unavailable, the assistant identifies the missing information and directs the user to the Price Finder. This ensures that an unknown price is treated as a gap to resolve rather than an opportunity for the AI to invent a value.
2.4 Price Finder for Supplier Research
Ingredient prices may be missing from the internal database, particularly when the team needs to quote an ingredient that has not previously been used or priced.
The Price Finder streamlines this process.
The team can paste in up to 50 ingredients at once. The system first checks Pure NSM’s own database and then searches supplier websites when additional pricing information is required.
The results are processed so that different package sizes can be compared on a price-per-kilogram basis. The system also assesses how closely each result matches the requested ingredient and presents the available options side by side.
After reviewing the options, the team can select a price and add it to the quote with one click.
This approach reduces repetitive supplier research and brings price discovery into the quoting workflow itself.
2.5 Formula Safety and Production-Risk Checks
The platform checks ingredient changes against known problematic combinations and production risks.
These checks are integrated into the quote-building process so that potential issues can be highlighted while the team is still preparing the quote.
This gives the team an opportunity to review known concerns before the quote is sent, rather than relying entirely on someone noticing the issue during a later review.
The purpose is to surface potential risks earlier; the checks do not replace the need for appropriate formulation and manufacturing review.
2.6 One-Click Quote Document Generation
Once a quote is ready, the team can click Send to generate a formatted quote document.
The document includes:
All six pricing tiers.
The associated cost breakdown.
The 50% deposit amount.
This reduces the manual work required to assemble the final quotation after the calculations have been completed.
Instead of preparing the calculations in one place and formatting the customer-facing document separately, the platform connects quote preparation with document generation.
2.7 Website Estimator for Prospective Customers
The same pricing engine also powers a public-facing estimator on Pure NSM’s website.
Prospective customers enter their formula and quantity through a three-step process. They then receive a ballpark price per bottle on screen and by email, without needing an account or a sales call.
The estimator also sends the customer’s details and formula information to the sales team.
This creates a direct connection between the pricing platform and lead generation. Prospective customers can explore indicative pricing independently, while the sales team receives information about the formula they are interested in.
The website estimator provides a ballpark price; it should not be confused with a fully reviewed manufacturing quotation.
03. End-to-End Workflow
The platform connects its internal pricing process and public-facing estimator through the same underlying pricing logic.
Public-facing path:
These paths address two related goals: helping the internal team prepare quotes faster and giving prospective customers a quicker way to understand indicative pricing.
04. What Makes This Solution Different?
Built Around Pure NSM’s Manufacturing Logic
The platform was designed for the pricing requirements of supplement manufacturing, including potency, overage, packaging, production labour, and order-volume tiers.
It uses Pure NSM’s own pricing logic rather than relying on a generic quoting process.
AI With Guardrails
The AI assistant proposes changes for human approval and does not invent missing prices. This keeps pricing decisions under team control while still providing the convenience of natural-language instructions.
Supplier Research Integrated With Quoting
The Price Finder connects missing ingredient costs with supplier research and price normalization. The team can compare potential matches and bring a selected price directly into the quote.
Cost Sources Remain Visible
Prices retain source information, helping the team review where costs came from instead of treating every figure as an unexplained spreadsheet value.
Internal Quoting and Public Estimation Share One Pricing Engine
The website estimator extends the same pricing system to prospective customers. This connects internal quoting operations with a self-service route for generating enquiries.
05. Business Impact
Quote Turnaround Reduced to 24–48 Hours
The reported turnaround improved from two to three weeks to 24–48 hours. Pure NSM can now respond to prospective customers much faster, which is particularly important when brands are comparing multiple contract manufacturers.
Less Dependence on Spreadsheet Specialists
The guided workflow and automated calculations make quote preparation less dependent on a few experienced spreadsheet users. The process is organized into defined stages that other team members can follow.
More Consistent and Traceable Pricing
The platform brings cost records into one searchable location, records price sources, and applies the manufacturing calculations consistently. Its calculation logic was also checked against a historical quote, with a difference of no more than ten cents.
Earlier Identification of Formula Risks
Known ingredient and production concerns can be surfaced during quote preparation. This gives the team more opportunity to review potential issues before sending a quotation.
Faster Access to Supplier Pricing
The Price Finder reduces the need to research and normalize supplier prices manually for every missing ingredient. It supports batches of up to 50 ingredients and presents potential matches for review.
Improved Customer Access to Indicative Pricing
The website estimator lets prospective customers obtain a ballpark estimate without first arranging a sales call. The sales team receives their details and the formula they are interested in, creating a more direct path from pricing exploration to follow-up.
06. Technology Stack
Technology
Role in the Solution
React
Frontend application interface
Node.js
Application backend
OpenAI
AI-assisted quote editing
Firecrawl
Supplier website research
n8n
Workflow automation
Google Sheets
Supporting data workflows
QuickBooks data
Existing pricing information used by the platform
The technologies support the platform’s main functions: cost-data management, quote calculations, AI-assisted changes, supplier price discovery, and connected workflows.
07. Future Enhancements
The following items were identified as future improvements rather than completed capabilities.
Quote History
Save quotes and their history directly in the platform so previous pricing decisions can be reviewed more easily.
CRM Integration
Feed winning quotes back into the CRM to track win rates and margins by customer. This would help connect quoting activity with subsequent sales outcomes.
Additional Formula and Packaging Guidance
Extend the safety-check process with capsule-size and bottle-fit recommendations to provide additional guidance during quote preparation.
Conclusion
Pure NSM’s original quoting process relied on a complex spreadsheet, dispersed pricing information, and specialist knowledge. Preparing a quote could take two to three weeks, while prospective customers had to wait for the sales team to provide an estimate.
Growlyze replaced that process with a custom quoting platform that centralizes more than 7,800 raw materials and 460+ packaging components, automates manufacturing calculations, supports AI-assisted editing with human approval, helps locate supplier prices, flags known formula risks, and generates formatted quote documents.
The same pricing engine also powers a website estimator, allowing prospective customers to obtain a ballpark price without a sales call.
The reported result is a reduction in quote turnaround from two to three weeks to 24–48 hours, supported by a more structured and traceable pricing proces
A full-stack MERN real estate operations platform with CRUD, Google Auth, live charts, and Cloudinary image management, built on the Refine framework with Material UI.
Section: Custom SaaS Platforms
Project Overview
Estato is a full-stack real estate management platform designed to help real estate teams manage property listings, agent information, and portfolio performance from a centralized dashboard. Built using the MERN stack, TypeScript, and the Refine framework, it combines property management, analytics, and authentication in a unified interface.
The platform provides complete property CRUD operations, allowing agents to create, view, update, and delete listings with structured details such as property type, location, price, description, and images. Cloudinary handles property image uploads and delivery, while MongoDB Atlas stores property records and agent information.
The dashboard presents key operational metrics, monthly revenue trends, property referral sources, and recently added listings. Google OAuth provides individual user authentication, while agent directories and profile pages help teams view agent information and property portfolios. Built with Material UI and ApexCharts, Estato also supports light and dark modes for a flexible user experience.
Project Details
Project Type: Full-Stack MERN Application Case Study
Product: Estato — Real Estate Management Dashboard
Frontend: React 18, TypeScript, Refine Framework, Material UI, ApexCharts
Backend: Node.js, Express, ESM Modules
Database: MongoDB Atlas with Mongoose ODM
Authentication: Google OAuth, Google Identity Services, JWT, localStorage
Media Storage: Cloudinary for property image uploads and delivery
Image: The Estato dashboard: revenue, property, agent and customer tiles, a monthly revenue chart and a property referrals breakdown.
Why We Built This
Real estate teams often manage property listings, agent information, and performance data across disconnected tools. Property records sit in listing portals, agent performance is tracked in spreadsheets, and photos are scattered across emails or local drives. Without a centralized dashboard, getting a complete view of operations becomes difficult.
The core challenges Estato was designed to solve:
Fragmented Property Data: Listings were spread across multiple platforms without a consistent structure for property type, location, price, and description.
Limited Agent Visibility: Managers lacked a clear overview of agent portfolios and how properties were distributed across the team.
Inefficient Listing Management: Creating and editing listings without standardized forms, structured property types, and direct image uploads was time-consuming.
Lack of Centralized KPIs: Tracking properties for sale and rent, total customers, and total agents required manual effort across multiple systems.
Limited Referral Insights: Teams lacked a centralized view of which channels, including social media, marketplaces, websites, and digital ads, generated enquiries.
Unmanaged Authentication: Shared credentials limited individual accountability and made it difficult to associate listings with specific agents.
Our goal was to build a unified MERN-stack dashboard where agents could sign in with Google and manage their own property listings, while managers could monitor key metrics, revenue trends, referral sources, and the entire agent directory from one place.
What this system does
Estato is a full-stack MERN application that gives real estate teams a complete operations interface: live analytics, a full property CRUD system, an agent directory, individual profiles, and Google-authenticated access. The Refine framework handles data fetching, routing, and auth integration; Material UI provides the component layer; ApexCharts and custom donut charts deliver the analytics.
Operations dashboard
Four donut-style KPI tiles at the top of the home page give instant visibility: Properties for Sale (live count from the API), Properties for Rent, Total Customers, and Total Agents, each with a percentage ring showing the proportion against a target
Total Revenue area chart (ApexCharts) renders monthly revenue data across the full year with a smooth curve and gradient fill
Property Referrals horizontal bar chart shows the contribution of each lead source: Social Media (64%), Digital Ads (80%), Websites (50%), Marketplace (40%), and Others (15%).
Latest Properties section beneath the charts shows the 4 most recently added properties as live cards pulled from the API in real time
Property management (full CRUD)
All Properties page renders the full listing catalogue as a responsive card grid, with live search by title, filter by 8 property types (Apartment, Villa, Farmhouse, Condos, Townhouse, Chalet, Studio, Duplex), price sort toggle, and server-side pagination with a configurable page-size selector (5, 10, 20, 30, 40, 50, All)
Property Detail page shows the full-size property photo, property type with a 5-star rating, title, location, price, and description on the left. The right sidebar shows the creator agent’s avatar, name, property count, and location. Context-aware action buttons adapt based on the logged-in user: Message and Call for other agents’ listings; Edit and Delete for the current user’s own listings
Create Property form collects title, property type, description, location, price, and photo. The photo is read into base64 via the FileReader API and submitted to the backend, which uploads it to Cloudinary and stores the CDN URL
Edit Property form pre-populates all existing field values and allows any field to be changed, including the photo. If the photo is unchanged, the existing Cloudinary URL is preserved
Delete uses a Mongoose session transaction to remove the property document and simultaneously pull it from the creator’s allProperties array, keeping both collections in sync atomically
Agent management
Agents List page displays every registered user as an agent card with their Google avatar, name, email address, and total property count
Agent Profile page shows the full agent detail view via the shared Profile component, including the agent’s complete property portfolio
My Profile page uses the same shared Profile component for the currently authenticated user, with data fetched by their own MongoDB user ID
Authentication
The login page renders a Google Sign-In button using the Google Identity Services API. The credential response is a signed JWT
parseJwt utility decodes the Google JWT on the client to extract name, email, avatar (picture), and sub (user ID) from the payload
On every login, the user profile is POST-ed to /api/v1/users, which is idempotent: it returns the existing MongoDB document if the email already exists, or creates a new user record if not
The raw Google credential token is stored in localStorage as token. Axios’s request interceptor attaches it as Authorization: Bearer <token> to every subsequent API call
On logout, token and user are removed from localStorage and google.accounts.id.revoke() is called to invalidate the Google session
Light and dark mode
ColorModeContextProvider wraps the entire application and exposes a setColorMode function through React context
The current mode is stored in localStorage to persist the user’s preference across sessions. On first load, the system’s prefers-color-scheme media query is checked to set the default
Two custom Material UI themes are defined: overridedLightTheme and overridedDarkTheme, each extending Refine’s built-in theme objects with custom palette overrides. The active theme is passed to ThemeProvider at runtime
Benefits
Single source of truth for the portfolio: every property, agent, and relationship lives in one MongoDB database with a consistent schema, accessible from any device
Live KPIs on every login: four dashboard tiles give the team instant situational awareness without opening a single spreadsheet
Consistent listing creation: the structured form with defined property types ensures every listing is created to the same standard, with a real photo uploaded directly to Cloudinary
Role-aware property actions: agents can only edit or delete their own listings; other agents’ listings show contact options instead
Atomic data integrity: create and delete operations use Mongoose session transactions to keep the Property collection and the User.allProperties array perfectly synchronised
Zero password management: Google OAuth means no passwords to store, reset, or manage; every agent has their own authenticated identity
Scalable Refine architecture: adding a new resource (reviews, messages, enquiries) requires registering it in App.tsx; the data provider, routing, and UI scaffolding are automatically available
Dark/light mode out of the box: system preference is respected on first load; the preference is then stored in localStorage and toggleable at any time
How it works
Agent visits the login page and clicks ‘Sign in with Google’. Google Identity Services returns a signed JWT credential
parseJwt decodes the JWT client-side to extract the user’s name, email, and avatar. The profile is POST-ed to /api/v1/users, which creates or finds the user in MongoDB
Token stored in localStorage; Axios interceptor attaches it as a Bearer token to every subsequent request. Refine’s checkAuth hook reads localStorage on each route change to decide whether to redirect to login
Dashboard loads and fires a useList call to /api/v1/properties (pageSize: 4) for the Latest Properties grid. The 4 KPI donut tiles and both ApexCharts components render with static or aggregate data
All Properties page uses Refine’s useTable hook, which manages current page, page size, sorter, and filters as state and translates them into query params on the API call (_start, _end, _sort, _order, title_like, propertyType)
Creating a property: the agent fills the form. On photo selection, FileReader reads the file as a base64 data URL. On submit, onFinish POSTs the full payload (including the base64 photo and the agent’s email) to /api/v1/properties
Server receives the POST, finds the user by email, uploads the base64 photo to Cloudinary, receives back a CDN URL, then opens a Mongoose session and atomically creates the Property document and pushes its _id to user.allProperties
Property Detail page calls useShow to fetch /api/v1/properties/:id with the creator user document populated. Action buttons (Edit/Delete vs Message/Call) are conditionally rendered by comparing user.email with propertyDetails.creator.email
Deleting a property opens a browser confirmation dialog. On confirm, useDelete fires a DELETE request. The server opens a Mongoose session, removes the Property document, and pulls its _id from creator.allProperties, then commits the transaction
Agent and profile pages call useList / useShow against /api/v1/users, which returns user documents with all properties populated. The shared Profile component renders the same layout for both Agent Profile and My Profile
System architecture
Page inventory
Estato consists of 9 pages, each a React TypeScript component managed by Refine’s routing and data layer.
Page
File
Key Content
Dashboard (Home)
home.tsx
4 PieChart KPI tiles, TotalRevenue ApexChart, PropertyReferrals bar chart, Latest Properties card grid (4 items live from API).
All Properties
all-properties.tsx
Full property grid with search by title, filter by 8 property types, sort by price (asc/desc), page size selector, Previous/Next pagination.
Property Details
property-details.tsx
Full-width photo, property type + 5-star rating, title, location, price, description. Agent sidebar: avatar, name, property count, location, Google Map, Book Now, Message/Edit + Call/Delete buttons.
Create Property
create-property.tsx
Delegates to shared Form component. Handles image file selection (FileReader to base64), attaches logged-in user email before submitting to API.
Edit Property
edit-property.tsx
Same shared Form component as Create. Pre-populates existing property data. Allows photo re-upload; photo URL preserved if unchanged.
Agents List
agent.tsx
Grid of all users (agents) from /api/v1/users. Each AgentCard shows avatar, name, email, and property count. Clicking navigates to agent profile.
Agent Profile
agent-profile.tsx
Full agent detail using shared Profile component. Shows avatar, name, email, properties count and full property list.
My Profile
my-profile.tsx
Logged-in user’s own profile using the same shared Profile component. Data fetched from /api/v1/users/:userId.
Login
login.tsx
Google Sign-In button using Google Identity Services. On success, JWT decoded, user POSTed to /api/v1/users, token stored in localStorage.
Data models
Two Mongoose schemas define the complete data layer. The bidirectional relationship between Property and User is maintained by the server using session transactions on create and delete operations.
Collection
Field
Type
Notes
Property
title
String (required)
Listing headline
Property
description
String (required)
Full description text
Property
propertyType
String (required)
Apartment, Villa, Farmhouse, Condos, Townhouse, Chalet, Studio, or Duplex
Property
location
String (required)
Free-text location / address
Property
price
Number (required)
Numeric value (rendered as $price per day in the UI)
Property
photo
String (required)
Cloudinary CDN URL after base64 upload
Property
creator
ObjectId → User
Populated on read to include full user document
User
name
String (required)
Full name from Google profile
User
email
String (required)
Google account email; used as unique identifier
User
avatar
String (required)
Google profile picture URL
User
allProperties
[ObjectId] → Property
Bidirectional reference array; maintained via Mongoose transactions
Note
The User schema does not require a password field because authentication is handled entirely by Google OAuth. The email address serves as the unique identifier and is used both for login matching and for associating new properties with the correct creator.
API reference
All endpoints are prefixed with /api/v1/ and served by the Express server on port 8080. No authentication middleware is currently applied server-side; auth is enforced client-side by Refine’s checkAuth hook and the Axios Bearer token interceptor.
Method
Endpoint
Description
GET
/api/v1/properties
List all properties. Supports _start, _end, _sort, _order, title_like, propertyType query params. Returns x-total-count header for Refine pagination.
GET
/api/v1/properties/:id
Fetch a single property with creator user populated (name, email, avatar, allProperties).
POST
/api/v1/properties
Create a new property. Uploads photo to Cloudinary via base64. Uses Mongoose session transaction to atomically create property and push to user.allProperties.
PATCH
/api/v1/properties/:id
Update an existing property. Re-uploads photo to Cloudinary. Falls back to original photo URL if upload fails.
DELETE
/api/v1/properties/:id
Delete a property. Uses Mongoose session transaction to remove from DB and pull from creator’s allProperties array atomically.
GET
/api/v1/users
List all users (agents). Supports _end for limit. Returns full user documents including allProperties references.
POST
/api/v1/users
Create or find a user by email (idempotent). Called on every Google OAuth login to ensure the user record exists in MongoDB.
GET
/api/v1/users/:id
Fetch a single user by MongoDB _id with allProperties populated. Used by agent profile and my profile pages.
Technology stack
The complete dependency surface for both client and server packages:
Layer
Package / Version
Role
UI Framework
@pankod/refine-core ^3.103
Data fetching (useList, useShow, useDelete, useGetIdentity), auth provider, routing
Component Library
@pankod/refine-mui ^3.63
Material UI integration for Refine: layout, notifications, theme provider
Forms
@pankod/refine-react-hook-form
react-hook-form integration for create/edit property forms with Refine’s onFinish lifecycle
Routing
@pankod/refine-react-router-v6
React Router v6 adapter; all navigation uses useNavigate, useParams
Data Provider
@pankod/refine-simple-rest
Maps Refine resource operations to REST calls against the Express API
Charts
apexcharts + react-apexcharts ^1.4
TotalRevenue (area chart) and PropertyReferrals (horizontal bar chart)
Charts (KPI)
Custom PieChart component
4 donut-style KPI tiles on the dashboard (Properties for Sale/Rent, Customers, Agents)
HTTP
axios ^0.28
All API calls; Axios interceptor attaches Bearer JWT token to every outbound request
Loading State
react-loader-spinner ^5.4
Consistent loading indicator shown across all async pages via the shared Loader component
Automate lead qualification, respond instantly through WhatsApp in multiple languages, assign prospects fairly, and track follow-ups with an AI-powered real estate platform for smarter sales and higher conversion rates.
Section: Custom SaaS Platforms
Project Overview
LeadFlow AI is an AI-powered SaaS platform designed for Dubai real estate brokerages. It automates lead qualification, multilingual WhatsApp responses, agent assignment, and follow-up tracking. Powered by GPT-4o, Firebase, and the WhatsApp Cloud API, the platform helps brokerages manage incoming enquiries, prioritize high-intent prospects, and maintain a complete history of customer interactions.
Its subscription-based model, integrated Stripe billing, and dedicated owner and agent dashboards provide a centralized solution for managing leads and sales activities.
Business Problem
Dubai’s real estate market moves quickly, with enquiries arriving around the clock from buyers, renters, and investors across different countries and time zones. Without an automated lead management process, brokerages risk delayed responses, missed opportunities, and inconsistent follow-ups.
LeadFlow AI addresses these challenges:
Inconsistent Lead Qualification: Agents lack a standardized process for identifying high-intent prospects and prioritizing enquiries.
Delayed Responses: Manual lead handling can leave international prospects waiting for a reply, reducing opportunities to engage them at the right time.
Unmanaged WhatsApp Conversations: Messages and customer interactions lack centralized tracking, making it difficult to maintain complete communication histories.
Language Barriers: Multilingual enquiries require professional responses in languages such as Arabic, Russian, Chinese, French, and English.
Unbalanced Lead Distribution: Manual assignment can create uneven workloads and inconsistent allocation across agents.
Missed Follow-Ups: Without automated reminders, scheduled calls and subsequent interactions can easily be overlooked.
These challenges create operational inefficiencies and make it harder for brokerages to deliver timely, consistent customer experiences.
Proposed Solution
LeadFlow AI provides an end-to-end SaaS platform that automates lead qualification, customer communication, agent assignment, and follow-up management for Dubai real estate brokerages.
Using GPT-4o, the system identifies each lead’s language, intent, and temperature, then generates a professional response in the lead’s own language. Leads are assigned to agents through a fair round-robin process, while WhatsApp integration enables two-way messaging and maintains conversation history.
The platform also includes role-based dashboards for owners and agents, automated follow-up reminders, and Stripe subscription billing. Together, these features help brokerages manage enquiries more efficiently, improve response consistency, and maintain better visibility across their sales pipeline.
Project Details
Category
Details
Project Type
Product Case Study · SaaS Platform
Industry
PropTech · Real Estate · Dubai, UAE
Frontend
React (Vite) · Tailwind CSS · Vercel
Backend
Node.js · Express · Render
Database & Authentication
Firebase Firestore · Firebase Auth
AI Engine
OpenAI GPT-4o
Messaging
WhatsApp Cloud API · Meta Graph API v21.0
Payments
Stripe · AED subscriptions · 7-day free trial
End-to-End Workflow
Image: The LeadFlow AI landing page: “Never miss a hot lead again”.
Automated lead pipeline
Accepts inbound leads via a REST API endpoint that can be embedded into any website contact form, landing page, or chatbot
Validates and checks the brokerage subscription before processing: if the Basic plan’s 100-lead monthly limit is reached, the endpoint returns a clear upgrade prompt
Sends the lead through GPT-4o for classification: language detection, intent classification (buy / rent / invest / general inquiry), temperature scoring (hot/warm / cold), and AI-generated reply
Assigns the lead to an agent via atomic round-robin rotation, a Firestore transaction ensures fair distribution even under concurrent submissions
Sends the AI-generated reply directly to the lead’s WhatsApp number via the Meta Cloud API, in the same language the lead wrote in
Stores the complete lead record, AI analysis, and message thread in Firestore for full history
AI engine (GPT-4o)
System prompt defines a “premium Dubai luxury real estate” tone, professional, no emojis, no slang, concise but warm
Detects lead language automatically (ISO 639-1 codes: en, ar, ru, zh, fr, and others) and replies in that language
Classifies intent as buy, rent, invest, or inquiry based on message content
Tags lead temperature: hot (specific budget/area / timeline), warm (genuine interest, lacks specifics), or cold (general browsing)
Runs at temperature 0.4 with JSON response format enforced, consistent, structured output on every call
Falls back to a safe default reply if the AI call fails, ensuring no lead is ever left without an acknowledgement
WhatsApp integration (Meta Cloud API)
Outbound: sends AI replies and agent messages to leads via the WhatsApp Cloud API (Meta Graph API v21.0)
Inbound: receives replies from leads via a verified Meta webhook, matches the sender’s phone number to the correct lead record, and stores the message in the thread
Webhook verification uses Meta’s challenge-response flow with a custom verify token
All incoming payloads are validated via HMAC-SHA256 signature using the Meta App Secret before processing
Phone numbers are cleaned (stripped of spaces, dashes, and plus signs) before every API call
Owner dashboard
Displays total leads, hot leads count, follow-ups due today, and new leads this week
Shows agent performance table: total leads assigned vs. leads closed per agent
Lists the 10 most recent leads with full status, temperature, and intent data
The owner can reassign leads between agents directly from the dashboard
Visible only to users with the owner role: enforced server-side via requireRole middleware
Agent dashboard
Shows assigned leads, active (non-closed) leads, and follow-ups currently due
Lists the agent’s 10 most recent assigned leads
Agents can only view and interact with leads assigned to them, enforced in every route handler
Agents can send messages to leads, update lead status, and set follow-up dates
Subscription billing (Stripe)
Two plans available: Basic (AED 149/month, 100 leads) and Pro (AED 399/month, unlimited leads + analytics)
Both plans include a 7-day free trial before billing begins
Stripe Checkout handles the payment flow; Stripe Billing Portal handles plan changes and cancellations
Stripe webhooks update Firestore user records in real time on subscription activation, update, and cancellation
Agents automatically inherit their owner’s subscription status: if the owner’s plan lapses, agents lose access too
Follow-up automation
Agents set a follow-up date on any lead directly from the lead detail page
A scheduled cron job runs every day at 8:00 AM UAE time (UTC+4) via node-cron
Any lead with a follow-up date on or before today and a non-closed status is flagged followUpDue: true in Firestore
The agent dashboard surfaces these flags as a follow-up due count, creating a daily task list without manual tracking
Benefits
Instant first response at any hour: every lead gets a professional WhatsApp reply within seconds, regardless of time zone or day of the week
Replies in the lead’s language: Arabic, Russian, Chinese, French, and English buyers all receive a response in their own language without any manual effort
Fair, automatic agent assignment: round-robin distribution via Firestore transactions means no agent is overlooked and no manager needs to manually route leads
Hot leads surface immediately: buyers who mention a specific budget, area, or timeline are flagged HOT so agents know exactly who to call first
Complete conversation history: every WhatsApp message in and out is stored against the lead record, giving agents full context before they pick up the phone
No missed follow-ups: the daily cron job ensures agents see overdue leads on their dashboard each morning without any manual diary management
Subscription-gated access: brokerages pay per month; if a plan lapses, access is revoked automatically via Stripe webhook sync
Multi-tenant by design: each brokerage’s data is isolated by ownerUid; no lead or agent data is ever visible across brokerage accounts
How the Platform Works
A lead submits a form on the brokerage’s website, the form POSTs to the public /api/leads endpoint with name, email, phone, message, and ownerUid
Subscription and plan limits are checked: the server verifies the brokerage has an active or trialing Stripe subscription, and that the Basic plan lead cap has not been reached
GPT-4o processes the lead: language is detected, intent classified, temperature scored, and a professional reply generated in the lead’s own language
The lead is assigned to an agent: a Firestore transaction reads the round-robin counter, selects the next agent in the rotation, and atomically increments the counter
The lead record is written to Firestore, all fields stored: name, contact details, message, AI analysis (language, intent, temperature), assigned agent, status, and timestamps
The AI reply is sent via WhatsApp: if a phone number was provided, the generated reply is dispatched through the Meta Cloud API, and the WhatsApp message ID is stored
The API returns a success response: the caller receives the lead ID, AI reply text, intent, temperature, and assigned agent ID
The agent is notified via their dashboard: the new lead appears in their assigned leads list with full AI analysis visible
If the lead replies on WhatsApp: the message arrives at the Meta webhook, is validated, matched to the lead by phone number, and stored in the messages collection
Follow-up dates are tracked automatically: the daily cron job at 8 AM UAE time flags any lead whose follow-up date has arrived, surfacing it on the agent’s dashboard
System architecture Flow Diagram
Subscription plans
LeadFlow AI is sold as a monthly SaaS subscription in UAE Dirhams. Both plans include a 7-day free trial before the first charge. Stripe Checkout handles the payment flow; Stripe Billing Portal handles self-service plan changes and cancellations.
Plan
Price
Lead Limit
Included Features
Basic
AED 149 / month
100 leads / month
AI classification, WhatsApp auto-reply, agent assignment, follow-up tracking
Pro
AED 399 / month
Unlimited leads
Everything in Basic + analytics dashboard, agent performance tracking, priority support
The Basic plan lead limit is enforced server-side on every lead submission. When the 100-lead monthly cap is reached, the API returns an HTTP 429 response with a clear upgrade message. Pro plan subscribers have no cap.
Dashboard overview
Owner dashboard
The owner's view is the brokerage’s operational command centre. It shows four headline KPIs (total leads, hot leads, follow-ups today, new leads this week), an agent performance breakdown, and a live feed of the most recent leads. Owners can reassign any lead to a different agent directly from this view.
Role-restricted: visible only to owner accounts
Agent dashboard
The agent's view is designed for daily use. It shows the agent’s assigned lead count, active (non-closed) lead count, and follow-ups currently due, the three numbers that define their working day. Below the KPIs is a list of their most recently assigned leads.
Agents only see leads assigned to them: enforced at the API level
Lead detail page
Each lead has a dedicated detail page showing all contact information, AI classification results (language, intent, temperature), the full WhatsApp message thread, and status controls. Agents can update the lead’s status, set or clear a follow-up date, and send new messages directly from this page.
Message thread includes AI replies, agent messages, and incoming WhatsApp replies in chronological order
Pricing page
Public-facing pricing page displays both plans with feature lists and a “Start Free Trial” call-to-action. Clicking a plan triggers Stripe Checkout in AED, with the 7-day trial clearly communicated before any payment details are entered.
Currency displayed in AED; trial communicated pre-checkout
Lead classification & AI scoring
Every inbound lead is processed by GPT-4o using a structured system prompt that enforces a consistent professional tone and returns strict JSON. The model evaluates four dimensions simultaneously and returns them in a single API call.
Temperature
Score
Routing Action
Classification Criteria
HOT
High
Immediate agent assignment + WhatsApp reply
Mentions specific budget, area, or timeline. Clearly ready to act.
WARM
Medium
Assigned + follow-up date set
Shows genuine interest but lacks specifics about budget, area, or timing.
COLD
Low
Stored, lower priority nurture
General inquiry, browsing behaviour, or unclear intent.
The AI prompt explicitly defines the classification rules for each temperature band, prohibits emojis and slang, and instructs the model to respond in the detected language of the lead’s message. The system prompt is fixed (not user-editable) to ensure brand consistency across all brokerages.
Project evolution & key milestones
The platform scope expanded significantly from an initial lead capture proof-of-concept. Key additions and refinements delivered across the build:
AI & classification
GPT-4 integration upgraded to GPT-4o for higher accuracy and lower latency
Temperature set to 0.4 after testing: lower values produced overly rigid replies; higher values produced inconsistent classification
Fallback reply added, so no lead is ever unanswered if the OpenAI API is unavailable
Intent classification expanded from buy/rent to include invest and inquiry as distinct categories
WhatsApp integration
Initial outbound-only integration expanded to support two-way messaging via the Meta webhook
Incoming message matching logic added: sender phone matched to the most recent lead record in Firestore
HMAC-SHA256 signature validation added using the Meta App Secret for all incoming webhook payloads
Phone number cleaning function added to handle +, spaces, and dashes from various form inputs
Agent assignment
Initial random assignment replaced with deterministic round-robin using a Firestore atomic counter transaction
Counter document stored per brokerage (assignment_{ownerUid}) to ensure correct rotation per team
Graceful fallback: if no agents exist, the lead is stored unassigned rather than failing
Subscription billing
Stripe integration added with two recurring AED products (Basic and Pro)
7-day free trial added to subscription_data at checkout session creation
Stripe webhook handler added for checkout.session.completed, customer.subscription.updated, and customer.subscription.deleted events
Subscription status synced to Firestore user record in real time on every Stripe event
Basic plan 100-lead monthly cap enforced server-side via Firestore count() query
Stripe Billing Portal endpoint added for self-service plan management
Security & access control
Firebase Auth middleware added to all protected routes; public lead capture endpoint intentionally left unprotected
requireSubscription middleware added to check subscription status for both owners and agents (agents inherit from the owner)
requireRole middleware added for owner-only routes (owner dashboard, agent management)
Raw body preservation implemented for Stripe and WhatsApp webhook routes (bypassing Express JSON parsing)
Follow-up system
followUpDate field added to lead schema; agents can set it from the lead detail page
Daily cron job added via node-cron: runs at 8:00 AM UAE time (UTC+4 = 04:00 UTC)
Batch Firestore update sets followUpDue: true on all leads whose date has arrived, for efficient dashboard display
Data flow architecture
A reference overview of how data moves through each stage of the system and at what cadence:
Stage
Source
Destination
Trigger / Cadence
Lead intake
Website form / API call
Express backend
On submission (real-time)
AI processing
OpenAI GPT-4o
Firestore lead record
Per lead, synchronous
Agent assignment
Firestore counters (round-robin)
Lead record (assignedAgentId)
Per lead, synchronous
WhatsApp reply
AI-generated reply text
Lead's phone (Meta API)
Per lead, async
Follow-up check
Firestore leads collection
followUpDue flag on each lead
Daily at 8:00 AM UAE time
Dashboard refresh
Firestore (Realtime queries)
Owner / Agent dashboard
On page load / request
Subscription sync
Stripe webhook events
Firestore user record
On Stripe event (real-time)
Note
Firestore is the single source of truth for all lead records, message threads, user profiles, subscription status, and round-robin counters. The Firebase Admin SDK (backend) and Firebase Web SDK (frontend) both read from the same Firestore project, with security rules and server-side middleware providing access control.
API reference
All endpoints are prefixed with /api/. Protected routes require a Firebase ID token in the Authorization: Bearer <token> header. The lead capture endpoint (/api/leads POST) is intentionally public to allow embedding on any brokerage website without authentication.
Method
Endpoint
Description
POST
/api/leads
Public lead capture: no auth required. Runs AI, assigns agent, sends WhatsApp.
GET
/api/leads
List leads (owners see all, agents see assigned only). Filterable by status, temperature, intent.
GET
/api/leads/:id
Single lead detail with access control (role-based).
PATCH
/api/leads/:id
Update lead status, follow-up date, or agent assignment.
GET
/api/leads/:id/messages
Retrieve full message thread for a lead.
POST
/api/leads/:id/messages
Agent sends a message, delivered via WhatsApp if phone is available.
GET
/api/dashboard/owner
Owner dashboard: total leads, hot leads, follow-ups today, agent performance.
GET
/api/dashboard/agent
Agent dashboard: assigned leads, active leads, follow-ups due.
POST
/api/stripe/create-checkout
Create Stripe Checkout session (Basic or Pro plan, AED, 7-day trial).
POST
/api/stripe/portal
Create Stripe Billing Portal session for plan management.
Meta webhook verification challenge (subscribe mode).
POST
/api/whatsapp/webhook
Receive incoming WhatsApp messages, match to lead by phone, store in messages collection.
GET
/api/health
Health check: returns server status and timestamp.
Security
LeadFlow AI is built with multi-tenant security as a first-class requirement. Each security layer is implemented independently so that no single point of failure exposes brokerage data.
Security Layer
Implementation
Firebase ID Token Auth
All protected routes verify Bearer token via Firebase Admin SDK. Invalid or expired tokens return 401.
Subscription Gate
Middleware checks owner subscription status (active / trialing) before allowing access. Agents inherit their owner’s subscription.
Role-Based Access Control
requireRole(‘owner’ | ‘agent’) middleware enforces role boundaries. Agents can only access their assigned leads.
WhatsApp Signature Validation
Incoming Meta webhooks validated via HMAC-SHA256 using App Secret. Invalid signatures return 401.
Stripe Webhook Verification
Stripe events verified using stripe.webhooks.constructEvent with the webhook signing secret.
Helmet HTTP Headers
Sets security headers (XSS, clickjacking, content-type sniffing) via the Helmet middleware.
CORS Restriction
Requests accepted only from the configured FRONTEND_URL. Credentials are required for authenticated calls.
Plan Limit Enforcement
Basic plan lead cap (100/month) enforced server-side via Firestore count query on every lead submission.
Image: The pricing page: a Basic plan at AED 149 per month and a Pro plan at AED 399 per month, both with a 7-day free trial.
Image: The live demo: a sample enquiry is classified by GPT-4o as a HOT lead, with intent, urgency, language and an AI-generated WhatsApp reply.
Closing Remarks
LeadFlow AI streamlines real estate lead management through AI-powered qualification, multilingual WhatsApp communication, automated assignment, and follow-ups helping brokerages improve efficiency and manage prospects more effectively.