Mintlify Automation & Approval Workflows
Run Mintlify on autopilot. Keep the veto.
14 actions
Mintlify runs doc deployments and background agent jobs that open pull requests. Rills queues those actions for approval before they execute.
Interactive. No signup. 14 days free · approvals always free.
Most automation fires first, asks later. Rills shows you the change before it ships.
Every consequential development action from Mintlify arrives on your phone first. Approve in seconds. Decline without explaining yourself. Workflows wait, paused at zero cost, until you decide.
Queue (3)
Trigger 3 doc updates with changelog and API reference fixes?
3 updates · 2 changelog entries, 1 reference fix
Same pattern as last week's approved batch
No negative feedback on these pages in past 30d
Free to wait. Free to think.
Approvals and logic don't cost a credit. Pause a workflow for three hours or three weeks. The price is the same: zero. You only pay when something real happens: an AI call, an outbound action.
Approve from your phone in five seconds.
Swipe right when you're sure. Decline when you're not. Between meetings, mid-coffee, on the train. No dashboard to babysit, no inbox triage, and no surprise send you find out about after it's already out the door.
Clear runs stop waiting on you.
Every run is scored against your review step. The ones that clearly match your judgment run above your threshold without a tap; the borderline ones still come to the queue. Autonomy is earned run by run, never switched on for good.
About Mintlify automation
A doc update ships while you're still drafting the next section, and an agent message answers a customer with half-baked advice. Mintlify automation without guardrails means your docs, previews, and assistant conversations — your communication backbone — go out before you've had a chance to catch the mistake.
When Mintlify runs unsupervised
Documentation, previews, and agent responses all move fast when you're not watching. A single unchecked action can ship broken copy, outdated answers, or a preview that exposes unfinished work.
- Trigger Preview: a broken link ships in a preview, and the page goes live before you can fix it.
- Trigger Update: a changelog with placeholder text pushes live, and the mistake is customer-facing.
- Send Agent Message: an AI assistant sends a confusing answer to a user, and the conversation goes sideways.
- Get Feedback: a negative feedback loop sits unaddressed for weeks, and the same complaint surfaces again.
What Rills does inside Mintlify
Rills intercepts the critical actions before they go live. It catches trigger previews, doc updates, and agent messages, then surfaces them for your approval with the context you need.
Preview deploys, updates, and agent messages queue up for your approval, and nothing ships until you say yes.
Why Mintlify has no triggers and how Rills fills the gap
Mintlify doesn't expose webhook triggers, so you can't just react to doc changes in real time. Rills polls the operations you care about on a schedule, or you can fire checks from other tools.
- Poll Get Update Status on a schedule: if a doc update has been pending for more than 4 hours, Rills proposes a Trigger Update to push it.
- Check Get Feedback daily: if a page has a new negative feedback score below 3, Rills alerts you to review and maybe send a follow-up agent message.
- Use an upstream trigger from Slack or email: someone flags a docs issue in a channel, and Rills queues a Trigger Preview or Agent Job to investigate.
- Poll Get Search Queries: if a search term shows zero results, Rills suggests creating a new doc page via Trigger Update or Agent Job.
What Rills can do in Mintlify
6 of 14 actions across reads, writes, and updates.
- 01
Create Agent Job
Start a background documentation agent job from a natural-language prompt.
- 02
Get Agent Job
Retrieve the status and details (status, PR link, model, source repo/ref) of a docs agent job.
- 03
Get Assistant Caller Stats
Get assistant query counts broken down by caller type (web, api, other, total) for a date range.
- 04
Get Assistant Conversations
Export the AI assistant conversation history (question, answer, cited sources, resolution status) for a Mintlify project, optionally filtered by date.
- 05
Get Feedback
Export a project's user feedback (thumbs / contextual comments / agent feedback), optionally filtered by date, source and status.
- 06
Get Feedback By Page
Retrieves aggregated feedback counts (thumbs up/down, code, total) for each documentation page path within a specified date range, helping you quickly assess which content resonates or frustrates your users.
Common questions about Mintlify automation
How do I automate Mintlify feedback responses without AI going rogue?
Rills queues AI-drafted responses to your feedback, but nothing goes out until you swipe. You review the draft on your phone: see the original feedback, the proposed reply, and the confidence score. Approve to send, or discard if it’s off. No auto-reply ships without your say-so. You pay only for the send action.
Can I approve Mintlify assistant messages from my phone before they send?
Yes. When Rills detects a conversation that needs a follow-up, it proposes an agent message. The proposal lands in your mobile approval feed with the user context and draft text. You decide from your phone. Swipe to approve and the message fires; reject and it’s gone. No message goes out until you give the thumbs-up.
How do I trigger doc updates based on Mintlify search queries?
AI spots rising search queries that return little or nothing and proposes a new page or an update. The proposal shows you the query pattern, the suggestion, and the affected pages. You review it on your phone, tweak if needed, and approve. Rills then triggers the Mintlify update. You pay only when the update actually fires.
How do I set up mobile alerts for Mintlify page views and approve AI actions?
Rills monitors your page views, feedback, and search queries for anomalies or opportunities. When it finds something worth acting on, it proposes a concrete step: send a message, trigger a preview, or update docs. You get a notification on your phone, see the reasoning, and swipe to approve or reject. Approvals and logic are free.
How is Rills different from Zapier for Mintlify automation?
Zapier executes tasks immediately. Rills inserts a mandatory human review step. Before any Mintlify action, like sending an agent message or triggering an update, you see the proposal on your phone. Zapier fires blind; Rills gives you a veto. Confidence scoring learns your approvals, so routine decisions can move faster while you keep control.
Why use Rills instead of Make for Mintlify?
Make automates, but it doesn’t pause for your judgment. With Rills, AI proposes the Mintlify action and you approve from your phone before anything ships. That’s the difference between waking up to a misfired update and waking up to a decision waiting for your swipe. Approvals are free; you only pay for real actions.
Does Rills support Mintlify webhooks?
Rills doesn’t rely on webhooks. It proactively checks your Mintlify data for feedback, conversations, and search queries. When it finds something worth acting on, it proposes a step and waits for your mobile approval. No missed webhook, no blind triggers. You stay in the loop without babysitting a dashboard.
How much does Rills cost for Mintlify automation?
Approvals and all workflow logic are free. You only pay when Rills performs a real action, like calling the Mintlify API to send a message, trigger an update, or create a job. There’s no charge for reviewing proposals, rejecting them, or letting the AI learn your patterns. You’re in control, and the cost only kicks in when you say yes.