Skip to main content
The FalkorDB GraphRAG n8n community node connects n8n workflows to a FalkorDB GraphRAG-Server. It does not talk to FalkorDB directly. Instead, it uses the GraphRAG-Server REST API to ingest content into a knowledge graph and answer questions against that graph. The package ships two nodes and one shared credential:
  • FalkorDB GraphRAG: a regular pipeline node for ingest and question-answering steps.
  • FalkorDB GraphRAG Tool: an AI Agent tool node that can be called autonomously.
  • FalkorDB GraphRAG Server API: the credential that stores the server URL, API token, and request timeout.

​
Typical workflow

​
Installation

Install @falkordb/n8n-nodes-graphrag from the n8n Community Nodes UI, or use npm in a self-hosted n8n instance:
After installation, FalkorDB GraphRAG appears in the node panel under the FalkorDB category, and n8n lists the FalkorDB GraphRAG Tool variant under Tools for use with AI Agents.

​
Setup

Create one credential under Credentials -> New -> FalkorDB GraphRAG Server API and reuse it across both nodes.

​
How to get an API token

Use these steps only for GraphRAG-Server deployments that require API-token authentication. If server authentication is disabled, leave the n8n credential API Token field blank.

​
1. Open Settings and API Access

Open your graph in GraphRAG-Server, then go to Settings and keep the API Access tab selected. GraphRAG-Server Settings page with API Access selected

​
2. Add your LLM key

In Your LLM Keys, add a provider key if one is not already present. API tokens run on your own LLM key, so this step is required first when API-token authentication is enabled. Self-hosted deployments may already manage provider credentials on the server. LLM key section in GraphRAG-Server Settings

​
3. Generate the client API token

In API Tokens, enter a token name (for example, n8n production), choose expiration, and click Generate. Copy the raw token value when shown and paste it into the n8n credential API Token field. API Tokens panel showing token generation controls

​
Screenshots

​
Node picker

Node picker showing FalkorDB GraphRAG and FalkorDB GraphRAG Tool

​
Pipeline node

Pipeline node configuration for the main action flow

​
AI Agent tool

AI Agent tool configuration

​
Credential

FalkorDB GraphRAG Server API credential screen

​
Retrieve only workflow

Retrieve-only workflow canvas with Manual Trigger, Set Question, and FalkorDB GraphRAG

​
When to use it

Use the pipeline node when you want to ingest documents, list documents, or answer questions as part of a workflow. Use the AI Agent tool when you want the agent to decide when to query the knowledge graph and fill the node parameters automatically.

​
Frequently Asked Questions

It connects n8n workflows to a FalkorDB GraphRAG-Server so a workflow can ingest content into a knowledge graph, list documents, and answer questions against that graph.
No. The node talks to the GraphRAG-Server REST API, and GraphRAG-Server is what talks to FalkorDB. You need a running GraphRAG-Server instance before the n8n nodes can do anything.
Install @falkordb/n8n-nodes-graphrag from the n8n Community Nodes UI, or run npm install @falkordb/n8n-nodes-graphrag on a self-hosted instance. After installation, FalkorDB GraphRAG appears under the FalkorDB category in the node picker, and the FalkorDB GraphRAG Tool variant is listed under Tools for use with AI Agents.
FalkorDB GraphRAG is a regular pipeline node — you place it in the workflow and it runs a step you configured. FalkorDB GraphRAG Tool is an AI Agent tool node, so the agent decides when to call it and fills in the parameters itself.
Do this only when your GraphRAG-Server deployment uses API-token authentication: open your graph, go to Settings and the API Access tab, then generate a token under API Tokens, copy the raw value when it is shown, and paste it into the n8n credential API Token field. If server authentication is disabled, leave API Token blank.
Not always. A provider key is required when your deployment uses GraphRAG-Server API-token authentication, because tokens run on your own LLM key. Self-hosted deployments may manage provider credentials on the server, and when server authentication is disabled the n8n credential API Token field stays blank.
No. Create one FalkorDB GraphRAG Server API credential and reuse it across both the pipeline node and the AI Agent tool node. It stores the server URL, the API token, and the per-request timeout.