Issues with Claygent Credit Charges and Access Problems | Clay

Issues with Claygent Credit Charges and Access Problems

Claygent doesn’t seem to be working, How can it charge me that many credits to state that it cannot access the link I provided?

4 comments

Abolade O.
·
·
https://app.clay.com/workspaces/394375/workbooks/wb_SZsfFuMdoy8j/tables/t_MhfcziZfrY6f/views/gv_8TzGZFV8GUpv
Channeled
APP
·
·
💤 You've caught us outside of our support hours (9am-9pm EST), but don't worry - we'll be back in touch within 24 hours (often sooner!). If you haven't already, please include the URL of your table in the thread below so that we can help you as quickly as possible!
Daniela D.
·
·
Hey Abolade! Thanks for reaching out. Sorry about this. For context, Claygent was unable to access that page due to LinkedIn's anti-scraping measures. The action still costs a credit because an API request was made. That is, Claygent still took steps to access the page and returned a result based on what it found. In this case, that the page is not accessible. I went ahead to add those credits back to your workspace. Here's what I recommend for your workflow: Use Zenrows' scraper with the settings in the screenshot below turned on. This will extract the page body text with the job description included, but the data will need to be formatted and cleaned up. To clean up this body text, you can use GPT. Your final output will be cleanly formatted as a job description. Here's an example prompt for this action: "Format and extract the job description" from {{BodyText}}. Only return the job description as your output". Let me know if this helps! https://downloads.intercomcdn.com/i/o/w28k1kwz/1219270824/b29f9ba5d018032e715323107888/CleanShot%2B2024-09-20%2Bat%2B12_24_55-402x.png?expires=1729168200&signature=6dea445ce0902d000710f7e8f15d1eab0ea7e69e63839323960891ca0231b049&req=dSImH8t5nYldXfMW1HO4zfenE4jzVIIeqck3S1y3BsbUSd739B0QP1BKhSs8%0A4r46%0A
Channeled
APP
·
·
Hi Abolade O.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: