Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify-mintlify-maintenance-followup-1778638591.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

Workflows run the agent automatically on a schedule or in response to pushes to a repository. Each workflow defines a prompt for the agent and a trigger for when to run it. Workflows support both GitHub and GitLab repositories. When a workflow runs, the agent clones any specified repositories as context and follows the prompt.
Use workflows that run on a schedule to automate recurring tasks, like publishing changelogs or checking for grammar and style issues.Use workflows that run on push events to automate reactive maintenance tasks, like updating API reference documentation or identifying documentation updates needed for new features.

​
Trigger types

Workflows support two trigger types.
  • Schedule (cron) — Run on a recurring daily, weekly, or monthly schedule. Workflows queue within 10 minutes of the scheduled time.
  • Push events — Run when changes push to a specific repository or branch, including pull request merges and direct pushes.
You cannot combine trigger types in a single workflow. Each workflow has exactly one trigger.

​
Maintenance follow-up

Some workflow templates apply documentation best practices across your project. These run as a follow-up pass on pull requests opened by other workflows so that maintenance checks aren’t skipped on bot-authored PRs. Maintenance workflow templates include:
  • Translations — Mirror prose changes into other configured languages.
  • Writing style — Enforce consistent voice, tone, and formatting.
  • Typo check — Catch spelling, grammar, and broken markdown.
  • Broken link detection — Find and fix links that don’t resolve.
  • SEO metadata audit — Check titles and descriptions for length and uniqueness.
When another workflow (for example, a changelog or feature docs workflow) opens a pull request, the agent applies every enabled maintenance workflow inline and pushes the fixes as additional commits to the same branch. The pull request is finalized — and automerge runs, if enabled — only after the maintenance pass completes. To enable a maintenance pass, turn on the corresponding template from the Workflows page. Maintenance workflows still run on their own trigger as usual; the follow-up behavior is additive.

​
Usage limits

Each workflow can run up to 500 times per day. Hobby plan projects have an additional limit of 100 total workflow runs per month. Runs that fail do not count towards these limits.