# AI Agents

> General-purpose AI agents you can point at almost any repetitive task to take it off your plate.

Page: https://mburhan.com/tag/ai-agents

21 case studies in full below.

# Meta Ads Agent

> 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

Page: https://mburhan.com/case/meta-ads-agent

## 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

1. 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.
2. It pulls the same days' orders and revenue from Shopify.
3. It saves both in a database.
4. It compares the revenue Meta claims with the orders Shopify recorded, and flags any day where Meta claims more.
5. 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.
6. Claude writes the briefing in plain English from those calculated numbers. Claude doesn't do the math.
7. It posts a short digest in Slack with a link to the full report page.
8. Every hour it checks the alert limits and messages Slack only when one is crossed.
9. Suggested changes, such as pausing an ad set or changing a budget, wait for a person to approve them.
10. 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.

Image (https://mburhan.com/uploads/4955fdd17e877c23aac67a73.png)

Image (https://mburhan.com/uploads/342f8fae14427292eaddbdd2.png)

## 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.

---

# 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

Page: https://mburhan.com/case/ai-voice-agents-for-lead-qualification-and-customer-support

### 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

1. **Capture New Leads:** When a prospect submits a Meta lead form, the n8n workflow receives the lead information and initiates the automated calling process.
2. **Immediate AI Follow-Up:** Hazel, the AI lead qualification agent, contacts the prospect within approximately 5–10 seconds of form submission.
3. **Qualify Prospects:** Hazel asks predefined qualifying questions, gathers project requirements, and captures relevant lead details using configured conditions and conversation instructions.
4. **Apply Conversation Guardrails:** Hazel avoids making pricing commitments, disclosing sensitive business information, or making decisions reserved for human representatives.
5. **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.
6. **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.
7. **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.
8. **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.
9. **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.
10. **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.

Image (https://mburhan.com/uploads/603431b326c2139e55ed68ae.png)

Image (https://mburhan.com/uploads/3fc3d0795b8280cf94b50fd6.png)

### 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.

Image (https://mburhan.com/uploads/d92bdba2e07881bca1b0f800.png)

Image (https://mburhan.com/uploads/954f69f4c7d98847fb97196f.png)

### 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.

---

# 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

Page: https://mburhan.com/case/ai-calling-agent-with-human-handover-and-automatic-ai-fallba

### 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

1. **Receive Incoming Call:** The caller dials the designated Twilio phone number, which routes the call through the inbound Twilio Function.
2. **Connect to ElevenLabs:** The inbound function registers the call with ElevenLabs and connects the caller to the AI voice agent.
3. **Handle the Conversation:** The ElevenLabs agent communicates with the caller and handles their request.
4. **Request Human Assistance:** When the caller asks for a human representative, the AI agent invokes the `connect_to_human` webhook tool.
5. **Transfer the Call:** The `/connect-human` Twilio Function initiates the transfer to the designated human phone number.
6. **Handle the Human Answer:** If the human answers, Twilio connects the caller and the human representative.
7. **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.
8. **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.

Image (https://mburhan.com/uploads/54c4edf24cc09e24e6f5d6c5.png)

Image (https://mburhan.com/uploads/649c9f4df797f16d441a7ccb.png)

### 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.

---

# 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

Page: https://mburhan.com/case/loanpro-mcp-server-ai-powered-financial-data-access-account

## 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

1. **Submit a Request:** A user asks Claude to find a customer or review a loan account.
2. **Connect Through MCP:** The AI client connects to the Go-based MCP server using SSE or stdio.
3. **Select a Tool:** The assistant selects an available tool, such as `search_customers`, and provides the required arguments.
4. **Process the Request:** The server prepares the corresponding LoanPro API operation.
5. **Retrieve Financial Data:** The server requests customer, loan, transaction, or balance information from LoanPro.
6. **Normalize the Response:** Go processes the returned JSON data and handles inconsistent identifier formats.
7. **Apply Review Logic:** Available tools and predefined prompts support customer reviews and past-due account filtering.
8. **Return Results:** The processed information is sent back to the AI assistant for a readable response or account summary.

## Architecture flow:

Image (https://mburhan.com/uploads/a0b0ea99371c2cde593c349e.png)

## 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.

---

# 2–3 weeks 24–48 hours

> CASE STUDY · SUPPLEMENT CONTRACT MANUFACTURING

Section: Custom SaaS Platforms, n8n Automations, AI Agents

Page: https://mburhan.com/case/2-3-weeks-24-48-hours

## 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.

Image (https://mburhan.com/uploads/6d9e3e89f2c79f059650057f.png)

Image (https://mburhan.com/uploads/dda4e3d4449b50f7993fc9e7.png)

Image (https://mburhan.com/uploads/a4997711fd0353c56ef08e41.png)

## 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.

### 1.3 Manufacturing Calculations Required Specialized Knowledge

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.

Image (https://mburhan.com/uploads/8a0d4fc58f41b6a6bd1809b0.png)

**Public-facing path:**

Image (https://mburhan.com/uploads/ddfdca6bdfb580ab0ac80981.png)

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

---

# HubSpot Industry Classifier with Gemini

> 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

Page: https://mburhan.com/case/hubspot-industry-classifier

## 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

1. **Scheduled Execution:** n8n starts the workflow every hour and loads its configuration, including the company limit, confidence threshold, and dry-run setting.
2. **Retrieve Company Records:** The workflow retrieves companies from a designated HubSpot list, collecting up to 100 records per run.
3. **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.
4. **AI Classification:** Google Gemini Flash analyzes the available company information and returns a suggested industry group, confidence score, exclusion flag, and reasoning.
5. **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.
6. **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.
7. **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.

Image (https://mburhan.com/uploads/480b3d2db06d67347fe2909b.png)

## 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.

---

# 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

Page: https://mburhan.com/case/ai-agent-ai-driven-instagram-video-breakdown-decode

## 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

1. **Retrieve Creators:** Read Instagram usernames from Airtable.
2. **Find the Top Reel:** Identify the most-viewed available Reel for each creator.
3. **Collect Video Details:** Capture the video link, caption, creator name, and view count.
4. **Download the Video:** Prepare the selected Reel for closer analysis.
5. **Analyze with AI:** Examine the hook, mood, visual style, and standout moments.
6. **Save the Insights:** Write the structured analysis back to Airtable.

### Demo:

Image (https://mburhan.com/uploads/c1fe909c3a5b3cf6087028c3.png)

## 05. Workflow

Image (https://mburhan.com/uploads/ab91f3f7eb9d34ce8ec55437.png)

## 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.

---

# 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

Page: https://mburhan.com/case/ai-agent-smart-amazon-product-tracker-for-price

## 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 (https://mburhan.com/uploads/6e5bf03831c9f80f652fcd4d.png)

### 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

Image (https://mburhan.com/uploads/34776ded6979a375ecf4f70d.png)

## 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.

---

# YouTube Video Details Scraper using Automation

> Automatically collect detailed info from YouTube videos of popular creators for content analysis.

Section: AI Agents

Page: https://mburhan.com/case/ai-agent-youtube-video-details-scraper-using-automation

## 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 (https://mburhan.com/uploads/31ccb47cc09a7ace921ec94b.png)

**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

Image (https://mburhan.com/uploads/31a18bce5be3170d1de9486d.png)

## 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.

---

# 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

Page: https://mburhan.com/case/ai-agent-smart-ai-podcast-audio-script-generator

## 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.

Image (https://mburhan.com/uploads/98292e044d35a7af1a07611c.png)

## 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.

Image (https://mburhan.com/uploads/db21ab2b6330b297e72e53d6.png)

**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

Image (https://mburhan.com/uploads/7e25cc964dce63602afa4fb2.png)

## 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.

Image (https://mburhan.com/case-content/ai-agents-general/image6.png)

---

# 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

Page: https://mburhan.com/case/ai-agent-tiktok-video-downloader-without-watermark-save

## 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 (https://mburhan.com/case-content/ai-agents-general/image8.png)

1. **Manual Trigger:** Start the workflow with a single click.
2. **Fetch Video Page:** Retrieve the TikTok page information.
3. **Extract Video URL:** Process the page data to identify the direct video link.
4. **Download Video:** Use the extracted URL to download the video file.
5. **Upload to Google Drive:** Store the downloaded video in Drive.
6. **Generate Shareable Link:** Configure the uploaded file for public access and create a link for sharing.

## 5. Workflow

Image (https://mburhan.com/uploads/ccf42729421b61f46c133916.png)

## 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.

---

# 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

Page: https://mburhan.com/case/ai-agent-ai-powered-social-post-generator-from

## 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 (https://mburhan.com/uploads/5b2d8ac3cc502d09241ff352.png)

1. **Manual Trigger:** The user starts the workflow with a click.
2. **Read Google Sheets:** Retrieve content ideas and their target platforms.
3. **Check Publishing Status:** Select ideas marked `0`, indicating they have not yet been published.
4. **Generate Social Content:** Google Gemini creates a concise, fact-based post with suitable emojis.
5. **Route by Platform:** Conditional branches determine whether the post should go to LinkedIn or X.
6. **Publish the Post:** The appropriate platform integration handles publishing.

## 5. Workflow

Image (https://mburhan.com/uploads/a530fcedf6976bf8f8966cb1.png)

## 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.

---

# 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

Page: https://mburhan.com/case/ai-agent-ai-powered-rag-chatbot-for-the

## 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:

Image (https://mburhan.com/uploads/386b7f32c8023c2c5ab5be3b.png)

### DEMO

Image (https://mburhan.com/uploads/53b8c0b89a1a78cd62680c19.png)

## 04. Workflow

Image: Simple analogy (https://mburhan.com/uploads/3b9620d4c2cf89c27269bc9a.png)

## 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.

---

# AI-Powered Customer Support Agent

> 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

Page: https://mburhan.com/case/ecom-agent-ai-powered-customer-support-agent

## 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 (https://mburhan.com/uploads/ea8f2285191974e7ff3ecd4e.png)

## 04. Complete System Workflow

### Main ticket-processing workflow

Image (https://mburhan.com/uploads/d2b51cc5582ad209e8ecb1eb.png)

### Knowledge retrieval workflow

Image (https://mburhan.com/uploads/38aee9c7fd012053a0d73dd7.png)

### Exception-handling workflow

Image (https://mburhan.com/uploads/2e6d98fd91c9c564261310d6.png)

### Knowledge maintenance workflow

Image (https://mburhan.com/uploads/de3cde2be472cff80fbde5a7.png)

## 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.

---

# AI-Powered Fashion Campaign Image Generation

> 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

Page: https://mburhan.com/case/ecom-agent-ai-powered-fashion-campaign-image-generation

## 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

1. A form trigger receives the uploaded clothing image.
2. The image is converted to Base64 for API processing.
3. Workflow logic analyzes the garment and develops a creative prompt, including the intended model persona.
4. An AI image generation API using Google Gemini creates the fashion model image.
5. The generated model image is uploaded to Google Drive.

### Phase 2: Prompt Generation and Campaign Image Creation

1. The original clothing image and generated model image are used as visual references.
2. The workflow creates prompts for eCommerce studio shots and lifestyle scenes.
3. AI image generation APIs produce the corresponding campaign visuals.
4. Generation results are checked for success.
5. Final images are uploaded to Google Drive.

## 05. Real-World Impact

- **Reduced Manual Prompting:** Creative direction and prompt generation are handled by the workflow.
- **Consistent Brand Visuals:** Products receive standardized eCommerce images and lifestyle scenes.
- **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

Image (https://mburhan.com/uploads/c86605bdf56b2ff7ed9b1e78.png)

- **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 (https://mburhan.com/uploads/43b28f623e6950ffc1b3440e.png)

## 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-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

Page: https://mburhan.com/case/ecom-agent-ai-powered-24-7-voice-support

## 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.

It:

- Provides natural, conversational voice responses 24/7.
- 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

1. A customer calls the support number.
2. VAPI answers with a configured greeting and voice.
3. The customer's speech is converted into text.
4. 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

Image (https://mburhan.com/uploads/441b8a39a9086aab67b8de19.png)

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

1. Open `ShopTalk AI – Call Summary & Lead Capture (1).json`.
2. Import the workflow into n8n.
3. Connect the VAPI webhook to the workflow.
4. Configure Slack and select the appropriate summary channel.
5. 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.

---

# AI-Powered Social Media Content Creation

> 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

Page: https://mburhan.com/case/ecom-agent-ai-powered-social-media-content-creation

## 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

Image (https://mburhan.com/uploads/78d804c57345629f032a041a.png)

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

1. Open the attached `Social Media Automation Workflow.json` file.
2. Copy the complete JSON content.
3. Open your n8n cloud or self-hosted instance.
4. Create a new workflow and paste or import the JSON.
5. 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.

---

# AI-Powered E-Commerce Product Price Monitoring

> 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

Page: https://mburhan.com/case/ecom-agent-ai-powered-e-commerce-product-price

## 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.

**Technologies:** n8n · Google Sheets · Slack · OpenAI · Gemini

## 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.
- **Reduced Notification Noise:** Users receive fewer unnecessary alerts.
- **Time Savings:** Approximately 20–25 hours saved per user each month.

## 06. Workflow Architecture

The automation follows this sequence:

Image (https://mburhan.com/uploads/82dcb7ad69950c413abf79b1.png)

Each component has a specific role:

- **Scheduler:** Starts the workflow at configured intervals.
- **Price Collection:** Retrieves product details and current prices.
- **Price Comparison:** Identifies differences between current and previous records.
- **Google Sheets:** Stores historical price data.
- **AI Analysis:** Evaluates price trends and potential opportunities.
- **Smart Notification:** Sends alerts when configured conditions are met.

## 07. How to Replicate the System

### Step 1: Import the Workflow

1. Open the attached `E-Commerce Price Monitoring Automation.json` file.
2. Copy its complete JSON content.
3. Open your n8n cloud or self-hosted instance.
4. Create a new workflow and import or paste the JSON.
5. Rename the workflow to **E-Commerce Price Monitoring Automation**.

### Step 2: Configure Connections

- **Scheduler:** Set the monitoring frequency.
- **HTTP or scraping nodes:** Configure product URLs and test price extraction.
- **Google Sheets:** Connect your account and map the Product, Price, Date, and Comparison Result columns.
- **AI analysis:** Configure OpenAI or Gemini credentials.
- **Notifications:** Connect Slack or email and configure alert messages.

### Step 3: Test the Workflow

Run the workflow manually and verify that:

- Product data is collected correctly.
- Price history is recorded in Google Sheets.
- AI analysis evaluates the collected data.
- Notifications are sent when the configured conditions are met.
- No alert is sent when prices remain unchanged and no other alert condition is triggered.

### Step 4: Activate the Automation

Once testing is complete, activate the workflow and confirm the schedule is configured correctly.

The system will then monitor product prices, maintain historical records, analyze changes, and send alerts according to the configured rules.

Image (https://mburhan.com/uploads/9a25b5d40f6ecf6f18d7c089.png)

## 08. Final Outcome

The AI-powered price monitoring workflow transforms repetitive, manual price checking into an automated and data-driven process.

Users can monitor multiple products, review historical prices, identify potential savings, and receive meaningful alerts without continuously checking online stores.

**The result:** Less manual work, better price visibility, and more informed purchasing decisions.

---

# AI-Powered Meta Ads Reporting

> 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

Page: https://mburhan.com/case/ecom-agent-ai-powered-meta-ads-reporting

## 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.
- **Creative Insights:** Recommend potential creative improvements.
- **Audience Optimization:** Suggest targeting adjustments.
- **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

Image (https://mburhan.com/uploads/15afd1c7a2bbc01c0ed294e7.png)

## 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.

---

# AI-Powered Shopify Abandoned Cart Recovery System

> 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

Page: https://mburhan.com/case/ecom-agent-ai-powered-shopify-abandoned-cart-recovery

## 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.

1. **Abandoned Checkout Detection:** Shopify provides abandoned checkout data.
2. **Wait and Verify:** The automation waits and checks whether the checkout remains abandoned.
3. **AI Email Generation:** OpenAI generates a friendly, personalized recovery message.
4. **Email Delivery:** Gmail or the configured email service sends the message to the customer.
5. **Scheduled Execution:** The workflow runs automatically according to its configured schedule.

## Workflow:

Image (https://mburhan.com/uploads/b7ebb79125925b2fb319880b.png)

No routine manual follow-up is required once the workflow is configured and activated.

## 05. Business Value

### Recover Potential Revenue

Re-engages customers who leave products in their carts and creates another opportunity to complete a purchase.

### Reduce Manual Work

Eliminates repetitive checkout monitoring and email-writing tasks.

### Improve Customer Experience

Delivers timely reminders with more relevant, personalized messaging.

### Ensure Consistent Follow-Ups

Provides a recovery attempt for every detected abandoned checkout that meets the workflow conditions.

### Scale With Store Growth

Handles increasing checkout volumes without requiring a proportional increase in manual effort.

## 06. How to Replicate the System

Use the provided workflow blueprint to configure the automation in Make.com.

### Step 1: Import the Blueprint

1. Open the attached JSON file: **Shopify Abandoned Checkout Recovery with Order Verification (1).json**.
2. Select and copy the complete JSON content.
3. Log in to Make.com and open **Scenarios**.
4. Create a new scenario and choose the blueprint import option.
5. Import the JSON, save the scenario, and name it **Shopify Abandoned Checkout Recovery with Order Verification**.

### Step 2: Configure Shopify

- Connect your Shopify account.
- Confirm that the workflow retrieves abandoned checkouts.
- Verify that the checkout status and required customer fields are mapped correctly.

### Step 3: Configure the Wait and Verification Logic

- Review the delay before sending the recovery email.
- Verify that the checkout has not been completed.
- Prevent duplicate or unnecessary recovery emails.

### Step 4: Configure OpenAI

- Add your OpenAI API key.
- Confirm that the AI generates a relevant, friendly recovery email.
- Check that the email body follows your desired format and tone.

### Step 5: Configure Email Delivery

- Reconnect Gmail or your SMTP email service.
- Map the customer's email address dynamically.
- Set the email subject to **You left something behind**.
- Verify the recipient, subject, and generated email body.

### Step 6: Test and Activate

1. Run the scenario once.
2. Verify that abandoned checkout data is retrieved.
3. Confirm that the checkout verification works.
4. Check that the AI-generated email is correct.
5. Confirm that the recovery email is delivered successfully.
6. Activate the scenario and configure an appropriate schedule, such as every 15–60 minutes.

**Important:** The actual schedule, delay, and verification rules should match your store's requirements and the imported workflow configuration.

## 07. Final Outcome

The AI-Powered Shopify Abandoned Cart Recovery System transforms abandoned checkouts into automated follow-up opportunities.

By combining Shopify checkout data, workflow automation, AI-generated emails, and automated delivery, the system helps businesses:

- Follow up consistently with abandoned carts.
- Reduce repetitive manual work.
- Deliver timely, personalized reminders.
- Create additional opportunities to recover lost sales.
- Scale their recovery process as the business grows.

**The result:** A reliable, always-on abandoned cart recovery workflow that supports revenue recovery without increasing routine workload.

---

# AI-Powered Whatsapp message Assistant

> 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

Page: https://mburhan.com/case/ecom-agent-ai-powered-whatsapp-message-assistant

## 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

1. **Customer Message:** Customers contact the business through WhatsApp.
2. **Message Understanding:** AI identifies the message type and intent.
3. **Knowledge Retrieval:** Relevant business information is retrieved using semantic search.
4. **Response Generation:** AI generates a context-aware answer based on the available information.
5. **WhatsApp Reply:** The response is delivered automatically to the customer.

The workflow processes messages automatically within seconds.

Image (https://mburhan.com/uploads/2b82f4098943c7849229055c.png)

---

## 06. Business Value

- **Reduced Manual Workload:** Automates repetitive customer support tasks.
- **Faster Responses:** Helps customers receive timely answers.
- **Consistent Communication:** Maintains more uniform, policy-aligned responses.
- **Multilingual Support:** Handles conversations in different languages.
- **24/7 Availability:** Supports customers beyond regular business hours.
- **Seamless Experience:** Customers continue using WhatsApp as usual.

---

## 07. Reliability and Safety

- **Business-Grounded Answers:** Uses available business knowledge to guide responses.
- **Graceful Fallbacks:** Handles unclear information without relying on unsupported answers.
- **Data Boundaries:** Does not process payments or sensitive data.
- **Human Escalation:** Complex cases can be directed to human agents when escalation is configured.

These measures help maintain reliable, consistent, and responsible customer support.

---

## 08. How to Replicate the System

The solution uses the **WhatsApp Cloud API, n8n, OpenAI, and Supabase Vector Store**.

### Step 1: Set Up WhatsApp Cloud API

Configure the WhatsApp Business account, phone number ID, and webhook events for incoming messages.

Ensure the integration supports receiving text, voice, and image messages and sending text or audio replies.

### Step 2: Create the WhatsApp Webhook in n8n

- Create a Webhook Trigger node in n8n.
- Copy the generated webhook URL.
- Add the URL to the Meta WhatsApp Webhooks configuration.

This connects incoming WhatsApp messages to the automation workflow.

### Step 3: Import the n8n Workflow

Create a new workflow in n8n and import the provided file:

`AI-Powered WhatsApp Assistant.json`

### Step 4: Connect AI and Data Services

**OpenAI**

- Add the OpenAI API key.
- Configure the chat model, audio transcription, image analysis, and text-to-speech capabilities.

**Supabase Vector Store**

- Add the Supabase project URL and API key.
- Verify that the vector table contains products, FAQs, policies, and business information.

This enables retrieval-augmented generation (RAG) for business-grounded responses.

### Step 5: Configure Message Routing

Open the Switch node and verify the routing rules:

- **Text:** Text message → AI Agent
- **Voice:** Voice message → Transcription → AI Agent
- **Image:** Image message → Image Analysis → AI Agent

This separates message-processing paths according to the input type.

### Step 6: Test the Workflow

Send test messages through WhatsApp, including:

- A text question, such as a product inquiry.
- A voice message.
- An image, such as a product photo.

Verify correct intent detection, relevant answers from business knowledge, successful WhatsApp replies, and voice responses when triggered.

### Step 7: Activate the Workflow

Switch the n8n workflow to **Active** after testing and validating the integrations.

The assistant can then respond to customer messages automatically through WhatsApp.

---

## 09. Final Outcome

With the WhatsApp AI Business Assistant deployed:

- Customer support became faster and more reliable.
- Staff could focus on higher-value conversations.
- Customers received timely, relevant assistance.
- Support could scale with business growth without proportionally increasing manual workload.

The system transformed WhatsApp from a manual support burden into an always-on, AI-powered customer assistant.
