Skip to content
FlowHubFluxonLab
HTTP Request
Supabasefree

Telegram Bot with Supabase memory and OpenAI assistant integration

by Mark Shcherbakovadapted from n8n official workflow galleryUpdated Aug 2026
RequiresHTTP RequestHTTP RequestSupabaseSupabaseTelegramTelegram
Share Post Share
Get New MessageHROPENAI - Create threadOPENAI - Create…Create UserMeMergeHROPENAI - Send messageOPENAI - Send m…HROPENAI - Run assistantOPENAI - Run as…HROPENAI - Get messagesOPENAI - Get me…Send Message to UserSend Message to…IfIf User existsFind User12345678910
1/5
STEPS · 10
Starts on a Telegram event

Video Guide I prepared a detailed guide that showed the whole process of building an AI bot, from the simplest version to the most complex in a template. .png) Who is this for? This workflow is ideal for developers, chatbot enthusiasts, and businesses looking to build a dynamic Telegram bot with memory capabilities. The bot leverages OpenAI's assistant to interact with users and stores user data in Supabase for personalized conversations. What problem does this workflow solve? Many simple chatbots lack context awareness and user memory. This workflow solves that by integrating Supabase to keep track of user sessions (via What this workflow does This Telegram bot template connects with OpenAI to answer user queries while storing and retrieving user information from a Supabase database. The memory component ensures that the bot can reference past interactions, making it suitable for use cases such as customer support, virtual assistants, or any application where context retention is crucial. 1.Receive New Message: The bot listens for incoming messages from users in Telegram.

Tags

n8nreference-onlysupabasetelegram
Connects
WHTTP RequestsupabaseSupabasetelegramTelegram
CategorySupabase
Triggermanual
Complexitycomplex
Nodes10
AddedOct 6, 2024

Related workflows

See all Supabase
Wsupabase
free

Call analyzer with AssemblyAI transcription and OpenAI assistant integration

Video Guide I prepared a detailed guide that showed the whole process of building a call analyzer. .png) Who is this for? This workflow is ideal for sales teams, customer support managers, and online education services that conduct follow-up calls with clients. It’s designed for those who want to leverage AI to gain deeper insights into client needs and upsell opportunities from recorded calls. What problem does this workflow solve? Many follow-up sales calls lack structured analysis, making it challenging to identify client needs, gauge interest levels, or uncover upsell opportunities. This workflow enables automated call transcription and AI-driven analysis to generate actionable insights, helping teams improve sales performance, refine client communication, and streamline upselling strategies. What this workflow does This workflow transcribes and analyzes sales calls using AssemblyAI, OpenAI, and Supabase to store structured data. The workflow processes recorded calls as follows: Transcribe Call with AssemblyAI: Converts audio into text with speaker labels for clarity. Analyze Transcription with OpenAI: Using a predefined JSON schema, OpenAI analyzes the transcription to extract

by Mark Shcherbakov
CWsupabase
free

Send DocuSign envelopes with Supabase contract data

Quick overview This workflow is triggered by another n8n workflow, fetches an assessment record from Supabase, generates an HTML contract, and sends it as a DocuSign envelope using JWT authentication in either production or sandbox based on the recipient email, then writes the envelope ID and status back to Supabase. How it works Receives an execution request from another workflow with an assessment ID (and optional contract title). Retrieves the matching assessment record from the Supabase assessments table. Generates a styled contract HTML document from the assessment data and Base64-encodes it for DocuSign. Chooses the DocuSign sandbox or production path based on whether the contact email contains a specific marker string. Calls a Supabase Edge Function to create a DocuSign JWT assertion, exchanges it for a DocuSign access token, and creates a “sent” envelope with two signers and anchor-based signature tabs. Updates the Supabase assessment record with the DocuSign envelopeId and sets the contract status to envelope_sent. Setup Create and connect Supabase credentials in n8n, and update the Supabase project URL for the Edge Function endpoint (/functions/v1/docusign-sign-jwt). Conf

by Pedro Olavarria
CWsupabase
free

Monitor brand visibility in AI search with ChatGPT, Perplexity, Gemini, Claude, and Supabase

Quick Overview This workflow asks buyer-intent questions to ChatGPT Search (OpenAI), Perplexity, Google Gemini Search, and Anthropic Claude, scores whether your brand is cited or mentioned in each answer, logs every check to Supabase, and outputs an overall and per-engine visibility scorecard. How it works Starts when you run the workflow manually. Sets your brand name/domain and a list of buyer questions, then creates one item per question. Sends each question to Anthropic Claude, OpenAI Chat Completions (gpt-4o-search-preview), Perplexity (sonar), and Google Gemini with Google Search enabled. Parses each engine’s response to detect whether your brand domain is cited or your brand name is mentioned, and assigns a score (1 for cited, 0.5 for mentioned, 0 for absent). Writes each scored check (brand, engine, question, score, cited, mentioned) as a row into a Supabase table. Aggregates the results into a per-engine percentage and an overall panel score, then prints a console scorecard with top “not cited” targets. Setup Add environment variables in n8n for ANTHROPIC_API_KEY, OPENAI_API_KEY, PERPLEXITY_API_KEY, and GEMINI_API_KEY. Create a Supabase table named ai_visibility_log with c

by Nocode Expert