Mintlify Workflows - Self-updating knowledge bases
by•
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.
Replies
Mintlify
Hi Product Hunt community!
We are excited to introduce Mintlify Workflows
What is it?
Automations that keep your knowledge base up-to-date without manual upkeep. Pick a workflow, choose when it runs, and let it maintain itself.
Why now?
With recent AI advancements, the gap between what your product does and what your knowledge base grows wider, and closing it becomes a project of its own. We built Workflows to save you time and automate the busywork of maintaining knowledge bases so you can stay focused on shipping.
What's included?
Each workflow is focused, tested, and ready to go. No prompts are required to write or maintain. We built them around the tasks teams want to automate the most:
- Codebase updates: sync content when PRs merge to your code repo
- Changelog: draft entries from recent product updates on a recurring schedule
- Translations: automatically translate your content to increase reach
- Broken links: find and fix links automatically
- SEO: audit titles, meta tags, headings, and canonical tags
- Grammar: catch typos and grammar errors
- Brand tone: enforce your style guide's voice and rules
@hahnbeelee Hey Hahnbee, congrats on shipping Workflows 🎉
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.
Mintlify
@arturbrugeman Hello! I'm one of the engineers here who's been building Workflows. Figuring out how to make sure inaccurate information doesn't get shipped is something we've been thinking a lot about.
The solution we have right now is that, on a per-automation basis, you can select whether you want changes to be on auto-accept or review-needed. For instance, in our setup we have the translation workflows and a broken-link fixer on auto-merge. It nails it every time. However, for net-new features we still need a human sign-off before it updates the docs.
Feels like an intersting long-term shift here. Curious if the hardest problem here eventually becomes technical or behavioural. Most knowledge bases don’t fail because information is missing.
They fail because teams stop trusting them. How do you think about preserving organisational trust once docs become AI-maintained instead of human-maintained?
@surabhi_minocha Hi! Great question. We have workflows like Translations which we feel can be greatly AI maintained and are often on auto merge. Other workflows such as Content sync with code we often see approval required for the or to merge, meaning having someone on a teams eyes on them is important. We don’t think this aspect will completely disappear, and keeping trust in the loop is something we will continue thinking about.
never gonna have to bug someone to update the docs ever again
Mintlify
Writing docs by hand is archaic.
Autumn
can't live without this product, workflows keep our docs totally updated. you're the best!!!
Mintlify
we can't live without autumn
@hahnbeelee Congrats, for the launch.
The PR merge trigger for codebase sync is the right design decision. Documentation drift usually starts the moment code ships and nobody updates the corresponding page.
But what I would like to know is that.. is the changelog workflow specifically: is it generating entries from commit messages, PR descriptions, or something deeper like actual diff analysis? The quality of auto-generated changelogs depends entirely on what signal it's reading from.
Mintlify
100% agree here. The quality of the changelogs depends on the context you give it.
You can specify non documentation repositories for the agent to have access to. When the agent runs, it clones them to a VM where it can look through commit history on that repo, seeing the diffs.
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.
Mailwarm
Congrats!! Docs are always the first thing to rot when the product ships fast.
Mintlify
@othman_katim one thing that really shocked me since turning this on is the amount of PRs that should have documentation changes. Most engineers on our team completely miss that a rename or rate limit change has corresponding documentation changes.
For us, around 20% of our source code changes solicit a documentation change. Our engineers definitely missed most of those updates.
Self-updating knowledge bases is the right framing — docs rot has always been an attention problem, not a tooling one. Curious how you handle conflicts when the codebase update workflow and the brand-tone workflow want different things in the same paragraph — does the user arbitrate, or does one always win?
Mintlify
@eran_shayshon terrific questions - this is something we've been thinking a lot about!
Right now, if you have any of our maintenance PRs turned on (brand-tone, SEO audit, etc.), those practices will be automatically applied to other workflow outputs via a follow-up commit.
For example, here is a documentation PR we have open right now. You can see there is a follow up commit from workflows adding translations.
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.
Super interesting addition to the Mintlify ecosystem. It’s tough to keep up with documentation when you’re shipping fast, so pre-built automations make a ton of sense. How tightly does this integrate with version control systems like GitHub or GitLab triggers? Can we customize the automated changelog generation based on specific commit tags?
Mintlify
@dreaming_eversince today is only works by listening to PR opens and merges in GitHub or GitLab. We will be shipping more version control triggers soon!