No trigger when custom fields change on users or orders
Automation tools have no trigger for custom field changes on users, orders, customers or subscriptions, so updates from other plugins go unnoticed
Tier II · Emerging Problems that are still building up.
4 public reports · first reported 21 February 2019 · last reported 10 August 2025
What's going wrong
Store owners who keep extra data in custom fields on users, orders, customers and subscriptions report that automation workflows cannot start when a field is added, changed or removed.
AI-assisted: written with the help of AI from the reports. The idea report has the full summary.
In the idea report
- The full summary.
- The products the 4 reports are about, and how many came each month.
- Related problems.
No business has been found with this problem yet, so the report has no contacts. All sales are final — no refunds. Pricing.