Find Mobile Number Actions: Full Reference
This article covers every action in TexAu that finds mobile and direct-dial phone numbers. It includes inputs, outputs, credit costs, and use cases by team type.
Before you begin
- Connect each integration at Settings > Integrations before running mobile number actions.
- Mobile phone data has lower coverage than email. Expect 20–50% hit rates depending on seniority and country.
- TexAu's built-in waterfall action tries multiple providers automatically, giving you higher overall coverage.
- Phone numbers are typically returned in international format (e.g.,
+1 555 555 5555). Use Normalize Phone Number (a free utility action) to standardize formats before pushing to a CRM.
Find Mobile Number by LinkedIn URL (B2B Enrichment)
Finds a person's mobile phone number using their LinkedIn profile URL via B2B Enrichment.
Integration: B2B Enrichment
Credit cost: 10 credits per row
Category: Enrichment
Inputs
| Field | Required | Description |
|---|---|---|
| LinkedIn URL | Yes | Full LinkedIn profile URL |
Outputs
| Field | Description |
|---|---|
| Raw Phone | Mobile phone number in raw format |
Use cases
Agencies: Use for high-value accounts where calling converts better than email. B2B Enrichment phone data works well for VP and C-suite contacts.
Founder-led teams: Direct-dial numbers let you bypass gatekeepers for cold calling. Combine with a verified email for multi-channel outreach.
RevOps: Flag rows where phone enrichment costs 10 credits: only run this on your tier-1 accounts to control spend.
GTM engineers: Run Normalize Phone Number on the raw output before pushing to Salesforce or HubSpot to ensure consistent format.
Find Mobile by LinkedIn URL (Apollo)
Finds a direct-dial mobile number from a LinkedIn profile URL via Apollo.
Integration: Apollo
Credit cost: Check the action details panel
Category: Enrichment
Inputs
| Field | Required | Description |
|---|---|---|
| LinkedIn URL | Yes | Full LinkedIn profile URL |
Outputs
| Field | Description |
|---|---|
| Phone Number | Direct mobile or work number |
| Phone Status | Verification status |
| First Name | From LinkedIn |
| Last Name | From LinkedIn |
| Job Title | Current title |
| Organization Name | Current employer |
Use cases
Agencies: Apollo phone coverage is solid for US-based enterprise contacts. Good starting point before trying more expensive providers.
RevOps: Apollo's output includes job title and employer name alongside the phone number. A single action can backfill multiple fields in your CRM at once.
Find Mobile by Name and Domain (Apollo)
Finds a direct-dial phone number using a person's first name, last name, and company domain via Apollo.
Integration: Apollo
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 |
|---|---|
| Phone Number | Direct mobile or work number |
| Phone Status | Verification status |
| Also returns work email if found | |
| Organization Name | Company name |
Use cases
Agencies: Use when you have a name+company list (e.g., from an event or directory) but no LinkedIn URL. Apollo can often match on name+domain alone.
RevOps: This action returns both phone and email in one call, reducing the number of actions and credits needed per row.
Find Mobile by LinkedIn URL (FullEnrich)
Finds a verified direct-dial phone number from a LinkedIn URL via FullEnrich.
Integration: FullEnrich
Credit cost: Check the action details panel
Category: Enrichment
Inputs
| Field | Required | Description |
|---|---|---|
| LinkedIn Profile URL | Yes | Full LinkedIn profile URL |
Outputs
| Field | Description |
|---|---|
| Phone Number | Direct-dial mobile number |
| Phone Status | Verification status |
Use cases
Agencies: FullEnrich has strong European phone coverage. If you're running campaigns targeting UK, DACH, or Nordics, FullEnrich often outperforms US-centric providers.
GTM engineers: Stack FullEnrich as a phone fallback after Apollo in your waterfall pipeline.
Find Mobile by Name and Domain (FullEnrich)
Finds a mobile phone number using first name, last name, and company domain via FullEnrich.
Integration: FullEnrich
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 |
|---|---|
| Phone Number | Direct-dial mobile number |
| Phone Status | Verification status |
Use cases
RevOps: Use when your CRM has name+company but no LinkedIn URL. Good for filling phone gaps in existing records.
Find Mobile by LinkedIn URL (Datagma)
Finds a mobile phone number from a LinkedIn profile URL via Datagma.
Integration: Datagma
Credit cost: Check the action details panel
Category: Enrichment
Inputs
| Field | Required | Description |
|---|---|---|
| LinkedIn URL | Yes | Full LinkedIn profile URL |
Outputs
| Field | Description |
|---|---|
| Phone Number | Mobile phone number |
Use cases
Agencies: Datagma performs well for contacts in Continental Europe and the Middle East, where other providers have gaps.
GTM engineers: Use Datagma as a fourth-tier fallback in a waterfall: Apollo → FullEnrich → B2B Enrichment → Datagma.
Find Mobile Using Email (Datagma)
Finds a mobile phone number for a contact when you already have their email address via Datagma.
Integration: Datagma
Credit cost: Check the action details panel
Category: Enrichment
Inputs
| Field | Required | Description |
|---|---|---|
| Yes | Work email address |
Outputs
| Field | Description |
|---|---|
| Phone Number | Mobile phone number |
Use cases
RevOps: Your CRM has emails but is missing phone numbers. Run this on all contacts where phone = empty to fill the gap in bulk.
Agencies: When a client hands off a list with emails but no phones, this is the fastest path to phone coverage without needing LinkedIn profiles.
Find Mobile by LinkedIn URL (Findymail)
Finds a direct-dial mobile number from a LinkedIn profile URL via Findymail.
Integration: Findymail
Credit cost: Check the action details panel
Category: Enrichment
Inputs
| Field | Required | Description |
|---|---|---|
| LinkedIn Profile URL | Yes | Full LinkedIn profile URL |
Outputs
| Field | Description |
|---|---|
| Phone Number | Direct-dial mobile number |
Use cases
Agencies: If you're already using Findymail for email finding, using Findymail mobile too avoids managing a second provider key.
Find Mobile by LinkedIn URL (Prospeo)
Finds a mobile phone number from a LinkedIn profile URL via Prospeo.
Integration: Prospeo
Credit cost: 2 credits per row
Category: Enrichment
Inputs
| Field | Required | Description |
|---|---|---|
| LinkedIn URL | Yes | Full LinkedIn profile URL |
Outputs
| Field | Description |
|---|---|
| Phone Number | Mobile phone number |
Use cases
Agencies: At 2 credits, Prospeo is one of the lower-cost mobile finders. Good for mid-tier accounts where you want phone coverage without paying 10 credits per row.
Find Mobile by LinkedIn URL (TexAu Waterfall)
Finds a mobile phone number by automatically trying multiple providers in sequence. Returns the first valid result. No individual provider API key required.
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 |
|---|---|
| Phone Number | Direct mobile number |
| Source | Which provider returned the result |
Use cases
Agencies: Fastest path to maximum phone coverage. TexAu tries providers in order and stops when a result is found, billing only for the lookup that worked.
Founder-led teams: No API key management needed. Add this action to any table with LinkedIn URLs and get phones automatically.
RevOps: Use the Source output to track which provider is filling most of your phone data: useful for evaluating enrichment vendor performance.
GTM engineers: Combine with Normalize Phone Number downstream to standardize formats before CRM sync or dialers.
Troubleshooting
Phone number returns empty
- Mobile coverage is lower than email coverage. 20–40% hit rates are normal.
- For senior contacts (C-suite, VP), coverage is typically higher because their direct numbers appear in more databases.
- Try a different provider if one returns empty. Coverage varies by region and seniority.
Phone number format is inconsistent
- Use the free Normalize Phone Number utility action after enrichment. It standardizes all numbers to E.164 format, which most CRMs and dialers require.
TexAu waterfall charges more credits than expected
- The waterfall tries providers in order. If the first provider returns empty, it tries the next, which costs credits. Each provider attempt charges its own credit cost. Check your Credit Usage log at Settings > Billing > Credit History.
Numbers are not mobile: they are office switchboards
- Some providers return office main lines rather than direct dials. Check the phone type field if the provider returns it. For direct-dial-only results, use B2B Enrichment or FullEnrich, which label their phone types more precisely.