Freelance Recruiter Workflow: From LinkedIn Shortlist to Contact Fields
Freelance recruiter workflow: turn a LinkedIn shortlist into contact fields with a lookup API – empty means not found, INR credits, no sales cloud required.

Freelance recruiters in India often already live in LinkedIn, WhatsApp, and a spreadsheet. The missing step is not another sales cloud – it is contact fields for people you already shortlisted. Invenitor is a contact lookup API: paste a LinkedIn (or GitHub) profile URL, get email, phone, or links when we have them, and treat empty as not found. Pay in INR credits (~₹2 each) via Razorpay/UPI. H1 vibe: Connecting people. A lookup API, not a sales cloud.
This Week 2 spoke is the freelance cadence. Pair it with the India boutique desk frame in India Boutique IT Staffing – Candidate Contacts Without a Sales Cloud and the category definition in What a Contact Lookup API Actually Does.
What does the freelance workflow look like end to end?
- Shortlist on LinkedIn – save people who fit the req, not a random scrape.
- Paste profile URLs into a sheet column (or a small script).
- Call the lookup –
POST /api/v1/findwith the URL (name helps). Docs: /docs. - Write back only returned fields – email and/or phone when found; leave empty empty.
- Outreach on channels you already use – WhatsApp, email, phone – with human judgment.
Hub HowTo if you want the API shape spelled out: LinkedIn or GitHub Profile URL → Contact Lookup API.
Why shortlist first, look up second?
Lookup without a shortlist turns into spray. Spray burns trust, burns time, and tempts people to invent mailboxes when coverage is thin. Soft mesh coverage means we return contacts when we have them – coverage varies by person and source. We do not publish hit-rate percentages. Empty completed finds are free under Credit B; inventing a mailbox to “fill the cell” is still wrong even when billing is fair.
Honesty deep dive: Empty Means Not Found – Why Guessed Emails Break Hiring.
How should a solo recruiter size credits for a week?
New accounts get 5 free lookups. After that, packs are about ₹2 per credit, expire in 30 days, paid on Razorpay (UPI/cards). 1 credit only when we return an email, a phone, or both. Empty completed finds are free. Timeouts and errors do not spend. Illustrative desk math only – not a forecast: if you paste 25 clean URLs in a week and some return contacts while others return empty, you spend only on found outcomes. Empties stay free. Timeouts stay free.
Commercial feel: INR Credit Packs for Contact Lookup – How Razorpay Pricing Feels. Seat comparison: Seat Subscriptions vs Pay-Per-Lookup Credits – A Cost Model.
What belongs in the sheet vs WhatsApp?
Keep the sheet as the durable record: name, profile URL, role, req id, contact fields, status. Use WhatsApp for confirmation and conversation – not as the only database. When a lookup returns empty, mark “not found” and decide whether to ask a referral, wait, or move on. Do not paste a guessed @gmail.com pattern into the email column.
Plain English enrichment language: Contact Enrichment Explained for Recruiters – Plain English.
How do agents fit a freelance desk without becoming scrapers?
If you use Claude, Cursor, or another agent to fill columns, point it at MCP or REST – not at scraping LinkedIn HTML. Agents welcome; scrapers are a detour. See MCP for Recruiting Agents – Wire Contact Lookup Without Building a Scraper and /mcp.md. Teach the agent: empty ⇒ not found; never invent.
What mistakes burn freelancers fastest?
- Looking up company pages instead of person profile URLs.
- Re-pasting the same URL hoping for a different answer without new evidence.
- Treating empty as “broken API” instead of not found.
- Buying a USD seat for a week of ten lookups.
- Mixing invented emails into client-facing shortlists.
Sibling Week 2 playbook for multi-recruiter desks: Agency Desk Playbook: Bulk Candidate Sheets + API Lookups in India.
How does this differ from a sales cloud?
A sales cloud wants seats, sequences, and a database narrative. A freelance recruiter usually wants: URL in → fields out when found → pay for found outcomes → stop when the sprint ends. That is Invenitor’s lane. Pricing live tiles: /pricing.
What should you do next?
Sign in, spend the five free lookups on real shortlist URLs, buy a small INR pack on pricing if the path fits, and keep /docs open. Write back only what was found. Keep empty empty. That is the freelance workflow – Connecting people without inventing them.
Daily cadence that keeps empty honest
Morning: update the LinkedIn shortlist. Midday: batch paste URLs and look up. Afternoon: outreach only where email or phone exists. Evening: mark empties (referral, wait, or drop). Soft mesh: contacts when we have them – share Empty Means Not Found in SOPs. Refill via /pricing inside the 30-day pack window.
Qualify URLs before you spend attention
Reject company pages and search URLs. Prefer person profile URLs. Dedupe before lookup. Category: What a Contact Lookup API Actually Does. Keep /pricing and /docs bookmarked. Soft mesh honesty beats fake hit-rate slides with clients.
Burst-week planning
PAYG fits bursty weeks better than seats – Pay-As-You-Go Contact APIs, Seat Subscriptions vs Pay-Per-Lookup Credits. Buy for the burst; 30-day expiry. GitHub reqs: GitHub Profile URL Contact Lookup. Primary fields: One Primary Contact, Never Invented.
Questions
What is the freelance recruiter workflow in one sentence?
Shortlist people on LinkedIn, call a contact lookup API with profile URLs, save email/phone only when returned, and leave empty as not found.
Do I need a CRM to use Invenitor as a freelancer?
No. A sheet plus WhatsApp is enough. Invenitor is a lookup API, not a sales cloud.
When does a credit spend?
1 credit only when we return an email, a phone, or both. Empty completed finds are free. Timeouts and errors do not spend.
Can I look up GitHub profiles too?
Yes. Person GitHub profile URLs work on the same find path. See the hub HowTo and /docs.
What if the API returns empty?
Empty means not found. Soft mesh coverage varies. Do not invent an email.
Where do I start today?
Sign in, use free lookups or buy a pack on /pricing, then POST /api/v1/find per /docs.
Is MCP useful for freelancers?
If you use an agent to fill columns, yes – wire MCP per /mcp.md instead of scraping.
More in this cluster

India Boutique IT Staffing – Candidate Contacts Without a Sales Cloud
India boutique IT staffing desks can look up candidate contacts from LinkedIn or GitHub URLs with an INR credit API – no USD sales cloud required.
Read

Contact Enrichment Explained for Recruiters – Plain English
Contact enrichment means adding email or phone to a person you already identified – usually from a LinkedIn or GitHub URL – without turning your desk into a sales cloud.
Read

Adding Contact Lookup to an ATS: Architecture Notes for Builders
Architecture notes for builders: add contact lookup to an ATS as an optional module – profile URL in, contacts out when found, empty UI that stays honest.
Read