Turn a plain-English workflow into an automation recipe

A store owner describes their process like this: "When someone spends over $150 in
one order, I want to tag them as a VIP in our email tool, send them a thank-you email
with a discount code for next time, and post a note in our team Slack so support
knows to prioritize them if they reach out."

AVAILABLE TOOLS: [WooCommerce (trigger), Uncanny Automator, Klaviyo (email/tagging),
Slack]

Turn this into an implementation-ready automation recipe, thinking through what the
plain description leaves ambiguous:
1. Trigger: the exact WooCommerce event to fire on. "Spends over $150 in one order"
   needs to be order total after discounts, not before, and you should specify which
   order status should fire it (pending vs. processing vs. completed), since firing
   on "pending" risks tagging abandoned or failed orders.
2. Conditions: state the exact conditional logic, including the edge case of a
   partial refund that drops the order below $150 after the automation already
   fired. Should the VIP tag be reversed? Decide and state your reasoning.
3. Actions in order, each mapped to a specific tool: Klaviyo tag, then Klaviyo email
   send (sequence matters if the email template pulls the tag), then a Slack message
   with the customer's name and order total.
4. Failure handling: if the Klaviyo tagging step fails, should the email and Slack
   steps still fire, or should the whole recipe halt? Recommend one and say why.
5. One edge case specific to this exact workflow that the plain description doesn't
   address, such as a customer who crosses $150 through two separate same-day
   orders.

Replace the workflow description and available tools with your own.