hivein for Drupal
Question a Drupal site through its own entity and bundle model, not a flattened copy of it.
Authenticated requests to Drupal's JSON:API root at /jsonapi, using HTTP Basic auth or an OAuth 2.0 bearer token from Simple OAuth.
- Read the site's own structure
- Audit content across bundles
- Check taxonomy health
- Inspect media and files
- Follow references into composed content
What the Drupal connector will do.
Read the site's own structure
Read the resource index a site publishes at /jsonapi to see which entity types and bundles it actually defines, then read a real document's attributes and relationships to see the fields a bundle carries and what its references point at.
Audit content across bundles
Every bundle is its own JSON:API collection, so a question lands on that bundle's resource type and uses JSON:API filters on published state, author and changed date, sorting and paging through large result sets.
Check taxonomy health
Read vocabularies and their terms, including parent hierarchy, and find terms that no node references any more.
Inspect media and files
Read media entities with their file fields, alt text and dimensions, and filter node collections by a media reference to find which nodes use a given item.
Follow references into composed content
Use include to pull paragraphs and other referenced entities alongside a node, so the answer reflects the whole composed page rather than the base fields.
It will read your Drupal data model, not a generic one.
The schema is read first, so a question that spans two of these is one question, not two lookups.
“Which article nodes are unpublished and have not changed in over a year?”
“Show me taxonomy terms in Tags that no node references”
“Which media items are missing alt text?”
“Which fields does a landing page node actually carry, and what do its reference fields point at?”
Drupal questions.
Does JSON:API allow writes?
Not by default. Core ships JSON:API in read-only mode, and an administrator has to switch that off in the JSON:API settings before any request can create or update an entity. Read-only sites still answer the questions on this page.
How does it authenticate?
Either HTTP Basic auth through the core basic_auth module or an OAuth 2.0 bearer token issued by Simple OAuth. Whichever you pick, the account's roles and permissions bound what can be seen.
What about Drupal 7?
JSON:API has been in core since Drupal 8.7, so the integration targets Drupal 9, 10 and 11. A Drupal 7 site would need a contributed REST module and is not part of the planned work.
More templates like this one.
WordPress
Open sourceYour editorial queue, taxonomy, comments and media library, answered from the WordPress site itself.
TemplateOpen template → — WordPress
Directus
Source availableAsk questions about the collections in your Directus project, whatever schema you have modelled.
In developmentSee the plan → — Directus
Ghost
Open sourceDraft posts, check newsletter sends and read member growth in one conversation with your Ghost site.
In developmentSee the plan → — Ghost
Joomla
Open sourceAsk about articles, categories, menu items and modules using Joomla's own admin vocabulary.
In developmentSee the plan → — Joomla
Strapi
Open sourceAsk about your own Strapi content types — entries, components, locales — without learning the query syntax.
In developmentSee the plan → — StrapiWant Drupal next?
Tell us what you would want it to do. Connector order follows demand, and the platforms people ask for get built first.