Configure process schedules and triggers for continuous autonomous verification.

Certyn automation is process-driven: define a process, then choose how and when it runs.

Scheduled runs

Processes support:

Go to Processes and click New Process (or open an existing process and click Settings).

Select tests with tags such as smoke or regression.

Set schedule type and timing (or cron expression).

Trigger on environment version change

Processes can run automatically when an environment version changes. This is ideal for verify-after-deploy automation.

Typical setup:

In process settings, enable Automatic Triggers for the target environment(s).
After deployment, update environment version in Certyn.

Add changelog text

Include a short changelog with each version update. It improves auditability and incident triage.

If your pipeline must explicitly gate merge or promotion:

On GitHub Actions, use certyn/action@v1.
On other CI systems, use:
- certyn run smoke --project <project-slug> --environment <environment-key>

For each environment, choose one primary deploy trigger:

Use both only if you intentionally want two independent verification events.

See the CI/CD section for concrete workflow templates.