Overview
Lemlist is a multi-channel outreach platform that supports touchpoints across LinkedIn, email, and more. Since many Bitscale users rely on Lemlist for outbound campaigns, we provide a native integration to streamline lead enrichment and campaign execution.
This integration allows you to:
- Add or update leads in Lemlist campaigns directly from Bitscale
- Look up leads in Lemlist to avoid duplication or retrieve specific profiles
Available Actions
- Add or Update Leads
- Push enriched, filtered, or qualified leads from Bitscale into Lemlist campaigns.
- Map campaign variables (e.g., name, company, personalization).
- Control duplicate handling with a simple toggle.
- Lookup Leads
- Query Lemlist for a specific lead by email or ID.
- Useful for avoiding duplicate outreach or building dashboards with synced leads.
Setting Up the Integration
- In Bitscale, go to Enrichments → Integrations → Lemlist.
- Select either Add/Update Lead or Lookup Lead.
- Click Add Account → Enter a name for the account (e.g., Marketing Account).
- Retrieve your API Key from Lemlist:
- Go to Lemlist → Settings → Integrations.
- Generate and copy your API key (it will only be shown once).
- Paste the API key in Bitscale and save.
Pushing Leads to Lemlist
- Select your connected Lemlist account.
- Choose the target campaign.
- Set the action: Add or Update Leads.
- Map required fields:
- Email (primary unique identifier in Lemlist)
- Additional fields such as First Name, Company, or custom variables
- Optionally:
- Enable/disable duplicates
- Map personalization variables to Lemlist’s custom fields
Looking Up Leads
- Select the Lookup Lead action.
- Provide an email (or Lemlist ID).
- Bitscale retrieves the lead’s full details from Lemlist.
- Use this data to enrich further or prevent duplicate outreach.
Best Practices
- Always map Email as the unique identifier when pushing leads.
- Use Lookup Lead before large pushes to avoid duplicates.
- Maintain personalization variables in your Bitscale grid and map them into Lemlist for contextual messaging.
- Keep API keys stored securely, as they are only shown once during creation.