Contact and Person Enrichment Actions Full Reference
This article covers every action in TexAu that enriches a person's professional profile. These actions return job title, company, location, LinkedIn URL, email, phone, career history, and other contact-level data.
For actions that only find an email or mobile number, see:
Before you begin
-
Connect each integration at Settings > Integrations before running enrichment actions.
-
People Data Labs and B2B Enrichment provide the deepest profile data but cost more credits per row. Reserve them for your highest-value contacts.
-
Enrichment actions do not update your CRM automatically. Use a CRM write action downstream (e.g., Update Contact (HubSpot)) to push results.
Enrich Contact (B2B Enrichment)
Extracts a full professional profile from a LinkedIn URL including job title, company, location, and employment history.
Integration: B2B Enrichment
Credit cost: 2 credits per row
Category: Enrichment
Inputs
| Field | Required | Description |
|---|---|---|
| LinkedIn Profile URL | Yes | Full LinkedIn profile URL (e.g., https://www.linkedin.com/in/username) |
Outputs
| Field | Description |
|---|---|
| First Name | Person's first name |
| Last Name | Person's last name |
| Headline | LinkedIn headline |
| Profile Picture | URL to profile image |
| Summary | LinkedIn about section |
| Industry | Industry from LinkedIn profile |
| Open to Work | Boolean. whether the person has open-to-work enabled |
| Premium | Boolean. whether the person has a LinkedIn Premium account |
| Country | Country from location field |
| City | City from location field |
| State | State or region |
| Full Location | Combined location string |
| Current Company Name | Name of current employer |
| Current Company Domain | Domain of current employer |
| Current Company Logo | Logo URL |
| Current Company LinkedIn URL | Company's LinkedIn page |
| Current Job Title | Current job title |
| Employment Type | Full-time, contract, etc. |
| Current Job Start Date | When they started the current role |
| Current Job End Date | End date if role has ended |
Use cases
Agencies: Run this before writing personalized cold emails. The headline and company name give you enough context to reference something relevant.
Founder-led teams: At 2 credits, this is the lowest-cost way to pull a full profile before a LinkedIn outreach or cold call. Use it on your ideal customer profile list.
RevOps: Feed the Current Company Domain output directly into CRM fields. Use it to standardize company names across your records ("TexAu Inc" vs "TexAu" vs "texau.com").
GTM engineers: Pull career history from this action and use an AI Column to write personalized openers based on previous companies or job titles.
Enrich Person by LinkedIn URL (People Data Labs)
Returns a deeply enriched professional profile from a LinkedIn URL via People Data Labs, including career history, education, skills, all emails, phone numbers, and social profiles.
Integration: People Data Labs
Credit cost: 30 credits per row
Category: Enrichment
Inputs
| Field | Required | Description |
|---|---|---|
| LinkedIn URL | Yes | Full LinkedIn profile URL (e.g., linkedin.com/in/seanthorne) |
Outputs
| Field | Description |
|---|---|
| Person ID | PDL internal ID for this profile |
| Full Name | Full name |
| Current Job Title | Job title at current company |
| Current Company | Company name |
| LinkedIn URL | Confirmed LinkedIn URL |
| Work Email | Primary work email address |
| All Emails | Array of all known emails (work + personal) |
| Phone Numbers | Array of known phone numbers |
| Location | Full location string |
| Skills | Array of listed skills |
| Experience History | Array of previous roles (company, title, dates) |
| Education History | Array of education records |
| Social Profiles | Array of social media profile URLs |
| Match Score | Confidence score (0–10) that the profile matches the input |
Use cases
Agencies: Use PDL when a client needs a complete ICP profile. not just an email, but job title, tenure, previous companies, and an education match score. The match score tells you how confident the result is before you act on it.
RevOps: PDL returns a full experience array. Use a formula or AI Column to extract previous company names and tag contacts who moved from a competitor. This is gold for competitor displacement campaigns.
Founder-led teams: At 30 credits, PDL is expensive. Use it only for top-10 or top-50 accounts where full context justifies the cost.
GTM engineers: The skills array from PDL is useful for persona segmentation. Filter your list to contacts who list "RevOps" or "HubSpot" in skills before launching a campaign.
Enrich Person by Name and Company (People Data Labs)
Returns the same full professional profile as above, but uses full name and current company name as the matching inputs instead of a LinkedIn URL.
Integration: People Data Labs
Credit cost: 30 credits per row
Category: Enrichment
Inputs
| Field | Required | Description |
|---|---|---|
| Full Name | Yes | Person's full name (e.g., Sean Thorne) |
| Company Name | Yes | Current company name (e.g., People Data Labs) |
Outputs
Same as Enrich Person by LinkedIn URL (People Data Labs) above.
Use cases
Agencies: Use when you have a name+company list from an event scan, directory download, or manual research, but no LinkedIn URL. This avoids the LinkedIn URL lookup step.
RevOps: Your CRM may have first name, last name, and company but no LinkedIn URLs. Run this on contact records missing LinkedIn to backfill profiles in bulk.
GTM engineers: Combine with Find LinkedIn URL by Name if you need the LinkedIn URL for downstream actions. Use PDL here if you need the full profile without the extra credit cost of a separate lookup.
Enrich Contact (Snov.io)
Enriches a contact record using their email address via Snov.io, returning name, job title, company details, location, and social profiles.
Integration: Snov.io
Credit cost: 4 credits per row
Category: Enrichment
Inputs
| Field | Required | Description |
|---|---|---|
| Yes | Work email address of the contact |
Outputs
| Field | Description |
|---|---|
| Profile ID | Snov.io internal ID |
| Full Name | Full name |
| First Name | First name |
| Last Name | Last name |
| Profile Photo | URL to profile image |
| Industry | Industry |
| Country | Country |
| Locality | City or locality |
| LinkedIn URL | LinkedIn profile URL |
| Twitter URL | Twitter profile URL |
| Current Company | Company name |
| Current Position | Job title |
| Current Company Website | Company domain |
| Company City | City of company HQ |
| Company State | State of company HQ |
| Company Country | Country of company HQ |
| Company Industry | Industry of company |
| Company Size | Employee count range |
| Company Type | Public, private, etc. |
| Current Job Start Date | Start date at current role |
| Last Update Date | When this record was last updated in Snov.io |
Use cases
Agencies: If you've already found emails with Snov.io, use this to enrich those contacts in the same workflow. You stay within one integration and can enrich in bulk.
RevOps: Your CRM has emails but is missing LinkedIn URLs, job titles, and company data. Run Enrich Contact (Snov.io) on all contacts where those fields are empty to fill gaps in bulk.
Founder-led teams: At 4 credits, Snov.io is a cost-effective middle ground between B2B Enrichment (2 credits, LinkedIn-only) and PDL (30 credits, full history). Good for volume enrichment where full history is not needed.
Enrich IP Address (Versium)
Maps an IP address to a company domain and returns company firmographic data including name, industry, employee range, and revenue range.
Integration: Versium
Credit cost: 4 credits per row
Category: Enrichment
Inputs
| Field | Required | Description |
|---|---|---|
| IP Address | Yes | IPv4 address to look up (e.g., 104.18.0.0) |
Outputs
| Field | Description |
|---|---|
| IP Usage Type | How the IP is being used (corporate, residential, etc.) |
| Is ISP | Whether the IP belongs to an ISP |
| Company Name | Name of the company at this IP |
| Company Address | Street address |
| Company City | City |
| Company State | State or province |
| Company ZIP | Postal code |
| Company Country | Country |
| Phone | Company phone number |
| Domain | Company domain |
| Website | Company website URL |
| Industry | Industry |
| Employee Range | Employee count band (e.g., 50–99) |
| Sales Revenue Range | Revenue band |
| Year Founded | Year the company was founded |
| SIC | SIC industry code |
| NAICS | NAICS industry code |
| NAICS Description | Industry description |
| Query ID | Versium internal query ID |
| Number of Matches | How many companies matched this IP |
Use cases
GTM engineers: Your product sends IP addresses from web session logs. Run this to identify which company visited your pricing page without signing up. Feed the domain output into Enrich Company from LinkedIn (B2B Enrichment) to get deeper firmographic data.
Agencies: Help clients attribute anonymous website traffic to named accounts. Map visitor IPs to company names, then cross-reference against their ICP to find warm leads.
RevOps: Enrich form submissions that contain an IP field from your analytics platform. Use Company Name and Domain to match the visitor against existing CRM accounts.
Find LinkedIn URL by Name
Finds a person's LinkedIn profile URL using their full name and company name.
Integration: BetterEnrich (TexAu built-in)
Credit cost: 2 credits per row
Category: Enrichment
Inputs
| Field | Required | Description |
|---|---|---|
| Full Name | Yes | Person's full name |
| Company Name | Yes | Current company name |
Outputs
| Field | Description |
|---|---|
| LinkedIn Profile URL | Found LinkedIn URL |
| Message | Status or error message |
Use cases
Agencies: You have a spreadsheet with name+company from an event, a directory, or a client list. Run this first to get LinkedIn URLs before any email or phone enrichment.
RevOps: CRM records often have first name, last name, and company but no LinkedIn URL. Run this in bulk to backfill LinkedIn URLs on older records.
GTM engineers: Use as the first step in a multi-step enrichment pipeline. Once you have LinkedIn URLs, feed them into Enrich Contact (B2B Enrichment), Find Email using LinkedIn URL (Apollo), or any other LinkedIn-based action.
Founder-led teams: The cheapest way to go from a name+company list to a LinkedIn-ready list before running any outreach enrichment.
Find LinkedIn URL by Email
Finds a person's LinkedIn profile URL using their email address.
Integration: BetterEnrich (TexAu built-in)
Credit cost: 4 credits per row
Category: Enrichment
Inputs
| Field | Required | Description |
|---|---|---|
| Email Address | Yes | Work email address |
Outputs
| Field | Description |
|---|---|
| LinkedIn Profile URL | Found LinkedIn URL |
Use cases
RevOps: Your CRM has emails but no LinkedIn URLs. Use this to reverse-lookup LinkedIn profiles from emails, then feed the URLs into a full profile enrichment action.
Agencies: A client sends a contact list with emails from an old database. Use this to get LinkedIn URLs and verify the contacts are still active in their claimed roles.
GTM engineers: When email bounce rates are high, LinkedIn URL lookup lets you redirect outreach to LinkedIn InMail without building a new list from scratch.
Troubleshooting
Enrichment returns empty for a known contact
-
The contact may have a private LinkedIn profile or a non-standard URL format. Ensure the URL follows
https://www.linkedin.com/in/usernameand does not include query strings or trailing slashes. -
PDL uses a likelihood score. A score below 5 indicates low confidence. Verify the input name and company are spelled correctly.
Match Score is low on PDL results
- This means PDL found a profile but is not confident it is the right person. Common causes: common names (e.g., "John Smith"), or the company name does not exactly match PDL's database. Try passing the LinkedIn URL instead of name+company for a more precise match.
Snov.io** returns empty for a valid email**
- Snov.io enriches its own contacts database. If the email was sourced outside Snov.io's coverage (e.g., scraped from a niche forum), there may be no matching record. Try Enrich Contact (B2B Enrichment) with a LinkedIn URL instead.
Versium returns ISP data instead of a company
- The IP belongs to a home office, coworking space, or mobile network. The Is ISP output will be
true. Filter these out before running downstream company enrichment.
Find LinkedIn URL by Name returns no result
- The person may not have a public LinkedIn profile, or the company name spelling does not match LinkedIn's data. Try variations of the company name (short form, without "Inc", etc.).