AutomateWoo 6.8.2 adds order and subscription address rules, so you can trigger workflows based on where an order is going rather than only who placed it. It also tightens how unsubscribe links identify a recipient.
The new rules cover billing and shipping addresses on both orders and subscriptions, including shipping phone numbers. That opens up workflows you couldn’t build before: a delivery-region follow-up that only goes to customers in a particular city or postcode, a different post-purchase sequence for orders shipping to a business address versus a home address, or an SMS workflow that checks a shipping phone number is present before it fires. Previously you could segment on the customer and the order contents, but not on the destination.
There’s also a change worth knowing about if you use unsubscribe links. The communication preferences unsubscribe endpoint no longer identifies a recipient by email address, and the legacy user URL parameter is now ignored — unsubscribe links must include the customer key instead. Links generated by AutomateWoo already include it, so normal sends are unaffected. If you hand-built unsubscribe URLs, hardcoded them into a template, or stored them outside AutomateWoo, those links will stop resolving to the right subscriber and need regenerating.
One smaller fix: the “Order – Custom Field” workflow rule no longer shows a redundant value field when the operator is set to “is blank” or “is not blank,” so the rule editor stops asking for a value it was never going to use.
How to get it
Update to AutomateWoo 6.8.2 in your WooCommerce dashboard. The new address rules are available when you add a rule to any order or subscription workflow. This release requires WordPress 7.0 or higher — update WordPress first if you’re on an older version. If you maintain unsubscribe links outside AutomateWoo, regenerate them so they include the customer key.