Facebook Groups Scraper
Pricing
$45.00/month + usage
Facebook Groups Scraper
Extract data from one or multiple public Facebook groups. Get group and post URLs, post text, comments, timestamp, likes and comments count, and basic commentator info. Download the data in JSON, CSV, and Excel and use it in apps, spreadsheets, and reports.
4.8 (12)
Pricing
$45.00/month + usage
127
Total users
10.1k
Monthly users
781
Runs succeeded
98%
Issue response
2.1 days
Last modified
7 days ago
5 minutes hard limit
Open
Very inconvenient. No way to change it, no way to predict. Messages limit reflects the number of ,messages in the group and if one group is large and other is small the first one would be trimmed. I've spend about 15$ trying to proceed with scrapping and then time outed. Very pity
Hi!
In your runs, only posts for 1 day are scraped by the relative date: https://console.apify.com/view/runs/ZxkxPLx99KWkbepNh - 709 posts for 12 groups https://console.apify.com/view/runs/VV5FCnxYRuGTsKdAz - 548 posts in 9 groups
Can you please clarify which groups exactly were trimmed?
m.churkin
I call the scrapper from n8n and API connection stopped after 5 minutes. Therefore n8n process stopped as well and I have to start from the beginning. This is due hard limit of 5 min for the API connection. So it's almost impossible to use it through API. It's unpredictable how many messages I could proceed for 5 minutes and it could not be regulated with max messages because this parameter is set for reach group and groups are different. Long story short 5 min hard limit for API makes it impossible to use.
Hi!
The actor can not change the way external integration works, however, you are not expected to wait for the run to finish, exactly because waiting might take too long.
Please check the options below: https://github.com/minhlucvan/n8n-nodes-apify https://n8n.io/integrations/apify/and/sms77/ https://n8n.io/workflows/2878-host-your-own-ai-deep-research-agent-with-n8n-apify-and-openai-o3/
m.churkin
would try to explain. Please see 2 runs. They are identical but takes different time. Both were summoned from n8n. First took more than 5 minutes and BY DEFAUT HARDCODED 5 min timeout API connection was dropped. Data were not transferred to n8n and processed was stopped. The second one (the same) took less than 5 min and was successfully finished. In the current API realization it's barely useful. I have to make a web hook and use it, no asynchrony execution, no option to increase 5 min hardcoded timeout. Pity.
