CI Integration
Run Monito from GitHub Actions or a deploy webhook.
Choose an integration
Use the CLI when the pipeline should wait for results and fail on test failure. Use a deploy webhook when a deployment should trigger Monito in the background and leave results in the dashboard.
GitHub Actions with the CLI
Create a long-lived API key:
Store the printed key as a GitHub Actions secret named MONITO_TOKEN.
project run exits with code 1 when any scenario fails, so the workflow fails automatically.
Run one scenario instead:
Deploy webhook
Rotate a project webhook secret from an authenticated shell:
The response contains webhookUrl and webhookSecret. Store them as deploy-platform secrets, for example MONITO_WEBHOOK_URL and MONITO_WEBHOOK_SECRET.
Trigger the webhook after deployment:
The webhook returns 202 Accepted once runs are queued. It does not block the deployment for pass/fail results; review the dashboard for the run output.
Run only selected scenarios: