LinkedIn Sales Trigger Intelligence
Pricing
from $1.79 / 1,000 actionable insights
Go to Apify Store
LinkedIn Sales Trigger Intelligence
Turn company, person, or job records into ranked, evidence-backed LinkedIn commercial signals.
LinkedIn Sales Trigger Intelligence
Pricing
from $1.79 / 1,000 actionable insights
Turn company, person, or job records into ranked, evidence-backed LinkedIn commercial signals.
Choose exactly one source. Inline is ideal for testing and integrations; dataset is safest for production pipelines.
Raw current records. Typical identity fields: id, jobId, companyId, linkedinUrl, url, companyName, title.
Dataset ID or name containing current records. Tokens in URLs are rejected.
Optional Actor ID/name to call. The caller pays upstream costs; use only an Actor you trust and are authorized to run.
JSON passed to the selected upstream Actor. Never paste credentials unless its schema marks them secret.
{}Optional first-party or licensed JSON endpoint. HTTPS only. Query-string tokens are rejected; use secret headers.
Optional request headers such as Authorization. Stored encrypted by Apify.
Dot path to the result array, for example data.items. Leave blank when the response itself is an array.
Optional prior snapshot used for state comparison. Omit for a first-seen baseline.
Optional dataset ID/name containing the previous snapshot.
Only deliver actionable records at or above this deterministic 0–100 score.
Hard output cap in addition to Apify maxTotalChargeUsd. Highest-priority records are delivered first.
Emit entities missing from the previous snapshot.
Emit entities with meaningful configured field changes.
Emit entities present previously but absent now.
Usually off to avoid paying for non-actionable records.
Optional override. Defaults: id, jobId, companyId, linkedinUrl, url, companyName, title.
Optional override. Defaults: companyName, title, location, employmentType, seniorityLevel, employeeCount, followersCount, jobCount, description, status.
Best-effort normalized-name matching when no strong identifier exists. Exact IDs always win.