Lemlist Data Source

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow, DB-CDC, Spark ETL, or Replication data flow that ingests data from a Lemlist source.

Lemlist

Follow the instructions below to create a new data flow that ingests data from a Lemlist source in Nexla.

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 Lemlist connector tile from the list of available connectors. Then, select the credential that will be used to connect to the Lemlist account, and click Next; or, create a new Lemlist credential for use in this flow.

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

   Lemlist sources can also be configured manually, allowing you to ingest data from Lemlist 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 Lemlist endpoints. Each template is designed specifically for the corresponding Lemlist 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.

  List Campaigns

  List Campaigns

  • This endpoint automatically retrieves the list of all campaigns from your Lemlist account. No additional configuration is required beyond selecting this endpoint template.
  • The endpoint uses GET requests to https://api.lemlist.com/api/campaigns?limit=100. The endpoint URL includes a default limit of 100 records per page.
  • The endpoint uses pagination (iteration.type: paging.incrementing.offset) to retrieve all campaigns. Pagination starts from offset 0 and uses the offset query parameter to navigate through pages. The limit parameter controls how many records are returned per page, with an expected 100 records per page. The endpoint will automatically fetch all pages until all campaigns are retrieved.
  • The response data path is $[*], which extracts all campaign objects from the response array in the API response.

  This endpoint retrieves a list of all campaigns from your Lemlist account. The endpoint requires Basic Authentication with your API key (used as the password with an empty username), which is handled automatically by your credential configuration. The endpoint supports pagination through the offset and limit parameters, which allows you to retrieve large lists of campaigns efficiently. For detailed information about listing campaigns, pagination, and API response formats, see the Lemlist API documentation.

  Get Activities

  Get Activities

  • This endpoint automatically retrieves activities from your Lemlist account. No additional configuration is required beyond selecting this endpoint template.
  • The endpoint uses GET requests to https://api.lemlist.com/api/activities?limit=100. The endpoint URL includes a default limit of 100 records per page.
  • The endpoint uses pagination (iteration.type: paging.incrementing.offset) to retrieve all activities. Pagination starts from offset 0 and uses the offset query parameter to navigate through pages. The limit parameter controls how many records are returned per page, with an expected 100 records per page. The endpoint will automatically fetch all pages until all activities are retrieved.
  • The response data path is $[*], which extracts all activity objects from the response array in the API response.

  This endpoint retrieves activities from your Lemlist account. The endpoint requires Basic Authentication with your API key (used as the password with an empty username), which is handled automatically by your credential configuration. The endpoint supports pagination through the offset and limit parameters, which allows you to retrieve large lists of activities efficiently. For detailed information about getting activities, pagination, and API response formats, see the Lemlist API documentation.

  List Unsubscribes

  List Unsubscribes

  • This endpoint automatically retrieves the list of all people who are unsubscribed from your Lemlist account. No additional configuration is required beyond selecting this endpoint template.
  • The endpoint uses GET requests to https://api.lemlist.com/api/unsubscribes?limit=100. The endpoint URL includes a default limit of 100 records per page.
  • The endpoint uses pagination (iteration.type: paging.incrementing.offset) to retrieve all unsubscribes. Pagination starts from offset 0 and uses the offset query parameter to navigate through pages. The limit parameter controls how many records are returned per page, with an expected 100 records per page. The endpoint will automatically fetch all pages until all unsubscribes are retrieved.
  • The response data path is $[*], which extracts all unsubscribe objects from the response array in the API response.

  This endpoint retrieves a list of all people who are unsubscribed from your Lemlist account. The endpoint requires Basic Authentication with your API key (used as the password with an empty username), which is handled automatically by your credential configuration. The endpoint supports pagination through the offset and limit parameters, which allows you to retrieve large lists of unsubscribes efficiently. For detailed information about listing unsubscribes, pagination, and API response formats, see the Lemlist API documentation.

  List Hooks

  List Hooks

  • This endpoint automatically retrieves the list of all hooks from your Lemlist account. No additional configuration is required beyond selecting this endpoint template.
  • The endpoint uses GET requests to https://api.lemlist.com/api/hooks. The endpoint URL does not include pagination parameters.
  • The endpoint does not use pagination (iteration.type: static.url), so it will fetch all hooks in a single request. The response data path is $[*], which extracts all hook objects from the response array in the API response.

  This endpoint retrieves a list of all hooks from your Lemlist account. The endpoint requires Basic Authentication with your API key (used as the password with an empty username), which is handled automatically by your credential configuration. The endpoint does not support pagination, so all hooks are returned in a single request. For detailed information about listing hooks and API response formats, see the Lemlist API documentation.

Configure Manually

Lemlist data sources can be manually configured to ingest data from any valid Lemlist 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 Lemlist sources, such as sources that use custom query parameters, different HTTP methods, or custom data transformations.

Content Format

1. Select the format in which the data from the Lemlist API will be received from the Content Format pulldown menu. Nexla will automatically parse the data in the selected format. The Lemlist API typically returns data in JSON format.

API Endpoint URL

2. Enter the URL of the Lemlist 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. Lemlist API endpoints typically follow the pattern https://api.lemlist.com/api/{endpoint_path}.

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. The endpoint requires Basic Authentication with your API key (used as the password with an empty username), which is handled automatically by your credential configuration. For detailed information about Lemlist API endpoints, authentication, and available APIs, see the Lemlist API documentation.