GraphRAG 1.1.0 Release Notes

Previously, conversation titles were automatically generated from the first question and could not be changed. This enhancement improves conversation organization. The following new endpoint has been introduced to allow clients to change the title of an existing conversation:

PATCH /conversations/{id}/title?title={new_title}

The new parameter custom has been added to the chat endpoint to forward and persist any type of custom data for a question. This allows clients to attach arbitrary metadata (such as session context, tracking IDs, or application-specific flags) to individual questions without requiring changes to the core API contract. Custom data is stored with the conversation, supporting downstream analytics, auditability, and client-specific processing logic.

Previously, the GraphRAG UI was optimized only for desktop browsers, limiting usability for stakeholders accessing the application from tablets or mobile devices. This enhancement broadens accessibility across form factors, supporting field-based and on-the-go usage scenarios without requiring a dedicated mobile application.

In addition to existing support for Elasticsearch and OpenSearch, GraphRAG now includes custom vector store presets, making it easier to integrate with any vector store accessible through the Components Service API and the main native n8n vector search nodes.

Two new message types have been added to the streaming contract to support observability and debugging:

The workflow engine now includes 27 organized workflows structured within a four-stage pipeline: Pre-processing → Data Gathering → Main Answer → Post-Answer Processing.

Key workflow architectural updates for this release include but are not limited to: