outreach-find-phone

Solid

Find direct mobile numbers for the people on a lead list with Emelia's phone finder, from their LinkedIn profile URL, one at a time or in bulk. States the credit cost before spending, polls each job to completion, handles found and not found honestly, and writes the numbers into outreach/leads.csv and outreach/enrichment.json. Emelia does not place the calls: the number goes to your phone or your CRM. Triggers on: find phone, phone finder, find mobile, mobile number, direct dial, phone number, cell number, find the number of, phone enrichment, cold call list, get phone numbers.

Data & Documents 12 stars 2 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
37
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Find direct mobile numbers ## What this does Turns a LinkedIn profile URL into a direct mobile number, using Emelia's phone finder. It counts the rows, states the credit cost before spending anything, runs the lookups, and reports found and not found without rounding either up. The number is data. Emelia does not dial it, does not record calls, and does not run a dialler. You call from your own phone, or you push the number into your CRM and your team calls from there. ## When to use it Use it when a segment is worth a call: high value accounts, a warm reply that went quiet, an executive who never answers email, a market where email is weak. Do not use it as a default step on a whole list. A mobile costs roughly fifty times what an email costs, so a phone run on 500 rows is a budget decision, not a formality. Enrich the top slice, not the list. Use a different skill when: - The list is not filtered. `outreach-filter` first, always. - You want email addresses. That is `outreach-find-email`, and it is far cheaper. - You want the full waterfall with one budget for the run. That is `outreach-enrich`, which calls this skill last and only on the rows you flagged. ## Inputs The finder takes exactly one input. | Field | Required | Notes | |-------|----------|-------| | `linkedinUrl` | yes | A public LinkedIn profile URL: `https://www.linkedin.com/in/<slug>`. | There is no name plus company path for phones. If a row has no LinkedIn URL, it cannot be looked up. Say so, ...

Details

Author
emelia-io
Repository
emelia-io/claude-outreach
Created
3 days ago
Last Updated
2 days ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

outreach-find-email

Find professional email addresses for the people on a lead list, one at a time or in bulk, with Emelia's email finder. Runs the three attempt fallback cascade that recovers the rows a single lookup misses: the domain first, then the company name, then the trade name. States the credit cost before spending anything, polls each job to completion, and records what was found, what was not and which attempt won in outreach/enrichment.json and outreach/leads.csv. What the finder returns is already verified and goes straight into a campaign, so it never needs a second pass through the verifier. Never guesses an address pattern and calls it found. Triggers on: find email, email finder, find emails, find the email of, email address, email lookup, email enrichment, enrich emails, missing emails, bulk email finder, retry the finder, email not found, get emails for my list.

12 Updated 2 days ago
emelia-io
Data & Documents Solid

outreach-enrich

The full enrichment waterfall on a lead list: filter first, find the missing emails, verify only the addresses that came from somewhere other than Emelia's finder, find mobile numbers only where they are worth 50 credits, then decide row by row who is sendable, who is on hold and who is dropped. Ends by routing the rows to separate destinations, one list per destination: addresses found go to the email campaign list, rows with no address but a valid LinkedIn profile URL are proposed as a separate LinkedIn campaign, and the rest is set aside and counted. Never pushes a whole enriched base into a single Emelia list. Runs under a credit budget fixed before the first call and stops when it is reached. Writes outreach/enrichment.json with every counter and updates outreach/leads.csv without losing a single original column, then fills the custom fields your sequence needs. Triggers on: enrich, enrichment, enrich my list, waterfall, find and verify, clean and enrich, contact data, credits budget, how much will this

12 Updated 2 days ago
emelia-io
Data & Documents Solid

outreach-leads

Build the lead list by actually querying the sources this repository supports: the Basile API for French B2B, where an ICP becomes a plan of several queries (adjacent job titles, size bands, zones, sources), each counted for free with countOnly before a single record is extracted, then merged, deduplicated and cut of what is obviously off target before any enrichment credit is spent; a LinkedIn Sales Navigator search collected through the Emelia LinkedIn scraper; or a CSV the user already has (encoding, separator and column mapping handled). Writes outreach/leads.csv with a fixed 26 column schema that every other skill in this repository reads, including a source and a source_url column on every row. Reads outreach/icp.json, a Sales Navigator URL or a file path. Triggers on: build a list, lead list, source leads, find companies, find prospects, Basile, api.basile.cc, docs.basile.cc, French companies, SIREN, NAF, activity filter, count before extracting, Sales Navigator, LinkedIn search, LinkedIn scraper, scra

12 Updated 2 days ago
emelia-io