Home Action Reference Find Work Email Actions: Full Reference

Find Work Email Actions: Full Reference

Last updated on Apr 06, 2026

Find Work Email Actions: Full Reference

This article covers every action in TexAu that finds work (professional) email addresses. It includes exact inputs, outputs, credit cost, and use cases by team type.

For personal email finding, see Find Personal Email Actions.
To understand how to chain multiple providers with automatic fallback, see Waterfall Enrichment.


Before you begin

  • Connect the relevant integration before running these actions. Go to Settings > Integrations and connect whichever provider you want to use.
  • Each provider requires a separate API key. You only need to connect the providers you plan to use.
  • TexAu's built-in Waterfall actions (Find Work Email by LinkedIn URL, Find Work Email by Name and Domain) automatically try multiple providers for you. You do not need to set up each provider individually for waterfall actions: TexAu handles the routing.

Find Work Email by LinkedIn URL (Apollo)

Looks up a person's verified work email using their LinkedIn profile URL via Apollo.

Integration: Apollo
Credit cost: 2 credits per row
Category: Enrichment

Inputs

Field Required Description
LinkedIn URL Yes Full LinkedIn profile URL (e.g., https://linkedin.com/in/janedoe)

Outputs

Field Description
Email Work email address
Email Status Verification status
First Name Person's first name
Last Name Person's last name
Job Title Current job title
Seniority Seniority level (e.g., senior, director)
Organization Name Current employer
Organization Domain Company website domain
Organization Industry Industry classification
Estimated Employees Approximate headcount
City / State / Country Location
Waterfall Status Status message from Apollo's waterfall

Use cases

Agencies: Enrich a client's list of LinkedIn URLs to get verified emails before launching email campaigns. Run in bulk across 100s of rows simultaneously.

Founder-led teams: After finding a prospect on LinkedIn, get their work email in one click without leaving TexAu or logging into Apollo separately.

RevOps: Backfill missing email fields on CRM contacts that only have a LinkedIn URL. Connect the output directly to Update Contact (HubSpot) to complete records.

GTM engineers: Build automated pipelines that take LinkedIn URLs from a scrape and output verified emails ready for sequencing in Instantly or Smartlead.


Find Email using Name and Domain (Apollo)

Finds a work email address using a person's first name, last name, and company domain via Apollo.

Integration: Apollo
Credit cost: 2 credits per row
Category: Enrichment

Inputs

Field Required Description
First Name Yes Person's first name
Last Name Yes Person's last name
Domain Yes Company domain (e.g., stripe.com)

Outputs

Field Description
Email Work email address
Email Status Verification status
Person ID Apollo internal ID
Job Title Current job title
Organization Name Company name
Organization Domain Company domain

Use cases

Agencies: Start from a CSV of contacts with names and company names (but no emails), derive the domain using Find Website from Company Name, then run this action to get emails.

Founder-led teams: Use when you know someone's name and where they work but can't find their LinkedIn profile.

RevOps: Repair CRM records that have name + company but are missing an email address.

GTM engineers: Build a pipeline: List of names + company names → Normalize Company Name → Find Website → Find Email using Name and Domain → push to outreach.


Find Work Email Using LinkedIn Profile URL (FullEnrich)

Discovers a verified work email by submitting a LinkedIn URL to FullEnrich's enrichment API. This is an async action: it submits the request and polls for results.

Integration: FullEnrich
Credit cost: 15 credits per row
Category: Enrichment

Inputs

Field Required Description
LinkedIn Profile URL Yes Full LinkedIn profile URL

Outputs

Field Description
Work Email Verified work email address
Work Email Status Status of the email (valid, risky, etc.)

Use cases

Agencies: Use when Apollo and Findymail don't return results. FullEnrich often covers contacts in industries or regions with lower Apollo coverage.

Founder-led teams: Pay-per-result model. At 15 credits per row, best used as a fallback, not a primary source.

RevOps: Queue FullEnrich as a second-pass enrichment for rows that returned empty from lower-cost providers.

GTM engineers: Place FullEnrich in a condition column: only run it if the previous email column is blank. This controls spend.


Find Email Using LinkedIn URL (Findymail)

Finds a work email address from a LinkedIn profile URL using Findymail's verification system.

Integration: Findymail
Credit cost: 2 credits per row
Category: Enrichment

Inputs

Field Required Description
LinkedIn Profile URL Yes Full LinkedIn profile URL

Outputs

Field Description
Email Verified work email address
Accept All Whether the domain accepts all emails
First Name First name from LinkedIn
Last Name Last name from LinkedIn

Use cases

Agencies: Strong coverage for European and mid-market contacts where Apollo has gaps. Good provider to run alongside Apollo.

Founder-led teams: Straightforward input-output: paste a LinkedIn URL, get an email. Low cost at 2 credits.

RevOps: Deduplicate against existing CRM emails before writing back to avoid overwriting verified data.

GTM engineers: Build a waterfall: Apollo → Findymail → FullEnrich (sorted cheapest first). Use condition columns to skip providers once a valid email is found.


Find Email Using Name and Domain (Findymail)

Finds a work email address using first name, last name, and company domain via Findymail.

Integration: Findymail
Credit cost: 2 credits per row
Category: Enrichment

Inputs

Field Required Description
First Name Yes Person's first name
Last Name Yes Person's last name
Domain Yes Company domain

Outputs

Field Description
Email Found work email
Accept All Whether the domain accepts all emails

Use cases

Agencies: Use when you have a contact list with names and companies but no LinkedIn URLs. No scraping required.

RevOps: Fill email gaps in CRMs where the name+company is known but the email was never captured at point of entry.


Find Email Using Name and Company Domain (Hunter.io)

Finds a professional email using first name, last name, and company domain via Hunter.io's Email Finder API.

Integration: Hunter.io
Credit cost: 2 credits per row
Category: Enrichment

Inputs

Field Required Description
Domain Yes Company domain (e.g., hubspot.com)
First Name Yes Person's first name
Last Name Yes Person's last name

Outputs

Field Description
Email Address Found work email
Confidence Score Hunter.io confidence percentage (0–100)
Position Job title
Company Company name
Verification Status Email verification result

Use cases

Agencies: Hunter.io consistently returns high-confidence scores alongside the email. Use the Confidence Score output to filter: only accept emails with a score above 70.

Founder-led teams: Combine with Enrich Company (Hunter.io) to get both the company domain and a contact email in a single workflow.

RevOps: The verification status output lets you update a "verified" field in your CRM at the same time you write the email.

GTM engineers: Hunter.io has the highest rate limit of any email finder (10 requests/second). Best suited for high-volume, time-sensitive enrichment runs.


Find Work Email Using Name and Company Domain (Datagma)

Finds a verified work email address using first name, last name, and company domain via Datagma.

Integration: Datagma
Credit cost: 4 credits per row
Category: Enrichment

Inputs

Field Required Description
First Name Yes Person's first name
Last Name Yes Person's last name
Domain Yes Company domain
LinkedIn URL No Optional: may improve match rate

Outputs

Field Description
Email Found work email
Email Domain Domain part of the email
MX Found Whether the domain has valid mail exchange records
SMTP Check Whether SMTP verification passed
Status Email status label

Use cases

Agencies: Datagma's SMTP check and MX validation are more detailed than most providers. Use when you need high deliverability confidence before importing into an email sequence.

RevOps: The smtp_check and mx_found outputs give you real delivery signal: not just pattern matching. Map these to custom fields in HubSpot for data quality tracking.

GTM engineers: Optional LinkedIn URL input can increase match accuracy. Chain with a LinkedIn URL find action first.


Find Email by LinkedIn URL (Prospeo)

Finds a professional email address from a LinkedIn profile URL via Prospeo's enrichment API.

Integration: Prospeo
Credit cost: 2 credits per row
Category: Enrichment

Inputs

Field Required Description
LinkedIn Profile URL Yes Full LinkedIn profile URL

Outputs

Field Description
Email Found work email address
Email Status Verification status (valid, accept_all, etc.)

Use cases

Agencies: Prospeo's coverage is strong for LinkedIn-sourced contacts. Good primary provider for outbound agencies doing LinkedIn-first prospecting.

Founder-led teams: Simple two-field action (URL in, email out). Run directly after any LinkedIn-based scrape.


Find Email by Name and Domain (Icypeas)

Finds a verified work email address using a person's name and company domain via Icypeas.

Integration: Icypeas
Credit cost: Check the action details panel
Category: Enrichment

Inputs

Field Required Description
First Name Yes Person's first name
Last Name Yes Person's last name
Domain Yes Company domain

Outputs

Field Description
Email Found work email address
Status Verification status

Use cases

Agencies: Icypeas is useful as a tertiary fallback provider in waterfall workflows: when Apollo, Findymail, and Hunter all miss.

RevOps: For contacts in Southern Europe and LATAM, Icypeas often returns results where other providers fail.


Find Work Email by Name and Domain (TexAu Waterfall)

Finds a verified work email by trying multiple providers automatically. TexAu submits the request to multiple email enrichment providers and returns the first valid result. No individual provider account required for this action: TexAu uses its shared pool.

Integration: TexAu (built-in waterfall)
Credit cost: Varies by provider used (check the action details panel)
Category: Enrichment

Inputs

Field Required Description
First Name Yes Person's first name
Last Name Yes Person's last name
Domain Yes Company domain

Outputs

Field Description
Email Found work email address
Source Which provider returned the result
Status Verification status

Use cases

Agencies: The fastest way to get email coverage without managing 3–5 separate API keys. TexAu rotates through providers and bills only for successful lookups.

Founder-led teams: No setup needed beyond your TexAu account. Point it at a column of names + domains and let it run.

RevOps: Use as the default email enrichment step before CRM sync. The Source field lets you track which data provider filled your records.

GTM engineers: Compare hit rates from this action against single-provider actions to decide whether to self-manage provider keys or rely on TexAu's waterfall.


Find Work Email by LinkedIn URL (TexAu Waterfall)

Finds a verified work email from a LinkedIn URL by trying multiple providers automatically.

Integration: TexAu (built-in waterfall)
Credit cost: Varies by provider used (check the action details panel)
Category: Enrichment

Inputs

Field Required Description
LinkedIn Profile URL Yes Full LinkedIn profile URL

Outputs

Field Description
Email Found work email address
Source Which provider returned the result
Status Verification status

Use cases

Agencies: One action covers all LinkedIn-to-email conversion needs. No provider management.

GTM engineers: Best starting point for LinkedIn-first enrichment pipelines. If you need more control over provider selection, swap to individual provider actions.


Find Email (B2B Enrichment)

Finds a work email using first name, last name, and company domain via the B2B Enrichment network.

Integration: B2B Enrichment
Credit cost: 0 credits (included in your B2B Enrichment subscription)
Category: Enrichment

Inputs

Field Required Description
First Name Yes Person's first name
Last Name Yes Person's last name
Domain Yes Company domain

Outputs

Field Description
Email Found email address
Email Status Validation status (valid, catch-all, etc.)
Sub Status Detailed sub-classification
Domain Type Type of email domain
Free Email Whether this is a free email provider
Generic Email Whether this is a role-based address (info@, support@)

Use cases

Agencies: Zero credit cost makes this ideal for high-volume client projects when you have a B2B Enrichment subscription.

RevOps: The is_generic flag is valuable: filter out role-based emails before loading into your CRM to keep data clean.

GTM engineers: The is_free_email flag helps segment personal Gmail/Yahoo addresses from corporate work emails automatically.


Troubleshooting

Email column returns blank for all rows

  • Confirm the integration is connected at Settings > Integrations.
  • Verify the input columns contain valid LinkedIn URLs (they must start with https://linkedin.com/in/).
  • For name+domain actions, check that the domain column contains just the domain (stripe.com) without https:// or www.

Email status shows "catch_all" or "risky"

  • These addresses exist at the domain but cannot be individually verified because the server accepts all email. You can still send: expect higher bounce rates. Use a dedicated email verification action before importing to sending tools.

FullEnrich runs slowly

  • FullEnrich is an async action. It submits the request, then polls every 2 seconds for up to 2 minutes. This is normal behaviour. Rows process sequentially per your account's rate limit.

Results are inconsistent across runs

  • Email providers update their databases continuously. Running the same list twice may return slightly different results. Always use the latest enrichment data before launching campaigns.

Apollo returns an email but status is "likely invalid"

  • Apollo uses a waterfall internally. When it cannot verify with certainty, it returns a best-guess email with a lower confidence status. Check the Email Status output field and filter rows with invalid status before sending.