directus-flows

Installation
SKILL.md

Directus Flows

Flows are Directus's built-in automation: one trigger, then a chain of operations that share a data chain. Build them in the Studio, over REST (/flows, /operations), or with the MCP flows and operations tools (admin only).

First checks

  1. Check the version before anything else. GET /server/info with a token returns data.version. Older than 12.6: read the version notes for its major in the directus skill (references/versions-v<major>.md), or without that skill https://directus.com/docs/raw/releases/breaking-changes/version-<major>.md. Newer: read the release notes since 12.6.0 first.
  2. Read what exists. GET /flows?fields=id,name,status,trigger,options,operation&limit=-1. Reuse or extend an existing utility flow before building a new one.
  3. Check the license. Active flows count toward the core-tier limit (GET /license), and that includes every utility flow. Inactive flows don't count. See utility-flows-and-loops.md.
  4. Ask where it's hosted before suggesting a hook instead. Directus Cloud runs custom extensions only on Enterprise.
  5. Confirm before changing a flow that's already active. Event flows fire on real writes as soon as they're saved.
Installs
19
GitHub Stars
6
First Seen
13 days ago