Transform support tickets into AI documentation with GPT-4, PDFs and Google Drive

Name: Transform support tickets into AI documentation with GPT-4, PDFs and Google Drive
Availability: InStock
Author: Jitesh Dugar

Transform support tickets into AI documentation with GPT-4, PDFs and Google Drive preview

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Important notice

This workflow is provided as-is. Please review and test before using in production.

Overview

Customer Support Ticket Documentation Automation

Automatically transform resolved support tickets into professional, AI-powered PDF documentation with complete tracking and team notifications.

Overview

This workflow automates the entire process of documenting resolved support tickets — from receiving ticket data to generating professional PDF case studies, storing them in Google Drive, tracking in spreadsheets, and notifying your team.

Powered by AI, it creates consistent, high-quality documentation that can be reused for knowledge base articles, training materials, and compliance records.

What This Workflow Does

Receives resolved support tickets via webhook from your support platform
Extracts and normalizes ticket data (works with Zendesk, Freshdesk, and custom formats)
Generates AI-powered summaries using OpenAI GPT-4, creating structured case studies with:
- Problem description
- Troubleshooting steps taken
- Final resolution
- Key takeaways and prevention tips
Creates professional PDF documents with branded HTML templates
Uploads PDFs to organized Google Drive folders
Tracks all tickets in a Google Sheets database for reporting and analytics
Sends Slack notifications to your team with links to completed documentation
Handles errors gracefully with automatic alerts when issues occur

Key Features

Fully Automated: Zero manual intervention after setup
AI-Powered Documentation: Intelligent summaries that extract insights from raw ticket data
Professional Output: Branded, print-ready PDFs with modern styling
Multi-Platform Support: Works with any support tool that can send webhooks
Centralized Tracking: All tickets logged in Google Sheets for easy reporting
Error Handling: Built-in failure detection with Slack alerts
Customizable: Easy to brand with your company colors, logo, and styling
Scalable: Handles hundreds of tickets per day

Use Cases

Knowledge Base Building: Automatically create searchable documentation from real support cases
Team Training: Build a library of resolved issues for onboarding new support agents
Compliance & Audit: Maintain complete records of all customer interactions
Performance Analytics: Track resolution times, common issues, and agent performance
Customer Success: Share professional case studies with stakeholders
Process Improvement: Identify recurring issues and optimize workflows

Prerequisites

Required Services & Accounts

n8n (self-hosted or cloud)
OpenAI Account with API access
PDFMunk Account (for HTML → PDF conversion)
Google Workspace (for Drive & Sheets)
Slack Workspace (optional but recommended)
Support Platform that can send webhooks (Zendesk, Freshdesk, Intercom, etc.)

Required Credentials

OpenAI API Key
PDFMunk API Key
Google Drive OAuth2 credentials
Google Sheets OAuth2 credentials
Slack Bot Token (OAuth2)

Setup Instructions

1. Import the Workflow

Copy the workflow JSON.
In n8n, click “Import from File” or “Import from Clipboard.”
Paste and import.

2. Configure Credentials

OpenAI API

Get API key from OpenAI
Add in n8n: Credentials → OpenAI API → Paste key

PDFMunk API

Sign up at pdfmunk.com
Copy API key → Add in Credentials → HtmlcsstopdfApi

Google Drive OAuth2

Create project at Google Cloud Console
Enable Drive API
Create OAuth 2.0 credentials
Add in n8n: Credentials → Google Drive OAuth2 → Connect

Google Sheets OAuth2

Enable Google Sheets API in the same project
Add in n8n: Credentials → Google Sheets OAuth2 → Connect

Slack OAuth2

Create app at Slack API
Add scopes: chat:write, chat:write.public
Install to workspace
Add bot token in Credentials → Slack OAuth2 API

3. Configure Node Settings

Google Drive Folder ID

Create a folder in Drive for PDFs
Copy folder ID from the URL → https://drive.google.com/drive/folders/FOLDER_ID_HERE
Paste in the “Upload to Google Drive” node

Google Sheets Configuration

Create a new sheet titled “Support Ticket Documentation Log.”
Add these headers in Row 1:

Ticket ID	Subject	Customer Name	Customer Email	Agent Name	Priority	Category	Resolved Date	Resolution Time	PDF Link	Document Generated	Status

Copy Sheet ID from URL → https://docs.google.com/spreadsheets/d/SHEET_ID_HERE/edit
Paste it in the “Update Google Sheets” node configuration.

Slack Channel ID

Right-click your Slack channel → View Channel Details
Copy the Channel ID
Update it in:
- “Send Slack Notification” node
- “Error – PDF Failed” node
- “Error – Upload Failed” node

4. Configure Webhook in Support Tool

Activate the workflow in n8n
Copy the Webhook URL from the “Webhook – Receive Ticket” node
In Zendesk/Freshdesk:
- Trigger: “Ticket Status = Resolved”
- Method: POST
- Paste the n8n webhook URL
- Send ticket data as JSON

5. Test the Workflow

Click “Execute Workflow” manually
Send a test webhook
Verify each step completes successfully
Check:
- Generated PDF in Google Drive
- Row entry in Google Sheets
- Slack notification delivery

How It Works

Webhook Trigger → Receives resolved ticket
Data Extraction → Normalizes ticket fields
AI Summarization (OpenAI) → Generates structured summary
HTML Formatting → Styles and adds branding
PDF Conversion (PDFMunk) → Converts HTML → PDF
Google Drive Upload → Saves and returns shareable link
Sheets Logging → Appends ticket info + PDF link
Slack Notification → Notifies team with summary
Error Handling → Detects and reports failures
Result → Clean, documented ticket case study in minutes

Customization

Branding

Update company name, logo URL, and color scheme in the “Format HTML” node.
Default color: #4CAF50 → Replace with your brand color.

AI Prompt Customization

Modify “AI Summarization (OpenAI)” node to add:
- Industry-specific terms
- Additional sections or insights
- Different summary tone or length

Notification Customization

Add @mentions or emojis in Slack messages for better visibility.

Data Flow

Webhook → Extract Data → AI Summary → Format HTML → Convert to PDF  
       ↓  
Download PDF → Upload to Drive → Log in Sheets → Notify Team  
       ↓  
Error Handling (if any)

Expected Output

PDF Document Includes:

Branded header with company name/logo
Resolution time badge
Ticket metadata (ID, priority, customer, agent, etc.)
Full AI-generated case study
Professional footer with timestamp

Google Sheets Entry:

All ticket info
Resolution metrics
Direct PDF link
Status = “Generated”

Slack Notification:

Summary of ticket
Clickable PDF link
Timestamp

Performance

Processing Time: 10–20 seconds/ticket
Capacity: 100+ tickets/day
PDF Size: 50–300 KB

Troubleshooting

Webhook not triggering → Check webhook URL, trigger conditions, and public access. PDF generation fails → Verify HTML syntax and PDFMunk API key. Google Drive upload fails → Re-authenticate credentials or check folder permissions. Slack notification missing → Ensure bot token, scopes, and channel ID are valid. Data extraction errors → Adjust field mappings or inspect payload format.

Best Practices

Test before production rollout
Monitor first-week error logs
Organize Drive by date/priority
Validate Sheets columns
Use a dedicated Slack channel
Archive old PDFs regularly
Review AI summaries weekly
Document configuration changes

Security Notes

All credentials stored securely in n8n
PDF links are restricted by Drive sharing settings
Webhooks use HTTPS for secure data transfer
No sensitive info logged in error messages

Future Enhancements

Multi-language summaries
Integration with Confluence or Notion
Customer satisfaction feedback link
ML-based issue categorization
Analytics dashboard
Weekly email digests
Public knowledge base generation

Support Resources

License

This workflow template is provided as-is for use with n8n under the MIT License.

Jitesh Dugar

119 workflows

Nodes

n8n-nodes-base.webhook n8n-nodes-base.stickynote n8n-nodes-base.code @n8n/n8n-nodes-langchain.openai n8n-nodes-base.if n8n-nodes-base.googledrive n8n-nodes-base.set n8n-nodes-base.googlesheets

Complexity

advanced

Published 04 Oct 2025

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/9260/9260.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Compare physical vs digital 24K gold costs and returns with GoldAPI, IBJA, Groq and Google Sheets

# Gold Investment Intelligence: Physical vs. Digital 24K Cost & Return Analysis This high-performance n8n workflow automates the complex task of comparing gold investment types in the Indian market. By pulling live data from the **GoldAPI** (Digital) and the **IBJA** (Physical benchmark), it calculates the "Landed Cost" including GST and making charges to provide a data-driven "Buy/Wait" verdict powered by a **Groq-hosted LLM**. Stop manually calculating gold spreads across different platforms. This workflow fetches real-time 24K gold rates, applies localized taxes (3% GST) and industry-standard fees (3-8%), analyzes global market sentiment via Yahoo Finance RSS and logs a professional investment report to Google Sheets. It transforms raw data into an actionable "Efficiency Score" using AI. ### Quick Implementation Steps: 1. **Import** the JSON file into your n8n canvas. 2. **Get API Key:** Sign up at GoldAPI.io and paste your token into the "Get Digital Price" header. 3. **Connect AI:** Add your Groq API credentials to the "Groq Chat Model" node. 4. **Prepare Sheet:** Create a Google Sheet with these headers: `Date`, `Digital_Price`, `Physical_Price`, `Arbitrage`, `Sentiment` and `Efficiency_Score`. 5. **Authorize:** Link your Google account in the "Add Report" node and select your spreadsheet. ## What It Does This workflow acts as a 24/7 Quantitative Financial Analyst specialized in the gold market. It eliminates the "hidden cost" surprise by calculating the absolute final price an investor pays out-of-pocket for 1 gram of 24K gold. It doesn't just look at the ticker price; it factors in the 3% GST applicable in India, platform spreads for digital gold apps and making charges for physical coins/bars. Beyond raw arithmetic, the workflow contextually understands the global landscape. By scraping the latest commodity headlines from Yahoo Finance, the integrated AI Agent determines if the current market vibe is "Greedy," "Neutral," or "Fearful." It then synthesizes the price gap and the news into a single "Efficiency Score" (1-100), telling you exactly how favorable the buying conditions are today. Finally, it maintains a permanent investment ledger. Every execution logs the data into a Google Sheet and formats a clean report ready to be sent to messaging apps, ensuring you never miss a buying opportunity when the "Arbitrage" (the price difference) favors one medium over the other. ## Who’s It For * **Retail Investors:** Who want to know if it's cheaper to buy gold on a digital app or from a local jeweler today. * **Financial Advisors:** Who need automated, data-backed daily gold market sentiment reports for their clients. * **Gold Enthusiasts:** Tracking the price variance (Arbitrage) between digital and physical assets to optimize their portfolio. * **FinTech Developers:** Looking for a professional blueprint on how to combine Web Scraping, Financial APIs and LLMs in n8n. ## Requirements * [n8n Instance (supporting LangChain nodes)](https://n8n.partnerlinks.io/om1efg2qgvwi). * **GoldAPI Token:** Free or Paid API key from GoldAPI.io. * **Groq API Key:** To power the AI analysis (supports Llama 3 or Mixtral models). * **Google Account:** For logging data into Google Sheets. * **Internet Access:** To scrape the IBJA (India Bullion and Jewellers Association) website. ## How It Works & Set Up ### Step 1: Data Collection The workflow starts with a **Manual Trigger** (can be changed to a **Schedule Trigger** for daily runs). It fetches the live 1-gram digital gold price in INR via an HTTP Request to GoldAPI. Simultaneously, it scrapes the official IBJA website to extract the physical benchmark rate using the CSS selector `#GoldRatesCompare999`. ### Step 2: The Math (Landed Costs) The **Comparator** node uses JavaScript to apply real-world fees: * **Digital:** Adds 3% GST and a 3% platform spread. * **Physical:** Adds 3% GST and 8% making charges (standard for coins). * It then determines which is cheaper and calculates the exact difference. ### Step 3: Market Context The workflow pulls the top 3 most recent gold market headlines from Yahoo Finance. These are bundled together so the AI can read them in one go. ### Step 4: AI Analysis & Output The **AI Agent** takes the math and the news headlines. It outputs a structured JSON verdict containing: * **Arbitrage Check:** A one-sentence summary of the best deal. * **Sentiment:** A label (Greedy/Neutral/Fearful). * **Efficiency Score:** A rating out of 100. ### Step 5: Logging The data is formatted into a readable message and appended as a new row in your designated Google Sheet. ## How To Customize Nodes * **Adjust Fees:** If your local jeweler charges 10% instead of 8%, simply open the **Comparator** node and change the `1.08` value in the code. * **Change AI Model:** In the **Groq Chat Model** node, you can switch between different models (e.g., Llama-3-70b vs 8b) depending on your speed and accuracy needs. * **Update Selectors:** If the IBJA website updates its design, you can update the CSS Selector in the **Extract Physical Price** node to point to the new data location. ## Add-ons * **WhatsApp/Telegram Notifications:** Add a node after "Message Format" to send the daily report directly to your phone. * **Email Summary:** Use the Gmail or Outlook node to send a weekly summary of the best buying days to your inbox. * **Price Drop Alert:** Add an **IF Node** to only trigger the workflow if the gold price drops by more than 2% in a single day. ## Use Case Examples * **Automated Savings:** Set the workflow to run every morning at 10 AM to decide where to put your daily savings. * **Jewelry Business Tool:** Use the data to show customers that your physical prices are competitive compared to digital market apps. * **Market Research:** Use the Google Sheet history to track how "Sentiment" affects the price of gold over several months. * **Arbitrage Trading:** Identify moments when digital gold is significantly undervalued compared to physical benchmarks. * **Wealth Management:** Proactively notify clients when the "Efficiency Score" hits 90+, indicating a prime buying opportunity. ## Troubleshooting Guide | Issue | Possible Cause | Solution | | :--- | :--- | :--- | | **Digital Price = 0 or Error** | API Key is missing or expired. | Check the "Get Digital Price" node; ensure the token is in the headers. | | **Physical Price Extraction Fails** | Website structure changed. | Verify the URL and the CSS selector `#GoldRatesCompare999` on IBJA. | | **AI Agent gives generic response** | Prompt is too vague or news is missing. | Ensure the "Data Array" node is successfully bundling headlines. | | **Google Sheets won't append** | Missing columns or incorrect ID. | Ensure headers (`Date`, `Sentiment`, etc.) match exactly in your sheet. | ## Need Help? Need assistance setting up your GoldAPI credentials, customizing the making charges or adding custom notifications to this workflow? We can help you build and scale your automation ideas. **[Contact WeblineIndia](https://www.weblineindia.com/contact-us.html)** to help you customize this workflow or build similar AI-powered financial tools for your business.

View

Qualify and route inbound leads with OpenAI, Trello, Slack and Gmail

## Description This n8n workflow automates a speed-to-lead system, capturing form submissions and quickly routing qualified leads to tools like Trello and Gmail for fast follow-up. ## Good to Know Speed-to-lead focuses on minimizing time from lead capture to sales engagement, boosting conversion rates. ## How it works - Triggers on form submission, feeding data into an AI Agent powered by an OpenAI Chat Model with chat memory. - The AI processes leads via a structured output parser, then a switch (rules mode) decides actions like editing fields or sending messages. - Outputs route to Trello (task creation), Gmail (notifications/emails), and possibly other apps for lead nurturing. ## How to use - Import the workflow into your n8n instance and connect credentials for OpenAI, Trello, Gmail, and your form tool (e.g., Google Forms). - Test by submitting a form; monitor the AI agent for lead qualification and verify outputs in Trello/Gmail. - Activate the workflow to run live, ensuring webhooks or triggers are set for production forms ## Requirements - n8n account (self-hosted or cloud); API keys for OpenAI, Trello, Gmail OAuth2. - Form tool integration (e.g., Google Forms webhook). - For verified creator status: Submit 2-3 approved public workflows via n8n Creator Portal, including this one, to gain the badge and directory listing.

View

Analyze weekly Fireflies sales calls with GPT-4o-mini, Google Sheets and Slack

### Description Connect your Fireflies account once and activate the workflow — every Monday at 9AM it runs automatically without any input from you. It pulls all sales call transcripts from the past 7 days, analyzes each one with GPT-4o-mini, and extracts six intelligence fields: pricing mentions, objections, buying signals, competitor mentions, a key takeaway, and a recommended next action. Every call is logged as one row in Google Sheets and a full weekly digest is posted to your Slack channel. Built for sales managers and revenue teams who want structured call intelligence delivered without manual review. --- ## What This Workflow Does - **Fetches last 7 days of calls automatically** — Pulls up to 50 recent transcripts from Fireflies and filters to only those recorded in the past week - **Analyzes every call individually** — GPT-4o-mini reads each transcript and extracts six structured fields per call, not a generic summary - **Detects objections and buying signals** — Surfaces exactly what concerns were raised and what positive signals suggest the deal is moving forward - **Flags competitor mentions** — Identifies any competitor names or alternative products that came up across all calls this week - **Logs each call to Google Sheets** — Appends one 13-column row per call so your team has a permanent, searchable record of every sales conversation - **Delivers a weekly Slack digest** — Aggregates all calls into one report covering totals, top objections, top buying signals, and a call-by-call overview - **Exits cleanly when no calls exist** — If no transcripts are found for the week, the workflow stops silently without errors or empty Slack messages --- ## Setup Requirements ### Tools Needed - n8n instance (self-hosted or cloud) - Fireflies.ai account with API access - OpenAI account with GPT-4o-mini API access - Google Sheets (one sheet with a tab named **Sales Call Analysis**) - Slack workspace with OAuth2 app configured ### Credentials Required - Fireflies API key (pasted directly into **2. Set — Config Values** — no n8n credential needed) - OpenAI API key - Google Sheets OAuth2 - Slack OAuth2 **Estimated Setup Time: 15–20 minutes** --- ## Step-by-Step Setup 1. **Import the workflow** — Open n8n → Workflows → Import from JSON → paste the workflow JSON → click Import 2. **Get your Fireflies API key** — Log in to fireflies.ai → go to Settings → Integrations → copy your API key 3. **Fill in Config Values** — Open node **2. Set — Config Values** → replace all placeholders: | Field | What to enter | |---|---| | `YOUR_FIREFLIES_API_KEY` | Your Fireflies API key from step 2 | | `YOUR_GOOGLE_SHEET_ID` | The ID from your Google Sheet URL (the string between `/d/` and `/edit`) | | `Sales Call Analysis` | Leave as-is, or change to match your sheet tab name exactly | | `#sales-team` | Your Slack channel name including the `#` | | `YOUR COMPANY NAME` | Your company name (used in the AI prompt and Slack report) | | `salesKeywords` | Comma-separated keywords to identify sales calls (default: `sales,client,demo,proposal,pricing,onboarding,deal,contract`) | 4. **Connect OpenAI** — Open node **10. OpenAI — GPT-4o-mini Model** → click the credential dropdown → add your OpenAI API key → test the connection 5. **Create your Google Sheet** — Open Google Sheets → create a new sheet → add a tab named exactly **Sales Call Analysis** → add these 13 column headers in row 1: `Call Date`, `Meeting Title`, `Duration (min)`, `Participants`, `Overall Sentiment`, `Pricing Mentions`, `Objections`, `Buying Signals`, `Competitor Mentions`, `Key Takeaway`, `Recommended Action`, `Transcript URL`, `Logged At` 6. **Connect Google Sheets** — Open node **13. Google Sheets — Log Call Analysis** → click the credential dropdown → add Google Sheets OAuth2 → sign in with your Google account → authorize access 7. **Connect Slack** — Open node **15. Slack — Send Weekly Report** → click the credential dropdown → connect your Slack workspace via OAuth2 → invite the n8n bot to your sales channel in Slack (`/invite @n8n`) 8. **Activate the workflow** — Toggle the workflow to Active — it will run automatically every Monday at 9AM > ⚠️ **Test before Monday** — To test immediately without waiting for Monday, open node **1. Schedule — Every Monday 9AM**, click "Execute step", then run the full workflow manually from there. --- ## How It Works (Step by Step) **Step 1 — Schedule: Every Monday 9AM** This step fires the workflow automatically every Monday morning at 9AM. No manual trigger is needed. Once the workflow is active, this runs on its own every week. **Step 2 — Set: Config Values** Your Fireflies API key, Google Sheet ID, sheet tab name, Slack channel, company name, sales keywords, and the 7-day date window are all stored here. The week start and end dates are calculated automatically based on today's date so you never need to update them manually. **Step 3 — HTTP: Fetch Recent Transcripts** A request is sent to the Fireflies API using your API key. It retrieves the 50 most recent transcripts from your account, including each call's ID, title, date, duration, and participants. This is a lightweight fetch — full transcript content comes later. **Step 4 — Code: Filter Last 7 Days** The 50 transcripts are filtered down to only those recorded in the past 7 days. Each transcript that passes the filter becomes its own separate item so the next steps process each call individually. If no transcripts exist at all, a fallback result is passed forward. **Step 5 — IF: Any Transcripts Found?** This is the gate check. If transcripts were found (YES path), each one moves forward to full analysis. If no transcripts were found this week (NO path), the workflow routes to **6. Set — No Calls This Week** and stops cleanly — no errors, no empty reports. **Step 6 — Set: No Calls This Week** This step handles the empty-week case. It sets a simple message confirming no calls were recorded and the workflow ends here for that run. **Step 7 — HTTP: Fetch Full Transcript** For each call that passed the filter, a second Fireflies API request is made to retrieve the complete transcript details: all sentences with speaker labels, AI-detected pricing sentences, questions, tasks, keyword summary, overview, and sentiment percentages. **Step 8 — Code: Extract Transcript Data** The full transcript is processed here. Sentences are assembled into readable text (limited to 4,000 characters for GPT efficiency). Fireflies AI-flagged pricing sentences and question sentences are extracted separately. Sentiment percentages are converted into a single label: Positive, Mostly Positive, Mixed, or Negative. All data is packaged cleanly for the AI step. **Step 9 — AI Agent: Analyze Sales Call** GPT-4o-mini receives the call details, sentiment data, Fireflies-detected pricing sentences, keywords, overview, and the transcript excerpt. It returns exactly six fields: pricing mentions, objections, buying signals, competitor mentions, a key takeaway under 25 words, and a recommended action for the sales rep to take within 48 hours. **Step 10 — OpenAI: GPT-4o-mini Model** This is the language model powering the analysis step. It runs at temperature 0.3 for consistent, factual extraction and is capped at 800 tokens per call to keep costs predictable across the full week's batch. **Step 11 — Parser: Structured Call Analysis** This step enforces the exact six-field schema GPT-4o-mini must return. It validates that all required fields are present and correctly typed before the results move forward, preventing malformed output from reaching your sheet. **Step 12 — Code: Combine Analysis Results** The AI output is merged with the original transcript metadata (date, title, duration, participants, sentiment, transcript URL). A log timestamp is also added. This creates the complete data row that goes to both Google Sheets and the Slack aggregation step. **Step 13 — Google Sheets: Log Call Analysis** One row is appended to your Sales Call Analysis tab for every call analyzed. All 13 columns are populated: date, title, duration, participants, sentiment, pricing, objections, buying signals, competitors, key takeaway, recommended action, transcript URL, and logged-at timestamp. **Step 14 — Code: Build Weekly Slack Summary** All analyzed calls are aggregated into a single weekly digest. The code counts total calls, positive calls, calls with objections, calls with buying signals, and compiles unique competitor mentions. The top 3 objections and top 3 buying signals are pulled from across all calls. A call-by-call overview line is added for every transcript. **Step 15 — Slack: Send Weekly Report** The complete weekly digest is posted to your Slack channel. The message includes the week date range, summary totals, top objections, top buying signals, competitor mentions, and a one-line overview of every call. A footer confirms the full analysis is logged in Google Sheets. --- ## Key Features ✅ **Fully automated weekly cadence** — Runs every Monday at 9AM with zero manual input after setup ✅ **Per-call AI intelligence** — Each call gets its own six-field analysis, not a rolled-up average ✅ **Fireflies AI signals as input** — Pricing sentences and questions detected by Fireflies are fed directly into GPT for more accurate extraction ✅ **Structured output enforced** — A schema parser validates every AI response before it reaches your sheet — no broken rows ✅ **Sentiment scoring per call** — Each call is rated Positive, Mostly Positive, Mixed, or Negative based on Fireflies sentiment percentages ✅ **Competitor tracking built in** — Competitor mentions are collected across all calls and deduplicated into one list in the Slack report ✅ **48-hour action item per call** — Every call ends with one concrete action the sales rep should take — not a vague suggestion ✅ **Clean empty-week handling** — No transcripts this week means a clean stop, not an error or blank Slack message --- ## Customisation Options **Change the schedule day or time** — In node **1. Schedule — Every Monday 9AM**, edit the cron expression `0 9 * * 1` to run on a different day or time. For example, `0 8 * * 5` runs every Friday at 8AM for an end-of-week review instead. **Increase the transcript fetch limit** — In node **3. HTTP — Fetch Recent Transcripts**, change `limit: 50` in the GraphQL query body to `100` if your team records more than 50 calls per week to ensure no calls are missed. **Expand the date window beyond 7 days** — In node **2. Set — Config Values**, change `{days: 7}` in both the `weekStart` and `sevenDaysAgoMs` fields to `{days: 14}` for a bi-weekly analysis window. **Add a Slack alert for high-objection calls** — After node **12. Code — Combine Analysis Results**, add an IF check: if the `objections` field does not contain "No objections", post an immediate Slack alert to a `#deal-risk` channel so the sales manager can follow up same day. **Add a Gmail summary to the sales manager** — After node **15. Slack — Send Weekly Report**, add a Gmail node to also email the full weekly digest to your sales manager's inbox as a backup record outside of Slack. **Filter to specific call types using keywords** — In node **2. Set — Config Values**, edit the `salesKeywords` field to narrow analysis to specific call types — for example, change to `demo,discovery,closing` to analyze only those pipeline stages. --- ## Troubleshooting **Fireflies returning no transcripts or an auth error:** - Confirm `YOUR_FIREFLIES_API_KEY` in node **2. Set — Config Values** is replaced with your actual key — not the placeholder text - Get your key from fireflies.ai → Settings → Integrations → API Key - Make sure your Fireflies plan includes API access — some free plans do not **Workflow not triggering on Monday:** - Confirm the workflow is toggled to Active — it will not run on a schedule if inactive - Check that the cron expression in node **1. Schedule — Every Monday 9AM** is `0 9 * * 1` — any edit to this field can break the schedule - To test immediately, click on node 1 and use the manual Execute option **Google Sheets not logging rows:** - Confirm the Google Sheets OAuth2 credential in node **13. Google Sheets — Log Call Analysis** is connected and not expired - Check that `YOUR_GOOGLE_SHEET_ID` in node **2. Set — Config Values** matches the ID in your sheet URL exactly - Confirm the tab is named **Sales Call Analysis** exactly — capitalization and spacing must match `sheetName` in Config Values **AI returning incomplete or missing fields:** - The schema parser in node **11. Parser — Structured Call Analysis** enforces all six fields — if output is missing fields, check the execution log of node **9. AI Agent — Analyze Sales Call** for the raw GPT response - Confirm the OpenAI credential in node **10. OpenAI — GPT-4o-mini Model** is connected and your account has available credits - If transcripts are very short, GPT may have little content to extract — the fallback text ("No objections detected", etc.) will be used automatically **Slack report not arriving:** - Confirm the Slack OAuth2 credential in node **15. Slack — Send Weekly Report** is connected and authorized - Check that the channel name in node **2. Set — Config Values** includes the `#` prefix and matches your actual Slack channel name exactly - Type `/invite @n8n` in your Slack channel to ensure the bot has posting permission --- ## Support Need help setting this up or want a custom version built for your team or agency? 📧 Email: [[email protected]]([email protected]) 🌐 Website: [https://isawow.com/](https://isawow.com/)

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Transform support tickets into AI documentation with GPT-4, PDFs and Google Drive

Workflow preview

Important notice

Overview

Customer Support Ticket Documentation Automation

Overview

What This Workflow Does

Key Features

Use Cases

Prerequisites

Required Services & Accounts

Required Credentials

Setup Instructions

1. Import the Workflow

2. Configure Credentials

OpenAI API

PDFMunk API

Google Drive OAuth2

Google Sheets OAuth2

Slack OAuth2

3. Configure Node Settings

Google Drive Folder ID

Google Sheets Configuration

Slack Channel ID

4. Configure Webhook in Support Tool

5. Test the Workflow

How It Works

Customization

Branding

AI Prompt Customization

Notification Customization

Data Flow

Expected Output

Performance

Troubleshooting

Best Practices

Security Notes

Future Enhancements

Support Resources

License