Directus integration
No native Directus connector, here is what does work.
We create items in your Directus collections, honoring the status semantics your schema defines.
How it works
Directus exposes every collection through its Items API, authenticated with a static token or bearer auth, and creating content is a POST to /items/{collection}. Directus deliberately has no built-in draft or publish state: the common pattern is a status field on the collection, and its values are whatever your schema says they are.
That convention-over-built-in design means we never assume. During setup we map your status field and its exact values, so a schema that uses draft and live gets those values, not a guessed published. And because Directus permissions are role-based per collection, our connect step runs a dry-run create and delete in the target collection to prove the token's role can actually do the work before real content depends on it.
Best forTeams using Directus as a headless content backend who want items created to match their own schema conventions exactly.
Setup, step by step
- Create a Directus role with create and update permission on the target collections, and a user or static token under it.
- Add the token and your Directus URL to SearchHandled's connector.
- Map the target collection, its fields, and your status field's exact values during setup.
- Run the connect check, which performs a dry-run create and delete in the collection to verify permissions.
- Choose which status value new items receive, typically your draft equivalent.
Best practices
Define status values once, precisely
Your status field's values are the publishing contract. We record them exactly at setup, including which value your front end treats as live, so an item never leaks to production carrying a guessed state.
Give the token a narrow role
Directus permissions are per collection per role. A role limited to creating and updating content items keeps our token from touching users, files outside content, or system collections.
Keep relations mapped, not implied
Categories, authors, and tags in Directus are usually relational fields. We map those relations at setup so items arrive properly linked instead of with loose text where a relation belongs.
Tell us about schema migrations
Renaming a collection or the status field changes the API we write against. A quick remapping after schema changes keeps the pipeline landing items in the right shape.
Known issues
What practitioners actually report, from official docs, issue trackers, and community forums.
Status semantics are schema conventions
Directus has no built-in draft or publish state, so a status field's meaning and values differ per project, and a wrong assumed value can make content live prematurely or invisible forever.
How we handle itWe map your status field and its exact values at setup and never assume a published value. New items receive the state you designated, verified against your schema.
directus.io
Role-based permissions per collection
A token whose role lacks create permission on the target collection fails at write time, sometimes with errors that do not name the missing permission.
How we handle itOur connect step runs a dry-run create and delete in the target collection, proving the role's permissions up front and pointing at the specific collection if the check fails.
directus.io
Questions teams ask
- How does SearchHandled know what our status values mean?
You tell us once, during setup. We record the field name and its exact values, including which one your front end treats as live, and every item we create uses your vocabulary.
- What permissions does the token need?
Create and update on the content collections we publish into, plus read for verification, under a role you define. The dry-run at connect confirms the role is sufficient before real content flows.
- Does this work with self-hosted and Directus Cloud?
Yes, both. The Items API is the same either way. For self-hosted instances behind an allowlist, we provide addresses to permit, and connection diagnostics report reachability separately from permissions.
Not connectable yet
Start with the plan, not the connector.
Build a Growth Map from your site to see the work itself. Approved pages can leave through the export or the webhook today, and telling us Directus matters moves it up the rollout.