Skip to main content

I have a Zap with a Whop trigger on Payment Succeeded.
My next step to to Retrieve a Product from step one.
This works when testing. Here is an image of the configure step and the Data in and out on the test step.


 



When the Zap runs after being published the Retrieve a Product step hits an error.

 

This Whop step hit an error

Required field "ID" (id) is missing.



This is what the configure step looks like.
 



This is the explanation of the error i receive in Zapier.

 

The error you're encountering indicates that the "ID" field required by the "retrieve_product" action in the WhopCLIAPI@1.5.1 step is missing or not correctly populated. The input data shows that the "id" field is set to "{{285653874__product}}", which suggests that it's expecting a dynamic value from a previous step, but it seems that the placeholder isn't being replaced with an actual product ID.

To resolve this issue, ensure that the previous step (TableCLIAPI@1.16.5) outputs the necessary product ID that the WhopCLIAPI step requires. You may need to adjust the configuration of the previous step to include the product ID in its output. If the product ID is not part of the output, consider adding a step before the WhopCLIAPI step to fetch or calculate the product ID. Use Zapier's "Formatter" tool to extract or transform data if needed, and ensure that the correct field is mapped to the "id" input in the WhopCLIAPI step.

Hi ​@Jim_A 

Check your Zap Runs history details to see the DATA OUT from Zap step 1.

Did it return a Product value?

https://zapier.com/app/history/

 

If no, then try adding a Filter step to prevent the Zap error.

https://zapier.com/apps/filter/help


This is what is shown form step 1.

I am curious if it could be because in step 1, it is called ‘Product’, as well as the input ID for step 2 BUT the data in on step 2 is ‘Product ID’

 

 

 


@Jim_A 

The Product variable value is definitely a product ID. (e.g. prod_XXX)

 

Can you provide more screenshots that show more context about the DATA IN/OUT for each Zap step in the Zap Run with the error?


 

 

 

Step 1 Data in/out
 

 



Step 2
 

 



 

Here is step 2 during testing when it works

 

 

 


@Troy Tessalone 

 

 

 

 



And here is what step looks like when it works during testing.

 

 


@Troy Tessalone 

Trying to respond, posts are being flagged for mod review.


Hey ​@Jim_A, looks like your posts were since approved 🙂

Thanks for sharing those helpful screenshots here. From the looks of it the Product field that is selected in the Zap doesn’t match the field that contains the ID when the Zap runs live:
7ad3a0c4074cf20c4fe75417b3557c14.png
40c6c58cd3aded7440beb3d5d52c3721.png

Can you try selecting the Product ID field instead and then replay the errored Zap run to see if that then is able to go through successfully? 


@SamB 

Thank you for replying. I have since been able to get my zaps working. The issue I was running into though was that in the editor, If I entered something into the field and it worked when I tested in editor, it would not work when ran live.

And the on the other side, If I chose a field that did not work in the editor, like in the image above where you see ! 1. Product, it DOES WORK when run live.

I have had this happen with almost all of the Whop steps I use.


Yay! So pleased to hear that your Zaps are working now, ​@Jim_A🎉

It does seem like the fields output from Whop’s test records don’t match those that are received during live Zap runs. I’m not sure if this is intentional on Whop’s end, so I can’t say for certain whether it is due to a bug or is more of a feature request. Either way, I’d recommend reaching out to our Support team to flag this to Whop’s developers so that the fields can be made consistent.

If anything else comes up, feel free to reach back out. Until then, happy Zapping! ⚡️