Skip to main content
Enrichment fills in what a LinkedIn search never gives you: the About section, the full work history, education, skills, languages, follower and connection counts, and recent posts. You then use those facts in filters, in sequence conditions, in message variables and in AI-written lines.

It is usually free

Before every invite, message, InMail, like, comment or endorse step, the platform already fetches the lead’s profile. It used to keep six fields and throw the rest away. Now it stores everything. Every lead in a sequence is enriched at no extra cost in profile views. These fetches are silent: the lead is never notified.

Leads that are not in a sequence

For imported leads waiting to be used, a background job tops them up using only the profile views left over after the day’s sequence actions are planned:
  • At most 30% of a sender’s daily allowance.
  • Inside the sender’s working hours, with the usual random spacing.
  • Senders at warm-up level 0 or 1 do none, because at 10–20 views a day it would starve their campaigns.
This is off by default. Turn it on under Settings → AI & data, tick it on an individual import, or use the bulk Enrich action on selected leads. Existing leads are never enriched in bulk without someone asking.

Freshness

Anything enriched in the last 90 days is skipped. Beyond that:
  • Re-enrich on the lead page forces a fresh read.
  • The Refresh profile sequence step re-reads the profile when the stored data is older than a number of days you choose (90 by default). A lead that has never been enriched is enriched by this step rather than skipped.

Posts

Listing someone’s posts is a separate call with its own daily allowance (post fetches, see Smart Limits). It does not spend a profile view. Posts are fetched only when something will use them: a {{enrich.recent_post}} variable, an AI variable marked needs recent posts, an AI routing step, or a “posted recently” filter on that sequence. Otherwise only the profile is stored.

Empty means unknown

LinkedIn throttles heavy use of full profile sections, and a throttled request comes back with empty sections and no error. So an empty section is treated as unknown, never as “this person has no About”. It never overwrites what is already stored, and a sender that returns empty sections twice in a row backs off for a few hours before trying again.

Where the data shows up

A Profile data card with About, current role, past roles, education, skills, languages and recent posts, plus when it was last enriched.
Filter the Leads list by past company, skill, school, profile language, follower count, or posted in the last N days.
A Condition step has a Profile data group: profile data is stored, months in current role, posted in the last N days, followers, connections, past company, skill, profile language, About section, school.
{{enrich.about}}, {{enrich.current_title}}, {{enrich.current_company}}, {{enrich.years_in_role}}, {{enrich.months_in_role}}, {{enrich.previous_company}}, {{enrich.previous_title}}, {{enrich.school}}, {{enrich.degree}}, {{enrich.top_skill}}, {{enrich.skills}}, {{enrich.language}}, {{enrich.follower_count}}, {{enrich.connections_count}}, {{enrich.recent_post}}, {{enrich.recent_post_date}}.Always give these a fallback. Not every profile has every field. See Personalization.

Wait for enrichment

In a sequence’s settings, Wait for profile enrichment before the first step holds each lead until its profile has arrived, so the first message never renders with empty variables. A lead starts anyway after 72 hours, so nobody waits forever. The lead page shows waiting, done or failed.

Q: Does enrichment show up as a profile visit?

No. These fetches are made without notifying the lead. A Visit profile step with notify on is the only thing that shows up on their side.

Q: Can I enrich a lead with no LinkedIn profile?

No. Enrichment reads LinkedIn. For email addresses, see the Find email step.