Urgent: Error in WhatsApp Cloud API Mapping for WooCommerce Abandoned Cart Flow

[bvolts]

Your Task History ID

IjU3NjUwNTZjMDYzNDA0M2Q1MjZkNTUzMTUxMzA1MTY1NTQzMDBmMzYi_pc

Dear Pabbly Support Team,

I hope this message finds you well. I am writing to report an issue we are currently experiencing with our abandoned cart flow in WooCommerce, specifically related to the WhatsApp Cloud API integration.

We have set up a flow that has been functioning without issues until recently. The problem arises with the mapping of the phone field: although it is correctly mapped in our workflow, the executed flow replaces the correct phone number with a different, incorrect one. This is a critical issue as it affects our ability to communicate effectively with our customers.

You can view the flow here for reference: Workflow Link.

Attached below are screenshots that illustrate the mapping issue we are encountering. We would greatly appreciate your urgent assistance in resolving this matter, as it was not present previously and the current malfunction is impacting our operational efficiency.

Thank you for your attention to this urgent issue. We look forward to your prompt response and solution.

 

[Preeti Paryani]

Hello @bvolts

It appears that WooCommerce recently updated the response keys. The Phone field mapped under the WhatsApp Cloud API: Send Template Message action is now received under the Phone Number key, as observed in the recent task histories.

I have corrected the mapping on your behalf, and the workflow should function properly now. Please monitor it and let us know if the issue persists.

 

[bvolts]

Hi @Preeti Paryani ,

Thank you very much for the prompt response and for resolving the mapping issue with the Phone field in our WooCommerce workflow.

We will closely monitor the corrected workflow and ensure everything functions as expected. I will keep you updated on the performance, and I will reach out if any further issues arise.

Thanks again for your quick and effective support.

Best regards,