Automation · Operations and reporting
Fix on WhatsApp an outdated step in your Mintlify documentation
When a customer reports a step that no longer works, an AI agent finds it in your Mintlify docs, fixes it and shows you the pending change.
How do I quickly fix a step in my Mintlify guide that a customer reported as broken?
Someone on your team forwards the customer's report to the Met on WhatsApp, for example "step 3 says the button is in Settings and now it is in Profile". The Met searches that text across every page of your documentation, opens the full page and finds where it sits in the navigation. It applies a targeted edit with the corrected text and lists the pending changes against the deploy branch to show you what changed. According to Mintlify, that change stays unpublished until someone on your team publishes it; the Met does not publish it in this procedure.
What starts it
When someone asks for it
It starts when someone on the team forwards a customer's report with the broken step to the Met on WhatsApp. The Met does not review the documentation on its own.
A manual task: someone on the team runs it with a button, or asks the Met for it in chat.
Who runs it
Internal Met that maintains your Mintlify documentation
This is not a named, seeded Met. It is an internal Met with Mintlify connected, for the support team or the agency that maintains the docs: its work ends when the fix is pending publication and it shows you the change.
Run by the content and social Met
Channels: WhatsApp
What you need connected
- Mintlify Automate and collaborate
5 steps · 5 tools
The procedure, step by step
Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.
- 1
Search the reported text
The Met searches every page on the deploy branch for lines matching the text the customer reported, to know which pages it appears on.
- 2
Open the full page
The Met reads the page's full MDX to understand the step in context before changing anything.
- 3
Find the page in the navigation
The Met walks the navigation tree to confirm which group or tab the page is in and tell you where the customer will see it.
- 4
Apply the targeted fix
The Met applies a targeted edit only to the step's text, without rewriting the page. The edit stays as an unpublished change.
- 5
Show you the pending change
The Met lists the pending changes against the deploy branch and replies on WhatsApp with what changed, so someone can review and publish it.
Before you start
What you need ready
The Met solves none of these for you. If one is missing, the automation stops there.
-
Mintlify connected in Met
In Met, open Connections → Mintlify → Connect and sign in with an account that can edit your documentation project.
-
An internal Met on WhatsApp
Assign the connector to a Met that only serves the team, not the one that talks to customers, because it can edit your documentation pages.
-
The project in the instructions
If your organization has several Mintlify projects, write in the Met's instructions which one holds the documentation it handles.
The limits
What this automation does NOT solve
Better said here than discovered halfway through the rollout.
-
It does not publish the fix. It stays as an unpublished change in Mintlify until someone on your team publishes it.
-
It does not confirm the product changed. The Met fixes the text with what is reported; checking in the app that the new step is right is your team's job.
-
It does not reply to the customer on its own. In this procedure the Met serves your team; telling the customer it is fixed is another conversation.
-
It does not update screenshots. The fix is text only, in the page's MDX.
FAQ
Questions about this automation
No. According to Mintlify, what is edited on the deploy branch stays unpublished until someone publishes it. If your project requires a pull request on that branch, Mintlify refuses the direct edit and changes nothing; this procedure does not create branches.
The search returns every match. The Met tells you which pages it is on and fixes the ones you name, one edit per page.
The listing has the rewrite action, but this procedure only uses the targeted edit so the rest of the page stays untouched.
Keep going
Other automations built on the same tools
Operations and reporting
Turn off on WhatsApp the feature flag that breaks the checkout in LaunchDarkly
How do I quickly turn off a feature flag that broke the checkout without opening LaunchDarkly?
- Starts:
- when someone asks for it
- Steps:
- 5, with 7 real tools
- Needs:
- LaunchDarkly
Operations and reporting
Build a department's higher education report without opening SNIES
How do I pull SNIES enrollment and program figures without going into the portal?
- Starts:
- when the customer writes
- Steps:
- 5, with 5 real tools
- Needs:
- SNIES
Operations and reporting
Build your team's org chart in Lucid on WhatsApp and share it
How do I build my business's org chart without sitting down to draw it?
- Starts:
- when someone asks for it
- Steps:
- 6, with 6 real tools
- Needs:
- Lucid
Operations and reporting
Tell customers on your status page that the store is down, asking on WhatsApp with Better Stack
How do I tell my customers my online store is down without opening Better Stack?
- Starts:
- when someone asks for it
- Steps:
- 6, with 6 real tools
- Needs:
- Better Stack
Want this automation running on your own data?
We will show it to you with your accounts connected, not with a canned demo.