PingBase GitHub Action

Example workflow

name: Deploy

on:
  push:
    branches: [main]

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Pause PingBase monitors
        uses: pingbase/pause-monitor-action@v1
        with:
          api-key: ${{ secrets.PINGBASE_API_KEY }}
          monitor-ids: "mon_abc123,mon_def456"

      - name: Deploy to production
        run: |
          # your deploy command here (wrangler deploy, fly deploy, etc.)

      - name: Resume PingBase monitors
        if: always()   # resume even if deploy fails
        uses: pingbase/resume-monitor-action@v1
        with:
          api-key: ${{ secrets.PINGBASE_API_KEY }}
          monitor-ids: "mon_abc123,mon_def456"

The if: always() on the resume step ensures monitors are re-enabled even if the deployment fails.

Or use the API directly

If you prefer not to use the marketplace action, call the API with curl:

- name: Pause monitors
  run: |
    curl -s -X PATCH https://pingbase-worker.workers.dev/api/monitors/mon_abc123 \
      -H "Authorization: Bearer ${{ secrets.PINGBASE_API_KEY }}" \
      -H "Content-Type: application/json" \
      -d '{"paused": true}'

- name: Resume monitors
  if: always()
  run: |
    curl -s -X PATCH https://pingbase-worker.workers.dev/api/monitors/mon_abc123 \
      -H "Authorization: Bearer ${{ secrets.PINGBASE_API_KEY }}" \
      -H "Content-Type: application/json" \
      -d '{"paused": false}'

Find your monitor IDs

curl https://pingbase-worker.workers.dev/api/monitors \
  -H "Authorization: Bearer YOUR_API_KEY"

# Response includes "id" for each monitor, e.g.:
# [{"id": "mon_abc123", "name": "Production API", ...}]