Mintlify
The intelligent knowledge platform
5.0•74 reviews•2.1K followers
The intelligent knowledge platform
5.0•74 reviews•2.1K followers
The next generation of documentation. AI-native, beautiful out-of-the-box, and built for collaboration.
This is the 4th launch from Mintlify. View more
Mintlify Workflows
Launched this week
Keep your docs moving as fast as your product. Mintlify Workflows lets teams turn on pre-built automations that update knowledge bases, generate changelogs, maintain translations, and handle repetitive documentation tasks whenever triggered. Instead of chasing every product change manually, teams can set up Workflows once and let Mintlify keep docs accurate, current, and ready for users.
Free Options
Launch Team
The codebase update workflow is actually intriguing. Keeping docs aligned with merged PRs is something that every developer team struggles eventually. Just wondering if the system is capable of detecting when code change actually impacts user-facing behavior versus internal refactors.
Mintlify
@aayushi6 I'd be interested to hear you experience with it.
For us, only about 20% of our codebase PRs the agent classifies as needing a documentation change. We accept about 50% of those.
There is a lot more we will be doing to improve the accuracy. We still want a human in the loop for now.
Self-updating docs is one of those things you don't realize you need desperately until you've spent an afternoon hunting for the one endpoint that changed three PRs ago. As a solo founder I always deprioritize documentation and then pay for it later. How does it detect what changed — does it watch the codebase directly or does it work from commit diffs?
Mintlify
We couldn't agree more! It's been shocking to see that 1/5 PRs for us internally needed a documentation change.
It monitors when new PRs get opened in your source code repositories!
It would probably also be great to use something like this for user-facing release updates — automatically generating feature announcements, changelogs, and product update posts whenever something changes.☺️
Mintlify
@julia_bar this is exactly what we are trying to nail! The tricky part is that these often needed context outside of just source code changes. That is why there often needs to be a human in the loop.
Really like the direction of self-maintaining docs—feels like a natural evolution as teams ship faster.
One thing I’m curious about: over time, as multiple workflows keep updating the same docs, how do you prevent “automation drift” where tone, structure, or even intent slowly diverges from the original?
Is there a way to enforce a kind of long-term consistency beyond just individual workflow rules?
The "docs as a project of its own that grows wider than your product" framing is exactly the pain. Most teams treat docs as a write-once artifact and then watch them rot.
Question on the trust boundary: when a workflow auto-updates a doc from a PR merge and gets it subtly wrong (misleading commit message, an edge case the diff did not reveal), what catches it before users build on bad information? Docs are uniquely unforgiving here. A wrong line in an auto-generated changelog is annoying, but a wrong line in an API reference means developers ship broken integrations and blame themselves first.
Is there a confidence threshold that routes uncertain updates to human review, a staging layer before docs go live, or is the bet that self-correcting workflows fix it on the next run? Asking because "maintains itself" only earns trust if the failure mode is visible, not silent.
Moda
this is a game-changer -- very excited to set it up with Slack and Notion!
curious what you've seen are the most popular integrations??
Mintlify
Starting an run when a linear issue is resolved is pretty common. We've been experimenting a lot with reading through support requests in plain to spot gaps in our documentation.
This is a good example of automation being useful because it removes a recurring ownership problem, not just a one-time task. Docs usually break because no one owns the boring update loop, so tying workflows to product changes makes a lot of sense.
@alpertayfurr We’re glad you think so, too! I hope you are enjoying using Workflows, and if you haven’t given them a try yet, I hope you do and let us know what you think.