Scheduled tasks and checks

Automate link validation, content audits, and other recurring checks for your docs.

Mintlify deployments are event-driven (triggered by Git pushes), but you can use GitHub Actions or GitLab CI to run scheduled checks on your docs independently of deploys.

Scheduled link validation

Broken links erode trust and hurt SEO. Set up a weekly or daily link check to catch broken links before readers do:

name: Link check
on:
  schedule:
    - cron: '0 9 * * 1'  # Every Monday at 9am UTC

jobs:
  link-check:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Check links
        uses: lycheeverse/lychee-action@v1
        with:
          args: --verbose --no-progress './**/*.mdx'

Fix broken links in a PR — the preview deployment lets you verify the fix before merging.

Scheduled content audits

Use a scheduled job to check for pages that haven’t been updated in a long time:

# Find MDX files not modified in the last 90 days
git log --all --format="%ai %H %s" -- "**/*.mdx" | \
  awk -v cutoff="$(date -d '90 days ago' +%Y-%m-%d)" '$1 < cutoff {print $0}'

Route the output to a Slack channel or create GitHub issues to track stale content.

Scheduled deployments

If you reference external data (an OpenAPI spec, a changelog, etc.) that updates independently of your docs repository, you can trigger a manual redeploy on a schedule:

name: Scheduled redeploy
on:
  schedule:
    - cron: '0 6 * * *'  # Daily at 6am UTC

jobs:
  redeploy:
    runs-on: ubuntu-latest
    steps:
      - name: Trigger Mintlify redeploy
        run: |
          curl -X POST https://api.mintlify.com/v1/projects/${{ secrets.MINTLIFY_PROJECT_ID }}/deploy \
            -H "Authorization: Bearer ${{ secrets.MINTLIFY_API_KEY }}"