What will you
build with it?

01 / WORKFLOW

Refresh CRM records

Turn a known LinkedIn profile or company URL into structured research for your CRM.

1 credit per company record

1. Read a profile for its headline, experience, education, and skills.
2. Read its company separately for industry, website, employee count, and locations.
3. Map available fields into your CRM; preserve existing values when a field is absent.

Scope: Your application owns CRM writes and record matching. Private personal emails and phone numbers are not returned.

02 / WORKFLOW

Check a person’s current role

Look up a named person at a known company without opening their LinkedIn profile.

1 credit for a returned match

1. Supply first_name, last_name, and current company name or ID.
2. Receive the matching search row: role, company, location, and available profile references.
3. Add a public profile URL when you need to disambiguate people with the same name.

Scope: No match costs zero. Ambiguous or incomplete matches fail without a charge. This does not return full experience or education history.

03 / WORKFLOW

Build a prospect research list

Discover people with Sales Navigator keyword search, then enrich the records you select.

1 credit per search row

1. Search a keyword such as founder to collect a bounded page of people.
2. Filter the returned title, company, or location in your own application.
3. Enrich selected profile URLs when you need more detail.

Scope: Client-side filtering allows targeting specific titles, locations, and companies from the returned candidate pool.

04 / WORKFLOW

Research people engaging with a post

Find relevant posts and collect the available context about their commenters and reactors.

1 credit per post, comment, or reaction

1. Search posts by keyword or request a known profile’s posts.
2. Pass the returned social_id to the comments or reactions action.
3. Store comment text, reaction type, and available profile URLs alongside your research.

Scope: Each list is one page. A comment or reaction is engagement context, not verified buying intent. The API does not send messages or connection requests.

05 / WORKFLOW

Build your own change alerts

Compare successive person or company reads to flag changes for your team.

Each new read is billed at the action’s normal rate

1. Use your scheduler to request a new read with a new idempotency key.
2. Store the result and collection time in your database.
3. Compare available fields and route meaningful changes to your own notification system.

Scope: Scheduling, snapshot storage, diffing, and notifications run in your application. Missing data is not proof of a job change. ProfileGlide has no built-in change feed or scheduler.

06 / WORKFLOW

Add LinkedIn data to your product

Use one REST interface for source reads instead of maintaining your own collection scripts.

1 credit per returned row

1. Create a named API key and choose one of the 16 data actions.
2. Set max_results and max_credits before submitting work.
3. Inspect run status, collect output, and reuse the same key and body only when retrying that request.

Scope: Managed access covers the implemented read actions. It does not include customer-connected identities, arbitrary LinkedIn routes, or an availability SLA.