Feature Request: Official Directus Node for n8n Integration
Hi Directus team
I’d like to propose the development of an official Directus node for n8n, the open-source workflow automation platform.
Motivation
Currently, there’s no native or official node to easily connect Directus with n8n. While the HTTP Request node can be used as a workaround, it requires manual setup for authentication, endpoints, and data mapping — which makes integration more complex and error-prone.
Having a dedicated Directus node would:
Simplify workflows and automation between Directus and other services
Enable no-code users to interact with Directus collections, items, assets, and permissions directly from n8n
Improve developer experience and adoption of Directus within the automation community
Potential Features
Some actions that could be included:
CRUD operations for Collections and Items
Authentication support (API Token, Static Token, OAuth2)
Trigger node for Directus events (e.g., item created/updated/deleted)
Asset management (upload/download files)
User and Role management
Impact
This would significantly enhance Directus’ interoperability, making it easier to integrate with CRMs, CMSs, databases, and other APIs — without needing custom code or manual API requests.
How I Can Help
I can help by testing the node, providing feedback on endpoints and use cases, or contributing documentation/examples once the feature is under development.
Thanks for considering this request!
An official n8n node could become a huge boost for the Directus ecosystem
Hey @Bruno_Avelino_Sittax, welcome to the community! Thanks for sharing this request and for your very kind offer to help test and provide feedback. We like the way you think, A LOT! We have something in the works and we’ll have an update for you soon.
Note: there are a couple of pending issues, but for most part, it works pretty great.
Also, i’m yet to incorporate a few of the very latest endpoints (‘versions’, ‘access_policies’ etc.)
I am planning to finally update/revamp it to the very latest standards, and then apply to publish it ‘officially’, but it won’t happen for some time.
Directus node for CRUD operations (items, users, files)
Directus Trigger node for event-based automation
Auth support (tokens)
Asset management
Verified, maintained, and supported by the Directus team
Huge thanks to everyone in the community who pushed this forward and helped validate the need for this integration and to those who’ve been building and experimenting with Directus + n8n already
For anyone starting today, we recommend using the official verified node for long-term support, updates, and compatibility moving forward.
Thanks all, we’re excited to see what workflows you build with it!