Block 1 - Schedule Trigger
- Type / Role
- n8n-nodes-base.scheduleTrigger - scheduleTrigger
- Config choices
- Version 1.2
This workflow is provided as-is. Please review and test before using in production.
What it does Customer support calls contain a wealth of valuable feedback and urgent issues, but manually reviewing audio files is inefficient. This workflow acts as an AI assistant for your call l...
n8n-nodes-base.scheduletrigger, n8n-nodes-base.googledrive, @n8n/n8n-nodes-langchain.lmchatgooglegemini, @n8n/n8n-nodes-langchain.outputparserstructured, n8n-nodes-base.telegram, n8n-nodes-base.switch, @n8n/n8n-nodes-langchain.agent, n8n-nodes-base.googlesheets
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Atta.
Original n8n.io sourceCustomer support calls contain a wealth of valuable feedback and urgent issues, but manually reviewing audio files is inefficient. This workflow acts as an AI assistant for your call log, transforming unstructured audio recordings into structured, actionable data. It provides a clean summary, sentiment analysis, and a list of required actions for every call, eliminating the need for manual listening and ensuring key insights are never missed.
The workflow runs on a schedule to fully automate the call analysis process from start to finish.
agent_name, client_name), a summary, the client_sentiment, a call_topic, a department_tag, and a list of action_items.To configure this workflow, you will need to set up your file storage in Google Drive, create a Google Sheet for logging, and configure credentials for all connected services.
BotFather in Telegram to get your Bot Token.Recording File, Sentiment, Department, Topic, Agent, Client, Summary, Actions, and Fulltext. Copy the Sheet ID from the URL and paste it into the "Log Recording Analysis" (Google Sheets) node.This workflow is a powerful starting point. Based on your specific needs, you can customize the inputs, the AI analysis, the logging method, and the final actions.
"competitor_mentioned": "Name of competitor if mentioned, otherwise null" to the JSON structure.
The current workflow asks the AI to populate a JSON object like this:{
"speaker_identification": {
"agent": "speaker_id",
"agent_name": "The agent's name",
"client": "client_id",
"client_name": "The client's name"
},
"summary": "A concise summary.",
"client_sentiment": "Positive, Negative, or Neutral",
"call_topic": "A brief phrase for the topic.",
"department_tag": "The most relevant department.",
"action_items": [
"A list of actionable tasks."
]
}
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.
| Workflow | Support call analysis & routing with Gemini AI, ElevenLabs & Telegram alerts |
|---|---|
| Complexity | advanced |
| Nodes | 16 |
| Categories | Ticket Management, AI Summarization |
| Author | Atta |
| Published | 02 Sept 2025 |
Use the JSON export at /data/workflows/8151/8151.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.
What it does Customer support calls contain a wealth of valuable feedback and urgent issues, but manually reviewing audio files is inefficient. This workflow acts as an AI assistant for your call l...
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 Ticket Management, AI Summarization use case.