What’s the most accurate source for LinkedIn data? I’m using Clay to pull “last LinkedIn post” dates and HR headcount for my account list, but the numbers don’t match what I see on LinkedIn. Anyone else noticed this? What’s your workaround?
apify
i have an api that gets the posts and people who engaged with the linkedin post in real time and can be integrated with clay
Hey there, thanks for reaching out. I second Muhammad's input - tools like Phantombuster & Apify.com have scrapers that can pull extensive records of LinkedIn posts. However, both options use your live session cookies which may risk you losing access to your Linkedin account. I found this actor, for example, which should get the job done for your specific use case. Apify integrates with Clay, so you'll be able to build tables based on Apify actor runs, or trigger actor runs at strategic points in your workflow. Here's how you can set up a Clay table from an Apify actor run: https://downloads.intercomcdn.com/i/o/1136960340/97e4e0aa1500879dbbe57ea0/CleanShot+2024-08-06+at+15_48_57.gif?expires=1734346800&signature=514e028d584aab47b63573f6d386b8d9da594e3f338d646253e1fd3d86399907&req=dSEkEMB4nYJbWfMW1HO4zejWawze7nEPAut9xPamiwAHxg%3D%3D%0A And here's how you can trigger an Apify actor in an active workflow: https://downloads.intercomcdn.com/i/o/1137852576/18ba4740bed56137b073908c/CleanShot+2024-08-07+at+11_15_01.gif?expires=1734346800&signature=835dd000767e3c6d201f05fcbe1b278311ac22b496d58f135ad09a1b127c39b6&req=dSEkEcF7n4RYX%2FMW1HO4ze%2BfS22oS%2FGe98ZbnAjuOC9QpQ%3D%3D%0A For the trigger-based approach you'll likely have to study the documentation of the specific actor, to see what JSON payload it expects to trigger the run. I hope this was helpful. If there's anything else I can assist you with, please let me know!
thanks!! so Apify could help with LI post. What about the HR team size?
I used it today and on Friday, it wasn’t accurate unfortunately
So I can’t use that for my customer
Have you made sure to flag this? You can left-click on the row/enrichment and pinpoint why it's not accurate! Our team will work on fixing this :)
nope I didn't, I'll make sure to flag this on the next projec
Of course!