Hello HunkyBill and thanks for the response.
Could you please specify what I could do with the customers/update event? Will it tell be telling me that the update is affecting the password? From the documentation it doesn't seem to be so..
Can you share your knowledge please?
You asked what event is triggered when Customer records are updated. If password changes are not triggering updates, then you're out of luck.
Curiosity killed the cat. Why do you care when a customer changes their password? Why is that interesting?
My customer (which is a shopify store owner) wants to send SMS to the user to inform him that password was changed.
I am the developer of the sms app for shopify https://apps.shopify.com/smshare
Now you are aware of everything ^^
So if a customer changes their own password, you wish to inform them of that via a text message? They already have had to deal with requesting the change, and they get an email from Shopify in the process. How does sending them an SMS make their life better?
In some countries, stores prefer SMS over email to exchange with customers. Having this "password change" action logged in the SMS conversation is good for #CustomerExperience. Store owners can add in the message something like: "... if you need help with your account, please call us or reply to this SMS". #engaging
This is also a nice #security feature. So if email account is hacked, customer will receive the notification of password change by SMS.
Those are some use cases that comes to my mind, but i believe there are some others.
I do not disagree with you. I have helped merchants bank a million dollars plus with SMS messages thrown into the mix for #CustomerExperience.
I am simply pointing out that you probably won't be getting this particular event in your App unless Shopify chooses to add a boolean attribute to the Customer Update webhook payload labelled "password_reset" or similar.
This is what i come for today: Shopify please add this attribute!
How can i make shopify developers hear me?
I am still waiting for the customer who would throw a million dollars at me with SMS for #CustomerExperience 🙂
A million is not that tough. Sell a compelling App to 2000 merchants for $500 and you've hit your target. 🙂
I know this is late but worth mentioning, in case you haven't found a solution or someone else is looking.
Aside from HunkyBill's generous ideas, here is a way you could do it, off the top of my head:
On the customer update password page, add a hidden field which will add a custom tag, i.e "changed-password". Then you will check in your webhook.
Failing that, i.e you cant get a property to update on change pass, then add some script to do this on your end via the api. You can do this however you want, whether you do this before the form is posted or after - just fire a request to your own server indicating the user who just changed their password.
Just got to think outside the box with Shopify a bit sometimes. It's easy to get tunnel vision when you're limited to Shopify's scope with things.
@nullable. Have you tested that pattern? If you embed a hidden field with a tag like "CHANGED", does the Shopify password update process actually accept that hidden field value and update customer tags? Please do report as this underpins your out-of-the-box approach, and if true, would present an chance that this pattern of monitoring password changes via customer update webhooks could work.
I did a 30 second test w/ the customer[tags] on reset form and it didn't work. If you really wanted to do this my suggestion would be, add ScriptTag tracking code (+ Cookies/LocalStorage + XHR calls) combined w/ tracking the customers/update webhook, which checks:
== user123's password was changed