Issues with Zenrows Scrape Using Clay's Account

Joe H. · 2025-03-11T00:42:23.565Z

Unable to run Zenrows scrape using Clay's Zenrows account, including with autoparse turned on and several second delay:

Issues with Zenrows Scrape Using Clay's Account | Clay

12 comments

· Sorted by Oldest

Joe H.
·
·
Channeled
APP
·
·
I'm sorry to hear you're having trouble with the Zenrows scrape. Let's troubleshoot this issue. First, ensure you've set up the integration correctly: 1. In your Clay table, click "Add enrichment" and search for Zenrows. 2. Select the Zenrows action under "Integrations". 3. Use the Clay-managed Zenrows account by default. Then, check your scrape settings: 1. Enter the correct Company URL. 2. Enable Autoparse (you've done this already). 3. Consider enabling other options like "Render Javascript", "Premium Proxy", and "Anti-Bot" for better results. If you're still experiencing issues, please request human assistance by clicking "Talk to a person" for more detailed troubleshooting.
Sources: Zenrows integration overview | Documentation | Clay University Deep Dive: Zenrows Scraping [Limitless Research] - Clay University
Joe H.
·
·
Still getting error after trying all of those suggestins
Joe H.
·
·
https://app.clay.com/workspaces/192229/workbooks/wb_6ZgmeTQTP57Y/tables/t_SvcfxpscmAgd/views/gv_XXkNYDarmgZ7
Joe H.
·
·
Had to use Claygent instead which costed me 2x the credits
Jorge M.
·
·
Has this same problem happen to me last week. Lmk if you find a fix.
Daniel K.
·
·
Hey there, thanks for reaching out! Zenrows issue should be resolved now! Please re-run the errored cells. Sorry for the hiccup.
Jorge M.
·
·
Thanks Daniel!
Channeled
APP
·
·
Sergio P.
·
·
Clay S. Zenrows using Clay's Zenrows account is still not working on my end. Any updates?
Anaum K.
·
·
Sorry for this, it looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
🙏🏾1
Tomi F.
·
·
Good news! Happy to report that we heard back from the team and this issue should be fixed. Try a quick refresh (Cmd/Ctrl + Shift + R) and let us know if the problem has been resolved on your end, or if you still have trouble. Thank you for your patience as we worked on it.

Joe H.
·
·
Channeled
APP
·
·
I'm sorry to hear you're having trouble with the Zenrows scrape. Let's troubleshoot this issue. First, ensure you've set up the integration correctly: 1. In your Clay table, click "Add enrichment" and search for Zenrows. 2. Select the Zenrows action under "Integrations". 3. Use the Clay-managed Zenrows account by default. Then, check your scrape settings: 1. Enter the correct Company URL. 2. Enable Autoparse (you've done this already). 3. Consider enabling other options like "Render Javascript", "Premium Proxy", and "Anti-Bot" for better results. If you're still experiencing issues, please request human assistance by clicking "Talk to a person" for more detailed troubleshooting.
Sources: Zenrows integration overview | Documentation | Clay University Deep Dive: Zenrows Scraping [Limitless Research] - Clay University
Joe H.
·
·
Still getting error after trying all of those suggestins
Joe H.
·
·
https://app.clay.com/workspaces/192229/workbooks/wb_6ZgmeTQTP57Y/tables/t_SvcfxpscmAgd/views/gv_XXkNYDarmgZ7
Joe H.
·
·
Had to use Claygent instead which costed me 2x the credits
Jorge M.
·
·
Has this same problem happen to me last week. Lmk if you find a fix.
Daniel K.
·
·
Hey there, thanks for reaching out! Zenrows issue should be resolved now! Please re-run the errored cells. Sorry for the hiccup.
Jorge M.
·
·
Thanks Daniel!
Channeled
APP
·
·
Sergio P.
·
·
Clay S. Zenrows using Clay's Zenrows account is still not working on my end. Any updates?
Anaum K.
·
·
Sorry for this, it looks like we've got a bug on our hands. I've escalated this to our engineering team to help look into it. We'll follow up here as soon as we know more!
🙏🏾1
Tomi F.
·
·
Good news! Happy to report that we heard back from the team and this issue should be fixed. Try a quick refresh (Cmd/Ctrl + Shift + R) and let us know if the problem has been resolved on your end, or if you still have trouble. Thank you for your patience as we worked on it.