Back to Catalog

Personalized AI assistant with voice support, email/calendar & web tools integration

Carl FungCarl Fung
1669 views
2/3/2026
Official Page

✨ Intro This workflow shows how to go beyond a β€œplain” AI chatbot by:

🧠 Adding a Personality Layer β€” Link an extra LLM to inject a custom tone and style. Here, it’s Nova, a sassy, high-fashion assistant. You can swap in any personality without changing the main logic.

🎨 Custom Styling with CSS β€” Easily restyle the chatbot to match your brand or project theme.

Together, these make your bot smart, stylish, and uniquely yours.

βš™οΈ How it Works πŸ“₯ Route Input

Chat trigger sends messages to a Switch.

If a Telegram video note exists β†’ runs the audio path.

Otherwise β†’ runs the text path.

🎀 Audio Path

Telegram Get a File β†’ OpenAI Speech-to-Text β†’ pass transcript to the agent.

πŸ’¬ Text Path

Chat text is normalized and sent to the agent.

πŸ›  Agent Brain

Uses tools like Gmail πŸ“§, Google Calendar πŸ“…, Google Drive πŸ“‚, Airtable πŸ“‹, SerpAPI 🌐, Wikipedia πŸ“š, Hacker News πŸ“°, and Calculator βž—.

🧾 Memory

Keeps the last 20 messages for context-aware replies.

πŸ’… Optional Personality Polish

An LLM Chain adds witty or cheeky tone on top of the agent’s response.

πŸ›  Setup Steps ⏱ Time Required

~10–15 minutes (+5 minutes for each Google/Airtable connection).

πŸ”‘ Connect Credentials

OpenAI (and/or Anthropic)

Telegram Bot

Gmail, Google Calendar, Google Drive

Airtable

SerpAPI

πŸ“Œ Configure IDs

Set Airtable base/table.

Set Calendar email.

Adjust Drive search query defaults if needed.

πŸŽ™ Voice Optional

Disable Telegram + Transcribe nodes if you only want text chat.

🎭 Choose Tone

Edit Chat Trigger’s welcome text/CSS for custom look.

Or disable persona chain for neutral voice.

πŸš€ Publish

Activate workflow and share the chat URL.

πŸ’‘ Detailed behavior notes are available as sticky notes inside the workflow.

Personalized AI Assistant with Voice Support & Integrations

This n8n workflow creates a personalized AI assistant that can respond to chat messages, utilize various tools, and integrate with external services like Telegram. It leverages LangChain agents to provide dynamic, context-aware responses and actions.

Description

This workflow acts as a central hub for an AI assistant, capable of understanding user queries, routing them to appropriate AI models and tools, and delivering responses. It's designed to be highly extensible, allowing for the addition of more tools and integrations to enhance its capabilities.

What it does

  1. Listens for Chat Messages: The workflow is triggered whenever a new chat message is received via the "Chat Trigger" node.
  2. Initial Field Editing: It then processes the incoming chat message, potentially modifying or adding fields to the payload for further processing.
  3. Routes Messages to AI Agent: The core logic is handled by an "AI Agent" (LangChain Agent) that receives the processed chat message.
  4. AI Agent Configuration:
    • Memory: The agent uses a "Simple Memory" (Buffer Window Memory) to maintain conversational context across interactions.
    • Language Model: It can be configured to use either an "OpenAI Chat Model" or an "Anthropic Chat Model" (e.g., Claude) for generating responses and understanding intent.
    • Tools: The AI Agent is equipped with several tools to perform specific tasks:
      • Calculator: For mathematical computations.
      • SerpApi (Google Search): To perform web searches and retrieve information.
      • Wikipedia: To look up information from Wikipedia.
  5. Conditional Response Handling: After the AI Agent processes the message and potentially uses its tools, a "Switch" node is used to determine the next action based on the AI's output.
  6. Sends Telegram Messages: If the AI Agent generates a response, it is sent back to the user via a "Telegram" node.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • Telegram Bot: A Telegram bot token and chat ID to send and receive messages.
  • OpenAI API Key or Anthropic API Key: Depending on which chat model you choose to use.
  • SerpApi API Key: Required for the Google Search tool.
  • Wikipedia: No specific API key is usually required, but internet access for the n8n instance is necessary.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Telegram: Set up your Telegram Bot credential with your bot token and chat ID.
    • OpenAI/Anthropic: Configure your OpenAI or Anthropic Chat Model credential with your respective API key.
    • SerpApi: Set up your SerpApi credential with your API key.
  3. Activate the Workflow: Ensure the workflow is active to start listening for chat messages.
  4. Interact with the Bot: Send messages to your configured Telegram bot, and the AI assistant will process them, use its tools if necessary, and respond.

This workflow provides a powerful foundation for building advanced conversational AI assistants with integrated capabilities.

Related Templates

Two-way property repair management system with Google Sheets & Drive

This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required β€” one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- βš™οΈ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (β€œRepair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (β€œRepair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row β€” enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚑ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- πŸ› οΈ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.

Matt@VeraisonLabsBy Matt@VeraisonLabs
208

Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API

Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) How to Use β€” Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➀ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen

RapiwaBy Rapiwa
183

Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack

πŸ“Š Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. πŸš€πŸ“šπŸ’¬ What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. πŸ“¦ Step 3: Logs release data into Google Sheets for record-keeping and analysis. πŸ“Š Step 4: Retrieves FAQ or documentation data from Notion. πŸ“š Step 5: Merges GitHub and Notion data to calculate documentation drift. πŸ” Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. πŸ”” Key Benefits βœ… Keeps SDK documentation aligned with product releases βœ… Prevents outdated information from reaching users βœ… Provides centralized release tracking in Google Sheets βœ… Sends real-time Slack alerts for overdue updates βœ… Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.

Rahul JoshiBy Rahul Joshi
31