# Alerts Alerts enable you to notify your team (or anyone else you want) when test runs pass, fail, or complete with any status. You can send messages to various places like Slack, Microsoft Teams, OpsGenie, or even webhooks.

#### Specifying Criteria in Alerts Testery uses the [SpEL expression language](https://docs.spring.io/spring-framework/docs/3.0.x/reference/expressions.html#expressions-language-ref) syntax for defining criteria in alerts. For example, you can use `environment.key=='foo'` to match a specific environment or `passCount < 100` or `failCount > 100` The following objects/parameters are available for use in expressions: ### Test Run

Parameter	Data Type	Nullable
environment	#environment	false
projectId	Long	false
ended	Boolean	false
priority	Int	true
passCount	Int	false
failCount	Int	false
ignoredCount	Int	false
totalCount	Int	false
timeoutCount	Int	false
totalTestingTime	Int	false
maxRunners	Int	false
hasFlakyTest	Boolean	false
retryFailedTests	Boolean	false
gitRef	String	true
branch	String	true
environmentId	Long	false
testSuiteId	Long	true
statusSetByUser	Boolean	false
includeTags	List<String>	true
excludedTags	List<String>	false
runnerConfigurationId	Long	true
testFilters	List<String>	false
defaultToParallelizeByFile	Boolean	false
testTimeoutSeconds	Int	false
timeoutMinutes	Int	false
recordVideo	Boolean	true

### Environment

Parameter	Data Type	Nullable
name	String	false
key	String	false
archived	Boolean	false
pipelineStageId	Long	true
url	String	true

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.testery.io/get-to-know-testery/alerts.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.