Find Work Email Using LinkedIn Profile URL (FullEnrich)
Full Enrich → Find Work Email Using LinkedIn Profile URL (FullEnrich)
/v1/fullenrich-work-email-enrichment{ "linkedin_url": "https://acme.com" }
{ "ok": true, "data": { "work_email": "[email protected]", "work_email_status": "[email protected]" } }
Discovers verified work email addresses from a LinkedIn profile URL via FullEnrich.
Install
Add find work email using linkedin profile url (fullenrich) to your MCP client.
Drop this into claude_desktop_config.json (or your client's equivalent) and the tool shows up in any chat.
{ "mcpServers": { "texau": { "command": "npx", "args": ["-y", "@texau/mcp-server"], "env": { "TEXAU_API_KEY": "..." } } } }
Tool name: texau__fullenrich-work-email-enrichment
When to use this.
The fullenrich-work-email-enrichment action enables users to discover verified work email addresses by utilizing a LinkedIn profile URL. This enrichment tool accepts a single input parameter, the linkedin_url, which is the URL of the LinkedIn profile belonging to the individual whose work email is sought. Upon execution, the action returns two key output fields: work_email, which provides the verified work email address, and work_email_status, indicating the status of the retrieved email. This action is particularly useful for sales professionals, recruiters, and marketers looking to enhance their outreach efforts by obtaining accurate contact information. Categorized under enrichment, this API action streamlines the process of gathering essential contact details, thus facilitating more effective communication and networking opportunities.
Try it
Run a sample request.
The response is a deterministic, cached example. No live call, no credits used.
Find Work Email Using LinkedIn Profile URL (FullEnrich)
Response
Output schema.
Every field returned in `data`. Click rows to expand nested objects.
work_emailWork Emailstringwork_email_statusWork Email Statusstring
Integrate
Copy-pasteable snippets.
Real endpoint: https://v3-api.texau.com/api/v1/fullenrich-work-email-enrichment. Auth: x-api-key.
/v1/fullenrich-work-email-enrichmentcurl -X POST 'https://v3-api.texau.com/api/v1/fullenrich-work-email-enrichment' \ -H 'x-api-key: $TEXAU_API_KEY' \ -H 'content-type: application/json' \ -d '{"linkedin_url":"https://acme.com"}'
{ "ok": true, "data": { "work_email": "[email protected]", "work_email_status": "[email protected]" } }
Compose
How this fits a workflow.
The next 2 actions most operators chain after this one.
enrichment
Find Work Email by Name and Domain (FullEnrich)
Generates and verifies work email addresses from a name and company domain via FullEnrich.
enrichment
Find Mobile Number Using LinkedIn Profile URL (FullEnrich)
Discovers mobile phone numbers from a LinkedIn profile URL via FullEnrich.
enrichment
Find Mobile Number by Name and Domain (FullEnrich)
Finds mobile phone numbers using a person's name and company domain via FullEnrich.
Output
Results land in a TexAu table.
Sample rows below.
Real result preview coming soon.
| Input | Status | Score |
|---|---|---|
| [email protected] | valid | 96 |
| [email protected] | risky | 54 |
| [email protected] | invalid | 12 |
Workflow
A real example.
Trigger → find work email using linkedin profile url (fullenrich) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.
Built for
Who runs this.
Reliability
Rate limits & reliability.
- Per-minute limit60 / min
- Per-day limit1,440 / day
- RetriesAutomatic w/ backoff
- ModeAsync
Errors
HTTP status codes.
What each response means and what to do about it.
| Code | Cause | Fix |
|---|---|---|
| 200 OK | Action ran. Data in `data`. | Read response. |
| 400 Bad Request | Missing or malformed input. | Validate against the input schema. |
| 401 Unauthorized | Missing or invalid `x-api-key`. | Re-issue from /api-platform. |
| 403 Forbidden | Workspace lacks plan tier. | Upgrade or contact sales. |
| 404 Not Found | Action key not recognized. | Verify the slug. |
| 429 Rate Limited | Per-minute or per-day cap hit. | Backoff; reduce concurrency. |
| 500 Server Error | Unexpected TexAu issue. | Retry with backoff. |
| 502 Bad Gateway | Upstream provider 5xx. | Retry; we surface root cause. |
| 504 Timeout | Upstream slower than maxLatency. | Switch to `isAsync` polling. |
Related
More Full Enrich actions.
enrichment
Find Work Email by Name and Domain (FullEnrich)
Generates and verifies work email addresses from a name and company domain via FullEnrich.
enrichment
Find Mobile Number Using LinkedIn Profile URL (FullEnrich)
Discovers mobile phone numbers from a LinkedIn profile URL via FullEnrich.
enrichment
Find Mobile Number by Name and Domain (FullEnrich)
Finds mobile phone numbers using a person's name and company domain via FullEnrich.
FAQ.
Is this real-time?
Yes. Synchronous actions return in ~1–4 s. Long-running work uses async polling (see status 504 → switch to async).
Do I get charged on failure?
No. Verified failures cost zero credits. Provider miss / 5xx / timeout cascade to the next provider in the waterfall when applicable.
Does it work with Claude / Cursor via MCP?
Yes. Add the texau MCP server to your client config, then call `texau__full enrich-...` directly.
What CRMs can I push results to?
HubSpot, Salesforce, Pipedrive, Zoho, and GoHighLevel are bidirectional. Smartlead, Instantly, Lemlist, HeyReach, Apollo Sequences, and Reply.io for outbound.
Run Find Work Email Using LinkedIn Profile URL (FullEnrich) in 60 seconds.
Pull your API key, paste the cURL, ship to your CRM.