Scalelist
Sales IntelligenceConnect AI agents to Scalelist, a B2B lead generation and data enrichment platform. Agents find verified contact details for a person or domain, and run bulk enrichment across a batch of prospects as an asynchronous job.
What This Integration Enables
Scalelist finds two things: verified work emails and mobile phone numbers. Everything else in the connector exists to manage what those two things cost. That is not a criticism, it is the correct reading of a product where credits are consumed only when a result is found, an email costs 1 credit, and a mobile number costs 20. A twentyfold price difference between two actions that look almost identical in a flow editor is the single most important fact about building on this API, and a flow designed as though they were interchangeable will surprise somebody.
The single lookups are straightforward. Find Email takes a name, either a full name or a first plus last, together with either a company domain, which is preferred, or a company name, and returns the email with a verification status and the resolved domain. Find Emails by Domain works the other way, returning up to 100 leads at a company with name, job title, department, seniority, social profile URL, and verification status, plus a meta block reporting the total matches available so a flow knows whether it saw everything. Find Phone is most accurate when given a LinkedIn ID or profile URL, and will otherwise work from a name plus company details refined by email, job title, or city.
The bulk actions are asynchronous and worth understanding precisely, because the catalog phrasing can suggest something the API does not do. Scalelist does not hold a list you enrich in place. Start Bulk Email Finder and Start Bulk Phone Finder take an array of people in the request, return a job id and a lead in queue count immediately, and process in the background. You then poll Get Bulk Email Results or Get Bulk Phone Results with that job id, with results accumulating while the job runs, or supply a webhook URL to have completed results POSTed to an endpoint of your choosing. That endpoint is yours; supplying it does not create a FlowRunner trigger and does not cause FlowRunner to receive an event. This connector has no triggers at all, so the shape of every flow here is a schedule or an upstream system starting the work and a poll collecting it.
One small feature does more for flow reliability than any of the above: every finder action accepts a custom object that is echoed back untouched in each result. Put your own record id in it and the reconciliation problem disappears. Also note that all request and response fields are snake_case, and the canonical name for a company website is company_domain, with legacy aliases still accepted but no longer documented by this extension.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A Sales Navigator export that arrives usable
A prospecting list is exported from LinkedIn with names, titles, and companies but no addresses. The agent calls Get Account Information first, because a batch that runs out of credits halfway through leaves a partially enriched list that is worse than an unenriched one. With the balance confirmed, it calls Start Bulk Email Finder with the batch, passing each row's CRM record id inside the custom object. The job id comes back with the queue count, and the agent polls Get Bulk Email Results until the status indicates completion, writing verified addresses into HubSpot as they accumulate. Because the custom object came back untouched, every address lands on the record it belongs to with no name matching, which is the step that quietly corrupts these imports when two prospects share a surname.
Mapping a target account before anyone calls it
An account is flagged as in-market and nobody knows who to talk to. Find Emails by Domain returns up to 100 people at that domain with job title, department, and seniority attached, and the meta block reports how many matches exist in total, so the agent knows whether a limit of 10 gave it the buying committee or the first ten names alphabetically. The agent filters to the two or three titles that actually sign, writes them to Google Sheets as a proposed contact map, and posts the summary to Slack. No phone lookups run at this stage. The point of the cheap pass is to decide who is worth the expensive one.
Watching the spend instead of reconstructing it
Get Credit History returns daily consumption as an array of records, each reporting the date, total credits consumed, the split between email credits and phone credits, and the transaction count for that day. A weekly flow reads it, computes the email-to-phone ratio, and posts it beside the number of meetings booked. That ratio is the useful number: a team spending most of its credits on mobile numbers and booking meetings by email is paying twenty times over for a channel it is not using. The agent reports the pattern and lets the sales leader decide what to change, which is a better use of the data than an automatic cap that stops a legitimate campaign mid-week.
Human-in-Loop Highlight
Start Bulk Phone Finder is where this connector stops being an ordinary data lookup. It takes a batch of people, ideally identified by LinkedIn ID or profile URL for accuracy, and returns their mobile phone numbers, consuming 20 credits per number found. Two things about that deserve a human and not a threshold. The first is arithmetic: at twenty times the cost of an email, a batch queued by mistake, or queued twice because a poll loop was retried, spends real money in a way no other action in this connector can, and the job is already running by the time the id comes back. The second is the more important one. A verified work email reaches someone at work. A mobile number reaches them wherever they are, on a device that is theirs, and the person on the other end never gave it to you. That is a different act from finding an address, and the API charges differently precisely because it is harder to get, which is another way of saying the person concerned did not publish it. Nothing in the response will flag this, and the failure mode is not an error, it is a campaign that works and damages the brand while it does. So the agent assembles the batch and hands over the decision. It calls Get Account Information for the current balance, counts the rows, and asks the outbound owner: "Batch of 240 prospects ready for Start Bulk Phone Finder. At 20 credits per number found, a full match rate costs 4,800 credits against a balance of 6,100. These are personal mobile numbers for people who have had no contact with us. Run the full batch, run only the 31 accounts already in an open opportunity, or skip phone and proceed with email only?" That is a question about spend, reach, and consent at the same time, which is exactly the kind a threshold cannot answer. Making it a human-in-the-loop step is what lets the email side of this connector run on a schedule without anyone watching it.
Agent Capabilities
9 actionsAccount and Credits
2- Get Account Information Returns the authenticated Scalelist account profile, including account id, email, name, remaining credit balance, and current subscription plan. The correct first call before any batch, because a bulk job that exhausts the balance mid-run leaves a half-enriched list.
- Get Credit History Returns daily credit consumption as an array of records, each reporting the date, total credits consumed, the split between email credits and phone credits, and the number of transactions that day. The split is the number worth watching, since email and phone differ in cost by a factor of twenty.
Single Lookups
3- Find Email Finds a verified work email for one person from their name and company. Supply either a full name or a first plus last name, together with either the company domain, which is preferred, or the company name. Returns the email, a verification status, and the resolved company domain. One credit is consumed only when an email is found.
- Find Emails by Domain Finds work emails for people at a given company domain, returning leads with email, name, job title, department, seniority, social profile URL, and verification status, plus a meta block reporting the total matches available. Limit accepts 1 to 100 and defaults to 10, so read the meta block before assuming the default returned everyone. One credit per email found.
- Find Phone Finds a mobile phone number for one person. A LinkedIn ID or profile URL gives the most accurate result; otherwise supply a name with company details, optionally refined by email, job title, or city. Returns the number and a status. Twenty credits are consumed only when a mobile number is found, which makes this the most expensive single action in the connector by a wide margin.
Bulk Jobs
4- Start Bulk Email Finder Starts an asynchronous bulk email lookup for a list of people supplied in the request. Each item accepts a name, a company domain or company name, and an optional custom object echoed back in the results. Returns a job id and the number of leads queued. Poll Get Bulk Email Results, or supply a webhook URL of your own to receive the completed results by push. One credit per email found.
- Get Bulk Email Results Fetches the current status and available results for a bulk email job by its job id, returning the status and an array of per-person results. Results accumulate while the job processes, so poll until the status indicates completion rather than treating the first response as final.
- Start Bulk Phone Finder Starts an asynchronous bulk mobile phone lookup for a list of people supplied in the request. Each item accepts a LinkedIn ID or profile URL for best accuracy, or a name with company details, plus optional email, job title, city, and a custom object echoed back in the results. Returns a job id and the queued count. Twenty credits are consumed per mobile number found, which is why this action belongs behind an approval rather than inside a loop.
- Get Bulk Phone Results Fetches the current status and available results for a bulk phone job by its job id, returning the status and an array of per-person results. As with the email job, results accumulate as the job runs.
Frequently Asked Questions
What can FlowRunner do with Scalelist?
FlowRunner agents can run Get Account Information, Get Credit History, and Find Email in Scalelist, plus 6 more actions.
Does connecting Scalelist to FlowRunner require OAuth?
No. Scalelist connects to FlowRunner with an API key, no OAuth flow required.
Can Scalelist trigger a FlowRunner workflow automatically?
Scalelist doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Scalelist
$100 in credits. No card required. Connect in minutes.