Just to react to the "i automated myself out of a Job" part: happened to me at my first job, as we automated more and more our deployment, we could take more and more clients, and I ended up spending 90% of my time fixing routing issues, onboarding clients, integrating their ETLs or inhouse software, or fixing their "chmod -R 777 /" and other mistakes. Which wasn't an issue when it was 30%, or even 50% of my job to be clear, but became extremely boring and soulcrushing at the end.
I'm still happy i automated stuff, that was the interesting part of the job,
Sounds like your company should have hired some (cheaper) ops folks to handle that stuff, and given you bigger projects to take on.
My current company is doing exactly that type of thing. We have tons of data imports from different clients that have to run regularly, and my team started out writing the ETLs and troubleshooting stuff, but eventually we were able to write out playbooks for how slightly less-technical folks can do this stuff. We're now trying to automate more tools and processes for those folks, so they can take on more clients without needing more people.