Block 1 - Transcribe with Deepgram
- Type / Role
- n8n-nodes-base.httpRequest - httpRequest
- Config choices
- Version 3
This workflow is provided as-is. Please review and test before using in production.
οΈ AI Audio Assistant with Voice to Voice Response Who is this for? Businesses, customer service teams, content creators, and organizations who want to provide intelligent voice based interactions...
n8n-nodes-base.httprequest, n8n-nodes-base.set, n8n-nodes-base.supabasetool, @n8n/n8n-nodes-langchain.memorybufferwindow, @n8n/n8n-nodes-langchain.lmchatopenai, @n8n/n8n-nodes-langchain.agent, n8n-nodes-base.if, n8n-nodes-base.telegramtrigger
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by RedOne.
Original n8n.io sourceWho is this for? Businesses, customer service teams, content creators, and organizations who want to provide intelligent voice-based interactions through Telegram. Perfect for accessibility-focused services, multilingual support, or hands-free customer assistance.
What problem does this solve?
What this workflow does:
Core Components:
Data Flow:
Telegram Bot Token
Deepgram API Key
OpenAI API Key
Supabase Database
Configure Telegram Bot
- Update telegramToken in "Prepare Voice Message Data" node
- Set correct bot token in Telegram nodes
- Test bot connectivity
Set Up Deepgram Integration
- Replace API key in "Transcribe with Deepgram" node
- Update TTS endpoint in "HTTP Request" node
- Test voice transcription accuracy
Configure Knowledge Base
-- Create knowledge_base table in Supabase
CREATE TABLE knowledge_base (
id UUID DEFAULT gen_random_uuid() PRIMARY KEY,
question TEXT NOT NULL,
answer TEXT NOT NULL,
category VARCHAR(100),
keywords TEXT[],
created_at TIMESTAMP WITH TIME ZONE DEFAULT NOW()
);
Customize AI Prompts
Test End-to-End Flow
// Current implementation has hardcoded tokens
// Recommended: Use environment variables
const telegramToken = process.env.TELEGRAM_BOT_TOKEN;
const deepgramKey = process.env.DEEPGRAM_API_KEY;
// Add to workflow for monitoring
console.log({
timestamp: new Date().toISOString(),
user_id: userData.user_id,
transcript_confidence: transcriptData.confidence,
response_length: aiResponse.length,
processing_time: processingTime
});
Multi-language Support
Voice Commands
Advanced AI Features
Integration Expansions
Voice Not Transcribing
Poor Audio Quality
AI Responses Too Generic
Memory Not Working
Note: This template requires active API subscriptions for Deepgram and OpenAI services. Costs may apply based on usage volume.
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 | ποΈ VoiceFlow AI: Telegram + Deepgram + OpenAI + Supabase audio assistant |
|---|---|
| Complexity | advanced |
| Nodes | 17 |
| Categories | Support Chatbot, AI Chatbot |
| Author | RedOne |
| Published | 04 Jun 2025 |
Use the JSON export at /data/workflows/4638/4638.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.
οΈ AI Audio Assistant with Voice to Voice Response Who is this for? Businesses, customer service teams, content creators, and organizations who want to provide intelligent voice based interactions...
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 Support Chatbot, AI Chatbot use case.