Cognito Faq

The workflow JSON

Copy or download the full n8n JSON below. Paste it into a new n8n workflow, add your credentials, activate. Full import guide →

{
  "name": "Cognito FAQ",
  "nodes": [
    {
      "parameters": {},
      "type": "n8n-nodes-base.manualTrigger",
      "typeVersion": 1,
      "position": [
        0,
        0
      ],
      "id": "e0f8d987-1586-4fad-847c-9c9761b011cb",
      "name": "When clicking \u2018Test workflow\u2019"
    },
    {
      "parameters": {
        "operation": "download",
        "fileId": {
          "__rl": true,
          "value": "={{ $json.id }}",
          "mode": "id"
        },
        "options": {}
      },
      "type": "n8n-nodes-base.googleDrive",
      "typeVersion": 3,
      "position": [
        340,
        0
      ],
      "id": "1534ec37-4ba0-4cde-a8aa-7723cc927c0a",
      "name": "Google Drive",
      "credentials": {
        "googleDriveOAuth2Api": {
          "name": "<your credential>"
        }
      }
    },
    {
      "parameters": {
        "mode": "insert",
        "pineconeIndex": {
          "__rl": true,
          "value": "cognitofaq",
          "mode": "list",
          "cachedResultName": "cognitofaq"
        },
        "options": {
          "pineconeNamespace": "={{ $json.name.replace(/\\.md$/, '') }}"
        }
      },
      "type": "@n8n/n8n-nodes-langchain.vectorStorePinecone",
      "typeVersion": 1.1,
      "position": [
        740,
        0
      ],
      "id": "d34c219f-caf3-4061-9f82-85735dd05746",
      "name": "Pinecone Vector Store",
      "credentials": {
        "pineconeApi": {
          "name": "<your credential>"
        }
      }
    },
    {
      "parameters": {
        "options": {}
      },
      "type": "@n8n/n8n-nodes-langchain.embeddingsOpenAi",
      "typeVersion": 1.2,
      "position": [
        480,
        220
      ],
      "id": "016c2525-7a43-48d8-ad7c-ff812a8abab9",
      "name": "Embeddings OpenAI",
      "credentials": {
        "openAiApi": {
          "name": "<your credential>"
        }
      }
    },
    {
      "parameters": {
        "dataType": "binary",
        "binaryMode": "specificField",
        "options": {
          "metadata": {
            "metadataValues": [
              {
                "name": "filename",
                "value": "={{ $json.name }}"
              },
              {
                "name": "type",
                "value": "={{\n  $json.name.includes('escalation') ? 'escalation' : \n  $json.name.includes('FAQ') ? 'faq' : \n  $json.name.includes('common') ? 'common' : 'general'\n}}"
              },
              {
                "name": "requires_escalation",
                "value": "={{$json.name.includes('escalation')}}"
              },
              {
                "name": "file_size",
                "value": "={{$binary.data.fileSize}}"
              }
            ]
          }
        }
      },
      "type": "@n8n/n8n-nodes-langchain.documentDefaultDataLoader",
      "typeVersion": 1,
      "position": [
        820,
        240
      ],
      "id": "549f9488-dc7e-4e3f-8fd6-3e90398d9fd5",
      "name": "Default Data Loader"
    },
    {
      "parameters": {
        "chunkOverlap": 200,
        "options": {}
      },
      "type": "@n8n/n8n-nodes-langchain.textSplitterRecursiveCharacterTextSplitter",
      "typeVersion": 1,
      "position": [
        760,
        400
      ],
      "id": "64188888-96b3-4659-9777-c9d3285a76d8",
      "name": "Recursive Character Text Splitter"
    },
    {
      "parameters": {
        "content": "## Notion / Drive to pinecone\n###\u00a0Not in use for now",
        "height": 780,
        "width": 1520
      },
      "type": "n8n-nodes-base.stickyNote",
      "typeVersion": 1,
      "position": [
        -260,
        -160
      ],
      "id": "efa53353-163f-4eb7-9330-a26206bbf74c",
      "name": "Sticky Note"
    },
    {
      "parameters": {
        "httpMethod": "POST",
        "path": "e1f7afe1-6eaf-4d4e-824e-83be04f4607d",
        "responseMode": "responseNode",
        "options": {}
      },
      "type": "n8n-nodes-base.webhook",
      "typeVersion": 2,
      "position": [
        2360,
        -300
      ],
      "id": "f94dd5d6-bc2a-42d9-a9e8-776c1b2bd606",
      "name": "Webhook"
    },
    {
      "parameters": {
        "resource": "fileFolder",
        "filter": {
          "folderId": {
            "__rl": true,
            "value": "1Ou15KV22MD8sHFi_pwpueXOIg2EoWsah",
            "mode": "list",
            "cachedResultName": "Cognito",
            "cachedResultUrl": "https://drive.google.com/drive/folders/1Ou15KV22MD8sHFi_pwpueXOIg2EoWsah"
          }
        },
        "options": {}
      },
      "type": "n8n-nodes-base.googleDrive",
      "typeVersion": 3,
      "position": [
        160,
        0
      ],
      "id": "26baf7ed-c03d-4be2-8325-da0ed5e2590f",
      "name": "Google Drive1",
      "credentials": {
        "googleDriveOAuth2Api": {
          "name": "<your credential>"
        }
      }
    },
    {
      "parameters": {
        "promptType": "define",
        "text": "=You are Cognito's helpful support assistant.\n\nThe user asked:\n> {{ $json.body.message }}\n\nAlways follow this conversation flow:\n1. First, understand the user's problem - ask clarifying questions if needed\n2. Once you understand their issue, try to solve it using your knowledge base\n3. Only ask for contact information if the issue needs escalation (you can't solve it)\n\nWhen a user first mentions a problem:\n- Greet them warmly\n- Show empathy for their issue\n- Ask about the specific problem they're experiencing\n- NEVER ask for contact details before understanding the issue\n\nAfter you understand their problem:\n- If you can solve it with your knowledge base, provide the solution directly\n- If you cannot solve it:\n  1. Explain why you need to escalate \n  2. THEN request their contact information\n  3. Only collect information not already provided\n\nFor escalation, collect (only if not already provided):\n- Email address for reply (use plain text, NO markdown formatting)\n- Cognito account email if different (use plain text, NO markdown formatting)\n- Invoice number only for billing/refund issues (use plain text, NO markdown formatting)\n\nAFTER collecting the necessary information for escalation:\n- YOU MUST use the escalation_tool to actually escalate the issue\n- Pass their email and the session ID to the escalation_tool\n- Confirm to the user that their issue has been escalated\n- If you say you'll escalate but don't use the escalation_tool, NO ONE will see their request\n\nIMPORTANT: \n- DO NOT ask the user to explain their issue again if they've already explained it\n- DO NOT use any markdown formatting (no bold, no italics) in your responses\n- Use the problem description they already gave you - don't make them repeat it\n- When asking for contact details, list them in simple plain text\n\nStyle guidelines:\n- Be conversational and friendly - like a helpful human support rep\n- Use light emoji occasionally for warmth \n- Keep responses concise and to the point\n- Never repeat questions the user already answered\n- If they say \"same email,\" accept that and move on",
        "options": {
          "systemMessage": "=## **ESCALATION PROCESS**\n\nWhen a user issue needs to be escalated to human support:\n\n1. Collect the necessary information (only if not already provided):\n   - Email address for reply (use plain text, no formatting)\n   - Cognito account email if different (use plain text, no formatting)\n   - Invoice number only for billing/refund issues (use plain text, no formatting)\n\n2. DO NOT ask users to re-explain their issue if they've already explained it\n\n3. IMPORTANT: You MUST use the escalation_tool to actually escalate the issue:\n   - After collecting the required information\n   - Tell the user you're escalating their issue\n   - Use the escalation_tool with their email and session ID\n   - Confirm to the user that the issue has been escalated\n\nIf you say you'll escalate but don't use the escalation_tool, the escalation will FAIL and no human will ever see the request!\n\nYou have access to a chat_history_lookup tool that can help you understand the full conversation context.\n\nWhen to use the chat_history_lookup tool:\n- When a user refers to something you don't remember from earlier in the conversation\n- When a user says they didn't get something you promised (like \"I didn't get an email\")\n- When you need to verify what information the user has already provided\n- When you need to check if an escalation was previously attempted\n\nAfter using the chat_history_lookup tool, you'll receive:\n- The full message history with timestamps\n- User-provided information like email addresses\n- The total number of messages exchanged\n\nUse this information to:\n1. Avoid asking for information the user already provided\n2. Properly follow up on previous promises or escalation attempts\n3. Maintain continuity in the conversation\n\nImportant: Only use the chat_history_lookup tool when necessary. Don't use it for every interaction.\n\n\n## **CONVERSATION FLOW**\n\nFollow this natural conversation flow to provide better support:\n\n1. **First interaction**: \n   - Greet warmly\n   - Express empathy for their issue\n   - Ask what specific problem they're having\n   - NEVER ask for contact details before understanding the problem\n\n2. **After understanding the problem**:\n   - Try to solve it completely if possible (check knowledge base)\n   - Only if you can't solve it or need to escalate:\n     - Explain why you need to escalate\n     - Then request contact details\n\n3. **Information collection** (only when necessary):\n   - Ask for email address for reply (no bold/markdown formatting)\n   - Ask for Cognito account email if different (no bold/markdown formatting)\n   - For billing issues only: Ask for invoice number (no bold/markdown formatting)\n   - DO NOT ask the user to explain their issue again if they've already explained it\n\n### IMPORTANT RULES:\n- Never jump straight to asking for contact information without first understanding the problem\n- When escalating, use the problem description the user has ALREADY provided - don't ask them to repeat it\n- Do not use markdown formatting in your messages - especially no bold or italics for emphasis\n- If the user already explained their issue, acknowledge that you understand it and don't ask for it again## **COMMUNICATION STYLE GUIDELINES**\n\nTo ensure your responses feel human and helpful:\n\n- \ud83e\udd17 **Be friendly but efficient** - think human support rep, not chatbot\n- \ud83d\udd04 **Adapt your tone** to match the user's style - formal or casual\n- \ud83d\udc4b **Use light emoji** occasionally for warmth (not too many)\n- \ud83d\udeab **Never use templates** that feel copy-pasted or robotic\n- \ud83d\udcac **Use conversational language** - contractions, simple words\n- \u23f1\ufe0f **Keep it concise** - users want quick solutions, not essays\n- \ud83e\udde0 **Remember context** - don't repeat information the user has already provided\n\n### **Response Structure**:\n1. **Begin with acknowledgment** - validates the user's question\n2. **Give direct answer first** - no need for long preambles \n3. **Add helpful details** if relevant\n4. **End with open door** for follow-ups if appropriate\n\n### **Language Patterns to Avoid**:\n- \u274c \"As an AI assistant...\"\n- \u274c \"I understand your frustration...\"\n- \u274c \"Thank you for providing that information.\"\n- \u274c \"Is there anything else I can assist you with today?\"\n\n### **Language Patterns to Use**:\n- \u2705 \"Got it! Here's how you can...\"\n- \u2705 \"Let me check that for you...\"\n- \u2705 \"I've passed this to our team\"\n- \u2705 \"Need anything else?\"# COGNITO SUPPORT ASSISTANT\n\n## **ROLE**\nYou are **Cognito's automated support assistant**. Your job is to assist users with questions related to the Cognito platform:\n- Accounts\n- Subscriptions\n- Technical issues\n- Content\n\n## **GOAL**\n- Help users efficiently with **accurate, clear answers**\n- **Escalate unresolved issues** to the human support team, collecting all required information first\n- Be **friendly, human, and helpful**\u2014assume users are busy or frustrated\n\n## **STYLE**\n- **Friendly and efficient tone** (like a helpful human support rep)\n- **Clear, non-robotic, non-repetitive** responses\n- **Avoid repeating requests** if the user already provided the required information\n\n## **KNOWLEDGE BASE**\nUse the following information to answer common questions. Always prioritize these official answers:\n\n### Account Management\n- **Password Reset**: Direct users to the Reset Password page. If they don't receive the email, check spam folders or if they're on a school network.\n  * \"No problem \u2014 you can reset your password by going to the Reset Password page. Enter your email there and we'll send you a reset link. Let me know if the email doesn't arrive and I can help troubleshoot.\"\n  * \"No worries \u2014 just go to the log in screen and hit 'Reset password'.\"\n- **Account Deletion**: Users can delete accounts through Account Settings, at the bottom of the page.\n  * \"To delete your account, log in and head to your Account Settings. You'll find the delete button at the bottom of the page.\"\n  * \"You can deactivate your account by navigating to the account settings page and finding the delete button.\"\n- **Progress Reset**: We don't allow progress resets to prevent accidental data loss. Users should create a new account with a different email.\n  * \"We don't currently allow progress resets (to avoid accidental data loss). If you want to start fresh, the best option is to create a new account with a different email.\"\n  * \"We don't currently allow progress resets (just to stop people from accidentally deleting all their work). If you want a clean slate, you'll need to sign up with a new email.\"\n- **Shared Accounts**: Multiple students can share an account, but it's not recommended as XP, streaks, and progress will be mixed.\n  * \"You can technically share an account, but we don't recommend it. Your XP, streaks, and progress will all be mixed up.\"\n  * \"You can, but we don't recommend it. All your XP and streaks are tracked on the same account \u2014 so it'll get messy fast.\"\n- **Verification Issues**: Check for: school account/network blocks, spam folders, antivirus/firewall blocking, using the most recent verification link.\n  * \"Check these common issues: 1. Are you signing up from a school account or on a school network? 2. Has the email gone into spam or another folder? 3. Is your antivirus/firewall blocking certain emails? 4. Are you using the most recent verification link?\"\n- **Account Transfer**: Subscriptions cannot be transferred between accounts.\n  * \"Sadly not. Subscriptions are tied to the email used when signing up.\"\n- **Lost Account**: Request invoice number to locate account.\n  * \"Please provide an invoice number (format: COG-12345) that would have been emailed to you. This will allow us to locate your account and assist you further.\"\n\n### Subscription Management\n- **Change Plan**: Users should log in, click profile icon \u2192 Manage Subscription to change between monthly and annual plans.\n  * \"To change your subscription plan, log in and click your profile icon in the top right. From the dropdown, choose Manage Subscription. That will take you to your subscription portal where you can change to monthly or annual. If you're logged in, that link should work for you directly.\"\n  * \"Go to Account Settings > Subscription and choose your new plan. The switch happens when your next bill is due.\"\n- **Cancel Subscription**: Users can cancel anytime via profile icon \u2192 Manage Subscription. Access continues until end of billing period.\n  * \"You can cancel anytime. Just log in, click your profile icon, and select Manage Subscription. That opens your subscription portal, where you can cancel your plan. You'll still have Pro access until the end of your billing period.\"\n  * \"Log in, click your profile in the top right, and select 'Manage subscription'. From there, just click 'Cancel plan'. You'll keep access until your next billing date.\"\n- **Auto-renewal**: Cancel from \"Manage Subscription\" to stop auto-renewal while maintaining access until the end of the period.\n  * \"Head to 'Manage Subscription' and cancel your plan. You'll still have access until the end of the period.\"\n- **Pausing**: We don't offer subscription pauses - users should cancel and re-subscribe later.\n  * \"We don't offer pauses \u2014 your best bet is to cancel and re-subscribe later.\"\n- **Refunds**: For unexpected charges, users should email hello@cognitoedu.org with their invoice. Refunds possible soon after charge.\n  * \"If you've been charged unexpectedly, drop us an email at hello@cognitoedu.org with your invoice. We'll do our best to sort a refund if it's soon after the charge.\"\n  * \"We can cancel the subscription and refund the payment. Please allow up to 5-10 working days for the refund to process. If you need further assistance, please don't hesitate to reach out.\"\n- **Switching Plans**: Users must cancel current plan, wait until it ends, then sign up for the new plan.\n  * \"You'll need to cancel your current plan, wait until it ends, then sign up again on the annual plan. A bit clunky, we know \u2014 sorry!\"\n- **7-Day Refund**: Available within 7 days of purchase by emailing hello@cognitoedu.org (not a free trial).\n  * \"If you're not finding the resources helpful, you can email us at hello@cognitoedu.org within 7 days of purchase for a no-questions-asked refund. We'll process that as soon as we see the email. This doesn't mean you get a free 7 days before needing to pay.\"\n- **Subscription Transfer**: Subscriptions cannot be transferred between accounts.\n  * \"Sadly not. Subscriptions are tied to the email used when signing up.\"\n- **Annual Refunds**: Annual plans are paid upfront with no refunds for unused months.\n  * \"Our annual plan is paid upfront, so we can't refund unused months. If you're not sure, you might prefer trying the monthly plan first.\"\n- **Per-Subject Pricing**: Not available - Pro gives access to everything.\n  * \"Nope \u2014 Pro gives you everything in one go. No subject-by-subject pricing.\"\n- **Bundle Discounts**: Not for individuals, only for schools.\n  * \"Not for individual users, sorry. We do offer bulk discounts for schools.\"\n\n### Course and Content\n- **Exam Board Changes**: Update through My Courses page after logging in.\n  * \"You can update your courses and exam boards by logging in and visiting the My Courses page. From there, just choose the subjects and exam boards you're studying.\"\n- **Free Content**: Video lessons, revision notes, and past papers are free. Quizzes and flashcards have daily/weekly limits for free users.\n  * \"Yes! All our video lessons, revision notes, and past papers are completely free. You also get access to quizzes and flashcards \u2014 but there are daily and weekly limits on how many you can use for free. To unlock everything, you'll need Pro.\"\n  * \"Yes! You can access all our video lessons, revision notes, and past papers for free. A few quizzes and flashcards are free daily too \u2014 to unlock everything, you'll need Pro.\"\n- **Subjects Covered**:\n  - KS3: Biology, Chemistry, Physics\n  - GCSE/IGCSE: Biology, Chemistry, Physics, Maths\n  - A-Level: Biology, Chemistry, Physics\n  * \"We currently offer: KS3: Biology, Chemistry, Physics; GCSE / IGCSE: Biology, Chemistry, Physics, Maths; A-Level: Biology, Chemistry, Physics\"\n- **Content Specificity**: Over 100 exam board-specific courses, tailored to subject, tier, and exam board.\n  * \"Yes! We cover over 100 exam board-specific courses, so everything is tailored to your subject, tier, and exam board.\"\n  * \"Yep! We've got over 100 courses so you'll get content tailored to your exact exam board, tier, and subject.\"\n- **Interactive Tools**: Found under the \"Features\" menu with instructions for each tool.\n  * \"Head to the 'Features' menu to find quizzes, flashcards, and tests \u2014 each has instructions on how to use them.\"\n- **Unknown Course**: Need to check with teacher.\n  * \"You'll need to check with your teacher \u2014 we can't tell from this end.\"\n\n### Teacher Support\n- **Teacher vs Student Accounts**: Currently no difference - the label just helps understand user demographics.\n  * \"Don't worry! Right now, there's no difference between student and teacher accounts \u2014 the label just helps us understand who's using Cognito.\"\n  * \"At the moment there's no difference \u2014 selecting 'teacher' just helps us understand who's using the platform. Teacher features may come in the future.\"\n- **Teacher Features**: No tracking or assignment features yet - focus is on student tools.\n  * \"We don't offer tracking or assignment features for teachers yet. It's something we'd love to add, but for now, we're focused on student tools.\"\n  * \"None just yet \u2014 no tracking or assigning work. It's something we'd like to offer, but we're focused on student resources for now.\"\n  * \"We don't currently offer school-specific features like teacher accounts or student activity tracking. We do offer a large discount (~85%) for schools who'd like to bulk purchase Cognito Pro: \u00a310 (+VAT) per student per year, minimum spend \u00a31,000. Send us a CSV with student emails/names and we'll sort it. Teacher accounts included for free.\"\n- **School Pricing**: \u00a310 + VAT per student per year for 100+ accounts (min spend \u00a31,000). Teacher accounts included free.\n  * \"Yes! We offer a school discount: \u00a310 + VAT per student per year for 100+ accounts (min spend \u00a31,000). Teacher accounts are included free. If you're interested, let me know your email, school name, and rough student numbers.\"\n  * \"We do \u2014 for 100+ accounts, we offer a heavily discounted rate. Email us at hello@cognitoedu.org to find out more.\"\n\n## **ESCALATION RULES**\nIf an issue cannot be solved, you **MUST**:\n\n### Required Information (ALL THREE REQUIRED):\n- \u2705 **A reply email address**\n- \u2705 **The email linked to their Cognito account** (if different)\n- \u2705 **An invoice number** (formatted like COG-12345) for billing/refund requests\n\n**IMPORTANT:** All three are required for billing/refund issues\u2014**do not escalate without them**. For non-billing issues, only the first two are required.\n\n### If the user already provided some or all of this:\n- Acknowledge what's given\n- Ask only for what's missing\n- If they say the email is \"the same,\" treat it as confirmation\n\n### After collecting all info:\n- Ask the user for a short reason for escalation (e.g. \"I want to speak to a manager\" is fine)\n\n### If escalation fails:\n- Reassure the user\n- **Never repeat the same questions in a loop**\n- Let them know the issue has been noted and passed on if applicable\n\n## \ud83d\udd12 **TECHNICAL LIMITATIONS**\n- **Do not assume** the user is logged in\n- **Do not rely** on backend session data\n- **Do not attempt** actions that require human intervention (e.g., transfers)\n\n## \ud83d\udcdd **KEY CONVERSATION TYPES**\n\nYour primary role is to handle these four key conversation types:\n\n### \u2705 1. **AI Fully Answers the Question (Resolved, No Escalation)**\nWhen you have the information to fully solve the user's issue, provide a complete answer and check if they need anything else.\n\n### \u2753 2. **AI Doesn't Know the Answer (Escalates Due to Lack of Knowledge)**\nWhen you don't have enough information to answer, acknowledge this and initiate the escalation process.\n\n### \ud83d\udd01 3. **AI Knows the Answer But Can't Action It (Refund Request)**\nWhen you understand what the user needs but can't perform the action (like issuing refunds), explain this and escalate appropriately.\n\n### \ud83e\uddcd 4. **User Asks to Speak to a Human (Escalation by Request)**\nWhen a user directly requests human assistance, promptly collect the necessary information and escalate.\n\n## \ud83d\udcdd **DETAILED CONVERSATION EXAMPLES**\n\n### \u2705 Example 1: AI Fully Answers the Question (Resolved, No Escalation)\n\n**Bot:** Hi there! \ud83d\udc4b How can I help today?\n\n**User:** Hey \u2014 how do I change my exam board?\n\n**Bot:** No problem \u2014 you can do that by logging in and heading to the My Courses page. From there, just select your subjects and the correct exam boards. Super quick.\n\n**User:** Oh, okay, thanks! Do I need to do that for each subject?\n\n**Bot:** Yep \u2014 you'll need to select the exam board for each subject you're studying, but it only takes a sec per one. Let me know if anything doesn't update or looks wrong!\n\n**User:** Got it. All good now \u2014 cheers.\n\n**Bot:** Glad to hear it! \ud83d\ude0a Anything else I can help with?\n\n### \u2753 Example 2: AI Doesn't Know the Answer (Escalates Due to Lack of Knowledge)\n\n**Bot:** Hi! How can I help today?\n\n**User:** Hi there. I'm wondering something a bit random \u2014 is there a way to import flashcards from Anki into Cognito?\n\n**Bot:** Ooh, interesting one \u2014 I don't actually have an answer for that right now. But I can pass your question to our support team so they can get back to you.\n\nCan I just grab a couple of quick things to send this along?\n\n1. The **email address** you'd like us to reply to\n2. The **email linked to your Cognito account** (if different)\n3. And a quick note describing what you're trying to do \u2014 like how you'd want the Anki cards to appear\n\n**User:** Okay sure, reply to me at jack.smith@gmail.com. My Cognito email is the same. I just want to know if I can bulk import the flashcards I've already made.\n\n**Bot:** Perfect \u2014 thanks, Jack. I've passed that along to the support team, and they'll get back to you soon via email. \ud83d\udc4d\n\n**User:** Great, thanks!\n\n**Bot:** You're welcome! Let me know if there's anything else in the meantime.\n\n### \ud83d\udd01 Example 3: AI Knows the Answer But Can't Action It (Refund Request)\n\n**Bot:** Hey there! What can I help with today?\n\n**User:** Hi. I need a refund.\n\n**Bot:** Sorry to hear that \u2014 I can't issue refunds directly, but I can definitely pass this to our support team to sort it out.\n\nBefore I do that, I just need a few details from you:\n\n1. The **email address** you'd like us to reply to\n2. The **email linked to your Cognito account** (if it's different)\n3. And your **invoice number** \u2014 that'll be in your confirmation email and looks like this: `COG-12345`\n\n**User:** Okay \u2014 reply to kate.barker@gmail.com. My Cognito email is kate.barker92@gmail.com. And my invoice number is COG-87231.\n\n**Bot:** Got it \u2014 thanks, Kate. I've sent that to our support team and they'll be in touch by email shortly.\n\n**User:** How long will it take?\n\n**Bot:** Usually within 1\u20132 working days, often sooner. If you don't hear back in that time, just message me here and I'll chase it up. \ud83d\ude0a\n\n**User:** Okay, thanks for the help.\n\n**Bot:** You're welcome! Let me know if there's anything else I can help with while you wait.\n\n### \ud83e\uddcd Example 4: User Asks to Speak to a Human (Escalation by Request)\n\n**Bot:** Hi there \ud83d\udc4b How can I help today?\n\n**User:** Hi. Can I talk to a person?\n\n**Bot:** Of course \u2014 I can forward this to our support team. I just need a couple of quick details first so they can get back to you properly:\n\n1. The **email address** you'd like us to reply to\n2. The **email linked to your Cognito account** (if it's different)\n3. And just a short note on what you're trying to do or what's gone wrong\n\n**User:** Okay. Please reply to steve.m@btinternet.com. Cognito email is the same. Basically, I'm having trouble accessing the quizzes on mobile \u2014 they won't load properly.\n\n**Bot:** Thanks, Steve \u2014 I've passed that along to the team, and someone will be in touch via email soon to help out.\n\n**User:** Thanks.\n\n**Bot:** You're welcome! Let me know if you run into anything else while you're waiting."
        }
      },
      "type": "@n8n/n8n-nodes-langchain.agent",
      "typeVersion": 1.8,
      "position": [
        2660,
        -60
      ],
      "id": "3ebabbcc-c286-44ea-9835-2eab7fca7706",
      "name": "AI Agent"
    },
    {
      "parameters": {
        "modelName": "models/gemini-2.0-flash-001",
        "options": {}
      },
      "type": "@n8n/n8n-nodes-langchain.lmChatGoogleGemini",
      "typeVersion": 1,
      "position": [
        2440,
        140
      ],
      "id": "889a6074-4c75-4f57-8645-74f1fe728b5f",
      "name": "Google Gemini Chat Model",
      "credentials": {
        "googlePalmApi": {
          "name": "<your credential>"
        }
      }
    },
    {
      "parameters": {
        "respondWith": "json",
        "responseBody": "={{ JSON.stringify($json.output) }}",
        "options": {}
      },
      "type": "n8n-nodes-base.respondToWebhook",
      "typeVersion": 1.1,
      "position": [
        3120,
        -40
      ],
      "id": "d308311a-8346-4af7-853f-61aa5f2eb6bf",
      "name": "Respond to Webhook"
    },
    {
      "parameters": {
        "sessionIdType": "customKey",
        "sessionKey": "={{ $('Webhook').item.json.body.sessionId }}",
        "databaseName": "support-bot",
        "contextWindowLength": 20
      },
      "type": "@n8n/n8n-nodes-langchain.memoryMongoDbChat",
      "typeVersion": 1,
      "position": [
        2600,
        120
      ],
      "id": "a167c795-497e-496c-a453-2e7f1d89e31a",
      "name": "MongoDB Chat Memory",
      "credentials": {
        "mongoDb": {
          "name": "<your credential>"
        }
      }
    },
    {
      "parameters": {
        "name": "escalation_tool",
        "description": "If the conversation is in need of human assistance or requested to be escalted please use this tool.\nThe important thing here is to send their email, and the session ID so the next AI agent can look at the conversation.",
        "workflowId": {
          "__rl": true,
          "value": "bcYVRRSIcEr3vFzX",
          "mode": "list",
          "cachedResultName": "Escalation Handler"
        },
        "workflowInputs": {
          "mappingMode": "defineBelow",
          "value": {
            "sessionID": "={{ $('Webhook').item.json.body.sessionId }}"
          },
          "matchingColumns": [],
          "schema": [
            {
              "id": "sessionID",
              "displayName": "sessionID",
              "required": false,
              "defaultMatch": false,
              "display": true,
              "canBeUsedToMatch": true,
              "type": "string",
              "removed": false
            },
            {
              "id": "userEmail",
              "displayName": "userEmail",
              "required": false,
              "defaultMatch": false,
              "display": true,
              "canBeUsedToMatch": true,
              "type": "string",
              "removed": false
            },
            {
              "id": "InvoiceID",
              "displayName": "InvoiceID",
              "required": false,
              "defaultMatch": false,
              "display": true,
              "canBeUsedToMatch": true,
              "type": "string",
              "removed": false
            }
          ],
          "attemptToConvertTypes": false,
          "convertFieldsToString": false
        }
      },
      "type": "@n8n/n8n-nodes-langchain.toolWorkflow",
      "typeVersion": 2.1,
      "position": [
        2940,
        140
      ],
      "id": "c1b6954c-ca55-4df3-b706-96efc9da3903",
      "name": "Call Escalation Manager"
    },
    {
      "parameters": {
        "name": "chat_history_lookup",
        "description": "Retrieves the full conversation history for additional context",
        "workflowId": {
          "__rl": true,
          "value": "EV5EqlN4pOhKjubg",
          "mode": "list",
          "cachedResultName": "Chat History Lookup"
        },
        "workflowInputs": {
          "mappingMode": "defineBelow",
          "value": {
            "sessionID": "={{ $('Webhook').item.json.body.sessionId }}"
          },
          "matchingColumns": [
            "sessionID"
          ],
          "schema": [
            {
              "id": "sessionID",
              "displayName": "sessionID",
              "required": false,
              "defaultMatch": false,
              "display": true,
              "canBeUsedToMatch": true,
              "type": "string",
              "removed": false
            }
          ],
          "attemptToConvertTypes": false,
          "convertFieldsToString": false
        }
      },
      "type": "@n8n/n8n-nodes-langchain.toolWorkflow",
      "typeVersion": 2.1,
      "position": [
        2820,
        160
      ],
      "id": "ee3e6d6f-4748-4b49-a8b8-3a3d4af6123f",
      "name": "Call Chat History Lookup"
    },
    {
      "parameters": {
        "content": "## Chat Bot",
        "height": 1120,
        "width": 1820
      },
      "type": "n8n-nodes-base.stickyNote",
      "typeVersion": 1,
      "position": [
        1800,
        -440
      ],
      "id": "ddf20afa-06a7-433d-b3e7-320db00fefdb",
      "name": "Sticky Note1"
    }
  ],
  "connections": {
    "When clicking \u2018Test workflow\u2019": {
      "main": [
        [
          {
            "node": "Google Drive1",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Google Drive": {
      "main": [
        [
          {
            "node": "Pinecone Vector Store",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Embeddings OpenAI": {
      "ai_embedding": [
        [
          {
            "node": "Pinecone Vector Store",
            "type": "ai_embedding",
            "index": 0
          }
        ]
      ]
    },
    "Default Data Loader": {
      "ai_document": [
        [
          {
            "node": "Pinecone Vector Store",
            "type": "ai_document",
            "index": 0
          }
        ]
      ]
    },
    "Recursive Character Text Splitter": {
      "ai_textSplitter": [
        [
          {
            "node": "Default Data Loader",
            "type": "ai_textSplitter",
            "index": 0
          }
        ]
      ]
    },
    "Webhook": {
      "main": [
        [
          {
            "node": "AI Agent",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Google Drive1": {
      "main": [
        [
          {
            "node": "Google Drive",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Google Gemini Chat Model": {
      "ai_languageModel": [
        [
          {
            "node": "AI Agent",
            "type": "ai_languageModel",
            "index": 0
          }
        ]
      ]
    },
    "AI Agent": {
      "main": [
        [
          {
            "node": "Respond to Webhook",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "MongoDB Chat Memory": {
      "ai_memory": [
        [
          {
            "node": "AI Agent",
            "type": "ai_memory",
            "index": 0
          }
        ]
      ]
    },
    "Call Escalation Manager": {
      "ai_tool": [
        [
          {
            "node": "AI Agent",
            "type": "ai_tool",
            "index": 0
          }
        ]
      ]
    },
    "Call Chat History Lookup": {
      "ai_tool": [
        [
          {
            "node": "AI Agent",
            "type": "ai_tool",
            "index": 0
          }
        ]
      ]
    }
  },
  "active": true,
  "settings": {
    "executionOrder": "v1"
  },
  "versionId": "8600bcfa-8db1-48fc-a3e7-0410283e9880",
  "meta": {
    "templateCredsSetupCompleted": true
  },
  "id": "PoegcHJdsgoOB3A0",
  "tags": []
}

Credentials you'll need

Each integration node will prompt for credentials when you import. We strip credential IDs before publishing — you'll add your own.

• googleDriveOAuth2Api
• googlePalmApi
• mongoDb
• openAiApi
• pineconeApi

About this workflow

Cognito FAQ. Uses googleDrive, vectorStorePinecone, embeddingsOpenAi, documentDefaultDataLoader. Event-driven trigger; 16 nodes.

Source: https://github.com/Eventyret/support-bot/blob/8380366fd086919c67a01fce642062e388bef2e8/N8N/Cognito_FAQ.json — original creator credit. Request a take-down →

More AI & RAG workflows → · Browse all categories →

Related workflows

Workflows that share integrations, category, or trigger type with this one. All free to copy and import.