Documentation is Essential. But let's be honest—it's also tedious. If you're like me and use Make.com for automations, you're probably familiar with how important yet time-consuming good documentation can be. I found myself repeating the same manual documentation tasks over and over and decided it was time for a change.
I got inspired by a YouTube video showing how to automate scenario documentation directly using Perplexity. It was a great starting point, but after experimenting, I realized ChatGPT produced clearer and more consistent documentation in a way I preferred. Since I was already using ChatGPT regularly, this was a no-brainer for me.
My goal wasn't to document every scenario, just the ones fully tested and ready for production. Here's how I initially set it up:
Clearly name each scenario and webhook in Make.com.
Once a scenario passes testing, an automation triggers from Make.com:
Extracts the scenario's blueprint JSON.
Sends this JSON through a ChatGPT module.
Posts generated documentation directly into Confluence.
Everything seemed smooth until I encountered two significant issues:
Character limits: OpenAI has limits on input size, so larger scenarios required multiple processing rounds.
Formatting frustrations: The documentation generated in Confluence Markdown often needed manual tweaks to look right once it was published.
To permanently eliminate formatting headaches, I developed a custom GPT designed specifically for documenting Make.com scenarios. The new workflow became straightforward:
Download your scenario's blueprint JSON from Make.com.
Upload it directly to the custom GPT.
Instantly get clean, well-formatted documentation output.
Copy-paste directly into Confluence—no editing needed.
This streamlined the whole process down to just a few minutes.
I strongly believe in open-source solutions, which is why I'm sharing this custom GPT openly. I hope it simplifies your workflow, enhances your productivity, and allows more room for innovation.
Give it a shot, adapt it to your needs, give feedback if you have any and let's keep automating smarter together!
Here's the YouTube video that originally sparked this idea.