Enterprise organizations are increasingly looking beyond traditional software development teams to drive automation. As AI-assisted development tools mature, infrastructure engineers, system administrators, and cloud architects can now solve complex operational challenges that once required dedicated application developers. This shift is expanding who can build enterprise automation while reducing manual processes, improving security, and accelerating delivery across IT operations.

From Infrastructure Engineer to Workflow Automation: How AI Helped Me Bridge the Gap

I’m not a developer. I don’t want to be a developer. I’m a Cloud Infrastructure Engineer.

My day-to-day work revolves around Azure infrastructure and Microsoft 365 management and configuration. I spend a lot of time working with PowerShell and the occasional Python script. Traditionally, I operate in the world of infrastructure, automation scripts, and systems management, not full-scale application development.

Recently, though, I ran into a problem that pushed me outside my comfort zone. I had to build something that was completely new to me, a little confusing at first, but ultimately had tremendous potential.

The Problem: A Fully Manual, Error-Prone Process

I needed to automate a workflow that looked like this:

• Monitor a Microsoft Teams channel folder for new files.
• Download those files.
• Encrypt them using a vendor-provided GPG key.
• Upload the encrypted files to a different Teams folder.
• Move the original files into an archive.

The process was repetitive, manual, and impossible to scale. More importantly, it introduced unnecessary risk when handling sensitive data.

The Tool Choice: n8n (With Zero Prior Experience)

I decided to use n8n to build the workflow, despite having no prior experience with the platform.

To get started, I:

• Deployed n8n on a Linux VM running Docker.
• Used Visual Studio Code as my primary development environment.
• Leveraged the n8n-as-codeextension to define workflows programmatically instead of relying entirely on the visual UI.

I’ll also admit that I had almost no Docker experience going into this project.

The Game Changer: GitHub Copilot

This project would have taken significantly longer (or may never have happened at all) without GitHub Copilot.

Copilot helped me:

• Set up and troubleshoot the Docker environment.
• Learn how n8n workflows are structured.
• Debug issues when things didn’t behave as expected.
• Design and build a custom microservice for GPG encryption, since n8n doesn’t support it natively.

That last piece was especially important. Rather than getting blocked by a platform limitation, I used AI assistance to extend the platform and build the missing functionality myself.

The Result: Fully Automated and Stable

The completed workflow now:

• Monitors the Teams folder.
• Processes new files automatically.
• Encrypts them through the custom Docker-based microservice.
• Delivers encrypted files to the correct destination.
• Archives the original files without any human intervention.

I also added:

• Microsoft Teams notifications when processing is complete.
• User visibility so people know exactly when their files are ready.

The workflow has now been running reliably for two months without any issues.

Expanding the Use Case: Azure VM Automation

Once I saw how effective this approach was, I started applying the same pattern elsewhere.

Using n8n and GitHub Copilot, I built another workflow that:

• Checks the status of Azure virtual machines that shut down nightly to reduce costs.
• Starts them automatically on a schedule when needed.
• Sends an email summarizing the startup status.

Could this have been accomplished with traditional scripts? Absolutely.

But building it in n8n made the workflow easier to visualize, manage, troubleshoot, and extend over time.

Key Takeaway: You Don’t Need to Be a Developer Anymore

This experience completely changed how I think about automation.

You no longer need to be a full-time developer to:

• Build workflows.
• Deploy services.
• Extend existing platforms.
• Solve real operational problems.

With tools like:

• n8n
• Docker
• Visual Studio Code
• GitHub Copilot

…the barrier to entry has become dramatically lower.

AI doesn’t replace technical knowledge. It amplifies it. Having an infrastructure background gave me the context to understand the problem, while AI helped me bridge the gaps in areas where I lacked experience.

Final Thoughts

If you have a solid technical foundation, AI-assisted development tools can help you:

• Accelerate your work.
• Solve problems more quickly.
• Automate tasks that once seemed to require much deeper software development expertise.

This project wasn’t just about automating a workflow. It demonstrated that combining infrastructure expertise with AI assistance opens the door to building solutions that many infrastructure engineers may have previously considered out of reach.