Linkedin Lead Qualification Research

Pricing

Rating

Developer

Actor stats

Categories

Share

Qualify a single LinkedIn lead through your API and store the result in Apify.

This Actor is built for teams that want to evaluate one LinkedIn profile at a time using structured filters such as industry, recent job changes, tech stack, job titles, skills, education, posting behavior, and company funding context.

What This Actor Does

The Actor takes a LinkedIn URL plus optional qualification filters, sends them to your /qualify-single endpoint, and saves the result to:

• The default dataset
• The OUTPUT record in the default key-value store

This makes the Actor easy to use from the Apify Console, schedules, integrations, or the Apify API.

How It Works

When a run starts, the Actor:

1. Reads the input from Apify.
2. Builds a form-data request for your qualification API.
3. Sends a POST request to apiBaseUrl/qualify-single.
4. Parses the API response.
5. Stores the first item from enriched_data when present.
6. Adds top-level fields such as status, message, error, and skipped_ai_processing when they are returned by the API.

If the request fails or required fields are missing, the Actor stores a structured error result instead.

Required Input

The following fields are required:

• apiBaseUrl
• linkedinUrl

apiBaseUrl

Base URL for your lead qualification API.

Default:

https://qualify-leads-932925834372.europe-west1.run.app

linkedinUrl

A single LinkedIn profile URL to qualify.

Example:

https://www.linkedin.com/in/example-person/

Optional Filters

You can refine qualification by filling any of the following fields.

Industry and company filters

• industryType: Industry to qualify against
• workingInFundedCompany: Whether the person should work at a funded company
• followerCount: Minimum follower count
• techStack: One technology selected from the predefined list

Career change filters

• recentJobChangeValue: Numeric job-change window
• recentJobChangeUnit: day, week, month, or year

These two values are combined and sent to the API as a single changed_job_time object.

Role and expertise filters

• jobTitlesIncluded: Comma-separated titles to include
• jobTitlesExcluded: Comma-separated titles to exclude
• skills: Comma-separated skills
• education: Education filter value

Example:

jobTitlesIncluded = Founder, CEO, Head of Growth
jobTitlesExcluded = Intern, Student
skills = B2B SaaS, outbound, GTM
education = Engineering

Content and activity filters

• postingFrequency: Posting frequency filter
• postedAbout: Topic the lead has posted about
• commentedAbout: Topic the lead has commented about

Example:

postingFrequency = weekly
postedAbout = sales automation
commentedAbout = lead generation

Example Input

{
"apiBaseUrl":"https://qualify-leads-932925834372.europe-west1.run.app",
"linkedinUrl":"https://www.linkedin.com/in/example-person/",
"industryType":"SaaS",
"recentJobChangeValue":6,
"recentJobChangeUnit":"month",
"techStack":"HubSpot",
"followerCount":1000,
"jobTitlesIncluded":"Founder, CEO, Head of Growth",
"jobTitlesExcluded":"Intern, Student",
"skills":"B2B SaaS, outbound, GTM",
"education":"Engineering",
"workingInFundedCompany":true,
"postingFrequency":"weekly",
"postedAbout":"sales automation",
"commentedAbout":"lead generation"
}

Output

The Actor pushes one result item to the default dataset.

In successful runs, the stored item is usually the first object from the API response's enriched_data array. If the API also returns fields such as status, message, error, or skipped_ai_processing, those are copied into the saved result.

Because the response body comes from your API, the exact output structure depends on what /qualify-single returns.

Typical output behavior

• If enriched_data exists, the first item is stored.
• If the API returns status metadata, it is added to the stored item.
• If the API returns an invalid response or the request fails, an error object is stored.

Error Handling

The Actor saves a structured error result for cases such as:

• Missing apiBaseUrl
• Missing linkedinUrl
• Network or timeout failures
• Invalid or unexpected API response bodies

Example:

{
"linkedin_url":"https://www.linkedin.com/in/example-person/",
"status":"error",
"error":"API request failed: <details>"
}

How To Use In Apify

In the Apify Console

1. Open the Actor.
2. Click Start.
3. Fill in apiBaseUrl and linkedinUrl.
4. Add any optional filters you want.
5. Run the Actor.
6. Open the dataset to inspect the result.

Via Apify API

Run the Actor with the same JSON input you would use in the Console, then read the dataset items or the OUTPUT record after the run finishes.

Best Practices

• Start with only linkedinUrl to validate the API connection.
• Add filters gradually so you can see which criteria most affect qualification.
• Keep apiBaseUrl pointed at the right environment, such as staging or production.
• Review several dataset outputs to confirm your API response format matches expectations.

Notes

• This Actor qualifies one LinkedIn URL per run.
• Requests are sent as form-data, not JSON.
• techStack is a single-select field in the input UI.
• Fields like job titles and skills are passed as comma-separated strings.

Summary

Use this Actor when you want an Apify wrapper around your LinkedIn qualification API:

• Input one LinkedIn URL
• Add structured qualification filters
• Call /qualify-single
• Save the result for downstream automation