Crawlnest Instagram Comments
Under maintenancePricing
from $1.12 / 1,000 results
Crawlnest Instagram Comments
Under maintenanceRun a packaged Scrapy spider and export complete records to an Apify dataset.
Pricing
from $1.12 / 1,000 results
Rating
0.0
(0)
Developer
samir pathak
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
Run the packaged crawler and collect its returned records in an Apify dataset. Download the results as JSON or CSV.
Input
params: Supply the Instagram post URL asurl. Post, reel and reels links are normalized to/p/CODE/.maxItems: Maximum saved comments. Defaults to 20; the runner automatically sets the internal spidermax_commentsto 10 times this value. Anyparams.max_commentsvalue is overridden. SettingmaxItemsto 0 makes both count limits unlimited; runtime limits still apply.blockMedia: Defaults to true. Skip images, media and fonts to reduce proxy bandwidth.timeoutSeconds: Run timeout in seconds, from 30 to 86400. Defaults to 1200.proxyConfiguration: Optional Apify or custom proxy configuration.
Output and limitations
Records are saved to the default dataset with all fields yielded by the spider. RUN_SUMMARY in the default key-value store reports counts and the finish reason. Source restrictions, spider-specific limits and run timeouts can reduce results. Playwright queues are in memory and cannot resume pending browser requests after interruption.
See the Actor's Pricing tab for its configured charges. Customize this documentation for your packaged spider before publishing it.
Example cloud input:
For local tests without proxy credentials, set proxyConfiguration.useApifyProxy to false. A limit is a maximum, not a guarantee: source availability, timeouts and rejected pagination can reduce results. Logs report comments-response status and scroll-target availability without dumping request credentials.
Diagnosing a cloud failure
The default key-value store contains COMMENTS_DIAGNOSTICS: bounded GraphQL request/response events, capture rejection reasons, visible scroll-container measurements, final path, title, login-form presence and finish reason. It excludes request bodies, cookies, query strings and comment text. For a missed browser capture, opt into saveDebugScreenshots: true to also save COMMENTS_FAILURE_SCREENSHOT (the screenshot can show publicly loaded page content). Download the JSON report and optional screenshot from the run's Storage tab; these are not dataset items.
