Block 1 - Webhook - Receive Ticket
- Type / Role
- n8n-nodes-base.webhook - webhook
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
Customer Support Ticket Documentation Automation Automatically transform resolved support tickets into professional, AI powered PDF documentation with complete tracking and team notifications. Over...
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
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Jitesh Dugar.
Original n8n.io sourceAutomatically transform resolved support tickets into professional, AI-powered PDF documentation with complete tracking and team notifications.
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.
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:
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
chat:write, chat:write.publichttps://drive.google.com/drive/folders/FOLDER_ID_HERE| Ticket ID | Subject | Customer Name | Customer Email | Agent Name | Priority | Category | Resolved Date | Resolution Time | PDF Link | Document Generated | Status |
|---|
https://docs.google.com/spreadsheets/d/SHEET_ID_HERE/editRight-click your Slack channel → View Channel Details
Copy the Channel ID
Update it in:
Activate the workflow in n8n
Copy the Webhook URL from the “Webhook – Receive Ticket” node
In Zendesk/Freshdesk:
POSTClick “Execute Workflow” manually
Send a test webhook
Verify each step completes successfully
Check:
#4CAF50 → Replace with your brand color.Modify “AI Summarization (OpenAI)” node to add:
Webhook → Extract Data → AI Summary → Format HTML → Convert to PDF
↓
Download PDF → Upload to Drive → Log in Sheets → Notify Team
↓
Error Handling (if any)
PDF Document Includes:
Google Sheets Entry:
Slack Notification:
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.
This workflow template is provided as-is for use with n8n under the MIT License.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
Showing the first 24 of 28 workflow blocks. Download the JSON for the full node graph.
| Workflow | Transform support tickets into AI documentation with GPT-4, PDFs and Google Drive |
|---|---|
| Complexity | advanced |
| Nodes | 28 |
| Categories | AI Summarization |
| Author | Jitesh Dugar |
| Published | 04 Oct 2025 |
Use the JSON export at /data/workflows/9260/9260.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
Customer Support Ticket Documentation Automation Automatically transform resolved support tickets into professional, AI powered PDF documentation with complete tracking and team notifications. Over...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your AI Summarization use case.