hivein for Directus
Ask questions about the collections in your Directus project, whatever schema you have modelled.
hivein will talk to your Directus instance over its REST and GraphQL endpoints with a static access token bound to a Directus user, so role and field permissions apply to every read.
- Read the schema you designed
- Query items with Directus filters
- Aggregate without exporting
- Stay inside the token's permissions
- See what changed and who changed it
What the Directus connector will do.
Read the schema you designed
The collections, fields and relations endpoints describe your own model, its field types and how the tables join, and a schema snapshot gives the same picture in one call where the token has admin rights. Nothing about the structure is assumed in advance.
Query items with Directus filters
The items endpoint takes filter operators such as _eq, _in and _between alongside sort, limit and offset, and related fields are pulled in by dot notation rather than a second round trip.
Aggregate without exporting
The aggregate and groupBy parameters return counts, sums and averages per group directly from the API, which settles how many and how much questions without a spreadsheet in between.
Stay inside the token's permissions
The access token belongs to a Directus user with a role, and Directus itself applies collection- and field-level permissions. A collection that role cannot read stays invisible to anything holding that token.
See what changed and who changed it
Activity and revisions record each create and update, with a delta of exactly what changed and a snapshot of the item as it stood at that revision, so questions about recent edits have a real answer rather than a guess.
It will read your Directus 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.
“What changed in the products collection this week, and who changed it?”
“How many items sit in each status in the orders collection?”
“Which fields on the events collection are required, and what type are they?”
“Which roles are allowed to update items in the customers collection?”
Directus questions.
Our collections are nothing like anyone else's, does that work?
That is the normal case for Directus, because the schema is your own database. The connector reads the collections and fields endpoints first and builds its picture from what it finds, so no collection names are assumed.
Directus has GraphQL as well, which one does hivein use?
Both interfaces expose the same data. Reads will go over REST by default, with GraphQL available for deeply nested queries, and the choice makes no difference to what permissions allow.
Can it trigger one of our flows?
A flow with a webhook trigger can be called over the API, so a flow you already trust can be run from a conversation. Anything that causes a change will be confirmed with you first.
More templates like this one.
WordPress
Open sourceYour editorial queue, taxonomy, comments and media library, answered from the WordPress site itself.
TemplateOpen template → — WordPress
Drupal
Open sourceQuestion a Drupal site through its own entity and bundle model, not a flattened copy of it.
In developmentSee the plan → — Drupal
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 Directus next?
Tell us what you would want it to do. Connector order follows demand, and the platforms people ask for get built first.