Zendesk ticket summarizer with Pinecone, OpenAI, and Slack
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
Nodes used (9)
- OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - Pinecone Vector Store
@n8n/n8n-nodes-langchain.vectorStorePinecone - Embeddings OpenAI
@n8n/n8n-nodes-langchain.embeddingsOpenAi - Slack
n8n-nodes-base.slack - Default Data Loader
@n8n/n8n-nodes-langchain.documentDefaultDataLoader - Wait
n8n-nodes-base.wait - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Zendesk
n8n-nodes-base.zendesk - AI Agent
@n8n/n8n-nodes-langchain.agent
What it does
Zendesk Ticket Summarizer with Pinecone, OpenAI, and Slack This workflow automates the process of summarizing recent Zendesk support tickets and sharing key insights in a Slack channel. It is ideal for support teams who want daily, AI-generated overviews of customer issues without manually reviewing each ticket. How it works Daily Trigger: The workflow runs every day at 10am. Fetch Tickets: It retrieves all Zendesk tickets created in the last 24 hours (optionally filtered by brand). Vector Storage: Tickets are stored in a Pinecone vector database, with relevant fields and metadata. AI Summarization: An AI agent (using OpenAI) analyzes the tickets, identifies main complaints, and counts how many tickets mention each issue. Slack Notification: The summary is posted to a specified Slack channel for your team to review. Setup Instructions 1. Configure your Zendesk, Pinecone, OpenAI, and Slack credentials in the respective nodes. 2. Set your Pinecone index and namespace in both Pinecone nodes. 3. Adjust the Zendesk query if you want to filter by a specific brand. 4. Set the Slack channel ID where you want to receive the summaries. Use case Get daily, actionable insights from your Zendesk tickets, helping your team quickly spot trends and recurring issues.