Back to Catalog

Build an AI chatbot with InfraNodus knowledge graph for enhanced responses

InfraNodusInfraNodus
589 views
2/3/2026
Official Page

Build an embeddable AI chatbot with an access to a knowledge base

InfraNodus knowledge graph

This is an example of a simple AI chatbot that has access to external knowledge to augment its responses.

The knowledge can be added manually or imported from multiple sources (text and PDF files, websites, CSVs, Google search results, AI generated, YouTube search results, RSS feeds, etc) using InfraNodus.

no OpenAI account needed • no vector store needed • easy data import: PDF, text, CSV, Google / YouTube results, RSS feeds, websites, or AI-generated

How it works

  1. First, you add your data into your InfraNodus graph — this will be your knowledge base.

  2. You can import this data from multiple sources or add it manually.

  3. You will have a visual interface available that will show the main concepts and topics in your knowledge base, so you can have an overview of its structure and know how to improve it, if necessary.

  4. Your data is represented as a knowledge graph which contains information about relations and topical clusters in your data, making the LLM responses much more precise.

How to use

  1. Copy the template
  2. Add your InfraNodus API key to the HTTP AI response node
  3. Create a new graph in InfraNodus with your data (or import from an external source)
  4. Add the name of this graph into the name field of the AI response HTTP node.
  5. That's it! You can query it using the embeddable web form available via a URL

Requirements

You only need an InfraNodus account to set this workflow up.

Free 14-day trials are available.

n8n AI Chatbot with Infranodus Knowledge Graph for Enhanced Responses

This n8n workflow provides a framework for building an AI chatbot that leverages an Infranodus knowledge graph to enhance its responses. It uses an n8n Form Trigger to initiate interactions, allowing users to submit queries, and an HTTP Request node to interact with external services, likely including an AI model and the Infranodus API.

What it does

This workflow outlines the following key steps:

  1. Listens for Form Submissions: The workflow is triggered when a user submits data through an n8n form. This form likely collects the user's query or input for the chatbot.
  2. Processes User Input: The submitted form data is then passed to subsequent nodes for processing.
  3. Makes HTTP Requests: An HTTP Request node is included, indicating interaction with external APIs. This would typically involve:
    • Sending the user's query to an AI model (e.g., OpenAI, custom LLM) for initial processing or response generation.
    • Querying an Infranodus knowledge graph to retrieve relevant context, facts, or relationships based on the user's input or the AI's initial response.
    • Potentially sending the combined information (user query, AI response, Infranodus context) back to the AI for a refined, knowledge-graph-enhanced response.
  4. Provides a Form Interface: A standalone n8n Form node is present, suggesting a user-friendly interface for submitting queries to the chatbot.
  5. Includes a Sticky Note for Documentation: A sticky note is included, which is often used for in-workflow documentation, instructions, or important notes for users or maintainers of the workflow.

Prerequisites/Requirements

To effectively use and extend this workflow, you will likely need:

  • n8n Instance: A running n8n instance to host and execute the workflow.
  • Infranodus Account/Instance: Access to an Infranodus knowledge graph, including its API endpoints and any necessary API keys for querying.
  • AI Service API Key: An API key for an AI service (e.g., OpenAI, Google AI, custom LLM) that will process natural language queries and generate responses.
  • Basic API Knowledge: Familiarity with making HTTP requests to configure the HTTP Request node for your specific AI and Infranodus APIs.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure the On form submission Trigger:
    • Access the On form submission node.
    • Ensure the form is set up to collect the necessary user input (e.g., a text field for the query).
    • Activate the workflow to get the webhook URL for the form.
  3. Configure the HTTP Request Node:
    • Edit the HTTP Request node.
    • AI API Integration:
      • Set the Method (e.g., POST) and URL for your chosen AI service's chat or completion endpoint.
      • Add Headers for authentication (e.g., Authorization: Bearer YOUR_AI_API_KEY).
      • Construct the Body of the request to send the user's query, potentially including system prompts or context.
    • Infranodus API Integration:
      • You might need additional HTTP Request nodes or modify the existing one to interact with the Infranodus API.
      • Determine the Infranodus API endpoints for querying your knowledge graph.
      • Add necessary authentication (e.g., API keys, tokens).
      • Construct the request body to send relevant terms or concepts extracted from the user's query or AI response to Infranodus.
  4. Process and Combine Responses: Add further nodes (e.g., Code, Set) to:
    • Extract the AI's response.
    • Extract relevant information from the Infranodus API response.
    • Combine these pieces of information into a single, enhanced response.
    • Potentially send the combined information back to the AI for a final, refined output.
  5. Display the Chatbot Response: Add a node to display the final, enhanced chatbot response to the user, perhaps by updating the form or sending it to another messaging service.
  6. Activate the Workflow: Once configured, activate the workflow to make it live.
  7. Test: Submit a query via the n8n form to test the end-to-end functionality.

Related Templates

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247

🎓 How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

DavideBy Davide
1616

Tax deadline management & compliance alerts with GPT-4, Google Sheets & Slack

AI-Driven Tax Compliance & Deadline Management System Description Automate tax deadline monitoring with AI-powered insights. This workflow checks your tax calendar daily at 8 AM, uses GPT-4 to analyze upcoming deadlines across multiple jurisdictions, detects overdue and critical items, and sends intelligent alerts via email and Slack only when immediate action is required. Perfect for finance teams and accounting firms who need proactive compliance management without manual tracking. 🏛️🤖📊 Good to Know AI-Powered: GPT-4 provides risk assessment and strategic recommendations Multi-Jurisdiction: Handles Federal, State, and Local tax requirements automatically Smart Alerts: Only notifies executives when deadlines are overdue or critical (≤3 days) Priority Classification: Categorizes deadlines as Overdue, Critical, High, or Medium priority Dual Notifications: Critical alerts to leadership + daily summaries to team channel Complete Audit Trail: Logs all checks and deadlines to Google Sheets for compliance records How It Works Daily Trigger - Runs at 8:00 AM every morning Fetch Data - Pulls tax calendar and company configuration from Google Sheets Analyze Deadlines - Calculates days remaining, filters by jurisdiction/entity type, categorizes by priority AI Analysis - GPT-4 provides strategic insights and risk assessment on upcoming deadlines Smart Routing - Only sends alerts if overdue or critical deadlines exist Critical Alerts - HTML email to executives + Slack alert for urgent items Team Updates - Slack summary to finance channel with all upcoming deadlines Logging - Records compliance check results to Google Sheets for audit trail Requirements Google Sheets Structure Sheet 1: TaxCalendar DeadlineID | DeadlineName | DeadlineDate | Jurisdiction | Category | AssignedTo | IsActive FED-Q1 | Form 1120 Q1 | 2025-04-15 | Federal | Income | John Doe | TRUE Sheet 2: CompanyConfig (single row) Jurisdictions | EntityType | FiscalYearEnd Federal, California | Corporation | 12-31 Sheet 3: ComplianceLog (auto-populated) Date | AlertLevel | TotalUpcoming | CriticalCount | OverdueCount 2025-01-15 | HIGH | 12 | 3 | 1 Credentials Needed Google Sheets - Service Account OAuth2 OpenAI - API Key (GPT-4 access required) SMTP - Email account for sending alerts Slack - Bot Token with chat:write permission Setup Steps Import workflow JSON into n8n Add all 4 credentials Replace these placeholders: YOURTAXCALENDAR_ID - Tax calendar sheet ID YOURCONFIGID - Company config sheet ID YOURLOGID - Compliance log sheet ID C12345678 - Slack channel ID tax@company.com - Sender email cfo@company.com - Recipient email Share all sheets with Google service account email Invite Slack bot to channels Test workflow manually Activate the trigger Customizing This Workflow Change Alert Thresholds: Edit "Analyze Deadlines" node: Critical: Change <= 3 to <= 5 for 5-day warning High: Change <= 7 to <= 14 for 2-week notice Medium: Change <= 30 to <= 60 for 2-month lookout Adjust Schedule: Edit "Daily Tax Check" trigger: Change hour/minute for different run time Add multiple trigger times for tax season (8 AM, 2 PM, 6 PM) Add More Recipients: Edit "Send Email" node: To: cfo@company.com, director@company.com CC: accounting@company.com BCC: archive@company.com Customize Email Design: Edit "Format Email" node to change colors, add logo, or modify layout Add SMS Alerts: Insert Twilio node after "Is Critical" for emergency notifications Integrate Task Management: Add HTTP Request node to create tasks in Asana/Jira for critical deadlines Troubleshooting | Issue | Solution | |-------|----------| | No deadlines found | Check date format (YYYY-MM-DD) and IsActive = TRUE | | AI analysis failed | Verify OpenAI API key and account credits | | Email not sending | Test SMTP credentials and check if critical condition met | | Slack not posting | Invite bot to channel and verify channel ID format | | Permission denied | Share Google Sheets with service account email | 📞 Professional Services Need help with implementation or customization? Our team offers: 🎯 Custom workflow development 🏢 Enterprise deployment support 🎓 Team training sessions 🔧 Ongoing maintenance 📊 Custom reporting & dashboards 🔗 Additional API integrations Discover more workflows – Get in touch with us

Oneclick AI SquadBy Oneclick AI Squad
93