node_ai_assistant

Node AI Assistant adds an AI-powered chatbot tab directly inside the Drupal node edit form. Content editors and moderators can instantly query all field values — including deeply nested paragraphs and entity references — using plain English, without navigating away from the edit screen.

Managing nodes with dozens of fields and complex paragraph structures is time-consuming. Editors often need to scroll through the entire form just to find a single field value. Node AI Assistant solves this by giving editors a conversational interface right inside the edit form where they can simply ask "What is in the hero paragraph?" or "List all empty fields" and get an instant answer.

Features

• Inline AI chat tab — A dedicated "AI Assistant" tab appears inside the node edit form vertical tabs group, keeping editors in context without opening new pages or admin screens.
• Full field awareness — The AI has access to every field on the node including text fields, entity references, image fields, link fields, and boolean fields.
• Deep paragraph support — Recursively extracts nested paragraph field data up to 5 levels deep, so even complex paragraph structures are fully queryable.
• Conversational memory — Chat history is maintained within the session so editors can ask follow-up questions naturally.
• Suggestion chips — Pre-built prompt suggestions help editors get started instantly without knowing what to type. You can create your own suggestion chips from back end configuration form.
• Provider agnostic — Works with any AI provider configured through the Drupal AI module including OpenAI, Anthropic Claude, Azure OpenAI, and Google Gemini.
• Read-only and safe — The assistant only reads and summarises field data. It never modifies node content, making it safe for all editorial roles.
• Role-based access — A dedicated permission use node ai assistant controls which roles can see the AI tab.
• Works on existing nodes — The tab only appears when editing an existing node, not on node creation forms where there is no data to query.
• Configuration to Select which fields need to send to AI — This configuration helps to set the fields which you want include in AI conversation. You can see the configuration for all content types in path - /admin/config/content/node-ai-assistant. if we exclude fields using this configuration form , any question about this fields will be unanswered.
• Configuration of default chat snippets
  users can provide chat snippets in configuration form so that users can just click on those snippets to get the results.

Use cases:

• A content editor needs to quickly check what text is inside a specific paragraph without scrolling through a long form.
• A moderator reviewing content needs a summary of all fields before approving a node.
• An editor wants to find all empty fields on a node before publishing.
• A site manager wants to quickly audit entity references and media fields on complex nodes.

Post-Installation

After enabling the module follow these steps:

• 1. Configure an AI provider — Go to Administration → Configuration → AI → Providers and configure at least one provider (e.g. OpenAI) with a valid API key using the Key module. Set it as the default provider for the "Chat" operation type.
• 2. Grant permissions — Go to Administration → People → Permissions and grant the Use node AI assistant permission to the roles that should have access to the chatbot tab (e.g. Content Editor, Moderator).
• 3. Open any existing node — Go to Content → Edit on any existing node. You will see a new "AI Assistant" tab inside the vertical tabs area at the bottom of the edit form alongside tabs like Authoring information and Promotion options.
• 4. Start chatting — Click the AI Assistant tab, type a question in the input box or click one of the suggestion chips, and the AI will respond with information drawn entirely from that node's field data.

No additional configuration pages, content types, or text format changes are required.

Additional Requirements

The following are required for this module to function:

• Drupal core 10.x or 11.x
• AI module (drupal/ai) — Provides the provider-agnostic AI abstraction layer and plugin manager that Node AI Assistant uses to communicate with AI services.
• Key module (drupal/key) — Required by the AI module for secure API key storage.
• At least one AI provider sub-module — Install and configure one of the following depending on your preferred AI service:
  • drupal/ai_provider_openai — for OpenAI (GPT-4o etc.)
  • drupal/ai_provider_anthropic — for Anthropic Claude
  • drupal/ai_provider_azure_openai — for Azure OpenAI
  • drupal/ai_provider_gemini — for Google Gemini
• Paragraphs module (drupal/paragraphs) — Required only if your content types use paragraph fields. The field extractor will gracefully skip paragraph extraction if the module is not installed.
• A valid API key from your chosen AI provider (OpenAI, Anthropic, etc.)

Additional notes:

This module was designed with editorial usability as the primary goal. The decision to make the assistant read-only was deliberate — content editors should feel confident that asking the AI a question will never accidentally modify their node. If you have a use case that requires the AI to write back to fields, consider using the AI Agents module in combination with custom agent tools instead.

The field extractor service (NodeFieldExtractor) is a standalone service that can be reused by other custom modules. If you need to extract all field values from any entity into a plain text string for AI context, you can inject node_ai_assistant.field_extractor into your own services and call extractAll($entity) directly.