Pricing

$20.00/month + usage

Go to Store

Network Linkedin batch Connection requests

Try for free

saswave/network-linkedin-batch-connection-requests

Developed by

SASWAVE

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

Monthly users

Runs succeeded

93%

Response time

15 hours

Last modified

19 hours ago

Lead generation Automation

Back to issues Create new issue

[Feature request] Result with different status when invitation limit met

Closed

sourcegeek opened this issue

Would it be possible to respond with a different status than NOT_SENT when weekly connection limit is met? Today you get the same status when you already have pending connection to the user or already connected.

SASWAVE (saswave)

You mean in the list you provide, happens to send duplicates as input ? Could you send me a list of profile at dev@saswave.com so that we can make some tests and understand if we can differentiate an error (already in network / already sent vs weekly or daily limit)

Also do you have a list of status in mind ? (ex: sent, not_sent, already_sent, already_friends, error, limit_reached)

sourcegeek

I meant linkedin allows 100-200 connections a week, if you reach this limit your script responds with NOT_SENT status. There is no way to differentiate the reason for NOT_SENT.

SASWAVE (saswave)

As mentioned in the documentation, the first use case we implemented has a hard limit of 20 add connections request per actor run

So if your input contains a list with more than 20 url, only the first 20 successful connection request will be handled and the rest marked as not sent

So that you can schedule the actor to run every 1h and add 20 people (for exemple)

sourcegeek

I use your actor in cron jobs, not Apify UI. I schedule a connection in my systems, not apify. So I send only one request ever N hours. At some point weekly linkedin limit is reached. All I'm saying is that based on the output from the actor is not clear when that's the case.

SASWAVE (saswave)

Got it , will keep you posted on updates

SASWAVE (saswave)

We have updated the actor output results status : NOT_SENT, SENT, ALREADY_SENT, ALREADY_FRIEND, WEEKLY_LIMIT_EXCEEDED

Presence of NOT_SENT means you can call the actor again to send connections requests. It will be replaced with WEEKLY_LIMIT_EXCEEDED, meaning even if you call the actor again ,wont be possible to send connection requests yet

SASWAVE (saswave)

Would you need a feature to handle removing requests not being accepted in batches (with some kind of date filter) ?

sourcegeek

What a great support I really appreciate this! I'll test out new statuses.

sourcegeek

I would love to have an option to remove request yes! Personally I don't care about date filter since I do that myself in scheduled jobs within my system.

SASWAVE (saswave)

Will try to implement 2 use case for connection request removal:

providing a list of profile and remove the connection request if still pending (no need for date filters)
select a date filter (last 7 days, 2 weeks, 1month ...) and let the script get the list of requests still pending and remove according to the selected date filter

sourcegeek

Thanks a lot, I appreciate it!

SASWAVE (saswave)

We also added a feature to list all pending connections requests with linkedin url, title, name, numbers of days since request

All 3 features are ready to be shipped, we will work on updating the apify actor (documentation and input schema) this afternoon or tomorrow morning

Keeping you posted when you can try. We take any feedbacks :)

sourcegeek

That's awesome, thank you! Look forward

sourcegeek

Is it currently possible to use proxy with your actor?

SASWAVE (saswave)

Actor is up and running, proxy are not supported yet

sourcegeek

Thank you I'll take a look!

sourcegeek

Hey, I’m getting issues with latest build. Am I missing something in the input?

2024-06-03T07:40:05.142Z ACTOR: Pulling Docker image of build 1rZMb6zFMS9BLuwte from repository. 2024-06-03T07:40:05.676Z ACTOR: Creating Docker container. 2024-06-03T07:40:05.948Z ACTOR: Starting Docker container. 2024-06-03T07:40:08.645Z https://www.linkedin.com/in/ACwAAAHHOXcBxdtuFgwIycyHTd3RWHSE7S4UDxE/ 2024-06-03T07:40:11.803Z Traceback (most recent call last): 2024-06-03T07:40:11.806Z File "/usr/src/app/src/main.py", line 376, in main 2024-06-03T07:40:11.808Z raise err 2024-06-03T07:40:11.810Z File "/usr/src/app/src/main.py", line 370, in main 2024-06-03T07:40:11.813Z final = add_to_network(urls, cookies) 2024-06-03T07:40:11.815Z ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2024-06-03T07:40:11.817Z File "/usr/src/app/src/main.py", line 72, in add_to_network 2024-06-03T07:40:11.819Z raise Exception('Failed to retrieve target identifier. Refresh cookies session and try again.') 2024-06-03T07:40:11.822Z Exception: Failed to retrieve target identifier. Refresh cookies session and try again. 2024-06-03T07:40:11.824Z 2024-06-03T07:40:11.826Z During handling of the above exception, another exception occurred: 2024-06-03T07:40:11.828Z 2024-06-03T07:40:11.830Z Traceback (most recent call last): 2024-06-03T07:40:11.833Z File "", line 198, in _run_module_as_main 2024-06-03T07:40:11.835Z File "", line 88, in _run_code 2024-06-03T07:40:11.837Z ... [trimmed]

SASWAVE (saswave)

can you share the url of the run that failed

sourcegeek

https://console.apify.com/view/runs/0EzRUkVe9PPkx7r1h

SASWAVE (saswave)

Seems like a request failed because of cookies not being valid anymore , Did you try reset your cookies and retry the actor ? If the error still persists maybe we need to update the logic if linkedin has made some changes

sourcegeek

Here is another run that fails with valid cookie

https://console.apify.com/actors/20VDLIYjfHcsNe0nj/runs/sFSfZ9Y0zfCTAxHHo#log

sourcegeek

Failure is random, succeeds first time but then fails all following times

sourcegeek

It seems like it’s not failing for my cookie but for others. Is it possible that windows os cookies are different for some reason?

SASWAVE (saswave)

OS isn't be relevent for success, can you send me by mail at dev@saswave.com a copy of the cookies that fails (not sure if the ones in your last linkedin run are still valid)

sourcegeek

My guess with OS is that somehow cookie may contain OS metadata and when it detects different architecture windows/linux it asks for extra verification.

This cookie must still be valid.

One thing to note is that my cookie is fine (mac os) and works with all connection requests but of another user (windows) is not, it succeeds first time but following attempts fail.

I think it would really help to pass proxy configuration to your script. You think this wouldn’t make any difference?

Add comment

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

Medium Following Scraper

easyapi/medium-following-scraper

Extract detailed information about Medium users' following lists. Get comprehensive data including usernames, bios, membership status, and more. Perfect for influencer research, network analysis, and understanding content creator communities. 🔍

EasyApi

5.0

Website Content Crawler

apify/website-content-crawler

Crawl websites and extract text content to feed AI models, LLM applications, vector databases, or RAG pipelines. The Actor supports rich formatting using Markdown, cleans the HTML, downloads files, and integrates well with 🦜🔗 LangChain, LlamaIndex, and the wider LLM ecosystem.

Apify

42.5k

4.6

🔥 Glassdoor jobs scraper

bebity/glassdoor-jobs-scraper

ℹ️ Elevate your job search with the sleek Glassdoor Scraper for Apify. Tailor-made for the modern job seeker, it's your secret weapon in the job market. Dive into a world of opportunities with custom searches, precise filtering. Fast, efficient, and incredibly user-friendly 🚀✨

Bebity

793

📩📍 Google Maps Email Extractor

lukaskrivka/google-maps-with-contact-details

Extract Google Maps contact details. Scrape websites of Google Maps places for contact details and get email addresses, website, location, address, zipcode, phone number, social media links. Export scraped data, run the scraper via API, schedule and monitor runs or integrate with other tools.

Lukáš Křivka

22.8k

Instagram Scraper

apify/instagram-scraper

Scrape and download Instagram posts, profiles, places, hashtags, photos, and comments. Get data from Instagram using one or more Instagram URLs or search queries. Export scraped data, run the scraper via API, schedule and monitor runs or integrate with other tools.

Apify

83.3k

Twitter (X.com) Scraper Unlimited: No Rate-Limits

apidojo/twitter-scraper-lite

Introducing Twitter Scraper Unlimited, the most comprehensive Twitter data extraction solution available. Our enterprise-grade scraper offers unmatched capabilities with a transparent event-based pricing model, making it perfect for both small-scale and large-scale data extraction needs.

API Dojo

2.9k

Facebook Posts Scraper

apify/facebook-posts-scraper

Extract data from hundreds of Facebook posts from one or multiple Facebook pages and profiles. Get post URL, post text, page or profile URL, timestamp, number of likes, shares, comments, and more. Download the data in JSON, CSV, and Excel and use it in apps, spreadsheets, and reports.

Apify

19.9k