Skip to main content

Lusha

Lusha is a B2B contact and company data platform that sales and marketing teams use to find, enrich, and prioritize prospects. The Lusha connector uses the Lusha V3 API to search, enrich, and prospect contacts and companies, find lookalikes, recommendations, buying groups, and signals, score accounts against your ideal customer profiles, and read tables, conversations, and webhook logs. It can also manage Lusha tables and webhook subscriptions. Most search, enrich, and scoring templates spend Lusha credits.

Lusha icon

Power end-to-end data operations for your Lusha API with Nexla. Our bi-directional Lusha connector is purpose-built for Lusha, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Lusha or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Lusha workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

  • Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
  • Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
  • API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
  • Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites​

Nexla connects to the Lusha V3 API (https://api.lusha.com) with a Lusha API key, which it sends in the api_key request header on every call. To get an API key:

  1. Sign in to the Lusha dashboard.

  2. Open the API page of the dashboard, and generate or copy your API key.

  3. Store the key securely. It gives access to your account's credits, so use it only in server-side tools such as Nexla, and never in client-side code.

For more information, see Lusha's API overview and API FAQ.

Lusha credits

Lusha bills credits for most V3 data operations: searches, enrichment, prospecting, lookalikes, recommendations, buying groups, signals, scoring, and reading table rows. All users and API keys on a Lusha account draw from the same credit pool, and once it runs out, credit-consuming calls return 402 Insufficient credits. The credit usage table below lists every template that spends credits. Every credit-consuming source template fetches one page of results per run, so each scheduled run is billed again. To check your balance and the credit price of each action, use the free Account Usage template. See Lusha's billing FAQ for details.

Authenticate​

Credentials required​

Authenticate with your Lusha API key.

FieldRequiredSecretDescription
API KeyYesYesYour Lusha API key (keep it secret)

Create a credential in Nexla​

  1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Lusha

LushaCred.png
  1. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

  2. In the API Key field, enter the API key from the API page of your Lusha dashboard.

    The API key is sensitive and should be kept secure. If it is exposed, regenerate it in the Lusha dashboard and update the key on this credential.

  3. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Nexla tests the credential by reading your account usage (GET /v3/account/usage), which does not use credits.

Use as a data source​

To create a new data flow, navigate to the Integrate section, click the New Data Flow button, and select the desired flow type. Select the Lusha connector tile, then select the credential that will be used to connect to the Lusha API, and click Next; or, create a new Lusha credential for use in this flow.

Credit usage​

The following templates spend Lusha credits. Every other template on this page is free. Lusha sets the price of each action per plan; the Account Usage template returns the current prices for your account.

TemplateTypeWhat Lusha charges for
Person Lookup (Search and Enrich Contacts)SourceEach person found, plus each revealed email or phone number
Company Lookup (Search and Enrich Companies)SourceEach company found
Search ContactsSourceEach contact matched
Search CompaniesSourceEach company matched
Enrich ContactsSourceEach revealed email or phone number
Enrich CompaniesSourceEach company enriched
Prospect ContactsSourceEach result returned
Prospect CompaniesSourceEach result returned
Contact LookalikesSourceEach result returned
Company LookalikesSourceEach result returned
Contact RecommendationsSourceEach result returned
Company RecommendationsSourceEach result returned
Buying Group ContactsSource1 credit per contact returned
Contact SignalsSourceEach matched signal
Company SignalsSourceEach matched signal
Score Contacts by Signal ActivitySource1 credit per scored contact, once priced on your account
Score Companies by Signal ActivitySource1 credit per scored company, once priced on your account
Score Contacts by ICP FitSource1 credit per scored contact
Score Companies by ICP FitSource1 credit per scored company
Website VisitorsSourceNot documented by Lusha; the response reports credits charged
Search ConversationsSource1 credit per 25 conversations returned, once priced on your account
Get Conversation TranscriptSource1 credit per request, once priced on your account
Get Contacts Table EntitiesSourceEach row returned
Get Companies Table EntitiesSourceEach row returned
Add Entities to Companies TableDestinationEach newly added company
Run Column on Contacts TableDestinationEach row processed, at the column's credit tier
Run Column on Companies TableDestinationEach row processed, at the column's credit tier

Two free destination templates can lead to charges later: Create Companies Table charges for companies seeded through ids, and each signal delivered to a subscription made with Create Webhook Subscriptions costs 1 credit.

To keep spending predictable, the credit-consuming templates default to small pages (10 results) and reveal emails only. Raise these settings only when you need more data.

Endpoint templates​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Lusha API endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Settings described as JSON arrays or objects are sent to Lusha as-is, so they must be valid JSON. Most V3 lookups accept up to 100 items per call.

Account​

Account Usage

This endpoint template returns your Lusha credit balance (total, used, and remaining), rate-limit usage, plan details, and the credit price of each billable action. Use it to monitor spending before running credit-consuming templates.

Search and enrich​

Person Lookup (Search and Enrich Contacts)

This endpoint template finds up to 100 people and reveals their contact data in one call, returning one record per person with name, job title, company, and the revealed emails or phone numbers. It replaces the V2 person lookup.

  • Credits: Consumes credits for each person found, plus each revealed email or phone number.
  • Enter Contacts as a JSON array of 1 to 100 contacts. Identify each by id, linkedinUrl, email, or firstName and lastName with companyName or companyDomain, for example [{"email": "jane@example.com"}].
  • Select Reveal: ["emails"] (default), ["phones"], or ["emails","phones"]. Each revealed data point is billed, and phones are priced higher than emails.
  • Reference: Lusha API reference: Person Lookup (Search and Enrich Contacts)

Company Lookup (Search and Enrich Companies)

This endpoint template finds up to 100 companies and returns full firmographics for each one in a single call. It replaces the V2 company lookup.

  • Credits: Consumes credits for each company found.
  • Enter Companies as a JSON array of 1 to 100 companies, each identified by domain, name, or id, for example [{"domain": "example.com"}]. An optional clientReferenceId on each item is returned with its result.
  • Reference: Lusha API reference: Company Lookup (Search and Enrich Companies)

Search Contacts

This endpoint template matches up to 100 contacts and returns a preview of each one, including which data points are available to reveal. It does not return emails or phone numbers; pass the returned IDs to Enrich Contacts for those.

  • Credits: Consumes credits for each contact matched.
  • Enter Contacts as a JSON array of 1 to 100 contacts. Identify each by id, linkedinUrl, email, or firstName and lastName with companyName or companyDomain, for example [{"email": "jane@example.com"}].
  • Reference: Lusha API reference: Search Contacts

Search Companies

This endpoint template matches up to 100 companies and returns a preview of each one (size, industry, location, and which data is available). Pass the returned IDs to Enrich Companies for full firmographics.

  • Credits: Consumes credits for each company matched.
  • Enter Companies as a JSON array of 1 to 100 companies, each identified by domain, name, or id, for example [{"domain": "example.com"}]. An optional clientReferenceId on each item is returned with its result.
  • Reference: Lusha API reference: Search Companies

Enrich Contacts

This endpoint template reveals emails and phone numbers for up to 100 contact IDs returned by Search or Prospecting. If Lusha needs more time, the response includes a job; read its results with Get Contacts Enrich Job.

  • Credits: Consumes credits for each revealed email or phone number.
  • Enter Contact IDs as a JSON array of 1 to 100 Lusha contact IDs (the id of results from Search Contacts or Prospect Contacts).
  • Select Reveal: ["emails"] (default), ["phones"], or ["emails","phones"]. Each revealed data point is billed, and phones are priced higher than emails.
  • Reference: Lusha API reference: Enrich Contacts

Enrich Companies

This endpoint template returns full firmographics (industry, size, revenue, locations, technologies, funding, and social links) for up to 100 company IDs returned by Search or Prospecting.

  • Credits: Consumes credits for each company enriched.
  • Enter Company IDs as a JSON array of 1 to 100 Lusha company IDs (the id of results from Search Companies or Prospect Companies).
  • Reference: Lusha API reference: Enrich Companies

Get Contacts Enrich Job

This endpoint template returns the status and any late results of an Enrich Contacts job.

Prospecting and filters​

Prospecting templates take filter objects. Use the free filter templates to find valid filter names and values before you spend credits on a prospecting search.

Prospect Contacts

This endpoint template searches Lusha for contacts that match filters such as job title, seniority, department, location, and company attributes. It returns one page of contacts without emails or phone numbers; enrich them with Enrich Contacts.

  • Credits: Consumes credits for each result returned.
  • Enter Filters as a JSON object, for example {"contacts": {"include": {"departments": ["Engineering"]}}, "companies": {"include": {}}}. Get valid filter names and values from the free contact and company filter templates below.
  • Page (default 0) and Page Size (default 10, 10 to 100) select one page of results. Each run fetches only that page.
  • Reference: Lusha API reference: Prospect Contacts

Prospect Companies

This endpoint template searches Lusha for companies that match filters such as industry, size, revenue, location, and technologies, and returns one page of companies.

  • Credits: Consumes credits for each result returned.
  • Enter Filters as a JSON object with a companies section (include and exclude) and, optionally, a contacts section. Get valid filter names and values from the free company filter templates below.
  • Page (default 0) and Page Size (default 10, 10 to 100) select one page of results. Each run fetches only that page.
  • Reference: Lusha API reference: Prospect Companies

List Contact Filter Types

This endpoint template lists the contact prospecting filter types and whether each one needs a search query to look up its values.

List Contact Filter Values

This endpoint template lists every valid value of a contact filter that takes no query.

Search Contact Location Filter Values

This endpoint template returns contact location values that match a text query, for use in Prospect Contacts filters.

List Company Filter Types

This endpoint template lists the company prospecting filter types and whether each one needs a search query to look up its values.

List Company Filter Values

This endpoint template lists every valid value of a company filter that takes no query.

Search Company Filter Values

This endpoint template returns company filter values that match a text query, for filters too large to list in full.

  • Credits: Free. Lusha does not charge credits for filter-discovery calls.
  • Select the Filter Type: names (default), technologies, or locations.
  • Enter the Query (2 to 256 characters), for example Salesforce.
  • Reference: Lusha API reference: Search Company Filter Values

Lookalikes, recommendations, and buying groups​

Contact Lookalikes

This endpoint template returns contacts that Lusha's AI considers similar to a set of seed contacts.

  • Credits: Consumes credits for each result returned.
  • Enter Seeds as a JSON object holding 5 to 100 seed contacts in total, using ids, emails, linkedinUrls, or contacts arrays, for example {"emails": ["jane@example.com", ...]}.
  • Enter the Limit (1 to 100, default 10).
  • Reference: Lusha API reference: Contact Lookalikes

Company Lookalikes

This endpoint template returns companies that Lusha's AI considers similar to a set of seed companies.

  • Credits: Consumes credits for each result returned.
  • Enter Seeds as a JSON object holding 5 to 100 seed companies in total, using domains and/or linkedinUrls arrays.
  • Enter the Limit (1 to 100, default 10).
  • Reference: Lusha API reference: Company Lookalikes

Contact Recommendations

This endpoint template returns contacts that Lusha recommends for your Target Profiles, sorted by lead score.

  • Credits: Consumes credits for each result returned.
  • Optionally, enter Filters as a JSON object (targetIcp, signals, and leadScore, signalScore, or icpFitScore ranges). The default, {}, returns all recommendations. Get valid values from List Contact Recommendation Filters.
  • Page (default 0) and Page Size (default 10, 10 to 100) select one page of results. Each run fetches only that page.
  • Reference: Lusha API reference: Contact Recommendations

Company Recommendations

This endpoint template returns companies that Lusha recommends for your Target Profiles, sorted by lead score.

  • Credits: Consumes credits for each result returned.
  • Optionally, enter Filters as a JSON object (targetIcp, signals, and leadScore, signalScore, or icpFitScore ranges). The default, {}, returns all recommendations. Get valid values from List Company Recommendation Filters.
  • Page (default 0) and Page Size (default 10, 10 to 100) select one page of results. Each run fetches only that page.
  • Reference: Lusha API reference: Company Recommendations

List Contact Recommendation Filters

This endpoint template lists the Target Profiles and signal types present in your contact recommendations, for use as recommendation filters.

List Company Recommendation Filters

This endpoint template lists the Target Profiles and signal types present in your company recommendations, for use as recommendation filters.

Buying Group Contacts

This endpoint template returns decision makers, champions, and end users at up to 25 target companies.

  • Credits: Consumes 1 credit for each contact returned.
  • Enter Companies as a JSON array of 1 to 25 companies, each identified by domain or id, for example [{"domain": "example.com"}].
  • Page (default 0) and Page Size (default 10, 10 to 100) select one page of results. Each run fetches only that page.
  • Reference: Lusha API reference: Buying Group Contacts

Signals and scoring​

Contact Signals

This endpoint template returns job-change and promotion signals for up to 100 contacts. By default, Lusha looks back six months.

  • Credits: Consumes credits for each matched signal.
  • Enter Contact IDs as a JSON array of 1 to 100 Lusha contact IDs (the id of results from Search Contacts or Prospect Contacts).
  • Enter Signal Types as a JSON array: allSignals (default), promotion, or companyChange.
  • Reference: Lusha API reference: Contact Signals

Company Signals

This endpoint template returns headcount, hiring, traffic, IT spend, news, and intent signals for up to 100 companies.

  • Credits: Consumes credits for each matched signal.
  • Enter Company IDs as a JSON array of 1 to 100 Lusha company IDs (the id of results from Search Companies or Prospect Companies).
  • Enter Signal Types as a JSON array (default ["allSignals"]). allSignals excludes the intent signal types; use List Company Signal Types for the full list.
  • Reference: Lusha API reference: Company Signals

List Contact Signal Types

This endpoint template lists the signal types that Lusha supports for contacts.

List Company Signal Types

This endpoint template lists the signal types that Lusha supports for companies.

List Company Signal Filter Types

This endpoint template lists the company signal filter types and whether each one needs a search query.

List Company Signal Filter Values

This endpoint template lists every valid value of a company signal filter that takes no query.

Search Company Signal Filter Values

This endpoint template returns company signal filter values that match a text query. Intent topics return up to 50 matches.

Score Contacts by Signal Activity

This endpoint template scores up to 100 contacts by their signal activity.

  • Credits: Consumes 1 credit for each scored contact once Lusha prices this action on your account; until then it is free.
  • Enter Contacts as a JSON array of 1 to 100 contacts. Identify each by id, linkedinUrl, email, or firstName and lastName with companyName or companyDomain, for example [{"email": "jane@example.com"}].
  • Reference: Lusha API reference: Score Contacts by Signal Activity

Score Companies by Signal Activity

This endpoint template scores up to 100 companies by their signal activity.

  • Credits: Consumes 1 credit for each scored company once Lusha prices this action on your account; until then it is free.
  • Enter Companies as a JSON array of 1 to 100 companies, each identified by domain, name, or id, for example [{"domain": "example.com"}]. An optional clientReferenceId on each item is returned with its result.
  • Reference: Lusha API reference: Score Companies by Signal Activity

List Target Profiles

This endpoint template lists the Target Profiles (ideal customer profiles) you can see: your own and those shared on the account. Use their IDs with the ICP fit templates.

Score Contacts by ICP Fit

This endpoint template scores up to 100 contacts against your Target Profiles.

  • Credits: Consumes 1 credit for each scored contact, including scores of 0, however many profiles you score against. Contacts that are not found or get no score are not charged.
  • Enter Contacts as a JSON array of 1 to 100 contacts. Identify each by id, linkedinUrl, email, or firstName and lastName with companyName or companyDomain, for example [{"email": "jane@example.com"}].
  • Enter Target Profile IDs as a JSON array of IDs from List Target Profiles.
  • Reference: Lusha API reference: Score Contacts by ICP Fit

Score Companies by ICP Fit

This endpoint template scores up to 100 companies against your Target Profiles.

  • Credits: Consumes 1 credit for each scored company, including scores of 0, however many profiles you score against. Companies that are not found or get no score are not charged.
  • Enter Companies as a JSON array of 1 to 100 companies, each identified by domain, name, or id, for example [{"domain": "example.com"}]. An optional clientReferenceId on each item is returned with its result.
  • Enter Target Profile IDs as a JSON array of IDs from List Target Profiles.
  • Reference: Lusha API reference: Score Companies by ICP Fit

Website visitors and conversations​

Website Visitors

This endpoint template returns companies ranked by their visits to the domains you track in Lusha, for a window of up to three months.

  • Credits: Treat as credit-consuming. Lusha does not document the price of this call, but its response reports credits charged.
  • Enter Domains as a JSON array of domains set up for tracking in the Lusha dashboard, for example ["example.com"].
  • Enter the Start Date and End Date (YYYY-MM-DD), at most three months apart.
  • Page (default 0) and Page Size (default 10, 1 to 150) select one page of results. Each run fetches only that page.
  • Reference: Lusha API reference: Website Visitors

Search Conversations

This endpoint template searches your recorded sales conversations and returns each one with its AI summary, coaching notes, and chapters.

  • Credits: Consumes 1 credit for each block of up to 25 conversations returned once Lusha prices this action on your account; until then it is free.
  • Enter Search as the JSON request body. Use query for keyword search, or filters such as dateFrom, dateTo, contactNames, companyDomains, and meetingTitles, plus page (starting at 1) and pageSize (1 to 100). The default is {"page": 1, "pageSize": 25}.
  • Reference: Lusha API reference: Search Conversations

Get Conversation Transcript

This endpoint template returns the speaker-attributed transcript of one conversation, one record per segment.

  • Credits: Consumes 1 credit per request once Lusha prices this action on your account; until then it is free. Requests for a conversation that is not found are not charged.
  • Enter the Conversation ID. Use the Search Conversations template to find it.
  • Reference: Lusha API reference: Get Conversation Transcript

Tables​

Lusha Tables are shared with the Lusha workspace, so tables created in either place appear in both. Listing and reading tables is free; reading table rows is charged per row.

List Contacts Tables

This endpoint template lists the contacts tables visible to a user. Nexla fetches all pages.

  • Credits: Free. Lusha does not charge credits to list, read, or manage tables.
  • Enter the Owner Email: the email of a user on your Lusha account. Lusha requires it on every Tables call made with an API key.
  • Reference: Lusha API reference: List Contacts Tables

Get Contacts Table

This endpoint template returns one contacts table: its name, visibility, status, owner, entity count, and columns.

  • Credits: Free. Lusha does not charge credits to list, read, or manage tables.
  • Enter the Table ID. Use the List Contacts Tables template to find it.
  • Enter the Owner Email: the email of a user on your Lusha account. Lusha requires it on every Tables call made with an API key.
  • Reference: Lusha API reference: Get Contacts Table

List Contacts Table Columns

This endpoint template lists the columns on a contacts table, with run status counts for each column.

  • Credits: Free. Lusha does not charge credits to list, read, or manage tables.
  • Enter the Table ID. Use the List Contacts Tables template to find it.
  • Enter the Owner Email: the email of a user on your Lusha account. Lusha requires it on every Tables call made with an API key.
  • Reference: Lusha API reference: List Contacts Table Columns

Get Contacts Column Catalog

This endpoint template lists the columns that can be added to a contacts table, with each column's key, category, and type.

Get Contacts Table Entities

This endpoint template returns one page of rows from a contacts table, with their column values.

  • Credits: Consumes credits for each row returned.
  • Enter the Table ID. Use the List Contacts Tables template to find it.
  • Enter the Owner Email: the email of a user on your Lusha account. Lusha requires it on every Tables call made with an API key.
  • Page (default 0, up to 100) and Page Size (default 10; Lusha's own default is 100) select one page of rows. Each run fetches only that page.
  • Reference: Lusha API reference: Get Contacts Table Entities

List Companies Tables

This endpoint template lists the companies tables visible to a user. Nexla fetches all pages.

  • Credits: Free. Lusha does not charge credits to list, read, or manage tables.
  • Enter the Owner Email: the email of a user on your Lusha account. Lusha requires it on every Tables call made with an API key.
  • Reference: Lusha API reference: List Companies Tables

Get Companies Table

This endpoint template returns one companies table: its name, visibility, status, owner, entity count, and columns.

  • Credits: Free. Lusha does not charge credits to list, read, or manage tables.
  • Enter the Table ID. Use the List Companies Tables template to find it.
  • Enter the Owner Email: the email of a user on your Lusha account. Lusha requires it on every Tables call made with an API key.
  • Reference: Lusha API reference: Get Companies Table

Get Companies Column Catalog

This endpoint template lists the columns that can be added to a companies table, with each column's key, category, and type.

Get Companies Table Entities

This endpoint template returns one page of rows from a companies table, with their column values.

  • Credits: Consumes credits for each row returned.
  • Enter the Table ID. Use the List Companies Tables template to find it.
  • Enter the Owner Email: the email of a user on your Lusha account. Lusha requires it on every Tables call made with an API key.
  • Page (default 0, up to 100) and Page Size (default 10; Lusha's own default is 100) select one page of rows. Each run fetches only that page.
  • Reference: Lusha API reference: Get Companies Table Entities

Webhooks​

List Webhook Subscriptions

This endpoint template lists your account's webhook subscriptions, newest first. Nexla fetches all pages.

Get Webhook Subscription

This endpoint template returns one webhook subscription.

  • Credits: Free. Lusha charges for webhooks only when it delivers a signal, not for managing or reading subscriptions and logs.
  • Enter the Subscription ID. Use the List Webhook Subscriptions template to find it.
  • Reference: Lusha API reference: Get Webhook Subscription

List Webhook Audit Logs

This endpoint template lists webhook delivery attempts with their status, HTTP code, duration, and error. Lusha keeps successful deliveries for 90 days and failed ones for 180 days. Nexla fetches all pages.

Get Webhook Audit Log Stats

This endpoint template returns webhook delivery totals for the account: successes, failures, permanent failures, success rate, and credits used by deliveries.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving. Testing a credit-consuming template calls Lusha and spends credits.

Manual configuration​

Lusha data sources can also be manually configured to ingest data from any valid Lusha API endpoint not included in the pre-built templates. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Lusha V3 endpoints use the base URL https://api.lusha.com/v3/, and webhook endpoints use https://api.lusha.com/api/. The api_key header is added automatically from your credential. Most V3 search, enrich, and prospecting calls are POST requests with a JSON body; their results are under $.results[*], and Tables results are under $.data[*].

Lusha has retired V2 API access for some accounts, so use V3 paths. See the V3 migration guide for the V3 equivalent of each V2 endpoint.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Lusha data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination​

Click the + icon on the Nexset that will be sent to the Lusha destination, and select the Send to Destination option from the menu. Select the Lusha connector from the list of available destination connectors, then select the credential that will be used to connect to Lusha, and click Next; or, create a new Lusha credential for use in this flow.

Endpoint templates​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Lusha endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Each record in the Nexset is sent as the JSON body of one request, one record at a time. ID settings, such as Table ID or Subscription ID, are fixed on the destination and apply to every record it sends. Lusha requires an owner.email (a user on your Lusha account) on every Tables call, so include owner in each Tables record unless the template takes an Owner Email setting.

Contacts tables​

Create Contacts Table

This endpoint template creates a contacts table from each record.

  • Credits: Free. Lusha does not charge credits to list, read, or manage tables.
  • Each record contains name, visibility, and owner ({"email": "user@example.com"}), and can include ids to seed the table with contacts.
  • Reference: Lusha API reference: Create Contacts Table

Update Contacts Table

This endpoint template renames, shares, or archives a contacts table.

  • Credits: Free. Lusha does not charge credits to list, read, or manage tables.
  • Enter the Table ID. Use the List Contacts Tables template to find it.
  • Each record contains any of name, visibility, or archived, plus owner ({"email": "user@example.com"}).
  • Reference: Lusha API reference: Update Contacts Table

Delete Contacts Table

This endpoint template deletes a contacts table. Because the table is set on the destination, send one record per destination.

  • Credits: Free. Lusha does not charge credits to list, read, or manage tables.
  • Enter the Table ID. Use the List Contacts Tables template to find it.
  • Enter the Owner Email: the email of a user on your Lusha account. Lusha requires it on every Tables call made with an API key.
  • Reference: Lusha API reference: Delete Contacts Table

Add Entities to Contacts Table

This endpoint template adds contacts to a contacts table.

  • Credits: Free. Adding contacts to a table does not charge credits.
  • Enter the Table ID. Use the List Contacts Tables template to find it.
  • Each record contains entityIds (up to 500 contact IDs) and owner ({"email": "user@example.com"}).
  • Reference: Lusha API reference: Add Entities to Contacts Table

Remove Entities from Contacts Table

This endpoint template removes contacts from a contacts table.

  • Credits: Free. Lusha does not charge credits to list, read, or manage tables.
  • Enter the Table ID. Use the List Contacts Tables template to find it.
  • Each record contains entityIds (up to 500 contact IDs) and owner ({"email": "user@example.com"}).
  • Reference: Lusha API reference: Remove Entities from Contacts Table

Add Columns to Contacts Table

This endpoint template adds columns to a contacts table. Adding a column is free; running it with Run Column on Contacts Table is charged.

  • Credits: Free. Lusha does not charge credits to list, read, or manage tables.
  • Enter the Table ID. Use the List Contacts Tables template to find it.
  • Each record contains columns (up to 10 objects with a columnKey) or a single columnKey, plus owner ({"email": "user@example.com"}). Use the Get Contacts Column Catalog source template to find column keys.
  • Reference: Lusha API reference: Add Columns to Contacts Table

Remove Column from Contacts Table

This endpoint template removes one column from a contacts table.

  • Credits: Free. Lusha does not charge credits to list, read, or manage tables.
  • Enter the Table ID. Use the List Contacts Tables template to find it.
  • Enter the Column ID. Use the List Contacts Table Columns source template to find it.
  • Enter the Owner Email: the email of a user on your Lusha account. Lusha requires it on every Tables call made with an API key.
  • Reference: Lusha API reference: Remove Column from Contacts Table

Run Column on Contacts Table

This endpoint template runs an enrichment column on a contacts table.

  • Credits: Consumes credits for each row processed, at the column's credit tier.
  • Enter the Table ID. Use the List Contacts Tables template to find it.
  • Enter the Column ID. Use the List Contacts Table Columns source template to find it.
  • Each record contains runScope (missing, all, or specific), entityIds when the scope is specific, and owner ({"email": "user@example.com"}).
  • Reference: Lusha API reference: Run Column on Contacts Table

Companies tables​

Create Companies Table

This endpoint template creates a companies table from each record.

  • Credits: Free to create. Seeding the table with companies through ids is charged per newly added company, like Add Entities to Companies Table.
  • Each record contains name, visibility, and owner ({"email": "user@example.com"}), and can include ids to seed the table.
  • Reference: Lusha API reference: Create Companies Table

Update Companies Table

This endpoint template renames, shares, or archives a companies table.

  • Credits: Free. Lusha does not charge credits to list, read, or manage tables.
  • Enter the Table ID. Use the List Companies Tables template to find it.
  • Each record contains any of name, visibility, or archived, plus owner ({"email": "user@example.com"}).
  • Reference: Lusha API reference: Update Companies Table

Delete Companies Table

This endpoint template deletes a companies table. Because the table is set on the destination, send one record per destination.

  • Credits: Free. Lusha does not charge credits to list, read, or manage tables.
  • Enter the Table ID. Use the List Companies Tables template to find it.
  • Enter the Owner Email: the email of a user on your Lusha account. Lusha requires it on every Tables call made with an API key.
  • Reference: Lusha API reference: Delete Companies Table

Add Entities to Companies Table

This endpoint template adds companies to a companies table.

  • Credits: Consumes credits for each newly added company.
  • Enter the Table ID. Use the List Companies Tables template to find it.
  • Each record contains entityIds (up to 500 company IDs) and owner ({"email": "user@example.com"}).
  • Reference: Lusha API reference: Add Entities to Companies Table

Remove Entities from Companies Table

This endpoint template removes companies from a companies table.

  • Credits: Free. Lusha does not charge credits to list, read, or manage tables.
  • Enter the Table ID. Use the List Companies Tables template to find it.
  • Each record contains entityIds (up to 500 company IDs) and owner ({"email": "user@example.com"}).
  • Reference: Lusha API reference: Remove Entities from Companies Table

Remove Column from Companies Table

This endpoint template removes one column from a companies table.

  • Credits: Free. Lusha does not charge credits to list, read, or manage tables.
  • Enter the Table ID. Use the List Companies Tables template to find it.
  • Enter the Column ID of the column to remove.
  • Enter the Owner Email: the email of a user on your Lusha account. Lusha requires it on every Tables call made with an API key.
  • Reference: Lusha API reference: Remove Column from Companies Table

Run Column on Companies Table

This endpoint template runs an enrichment column on a companies table.

  • Credits: Consumes credits for each row processed, at the column's credit tier.
  • Enter the Table ID. Use the List Companies Tables template to find it.
  • Enter the Column ID of the column to run.
  • Each record contains runScope (missing, all, or specific), entityIds when the scope is specific, and owner ({"email": "user@example.com"}).
  • Reference: Lusha API reference: Run Column on Companies Table

Webhook subscriptions​

Create Webhook Subscriptions

This endpoint template creates up to 25 webhook subscriptions from each record, so Lusha posts signals for the subscribed contacts or companies to your URL.

  • Credits: Free to create, but Lusha charges 1 credit for each signal it delivers later.
  • Each record contains defaults (url, entityType, and signalTypes) and subscriptions, a list of up to 25 objects with an entityId.
  • Reference: Lusha API reference: Create Webhook Subscriptions

Create Opt-Out Subscription

This endpoint template creates a subscription that notifies your URL when a contact opts out.

Update Webhook Subscription

This endpoint template updates a webhook subscription.

  • Credits: Free.
  • Enter the Subscription ID. Use the List Webhook Subscriptions source template to find it.
  • Each record contains any of signalTypes, url, name, isActive, or regenerateSecret.
  • Reference: Lusha API reference: Update Webhook Subscription

Delete Webhook Subscriptions

This endpoint template deletes webhook subscriptions.

Test Webhook Subscription

This endpoint template sends a mock signal to a subscription's URL so you can check your receiver. Because the subscription is set on the destination, send one record per destination.

  • Credits: Free. Test deliveries do not charge credits.
  • Enter the Subscription ID. Use the List Webhook Subscriptions source template to find it.
  • Select the Mode: full (default; both paths), direct (HTTP only), or kafka (Lusha's pipeline only).
  • Reference: Lusha API reference: Test Webhook Subscription

Manual configuration​

Lusha destinations can also be manually configured to send data to any valid Lusha API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Save & activate​

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Lusha endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Lusha endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.