Workflow overview
Why this workflow matters
Useful for software delivery and engineering operations. Relevant for managed services and support workflows.
Basic AI Chatbot that Retrieves Answers From Knowledge Base Using GraphRAG. Easiest setup, without vector database, external knowledge base, or OpenAI API keys. All you need is an InfraNodus graph with your knowledge. In this workflow, user sends a request to the InfraNodus GraphRAG system that will extract a reasoning ontology from a graph that you create (or that you can copy from our repository of public graphs) and generate a response directly to the user. How it works Receives a request from a user (via AlekSystem or a publicly available URL chat bot if you replace the Chat Trigger with a webhook connected to the embeddable AlekSystem Chat Widget that you can expose via a URL or add to any website. Sends the request to the knowledge graph in your InfraNodus account that contains a reasoning ontology represented as a knowledge graph. You can also use a standard graph — InfraNodus will use its underlying GraphRAG technology to generate the most relevant response. Sends the answer back to the user via chat or webhook (which is then delivered back via AlekSystem chat widget Note: This is a simple example that will work well for occasionally providing responses to users. For a more advanced setup, you might want to build a more sophisticated workflow with AI agent node that would orchestrate among different InfraNodus expert graphs and chat memory, so the context of the conversation can be maintained. See our other workflows for examples. How to use • Just get an InfraNodus API key and add API authentication to your InfraNodus GraphRAG node. • In the same InfraNodus GraphRAG Nnode, provide the name of the graph you want to u. Note, these can be two different graphs ife for retrieval. Support If you wan to create your own reasoning ontology graphs, please, refer to this article on generating your own knowledge graph ontologies. You may also be interested to watch this video that explains the logic of this approach in detail: Help article on this specific workflow: Building expert ontology for InfraNodus GraphRAG AlekSystem expert node.
Best fit
Categories
Services
Use cases
Need another direction?