
Linkedin post scraper
Pricing
$30.00/month + usage

Linkedin post scraper
Scrape linkedin posts or updates from linkedin post search results. Supports advanced linkedin search filters. Extract posts from any linkedin member
2.8 (9)
Pricing
$30.00/month + usage
216
Total users
5.6k
Monthly users
602
Runs succeeded
83%
Issue response
10 days
Last modified
4 months ago
Occassionally get the wrong LinkedIn person
Open
Every once in a while, the information returned is a different LinkedIn URL than the one that I sent via the API. I can try to trap the error in Make.com, but it will take quite a few operations. If you are not aware of the issue, I will try to send an example the next time it occurs.

In order to quickly identify the reason of your issue, I need to inspect your run.
Please share the URL of the run where you faced this issue. You can find your runs on this page: https://console.apify.com/actors/runs

FYI - I will have to close the issue if I don't get the run URL in next 24 hours
bluegrass_irishman
I understand. When I see the mistake happen again, I will open the case. This request was primarily if you already knew of the problem and looking for a work around or if there was something I was doing wrong.
bluegrass_irishman
And now I found that it occurred this morning. Run id xltJQCSjArTkoBvRV had an error. I never asked for Alex Membrillo and yet it returned https://www.linkedin.com/posts/alexmembrillo_i-talk-to-the-smartest-healthcare-marketers-activity-7316088181618008065-WGup?utm_source=combined_share_message&utm_medium=member_desktop&rcm=ACoAAAAyYAcB2G-SXsLSm6WHkcW_Ee3hgsKtB6o.
Let me know if you need more information from me.
bluegrass_irishman
By looking at the Table that this scraper creates on Apify, it looks like the requested LinkedIn URL was https://www.linkedin.com/in/colinjeffries, and the return was for Alex Membrillo.
bluegrass_irishman
I only gave you the ID for the run above. Here is the URL: https://console.apify.com/actors/kfiWbq3boy3dWKbiL/runs/xltJQCSjArTkoBvRV
natural_apron
I've seen this as well on my runs. I didn't report it, but +1 for seeing the same issue btw.