Skip to main content

Lusha Feeds

Lusha is a B2B data platform that provides accurate contact and company information for sales prospecting, lead enrichment, and go-to-market intelligence. The Lusha Feeds connector is a source-only ELT connector that ingests Lusha data as a set of feeds — person and company lookups, prospecting contact and company search, prospecting enrichment, prospecting filter metadata, and account usage. Rather than configuring one request at a time, you select the Lusha resources you want and Nexla ingests each as its own feed on a schedule. For the request-response REST variant of this connector, see the Lusha API connector.

Lusha Feeds icon

Power end-to-end data operations for your Lusha Feeds API with Nexla. Our bi-directional Lusha Feeds connector is purpose-built for Lusha Feeds, 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 Feeds or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Lusha Feeds 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

The Lusha Feeds connector authenticates to the Lusha API with an API key. Before creating a credential in Nexla, generate an API key in your Lusha account.

API key access is available to Admins and Managers on Lusha's paid plans that include API access (the Premium and Scale tiers). Confirm your account has an eligible plan and role before generating a key.

To generate a Lusha API key:

  1. Sign in to your Lusha account as an Admin or Manager.

  2. Open your account Settings and go to the API page (also reachable through the API HubManage API Keys).

  3. Click Create new Key to generate a new API key, or copy an existing active key.

  4. Copy the API key and store it securely. The key is issued at the account level, so a single key represents your whole Lusha account.

Treat the Lusha API key as a sensitive secret and use it only in server-side environments. You can create and revoke multiple keys from the API page, so use a dedicated key for the Nexla integration and rotate it if it is ever exposed.

Lusha charges credits for API usage — typically a minimum of one credit per request, plus additional credits per block of returned results — so review your plan's credit allowance before scheduling high-frequency feeds. For more information, see the Lusha API documentation and Lusha API authentication guide.

Authenticate

Credentials required

Connect to Lusha using your API key.

FieldRequiredSecretDescription
API KeyYesYesYour Lusha API key (found in your Lusha account settings)

Create a credential in Nexla

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

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

    Resource descriptions are recommended but are not required. Use them to identify the Lusha account or access level represented by this credential.

  3. Enter your Lusha API key in the API Key field. Nexla sends this key to Lusha in the api_key request header when ingesting feeds, and stores it securely as a secret.

  4. 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 creation and can be selected for use with Lusha Feeds flows.

Use as a data source

How This Connector Works

The Lusha Feeds connector is a source-only ELT connector. Rather than configuring one endpoint at a time, you select the Lusha resources you want to ingest, and Nexla loads each selected resource as its own feed against the Lusha API (https://api.lusha.com).

  • Discovery: When you create the source, Nexla presents the available Lusha resources for selection.

  • Loading strategy: Each resource maps to the appropriate Lusha request pattern automatically — a paginated GET for lookups and filter metadata, a paginated POST for prospecting search, or a batch POST for prospecting enrichment. Paginated resources use offset-based paging, controlled by the Page Size setting (1–100 records per page, default 50).

  • Parallel ingestion: Selected resources are ingested in parallel, so a single source can pull multiple Lusha resources on the same schedule. The id field is used as the primary key to uniquely identify records within each feed.

Create a New Data Flow

  1. To create a new data flow, navigate to the Integrate section, click the New Data Flow button, select the ELT flow type, and click Create.

  2. Select the Lusha Feeds connector tile from the list of available connectors. Then, select the credential that will be used to connect to Lusha and click Next; or, create a new Lusha Feeds credential for use in this flow.

Select the Objects to Ingest

After authenticating, Nexla lists the Lusha resources available from the connector. Select one or more of the resources below to ingest. Each selected resource becomes its own feed and is loaded on the configured schedule. Click a resource to view details and its configuration inputs.

Person Lookup

Enriches a single person and returns their contact and professional profile from Lusha. This resource calls the Lusha person API (v2/person) as a GET request using the identifiers you provide.

  • Provide one or more of the following inputs to identify the person: Person Email, Person First Name, Person Last Name, Company Name, and Company Domain.
  • An email address alone is often sufficient. When looking up by name, supply the company name or company domain to disambiguate the person.
  • Returned data is the enriched person profile, including the Lusha record ID used as the feed's primary key.

Company Lookup

Enriches a single company and returns its firmographic profile from Lusha. This resource calls the Lusha company API (v2/company) as a GET request.

  • Provide the Company Domain and/or Company Name to identify the company.
  • Using the company domain generally returns the most precise match.
  • Returned data is the enriched company profile, including the Lusha record ID used as the feed's primary key.

Prospecting Filters

Retrieves the filter definitions available for Lusha prospecting search (v1/prospecting/filters) as a GET request. Use this resource to discover the valid filter fields and values you can supply when configuring the Prospecting Contacts Search and Prospecting Companies Search resources.

  • No additional inputs are required.
  • Returned data is the set of supported prospecting filter definitions.

Prospecting Contacts Search

Searches Lusha's prospecting database for contacts matching a set of filters (v1/prospecting/contacts/search) as a paginated POST request. Use this resource to build lists of prospects that meet targeting criteria such as job title, seniority, or industry.

  • Enter your search criteria as a JSON object in the Prospecting Filters field — for example, {"jobTitle": "CEO", "industry": "Technology"}. Use the Prospecting Filters resource to confirm the supported filter fields and values.
  • Set the Page Size field to control how many records are returned per page (1–100, default 50).
  • Returned data is the list of matching contacts, each including the Lusha contact ID used as the feed's primary key. Use these contact IDs with the Prospecting Contact Enrich resource to retrieve full contact details.

Prospecting Companies Search

Searches Lusha's prospecting database for companies matching a set of filters (v1/prospecting/companies/search) as a paginated POST request. Use this resource to build target account lists based on firmographic criteria.

  • Enter your search criteria as a JSON object in the Prospecting Filters field — for example, {"industry": "Software", "companySize": "201-500"}. Use the Prospecting Filters resource to confirm the supported filter fields and values.
  • Set the Page Size field to control how many records are returned per page (1–100, default 50).
  • Returned data is the list of matching companies, each including the Lusha company ID used as the feed's primary key. Use these company IDs with the Prospecting Company Enrich resource to retrieve full company details.

Prospecting Contact Enrich

Enriches a batch of prospecting contacts by their Lusha contact IDs (v1/prospecting/contacts/enrich) as a batch POST request. Use this resource after Prospecting Contacts Search to retrieve full contact details for the IDs you selected.

  • Enter a JSON array of Lusha contact IDs in the Contact IDs field — for example, ["id1", "id2"]. These IDs come from the Prospecting Contacts Search results.
  • Returned data is the enriched detail for each requested contact, including the Lusha contact ID used as the feed's primary key.

Prospecting Company Enrich

Enriches a batch of prospecting companies by their Lusha company IDs (v1/prospecting/companies/enrich) as a batch POST request. Use this resource after Prospecting Companies Search to retrieve full company details for the IDs you selected.

  • Enter a JSON array of Lusha company IDs in the Company IDs field — for example, ["id1", "id2"]. These IDs come from the Prospecting Companies Search results.
  • Returned data is the enriched detail for each requested company, including the Lusha company ID used as the feed's primary key.

Account Usage

Retrieves your Lusha account's API credit usage (account/usage) as a GET request. Use this resource to monitor credit consumption over time.

  • No additional inputs are required.
  • Returned data is the current account usage snapshot.

Lusha charges credits for prospecting search, lookup, and enrichment requests. When ingesting these feeds on a recurring schedule, choose a page size and schedule frequency that stay within your plan's credit allowance.

Schedule and Activate

Use the default sync schedule or adjust the schedule in the source settings before activating the flow. On each run, every selected resource is loaded as its own feed.

Reference

For object schemas, filter definitions, credit costs, and request/response details for each Lusha endpoint, see the Lusha API documentation. For the request-response REST variant of this connector, see the Lusha API connector.