Skip to main content

I am trying to update my CRM with customer history lifetime revenue every time an order is placed.  It appears that Total Orders is available but I am not seeing anything regarding total dollars purchased.  I am assuming that there is something that I can do on the Woocommerce side to get that to show up but I just don’t know what.  Please help.  Thank you in advance

Hi ​@JamieV121, welcome to the Community! 🎉

I wouldn’t have expected a customer’s total lifetime revenue value to be supplied when the WooCommerce Order trigger runs as that should only return the information for the order that was just placed. As it’s information that relates to the customer rather than the order you might be able to obtain it via a Find Customer WooCommerce search action. But if that doesn’t give access to that information either, then you could try using an API Request (Beta) action to obtain the lifetime revenue amount, assuming WooCommerce’s API allows access to that information via their API. API Request actions are a bit more advanced as you’d need to reference WooCommerce’s API documentation in order to get them set up correctly but we have a general guide on how to use them here which you might find helpful: Set up an API request action

If not, then you could use a Formatter action to add the order value to the existing customer revenue amount that’s in the CRM. To find the existing revenue amount for the customer that’s stored in the CRM you’d need to use a “Find Customer” type of action for the CRM app you’re using, then pass that to the Formatter action. You can learn more about using Formatter to perform calculations here: Use spreadsheet-style formulas in Zaps.

Hope that helps to get you pointed in the right direction. If you run into any issues on that or have further questions do let us know!


I apologize that I was not more clear.  I am currently using a Find Customer and getting all of the information I can which is what is giving me Lifetime number of orders but not total dollars.  I will try the API request.  Thanks,


Ah, I see! Thanks for Clarifying that, ​@JamieV121🙂

Please do keep us updated on how things go with that API Request action—fingers crossed it’ll do the trick! 🤞


Reply