SureCart Data Issue

Status: Open · Asked by Marlon M on · 0 views

Marlon M — Question ·

Hi, I am using SureCart orders or purchases as a trigger; however, bizarrely, the captured data doesn't include any customer details such as name, email and product purchased, so how am I supposed to map the action steps?

What am I missing here?

I tried testing multiple times and still the same thing, as you will see from my webhook data.

Please let me know.

Thanks.

Marlon

Hrishabh Tiwari — Reply ·

Hi @Marlon M ,

Thank you for sharing the workflow URL and granting us access.

We reviewed your workflow and noticed that the SureCart Order trigger only provides order-level data, which is why customer details (name, email, product details) were not available for mapping.

To resolve this, we have added the required action step in your workflow to fetch the customer details using the checkout/customer information from SureCart. You should now be able to see and map the customer name, email, and related details in the subsequent action steps.

Please test the workflow again and let us know if everything is working as expected or if you need help with mapping any specific fields.

Marlon M — Reply ·

Ok, thank you. That wasn't expected, as other platforms include this information in just 1 step (Order created), so not sure why you require this extra step. Please let me know if there are plans to include this in the first step.

Arshil Ahmad — Reply ·

For now, the SureCart: Order Created trigger event returns only order-level information. You need to use SureCart: Get Checkout by ID action step to get the additional information.

If you would like the SureCart trigger step to fetch additional information as well, you can submit your request on our dedicated platform:

https://roadmap.pabbly.com/b/Update-Existing-Application

Our integrations team will review your request and, if possible, make the desired changes.

Thanks & Regards,
Arshil Ahmad
Customer Support Associate
? Pabbly.com
?Rate your support

Back to all forum threads · Log in to reply