I’m new to n8n and I’m trying to figure out how to edit my workflows using JSON. Does anyone know if this is possible in the cloud version? I noticed there are different project types in my dashboard. What’s the deal with ‘personal’ and ‘JSON-based’ projects? They both seem to use JSON, so I’m confused about the difference.
Also, I know we can import workflows from JSON files, but can we edit them directly in the n8n editor using JSON? It would be really helpful if someone could explain this. I’m just trying to understand the best way to manage my workflows. Thanks!
hey there, ive used n8n a while. in cloud, you cant directly edit json workflows. the json-based projects let pros work with raw json. you’ll still use the gui for editing, tho. hope this clears it up!
Having used n8n for several years, I can offer some insights. In the cloud version, direct editing of workflows in JSON is not available. The ‘JSON-based’ projects cater to users comfortable with raw JSON, yet the visual editor remains central for everyday tasks. Meanwhile, ‘personal’ projects are designed for standard user needs. While exporting workflows as JSON is useful for sharing or backing up, I recommend relying on the visual interface for most edits to avoid possible errors and ensure a more streamlined experience.
I’ve been using n8n for a while now, and I can shed some light on your questions. In the cloud version, you can’t directly edit workflows in JSON format within the n8n editor. The ‘JSON-based’ projects are more for advanced users who prefer working with raw JSON, but even then, you’ll mainly use the visual editor for modifications.
The ‘personal’ projects are the standard type most users work with. They’re easier to manage and don’t require JSON knowledge. While you can import workflows from JSON files, the editing process still happens in the visual interface.
From my experience, sticking to the visual editor is the best approach for most users. It’s more intuitive and less prone to errors. If you need to share or back up workflows, that’s when exporting to JSON comes in handy. Hope this helps clarify things!