Make's documentation team used AI automation to create 700 community app guides in two weeks

Make's documentation team is responsible for empowering users with the knowledge and guidance they need to build, troubleshoot, and succeed with Make. Their job is essential to our customers’ success. However, managing 3,000+ apps is hard for a small team, especially when new ones are being added every day. 

While the team could focus on the most popular apps, hundreds of community-developed apps remained undocumented. That could hold customers back from using Make to its full potential.

All that has changed, though, when Ella and her team implemented a powerful solution very close to home - Make AI. 

By building an AI-powered documentation generation system, the team went from zero coverage to documenting 700 community apps. They managed this in just two weeks after the initial automation development began, while maintaining complete process control and quality oversight.

Ella Dombrovskaya, Head of Documentation at Make and the leader of this automation initiative, explains how her team turned an impossible manual task into an intelligent, scalable system that automatically creates comprehensive documentation.

"It has always been challenging for us to keep up with the app development pace, whether it's developed inside Make, by partners, or by community enthusiasts. We needed a solution that could scale. Manual documentation simply couldn't keep pace with the volume of new apps."

Ella Dombrovskaya, Head of Documentation at Make

The challenges: 3,000+ apps, two dedicated writers

Over the years of rapid platform growth, Make's documentation team faced several bottlenecks:

Hard to keep pace with app development

Until now, it had been very challenging to keep up with the pace of the rapidly growing number of apps. With 3,000+ apps on the platform and counting, the small documentation team simply couldn't cover them all.

Complex, time-intensive manual documentation

The scope of documenting even a single app was overwhelming. Some apps have hundreds of modules, and each module is different. Documenting them manually is time-consuming, since a writer needs to be fully dedicated for several days just to complete one app.

Keeping up with community apps

Community apps are valuable integrations developed by partners and enthusiasts. But providing detailed documentation for this growing number of apps was highly challenging, as documentation for Make’s verified apps took priority.

The initial step: Choosing the strategy

Before they started building the automation, the documentation team needed to choose the most fitting apps group to test. In the end, the team decided to work on the community apps first. There were plenty to work with (over 760), and they were completely undocumented – a clean slate. 

The solution: Weeks of app documentation work cut to minutes  

Make's documentation team, together with Business Automation and AI experts, built a sophisticated AI-powered documentation generation system that transformed their workflow entirely. 

AI-generated documentation with quality control

The team started by creating a reliable template that would serve as the foundation for all documentation. They mapped out what users needed: general app descriptions, connection instructions, detailed module information, and links to relevant developer resources.

Next, they identified which information sources to tap into. They could retrieve module data directly from Make itself, which is extremely valuable. They also sourced publicly available information from app providers and community resources.

Once the automation pulls module data from Make, it combines it with publicly available provider information to generate comprehensive documentation. With around 2,000 words on average, each document includes:

• An app description

• Support contact information

• Usage requirements

• A connection guide for Make

• A list of associated modules and templates

• Links to available app templates and resources

The team also clearly marks all AI-generated content on the website, encouraging users to treat it as a helpful starting point while verifying sensitive information.

"Even if our automation couldn't find every piece of information, it's a good starting point. Otherwise, our users would be spending time Googling instead of building."

Autonomous updates with complete visibility

The automation works end-to-end without manual intervention. When a new community app is developed or an existing one updated, the system automatically generates or refreshes the documentation and publishes it to Make's content management system.

The team decided that since apps are constantly being updated, checking with developers or the apps team every time something changed would be unsustainable. Instead, the AI is triggered automatically. 

The documentation team integrated the process with Jira for complete visibility. Tasks appear in Jira automatically, move from one status to another as the automation progresses, and are marked as done once documentation is published. If something fails for any reason, the team receives a report and can rerun the automation within a week.

In-depth testing and refinements

Before rolling out the system, the team carried out extensive testing. They went through the connection process and manually verified all the modules across approximately 70 apps. When the team noticed specific gaps and patterns, they refined the scenario and template accordingly.

Through iterative refinement of both the automation scenario and the documentation template, the team achieved a success rate of above 90% before trusting the system for full deployment.

"We'd have to dedicate lots of time to manually documenting one app. With automation, we simply run a scenario that pulls all the information from Make into our content management system. All the data already exists. Why not use it?" 

Ella Dombrovskaya, Head of Documentation at Make

The results: From 0 to 90% of apps documented

Make's documentation automation delivered remarkable outcomes:

• Zero to 90% coverage in weeks – The team generated documentation for 700 community apps in two weeks, going from no documentation to near-full coverage.

• Hundreds of hours saved – What previously would have required weeks of dedicated work per app now happens automatically.

• Improved SEO and discoverability – Comprehensive documentation improves search visibility, site visits, and overall platform recognition

• Potential to grow – The system is fully scalable, designed to expand beyond community apps. 

“We turned a capacity problem into a flagship documentation engine that covers hundreds of apps. That's a game-changer for our entire user experience."

Ella Dombrovskaya, Head of Documentation at Make

Make AI: Redefining the documentation process

Make's documentation team proved that the right automation can solve problems that once seemed impossible, turning a documentation bottleneck into a scalable system serving thousands of users daily.

The team is now exploring how to refine the automation and apply it to other apps, particularly documenting the modules and module descriptions, including how to set up each module for each app.

As Ella reflects on the project, it represents a fundamental improvement in the Make user experience and shows what's possible when teams apply automation to their own challenges.

“I think it's a huge milestone for us. We went from empty pages to comprehensive documentation that helps users find answers and stay up-to-date with Make.”

Ella Dombrovskaya, Head of Documentation at Make