LinkedIn Comment Opportunity Monitor

Watch selected LinkedIn posts for newly observed comments, questions and request language. Export the original comment, a direct LinkedIn link, available author details and exact text evidence for your review. Useful for GTM research, community listening and finding conversations where you can contribute.

Live collection uses the separately billed HarvestAPI LinkedIn Post Comments. This Actor adds persistent monitoring and literal filtering; it is not an independent LinkedIn extraction engine. Existing-dataset mode processes compatible comments you already collected. No LinkedIn login, cookies, publishing or automated outreach are involved.

Live mode requires an Apify plan that permits running public Store Actors. Some Creator plans restrict this. Those accounts can use existing-dataset mode; this Actor never upgrades your plan or uses a different account.

Quick start

{
  "sourceMode": "comments",
  "postUrls": ["https://www.linkedin.com/feed/update/urn:li:activity:7511362109293731840/"],
  "postedLimit": "week",
  "requestsOnly": true,
  "mode": "new",
  "monitorName": "gtm-conversations",
  "maxScanComments": 25,
  "maxResults": 25,
  "maxSourceChargeUsd": 0.1,
  "sourceTimeoutSecs": 180
}

Supply up to five post URLs, including URLs discovered by our LinkedIn Keyword Post Monitor. Reuse the same monitor name and settings on later runs. Create an Apify schedule yourself if needed; no schedule is created automatically.

Use includePhrases and excludePhrases for case-insensitive literal filters. requestsOnly keeps simple English request phrases or question punctuation. It can include rhetorical and promotional questions: a match is not verified buying intent, a qualified lead or a recommendation to contact someone. Review the text and context yourself.

The source collects root comments. Nested replies supplied inside those records are not expanded or monitored. Full author enrichment and separate reply collection are disabled. Direct links retain the comment identifier so “Open on LinkedIn” points to the comment when the source provides it.

Output

Each delivered record includes original text, comment identity, available comment and parent-post links, available author and date fields, literal qualification evidence, source provenance and a stable eventId. Unknown fields remain null. Reaction counts are observations, not measures of purchase intent.

The run's SUMMARY reports delivered/pending counts, collection status, coverage warnings and provisional source charges. SOURCE_RUN identifies the paid child run; its settled billing is authoritative. ERROR records a failure. Results are available through Apify's dataset API and JSON/CSV/Excel exports.

For dataset mode, select sourceMode: "dataset" and choose sourceDatasetId. Compatible root rows use type: "comment", id, commentary, linkedinUrl with comment query parameters, postId, optional actor and createdAt. Dataset mode examines the first maxScanComments records and does not reapply the source time window.

Pricing and limits

Our fee is $1.98 per 1,000 delivered qualifying comments, plus a $0.00005 startup event per allocated GB (minimum one). Apify compute and storage are separate.

Live collection also pays HarvestAPI on the running customer's account. On 1 October 2026 its base Free/Starter price was $2 per 1,000 source comments, with discounts on some plans. Check current source pricing. This is an additional cost, including comments later excluded or already seen.

For example, collecting 100 comments and delivering 20 matches costs approximately $0.20 in source fees + $0.0396 in monitoring fees, plus startup/platform usage. A run with zero output can still incur collection and platform costs.

• maxScanComments is a shared source cap; each post receives floor(cap / number of posts). It is never sent as an unlimited zero value.
• maxResults caps our output. Qualifying overflow is saved and delivered on the next run before another collection starts.
• maxSourceChargeUsd controls the separate source's PPE ceiling. It is not the parent fee or a total account budget.
• Apify's maximum Actor charge controls our event charges. Collection has its own budget and timeout.
• No profile enrichment or expanded reply collection is purchased.

Monitoring and reliability

mode: "new" suppresses previously delivered comment identities. First-run matches are delivered by default; emitInitial: false saves a baseline without comment-record output fees. Snapshot mode outputs all qualifying observations each scan.

Post URLs, source, time window and phrase filters define a history scope. Changing them starts a separate baseline; changing only maxResults does not. A fresh monitor name deliberately starts new history. New means newly observed, not necessarily newly published. Edits or reaction changes do not produce new-comment events.

A monitor lock prevents simultaneous writers. Pending output is saved before delivery. Delivery is at least once: a crash after writing output but before saving its checkpoint can repeat and charge the same eventId; deduplicate that ID downstream. History never silently expires. At the configured history count or 16 MB state limit, the Actor stops instead of forgetting identities.

Searches and comment ordering can be incomplete, delayed or restricted. Zero output does not prove no new comments exist. Missing comments do not generate deletion events. Failed or uncertain source runs never establish an empty baseline. A supplier can report success after reaching its charge cap, so even a successful scan covers only the returned observations. An ambiguous source launch is not automatically retried inside that parent run.