LinkedIn Scrape module still unreliable

I could now run further experiments with the LinkedIn scrape module:

  • funnily enough it seems to be working on my, or on Rahul’s profile (+I found one more connection of mine where the data is returned)
  • but on most profiles I tried it does not find the profile. I also tried profiles that I actually scraped previously, so it worked earlier - but not anymore

Unfortunately LI scraping is rather important for our flows: we have created a few flows we actually use based on those… eg. pre-meeting briefings, downloading business data for AI processing, storing connection data (the majority of our credits went into such direct or indirect services). So any help would be welcome how to restore or find a new LinkedIn Scrape that can fit into flows (we found Phantom Buster less automatable)

Previous forum already closed due to my inactivity:

Hey @lacikiszely_AbilityMatrix! If you’re reporting an issue with a flow or an error in a run, please include the run link and make sure it’s shareable so we can take a look.

  1. Find your run link on the history page. Format: https://www.gumloop.com/pipeline?run_id={{your_run_id}}&workbook_id={{workbook_id}}

  2. Make it shareable by clicking “Share” → ‘Anyone with the link can view’ in the top-left corner of the flow screen.
    GIF guide

  3. Provide details about the issue—more context helps us troubleshoot faster.

You can find your run history here: https://www.gumloop.com/history

Hey @lacikiszely_AbilityMatrix – There was a temporary issue with the data provider that we were using for the LinkedIn profile scraper node. That has been resolved, and the node should be fully functional now. All you would have to do is hover over the node and upgrade its node version. Let me know if it works as expected now.

Still does not work for me:

  1. In this flow, I could update v1->v2 (and not v2->v3 as in your screenshot): https://www.gumloop.com/pipeline?workbook_id=68EG6av3ytoGKQuhfW5ahx&run_id=WAz2dcM69W6C2F35gJifCm

  2. The profile resulted in error (“not found”) though I have already scraped that a few month ago

  3. In another flow, update is not offered (node is embedded in an error shield, so simply no results are returned)
    https://www.gumloop.com/pipeline?workbook_id=jRbTLkcrjGGsjF1g13WLzw

Hey @lacikiszely_AbilityMatrix – do you mind deleting the LinkedIn Scraper node instead and then adding it back again please? The reason why you’re not seeing the upgrade version option is likely because you’ve not refreshed the workflow. If you refresh, you should be able to see it. Deleting and adding back would always add the latest version and should work. I tested this on my end as well.

https://www.gumloop.com/pipeline?workbook_id=dJ8fT5CB5zQ6K9RBYmjB2o&run_id=Gc94CNqtmEzrBhnxZJGwZn

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.