Skip to main content

Lusha Data Source

The Lusha connector enables you to enrich person and company data, perform person and company lookups, run prospecting queries, and retrieve API usage information. This connector is particularly useful for applications that need to enrich contact databases, perform lead research, build prospecting tools, or integrate contact data with CRM and sales systems. Follow the instructions below to create a new data flow that ingests data from a Lusha source in Nexla.
lusha_api.png

Lusha

Create a New Data Flow​

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

  2. Select the Lusha connector tile from the list of available connectors. 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.

  3. In Nexla, Lusha data sources can be created using pre-built endpoint templates, which expedite source setup for common Lusha API endpoints. Each template is designed specifically for the corresponding Lusha API endpoint, making source configuration easy and efficient.
    • To configure this source using a template, follow the instructions in Configure Using a Template.

    Lusha sources can also be configured manually, allowing you to ingest data from Lusha API endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this source manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Lusha API endpoints. Each template is designed specifically for the corresponding Lusha API endpoint, making data source setup easy and efficient.

Endpoint Settings​

  • 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. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.

    Person Lookup

    This endpoint looks up a single person by email, LinkedIn URL, or fullName+company. Use this endpoint when you need to enrich person data, find contact information, or retrieve person details for lead research.

    • Optionally, enter the email address of the person to look up in the Email field. You can use email, LinkedIn URL, or fullName+company to search for a person.
    • Optionally, enter the full name of the person in the Full Name field. When using fullName, you should also provide company information for better matching.
    • Optionally, enter the LinkedIn profile URL in the LinkedIn URL field. This can be used to look up a person by their LinkedIn profile.

    The Person Lookup endpoint requires at least one search parameter (email, fullName, or linkedin). The endpoint returns enriched person data including contact information, job title, company, and other professional details. For more information about the Person Lookup endpoint, refer to the Lusha API Documentation.

    Company Lookup

    This endpoint looks up a single company by domain or name. Use this endpoint when you need to enrich company data, find company information, or retrieve company details for prospecting.

    • Optionally, enter the company domain in the Domain field. You can use domain or company name to search for a company.
    • Optionally, enter the name of the company in the Company Name field. This can be used to look up a company by its name.

    The Company Lookup endpoint requires at least one search parameter (domain or name). The endpoint returns enriched company data including company information, industry, size, and other company details. For more information about the Company Lookup endpoint, refer to the Lusha API Documentation.

    Prospect Contact

    This endpoint searches contacts using filters and enriches their details. Use this endpoint when you need to perform bulk prospecting, find contacts matching specific criteria, or enrich multiple contacts at once.

    • Enter a JSON string with filters for enrichment in the Prospect Filters field. The filters should be formatted as a JSON object, for example: {"company": {"name": "Example Corp"}, "seniority": "C-Level"}. Refer to the Lusha API documentation for the complete list of available filters.

    The Prospect Contact endpoint uses POST requests to send filter criteria and returns enriched contact data matching the specified filters. The endpoint supports various filter criteria including company information, job titles, seniority levels, and more. For more information about the Prospect Contact endpoint, refer to the Lusha API Documentation.

    Account Usage

    This endpoint fetches your API usage report from Lusha. Use this endpoint when you need to monitor API usage, track credit consumption, or analyze API usage patterns.

    • This endpoint automatically retrieves your current API usage information. No additional configuration is required beyond selecting this endpoint template.

    The Account Usage endpoint returns information about your API usage including credits consumed, remaining credits, and usage statistics. This endpoint is useful for monitoring your API usage and managing your Lusha account. For more information about the Account Usage endpoint, refer to the Lusha API Documentation.

Endpoint Testing​

Once the selected endpoint template has been configured, Nexla can retrieve a sample of the data that will be fetched according to the current settings. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Configure Manually​

Lusha data sources can be manually configured to ingest data from any valid Lusha API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

With manual configuration, you can also create more complex Lusha sources, such as sources that use chained API calls to fetch data from multiple endpoints or sources that require custom authentication headers or request parameters.

API Method​

  1. To manually configure this source, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Lusha API from the Method pulldown menu. The most common methods are:

    • GET: For retrieving data from the API (most Lusha lookup endpoints use GET)
    • POST: For sending search queries to the API (prospecting endpoints use POST)

API Endpoint URL​

  1. Enter the URL of the Lusha API endpoint from which this source will fetch data in the Set API URL field. This should be the complete URL including the protocol (https://) and any required path parameters. Lusha API endpoints typically follow the pattern https://api.lusha.com/v2/{resource} for v2 endpoints or https://api.lusha.com/v1/{resource} for v1 endpoints.

Ensure the API endpoint URL is correct and accessible with your current credentials. You can test the endpoint using the Test button after configuring the URL. Lusha API endpoints require the api_key header for authentication.

Path to Data​

Optional

If only a subset of the data that will be returned by API endpoint is needed, you can designate the part(s) of the response that should be included in the Nexset(s) produced from this source by specifying the path to the relevant data within the response. This is particularly useful when API responses contain metadata, pagination information, or other data that you don't need for your analysis.

For example, when a request call is used to fetch prospect contacts, the API will typically return contact data along with metadata. By entering the path to the relevant data, you can configure Nexla to extract the specific contacts you need.

Path to Data is essential when API responses have nested structures. Without specifying the correct path, Nexla might not be able to properly parse and organize your data into usable records. For Lusha API responses, common paths include $ for the entire response or $.contacts[*] for arrays of contacts.

  • To specify which data should be treated as relevant in responses from this source, enter the path to the relevant data in the Set Path to Data in Response field.

    • For responses in JSON format enter the JSON path that points to the object or array that should be treated as relevant data. JSON paths use dot notation (e.g., $.contacts to access the contacts array).
    Path to Data Example:

    If the API response is in JSON format and includes a contacts array that contains the prospect contacts, the path to the response would be entered as $.contacts[*].

Autogenerate Path Suggestions​

Nexla can also autogenerate data path suggestions based on the response from the API endpoint. These suggested paths can be used as-is or modified to exactly suit your needs.

  • To use this feature, click the Test button next to the Set API URL field to fetch a sample response from the API endpoint. Suggested data paths generated based on the content & format of the response will be displayed in the Suggestions box below the Set Path to Data in Response field.

  • Click on a suggestion to automatically populate the Set Path to Data in Response field with the corresponding path. The populated path can be modified directly within the field if further customization is needed.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this source, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2). Additional headers are often required for API versioning, content type specifications, or custom authentication requirements.

    You do not need to include any headers already present in the credentials. Common headers like Authorization, Content-Type, and Accept are typically handled automatically by Nexla based on your credential configuration. For Lusha, the api_key header is automatically included from your credential.

Request Body​

Optional

  • If the API endpoint requires a request body (which is common for POST requests to Lusha), enter the request body in the Request Body field. The request body should be formatted as JSON and include the necessary parameters for the request, such as filters for prospecting endpoints.

    For Lusha prospecting endpoints, the request body typically includes a filters field containing filter criteria for searching contacts. Refer to the Lusha API documentation for the complete list of available filters and their formats.

Endpoint Testing​

After configuring all settings for the selected endpoint, Nexla can retrieve a sample of the data that will be fetched according to the current configuration. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Save & Activate the Source​

  1. Once all of the relevant steps in the above sections have been completed, 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.