Skip to main content

Lemlist Destination

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 sends data to a Lemlist location.
lemlist.png

Lemlist

Create a Lemlist Destination​

  1. Click the + icon on the Nexset that will be sent to the Lemlist destination, and select the Send to Destination option from the menu.

  2. Select the Lemlist connector from the list of available destination 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 destinations can be created using pre-built endpoint templates, which expedite destination setup for common Lemlist endpoints. Each template is designed specifically for the corresponding Lemlist endpoint, making destination configuration easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    Lemlist destinations can also be configured manually, allowing you to send data to Lemlist endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Lemlist endpoints. Each template is designed specifically for the corresponding Lemlist endpoint, making destination setup easy and efficient.

  • To configure this destination using a template, 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.

    Add a Lead in a Campaign

    Add a Lead in a Campaign

    • Enter the ID of the campaign to which you want to add the lead in the Campaign ID field. This is the unique identifier for a specific campaign in your Lemlist account. You can obtain Campaign IDs from the "List Campaigns" endpoint or from your Lemlist account dashboard.
    • Optionally, enter the email address of the lead in the Email field. If the email is not provided, it will be extracted from the Nexset data. If the lead doesn't exist, it will be created, then inserted into the campaign.
    • The endpoint uses POST requests to https://api.lemlist.com/api/campaigns/{campaign_id}/leads/{email} where {campaign_id} is the Campaign ID you configured and {email} is the Email you specified or extracted from the Nexset. The endpoint URL is automatically constructed based on your configuration.
    • The endpoint sends data from your Nexset as the request body in JSON format. The request body is automatically formatted according to the schema fields and data mapping you configure. Each record in your Nexset will be sent as a JSON object containing the lead data to add.

    The request body must be properly formatted JSON that matches the Lemlist API specification for adding leads. 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 Content-Type: application/json header is automatically included in requests. If the lead doesn't exist, it will be created automatically, then inserted into the campaign. For detailed information about adding leads to campaigns, including required fields, field names, and request formats, see the Lemlist API documentation.

    Unsubscribe

    Unsubscribe

    • Enter the email address or domain to unsubscribe in the Email or Domain field. If this is a domain, it must start with @ (e.g., @example.com). This will add the email address or domain to the unsubscribes list in your Lemlist account.
    • The endpoint uses POST requests to https://api.lemlist.com/api/unsubscribes/{email} where {email} is the Email or Domain you configured. The endpoint URL is automatically constructed based on your configuration.
    • The endpoint sends data from your Nexset as the request body in JSON format. The request body is automatically formatted according to the schema fields and data mapping you configure. Each record in your Nexset will be sent as a JSON object containing the unsubscribe data.

    The request body must be properly formatted JSON that matches the Lemlist API specification for unsubscribing. 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 Content-Type: application/json header is automatically included in requests. If you're unsubscribing a domain, it must start with @ (e.g., @example.com). For detailed information about unsubscribing email addresses or domains, including required fields, field names, and request formats, see the Lemlist API documentation.

    Add Hook

    Add Hook

    • This endpoint automatically adds a hook to your Lemlist account using data from your Nexset. No additional configuration is required beyond selecting this endpoint template.
    • The endpoint uses POST requests to https://api.lemlist.com/api/hooks. The endpoint URL is fixed and does not require any path parameters.
    • The endpoint sends data from your Nexset as the request body in JSON format. The request body is automatically formatted according to the schema fields and data mapping you configure. Each record in your Nexset will be sent as a JSON object containing the hook data to add.

    The request body must be properly formatted JSON that matches the Lemlist API specification for adding hooks. 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 Content-Type: application/json header is automatically included in requests. For detailed information about adding hooks, including required fields, field names, and request formats, see the Lemlist API documentation.

Configure Manually​

Lemlist destinations can be manually configured to send data to 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 destinations, such as destinations that use custom request headers, different HTTP methods, or custom data formatting.

Content Format​

  1. Select the format in which the Nexset data will be sent to the Lemlist API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call. The Lemlist API typically uses JSON format for request bodies.

API Endpoint URL​

  1. Enter the URL of the Lemlist API endpoint to which you want to send the Nexset data in the 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.