Automations currently support conditions, but it would be extremely helpful if a single-select field could act as a condition that controls the behavior of a button automation.

Example Use Case: Client Payment Plans

Depending on the selected payment plan, the same button should be able to trigger an export of a different invoice PDF.

Button + Early Invoice selected → Export Early Invoice PDF

Button + Payment Plan selected → Export Payment Plan Invoice PDF

Button + Bill on Completion selected → Export Bill on Completion Invoice PDF

Currently, achieving this requires building multiple separate automations to replicate what could theoretically be handled by a single button with conditional logic tied to a single-select field.

Allowing button automations to reference the value of a single-select field would simplify workflows, reduce redundant automations, and make button actions far more flexible.