IntegrationsIntegrations and notifications

Integrations and notifications

Connect issue trackers, deployment events, and run notifications.

AegisRunner groups integrations by what they do. Open Project setup in the project you want to connect.

Issue trackers

Under Integrations, configure GitHub or Jira with access to the intended repository or project. The form explains the required credentials and destination fields.

Choose whether failed tests should create issues and whether issues should close after a passing run. Review the destination and automation switches before saving.

Start with a known test run and confirm the resulting issue lands in the correct place.

Deployment automation

Under CI/CD, configure a supported deployment integration such as Vercel or Netlify, or generate a CI token for your own pipeline.

Use the webhook URL and verification settings displayed by the integration. A deployment must be reachable by the scanner or executor before tests can succeed.

For a pipeline you control, follow the CI guide.

Notifications

Open Project setup → Notifications and select the available channels and events appropriate to the team. Test the configuration before relying on it for release monitoring.

Integration and notification availability depends on your plan. Keep connected credentials current and remove a connection when it is no longer used.

Avoid duplicate automation

If both a deployment webhook and a CI job trigger the same suites, a single deployment may start multiple runs. Pick the intended trigger and inspect Runs after enabling it.

For complete setup steps, choose GitHub and Jira, Notifications, Custom webhooks, or Deployment webhooks.