Ask for what you want
Check the filters
NASSCOM membership
The actor has no membership filter, so this is applied to the leads after they come back. Apify still bills every lead it scraped.
Email verification
Every scraped address is checked with MillionVerifier before the CSV is written. By default only the confirmed-deliverable ones survive, so the file you download is ready to load straight into a sender.
Run it
The run
Import a CSV
Already scraped these leads somewhere else? Drop the actor's CSV here and it becomes a run like any other — verified, NASSCOM-matched, and ready for personalization, icebreakers, Sheets and Instantly. No Apify credit is spent.
Drop a CSV here, or
Up to 25 MB and 50,000 rows. Nothing is read or spent until you press Import.
NASSCOM membership
Email verification
Every run
Detail
No run selected.
Pick a finished run under Runs, then write your email here.
Write the email
Write the email you actually intend to send. Put
{{variables}} wherever something should change per lead. Click a column
below to drop it in filled from the scrape, or name a new one for the model to write
from that company's own description.
How to write them
Tell the model what a good fragment looks like — what to draw on, what tone, how long. It always works from the company description; this is how you steer what it does with it.
Preview
Nothing previewed yet.
Four real leads from this run, rendered as the email they'd receive.
Choose a run
Every finished run that has leads in it. Pick the list you want to send connection requests from — this also becomes the active run everywhere else in the app.
No run selected.
Pick one above to write icebreakers and choose who to connect with.
Write the icebreakers
One line per lead, the note that goes with the connection request: Hey {name}, loved seeing {something about them}. I'm also into {a plausible tie-in}, thought I'd connect. Written from the profile the scrape already holds — title, company, headline, what the company does — never from anything invented. Tell it who the sender is, so the tie-in has something to tie to.
Pick who to connect with
Send
The ticked leads go to the agency's LinkedIn Auto Connect phantom as a CSV it fetches from this server; the phantom sends the requests from the connected LinkedIn account and skips anyone it has already asked. PhantomBuster's guidance is 20 requests a working day, spread over launches; LinkedIn allows about 100 a week per account, shared by every client because one account sends.
Google Sheet
Push this run into a sheet with every column it has, fix the lines you don't like, delete the rows you don't want, then pull it back. Only the personalization columns are read back — the scraped facts stay as scraped. A deleted row is a dropped lead.
Instantly
Leads go into the campaign you pick, with every field they carry attached as custom variables you can use as merge tags. Pushing never starts sending — activation is the separate button below.
Weekdays only. The campaign is created paused and empty — write the sequence in Instantly, then come back and push.
This becomes the campaign's first email, replacing whatever
sequence is in it now. Your column names are translated to Instantly's own merge tags on
the way over, so {{first_name}} arrives as {{firstName}} and
your written variables go across unchanged.
API keys
Paste your own keys here and they take effect immediately — no restart, no command line. A key saved here beats the one set on the server; clearing a field falls back to the server's. Values are stored on this app's private disk and never shown again, only their last four characters.
NASSCOM member directory
Crawled from the public directory under a stable sort. Pick companies here and scrape only their people — that turns membership from an after-the-fact check into a filter the actor actually applies.
| Company | City | Domain |
|---|