Integration
Connect your Directus instance with n8n to automate workflows, sync data between systems, and build powerful integrations.
- Install the node: Click the + button in n8n, search for "Directus", and install the verified node (look for the verification badge)
- Configure credentials: Add your Directus URL and API token
- Start building: Use the Directus node for actions or Directus Trigger node for automation
Available Nodes
The Directus community node provides two components:
- Directus Node: Perform CRUD operations on items, users, and files
- Directus Trigger Node: Automatically start workflows when events occur in Directus
Installation
Install the Community Node
- In n8n, open the node palette (click the + button to add a node)
- Search for "Directus" in the search bar
- The Directus verified node will appear in the results
- Click the Install button
If you can't find the Directus node when searching, ensure community nodes are enabled:
- Set
N8N_COMMUNITY_PACKAGES_ENABLED=truein your n8n environment variables - Restart your n8n instance
Configure Credentials
Before you can use the Directus nodes, you need to connect to your Directus instance:
- In any Directus node, click on Credential to connect with
- Click Create New Credential (or select an existing one)
- Fill in your connection details:
- Directus URL: Your Directus instance URL
- Token: Your Directus API token
- Click Save to store your credentials
Getting Your API Token
- In Directus, go to Users
- Select or create a user for n8n integration
- Open the user's detail page
- Scroll to Token section
- Click Generate Token
- Copy the token and paste into n8n
- Important: Click the checkmark (✓) to save
Admin Token (Recommended for Getting Started)
Many operations, including creating webhooks for triggers, require Administrator permissions. Assign the Administrator role to the user for the easiest setup and full access to all collections and features.
Custom Role (For Production)
For better security, create a custom role with specific permissions. This allows you to limit access to only the collections and operations your workflows need. The token inherits the user's role permissions, so you can lock down access while still allowing necessary operations.
Troubleshooting
"The specified package could not be loaded" or "Class could not be found"
This error occurs when stale files remain in n8n's community nodes directory after updates or reinstallation. This is a known n8n platform issue, not specific to the Directus node.
For Docker deployments:
docker exec -it <container-name> sh -c "cd /home/node/.n8n/nodes && rm -rf package.json node_modules"
docker restart <container-name>
For standard installations:
- Stop n8n
- Delete the community nodes directory:
rm -rf ~/.n8n/nodes - Start n8n
- Reinstall the Directus node through the node palette (search for "Directus")
"Package is not vetted for installation"
If you see this error, you're likely trying to install via Settings → Community Nodes using the package name @directus/n8n-nodes-directus.
Solution: Install through the node palette instead:
- Click the + button to open the node palette
- Search for "Directus"
- Install the verified node (it will have a verification badge)
The Directus node is officially verified by n8n, but the verification system only works when installing through the node palette search, not through manual package name entry.
Docker Volume Persistence
If your Directus nodes disappear after container restarts, ensure you're persisting the ~/.n8n/nodes volume:
volumes:
- n8n_data:/home/node/.n8n
Documentation
Working with Directus Actions →
Perform operations on your Directus data: create, read, update, and delete items, users, and files.
Set up automated workflows that trigger when events happen in Directus.
Use raw CRUD operations with Directus filter syntax, complex queries, and advanced query parameters.
Get once-a-month release notes & real‑world code tips...no fluff. 🐰