In your shoes, I'd ask yourself whether you'd enjoy the day-to-day of the work. Low-code work means closer contact with users and having to deal with a lot more platform history and idiosyncrasy. So it will be more anthropological (on the user side) and archaeological (on the code side) than standalone development. But as long as you're matching the right tool to the job, you'll be able to deliver more to users than when building from scratch.
Using a low-code solution, I find I can build much faster a lot of the time and move onto the next problem. I also feel better knowing that whoever has to maintain that low-code "workflow" will have an easier time figuring it out than reading "normal" code.
On the other hand, depending on the low-code solution, you are beholden to whatever functionality is available to create your solution, which can be really limiting at times.
You're right.