I’m really confused about the new version 1.88.0 of n8n. It looks like they changed how templates work. Before, I could easily install templates right into my self-hosted setup. But now, when I check out the Templates section, it’s totally different.
Instead of the simple install option, it gives me two choices. I can either copy some JSON to my clipboard or look at docs about how to self-host n8n. The docs don’t even seem helpful for this issue!
I’m pretty bummed out. The old way was so quick and easy. Has anyone else noticed this change? Is there a way to get the old template installation method back? Or am I just missing something obvious here?
I’ve encountered similar issues with the latest n8n update. It’s indeed a significant change in how templates are handled, and it’s not just you feeling frustrated. The shift seems to be pushing users towards their cloud offering, which is disappointing for those of us who prefer self-hosting.
While it’s not ideal, I’ve found that using the JSON copy method isn’t too cumbersome once you get used to it. It requires a few extra steps, but you can still access and use the templates. As for reverting to the old system, I wouldn’t expect that to happen.
If this change severely impacts your workflow, you might want to consider sticking with an older version of n8n for now, or look into alternatives like Airflow or Zapier. It’s unfortunate, but sometimes we have to adapt or move on when software evolves in directions that don’t align with our needs.
yeah, i noticed that too. its kinda annoying tbh. seems like theyre trying to push ppl towards their cloud stuff. the json method works but its not as smooth. might be worth looking into other options like n8n alternatives if this is a dealbreaker for you. sucks when companies make things harder for self-hosters
I’ve been using n8n for a while now, and I noticed the same changes with the latest update. It’s definitely a shift from the previous user-friendly approach. From what I can gather, this seems to be part of a larger strategy to encourage more cloud usage.
While it’s frustrating for self-hosters like us, I’ve found a workaround. If you’re comfortable with JSON, you can still use the templates by copying the JSON and importing it directly into your workflows. It’s not as seamless as before, but it works.
As for getting the old method back, I wouldn’t hold my breath. Software companies rarely revert such significant changes. My advice would be to adapt to the new system or consider exploring alternative automation tools if this change is a deal-breaker for your workflow needs.
It’s a shame they’ve made it more complicated for self-hosters, but I suppose that’s the direction they’re heading.
