# Automation Trigger: Condition Based Trigger

**URL:** https://community.glideapps.com/t/automation-trigger-condition-based-trigger/78860
**Category:** Feature Requests
**Created:** [December 30, 2024, 4:15pm UTC](https://community.glideapps.com/t/automation-trigger-condition-based-trigger/78860 "2024-12-30T16:15:06Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Connor\_Finlayson](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/connor_finlayson/32/79079_2.png) [@Connor\_Finlayson](https://community.glideapps.com/u/Connor_Finlayson)
#### Post date: [December 30, 2024, 4:15pm UTC](https://community.glideapps.com/t/automation-trigger-condition-based-trigger/78860/1 "2024-12-30T16:15:06Z")

</div>

In line with all the new automation triggers available via workflows, I wanted to share one more that I think would really take things a step further:

Condition-based triggers

Use case:  
Imagine you are keeping track of usage (i.e. tokens for api calls or something like that). When they hit limit, would be good to trigger an automation that changes other data in the app.

---

<div class="post-metadata">

### Author: ![MaximeBaker](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/maximebaker/32/80877_2.png) [@MaximeBaker](https://community.glideapps.com/u/MaximeBaker)
#### Post date: [December 30, 2024, 8:22pm UTC](https://community.glideapps.com/t/automation-trigger-condition-based-trigger/78860/2 "2024-12-30T20:22:33Z")

</div>

You need to vote on your own post 😉