Vayne
Sales IntelligenceScrape LinkedIn Sales Navigator data with the Vayne API, extracting leads and accounts and scraping profiles and job listings. Agents build target lists from live hiring and headcount signals.
What This Integration Enables
Vayne is the volume end of this category, and two facts about it shape every workflow you build on top. The first is that scraping runs under a LinkedIn session cookie you upload to your own Vayne account, which Get LinkedIn Authentication Status reports on and Update LinkedIn Session Cookie replaces. The extraction happens as you. The second is that everything is priced and everything is asynchronous. Vayne publishes what each operation costs, from profile scraping and job scraping through to email and phone enrichment, and it exposes Get Credits so a flow can read the balance before it commits. Create actions return an identifier and a get action reports status, so the shape of a Vayne workflow is always submit, poll, collect.
Between those two facts sits the action that makes the whole thing governable. Check Sales Navigator URL validates a search, tells you how many prospects it currently matches and whether it is a leads or an accounts search, creates no order, and consumes no credits. Vayne built a free pre-flight into a metered product, which is a vendor telling you exactly where the decision point belongs. FlowRunner agents take that hint literally. The agent sizes the job, prices it, checks the session, and then puts the number in front of a person, because a search that matched forty thousand rows is not a bigger version of a search that matched four hundred. It is a different decision. Everything downstream, the job scraping at batch scale, the post scrapers that collect who reacted and who commented, the reverse lookups that match emails back to profiles, follows the same submit-and-poll rhythm with the same cost visibility.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Hiring as the buying trigger, monitored at batch scale
A team sells into engineering organizations and treats a specific kind of job posting as the strongest signal it has. An agent runs Create Job Search each morning on a boolean expression covering the relevant titles, scoped by location and company, and calls Load More Job Search Results until the requested pages are in. It then submits the new postings through Scrape LinkedIn Jobs Batch, which accepts up to two thousand entries, and polls Get LinkedIn Job Scraping Batch until the records and the CSV export are ready. What lands is not a list of jobs, it is a list of accounts that just told the market what they are building, with the seniority, employment type, description and hiring team on each posting. Those roll into HubSpot as account signals, and the ones crossing a threshold get a Slack notification to the owning rep.
Post engagement converted into a working list
A relevant post draws real engagement. Rather than reading it manually, the agent first calls Estimate Post Scraper Credits in Profile Posts or Company Posts mode, which projects how many posts, engaged people and credits the scrape would consume without creating anything. If the estimate fits the budget the flow allows, the agent calls Create Post Scraper and polls Get Post Scraper until it completes, collecting the posts with their engagement counts and the profiles that reacted or commented, including reaction type and comment text. Contact details for the shortlist come from Find Contact Details, and the finished rows go to Airtable with the comment attached so the outreach can reference what the person actually said.
Reattaching a purchased or inherited email list to live profiles
A team inherits a list of ten thousand email addresses with no other structure. The agent submits them through Create Reverse Lookup, which matches addresses back to LinkedIn profile URLs and charges only for successful matches at the rate the response reports. It polls Get Reverse Lookup through pending, processing, refunding and generating_csv until the pairs are available, then calls Get Reverse Lookup Export URL for the file. Unmatched addresses are separated out rather than silently carried forward, and the matched ones go through Scrape LinkedIn URLs Batch so every row arrives with a current title and employer instead of whatever was true when the list was made.
Human-in-Loop Highlight
Check Sales Navigator URL exists because Vayne knows what an oversized order does. A rep pastes a search they believe is tight, the pre-flight comes back with twenty seven thousand matches, and placing that order would consume most of the credit balance and run for hours against LinkedIn under the session cookie sitting on your account. Credits already spent are not returned by narrowing the search afterwards, and the exposure of a very large automated extraction belongs to the identity in that cookie, not to the connector. So the agent does not place the order. It reads Get Credits for the scraping and enrichment balances and the daily extraction limits, then Get LinkedIn Authentication Status to confirm the session is active rather than still checking. It posts all four numbers to the list owner in one message: the match count, the search type, the projected credit cost including the enrichment flags requested, and the balance that would remain. The question is a real choice, not a rubber stamp. Run it as sized, narrow the search and re-check, or split it across days inside the daily limit. Create Order is only ever called after a person has answered. This is what human-in-the-loop means on a metered connector: the agent does the arithmetic, the person owns the spend and the account it runs under.
Agent Capabilities
30 actionsAccount
3- Get Credits Retrieves the account's remaining scraping credits, enrichment credits, and the daily extraction limits that apply to leads and accounts orders. Read this before any large submission so the flow knows whether the balance covers the request.
- Get LinkedIn Authentication Status Reports whether the LinkedIn session cookie stored on the account is currently active and whether one is configured at all. Scraping depends on that session, so this is the first thing to check when orders fail to start.
- Update LinkedIn Session Cookie Replaces the stored LinkedIn session cookie. After the update the status moves to checking while Vayne validates the new value.
Sales Navigator Orders
5- Check Sales Navigator URL Validates a Sales Navigator search URL and returns how many prospects it currently matches, plus whether it is a leads or an accounts search. Creates no order and consumes no credits, which makes it the correct way to size a search before ordering.
- Create Order Submits a Sales Navigator search URL for extraction and returns the order with its initial status. Extraction runs asynchronously. Email and phone enrichment are available on leads searches only and must be disabled for accounts searches.
- List Orders Lists the account's non-expired orders, newest first. Each entry reports the order type, extraction progress, enrichment flags and creation time.
- Get Order Retrieves a single order with its extraction progress and, once finished, the per-format export block carrying downloadable CSV URLs. This is the operation a flow polls after Create Order.
- Generate Order Export Triggers CSV export generation for a finished order in the requested column format. Generation is asynchronous, so the flow polls Get Order until the matching export entry reports completed.
Contact Enrichment
3- Find Contact Details Submits a single-contact enrichment request for a work email, a mobile phone number, or both, and returns the reserved credit cost. Email lookups need first name, last name and company domain; phone lookups need a profile URL. Processing is asynchronous.
- List Contact Enrichments Lists recent enrichment requests created through the API, the MCP server or the Vayne dashboard, newest first. Enrichments attached to a Sales Navigator order export are not included.
- Get Contact Details Retrieves an enrichment request and, once complete, the resolved details including the work email and its service provider, the mobile number, its line type and country. Multi-contact requests expose their rows through pagination.
Profile Scraping
3- Scrape LinkedIn URL Scrapes a single profile or company URL using the configured session and returns the record synchronously. Profiles come back with headline, about, location, connection and follower counts, full experience and education history, and the profile picture URL.
- Scrape LinkedIn URLs Batch Submits multiple profile or company URLs for asynchronous scraping and returns the batch identifier with its reserved credit cost.
- Get LinkedIn Scraping Batch Retrieves a batch profile scraping job with its progress counters and, once complete, the extracted records and the CSV export URL. Results are paginated.
Job Scraping
3- Scrape LinkedIn Job Scrapes a single job posting synchronously and returns the flattened record, including title, canonical URL, job state, location, company, seniority, employment type, description and hiring team. Accepts either the numeric job identifier or the job URL.
- Scrape LinkedIn Jobs Batch Submits up to two thousand job postings for asynchronous scraping and returns the batch identifier and reserved credit cost. Each entry carries either a numeric identifier or a URL.
- Get LinkedIn Job Scraping Batch Retrieves a batch job scraping order with its lifecycle status and progress counters. Status moves through pending, processing and generating_csv before the records and the signed CSV export URL become available.
Job Search
3- Create Job Search Runs a job search using the configured session and fetches the requested number of result pages upfront. The search expression supports AND, OR and NOT operators and quoted phrases, and at least one of search text, location, geo ID or company must be supplied.
- Get Job Search Retrieves a job search with its status, page counters and the listings collected so far, each carrying the job identifier, title, company, location, posted date and easy-apply flag. When auto scrape was enabled the response also exposes the resulting scraping identifier.
- Load More Job Search Results Requests the next page of an existing job search. Pages loaded this way are never covered by the search's auto scrape, so a flow that relies on auto scrape needs to account for them separately.
Post Scraping
4- Create Post Scraper Submits a post scraping job that collects the people who reacted to or commented on posts, together with the post content and engagement counts. Single Post mode takes a post URL; Profile Posts and Company Posts modes take a profile or company page URL and support a time window and a post count limit.
- List Post Scrapers Lists the account's post scraping jobs with their mode, status, post and profile counts, credits used and CSV export URL where available.
- Get Post Scraper Retrieves a post scraping job and, once complete, the scraped posts with author, content and engagement estimates, plus the profiles that reacted or commented including reaction type and comment text.
- Estimate Post Scraper Credits Estimates how many posts, engaged people and credits a Profile Posts or Company Posts scrape would consume, without creating a job or spending anything. Passing the estimate to Create Post Scraper reserves the exact amount rather than the default reservation.
People Search
2- Find People Searches profiles at one or more companies by job title, returning up to twenty five profiles per page with name, position, tenure, location and company details. Job titles are expressed as a boolean query using AND, OR, NOT, parentheses and quoted phrases. Supplying a webhook URL runs the search asynchronously.
- Get People Search Result Retrieves an asynchronous people search by identifier, reporting its status and, once complete, the matched profiles together with the credits reserved and charged.
Reverse Lookup
4- Create Reverse Lookup Submits up to ten thousand email addresses to be matched back to LinkedIn profile URLs. Credits are charged per successful match only, at the rate the response reports.
- List Reverse Lookups Lists the account's reverse lookups with their status, email and match counts, per-match credit rate and CSV export URL where available.
- Get Reverse Lookup Retrieves a reverse lookup with its progress counters and the matched email-to-profile pairs. Status moves through pending, processing, refunding and generating_csv before completing.
- Get Reverse Lookup Export URL Returns the CSV export URL for a completed reverse lookup. While the file is still generating the response says so, so the flow retries once the lookup itself reports complete.
Frequently Asked Questions
What can FlowRunner do with Vayne?
FlowRunner agents can run Get Credits, Get LinkedIn Authentication Status, and Update LinkedIn Session Cookie in Vayne, plus 27 more actions.
Does connecting Vayne to FlowRunner require OAuth?
No. Vayne connects to FlowRunner with an API key, no OAuth flow required.
Can Vayne trigger a FlowRunner workflow automatically?
Vayne doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Vayne
$100 in credits. No card required. Connect in minutes.