> ## Documentation Index
> Fetch the complete documentation index at: https://docs.quivly.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Describe exactly what should start a Play

> Turn a condition such as a lost deal or a custom-field change into a reviewed Play trigger.

[Back to What's new](https://docs.quivly.ai/changelog.md)

[<time dateTime="2026-10-28">October 28, 2026</time>](https://docs.quivly.ai/updates/2026-10.md)

v1.33.0

# Describe exactly what should start a Play

Turn a condition such as a lost deal or a custom-field change into a reviewed Play trigger.

Under **When to run → When data changes**, describe a condition and choose **Add**. Quivly matches it to available records and fields, including custom fields. Review the resulting conditions before publishing.

**Suggest triggers** starts from the successful outcome and Skill; **Improve triggers** suggests changes to an existing list that you can choose to apply. Only supported, available sources can start the Play. Use a schedule for recurring checks or inactivity; switching to a schedule replaces the data triggers.

See [Play setup](https://docs.quivly.ai/product/plays.md#creating-a-play).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.