The Trip Status Changes trigger is one of the most flexible automation triggers in TripLoft, but it's also the one most likely to silently do nothing if it's set up wrong. This article covers exactly when it fires, the full list of target statuses you can pick from, and how to spot the most common misconfiguration.
How the trigger works
When you build an automation and choose Trip Status Changes as the trigger, you must also choose one specific target status from a dropdown. The automation fires only when a trip transitions into that exact status — not on any status change, and not on every status the trip passes through on its way there.
"Fires on trip status changes" really means "fires when the trip becomes [target status]." If you want an automation to react to more than one status, you need a separate automation per target status.
The most common misconfiguration
By far the most common issue with this trigger is picking the wrong target status and then wondering why the automation "never fires." Because the trigger only reacts to trips transitioning into the exact status you selected, there's no error, no warning, and nothing in the trip's activity to flag the mismatch — the automation just quietly never runs, because the trip never actually reaches that specific status.
A few ways this shows up in practice:
Wrong target picked at setup: you meant "when a trip is booked" but the dropdown was still on its default of Active when you saved.
Trip skips the target status: if your workflow moves trips directly from Active to Booked without ever passing through some intermediate status, an automation targeting that intermediate status will never fire for those trips.
Trip never reaches that status at all: for example, targeting Archived on an automation meant to run for most trips, when most trips in your pipeline end at Travelled or Paid and are never actually archived.
Note: If an automation using this trigger is already active, changing the target status requires deactivating the automation first — you can't silently swap the target status on a live automation. This is intentional: it stops a running automation's trigger conditions from changing under trips that are already mid-flow. |
If an automation on this trigger seems to "never run," the first thing to check is always the exact target status selected in the trigger panel, and whether trips in your pipeline actually transition into that precise status.