Error on " readiness_state_id "

i am Having problem with Etsy Node

Error message:
exec command error: request to pd server code 500 error: {“error”:“A readiness_state_id is required for physical listings.”}

But in Node There not section to set

readiness_state_id

Yeah, I’m running into the same issue too. It seems like Etsy recently made the readiness_state_id field mandatory for physical listings, but there’s no clear option to set it in the Node module yet. Kinda frustrating hopefully they’ll patch it soon or update the docs to show how to include that field properly.

Hello! There is already a planned update from the developers, and it will be released soon.

In the meantime, as a quick solution, you can set up a manual integration using HTTP or JS. Here’s a link for reference: How to Create Missing Actions in Latenode.

As soon as the update is released, I will notify you

Hi! The issue with readiness_state_id has been fixed. You can check it now.

If you have any other questions, we’ll be happy to answer them.

A readiness_state_id is required for physical listings.

If the fix rolls out slower than hoped, I’ve had some luck dropping a quick manual patch with a small HTTP call before the main Etsy node to set missing fields. It’s a bit of tape and glue, but it kept my flows from stalling. Once the updated node lands, swapping it out is painless. Kind of a keep-things-moving trick till the dust settles.

If the fix rolls out slower than hoped, I’ve had some luck dropping a quick manual patch with a small HTTP call before the main Etsy node to set missing fields. It’s a bit of tape and glue, but it kept my flows from stalling. Once the updated node lands, swapping it out is painless. Kind of a keep-things-moving trick till the dust settles.

If the fix rolls out slower than hoped, I’ve had some luck dropping a quick manual patch with a small HTTP call before the main Etsy node to set missing fields. It’s a bit of tape and glue, but it kept my flows from stalling. Once the updated node lands, swapping it out is painless. Kind of a keep-things-moving trick till the dust settles.

Late to the party, but I’m curious: how are everyone’s experiences with the new “Pay as You Go” model on Latenode? Are the changes making a significant difference in your setup, especially with the new integrations? And does anyone have thoughts on the removal of the Soax - SERP: Google Search node? Would love to hear your insights!