Network Linkedin batch Connection requests avatar
Network Linkedin batch Connection requests

Pricing

$20.00/month + usage

Go to Store
Network Linkedin batch Connection requests

Network Linkedin batch Connection requests

saswave/network-linkedin-batch-connection-requests

Developed by

SASWAVE

Maintained by Community

SEND / REMOVE / LIST batch of linkedin connection requests. Recommended to call the actor once a day when ADDing. The script has a hard limit of 20 successfull connections requests per run. Linkedin has weekly limits setup (100-200) recommended usage: One run per day with 15-20 automated connection

0.0 (0)

Pricing

$20.00/month + usage

5

Monthly users

5

Runs succeeded

92%

Response time

15 hours

Last modified

a day ago

SO

Error: UnboundLocalError: cannot access local variable 'final' where it is not associated with a value

Closed
sourcegeek opened this issue
9 months ago

Hi I'm getting an error:

Error: UnboundLocalError: cannot access local variable 'final' where it is not associated with a value

Could you help with this?

saswave avatar

SASWAVE (saswave)

9 months ago

Hi, the first error raised : Exception: Failed to retrieve target identifier. Refresh cookies session and try again.

We should update the error handling but refreshing cookies should do the trick

SO

sourcegeek

9 months ago

Thanks for your quick support!

Do you have an idea why a cookie that’s been used few times with your script get invalid at some point? I have few successful runs and all of a sudden continues failures.

SO

sourcegeek

9 months ago

I'm sending connections at an interval of 10 minutes. My guess is that linkedin might not like that. Also it would be helpful if I could provide proxyUrl to your scraper to use the same IP address.

saswave avatar

SASWAVE (saswave)

9 months ago

depends how much you use the cookies, but if you run the actor every 10 minutes and you send requests to multiple profiles , that might be a problem

Linkedin does not like automations

Sure, proxy is in our TODO

SO

sourcegeek

9 months ago

I think they are 3 key parts:

  • cookie
  • IP
  • user agent

If we keep both consistent then we should have increased connection limits. If you allow consumer provide those 3 I think it would be awesome!

FN

finding_nemo

8 months ago

Is there any update on this issue? I am facing the same.

saswave avatar

SASWAVE (saswave)

8 months ago

Cookies and user agent are consistent , unless you are able to provide the same IP as the one you use usually , you might have the same problem.

We can try asking the user to provide a proxy and implement a browser approach (runtime might get more expensive)

Pricing

Pricing model

Rental 

To use this Actor, you have to pay a monthly rental fee to the developer. The rent is subtracted from your prepaid usage every month after the free trial period. You also pay for the Apify platform usage.

Free trial

3 days

Price

$20.00