Yes we're deploying a lot of no-code for back office processes (accounting, purchasing, payroll, HR, recruiting, etc.)
No code and low code are somewhat marketing lies. It's true that you can create certain solutions without any custom "code" (at least in some platforms), but even then you have to understand program control flow, logic, integrations, data structures, etc. in order to create anything substantial.
To give an example, we have a no code workflow for purchase requests, and in order to make meaningful human readable and informative instance IDs for process tracking, we had to use regex to replace GUIDs. There's no earthly way random accountant person is going to figure that out on their own.
What this means for us is that some management, some devs and some BAs work on developing solutions as DT projects come up. Most business users are completely incapable, but a few may be able to manage some admin and updates.
Feedback from my devs is that it's really effective and time saving IF your solutions fit the box the platform offers. For us we went with Nintex over Outsystems (and others) because we had a high focus on paperwork reduction. Nintex has much more robust form building/controls, whereas Outsystems has more "app focus" (like MS PowerApps). It reduces a lot of technical debt from random one off web apps to handle one piece of paper some guy made 15 years ago.