Skip to main content

Integrate lemlist with Integromat

Automate your workflows with lemlist + Make (formerly Integromat)

Updated over a week ago

Learning Objective

By the end of this guide, you'll know how to connect lemlist with Make (formerly Integromat), obtain your API key, and start creating automated workflows that integrate lemlist with your favorite tools.

Why This Matters

Connecting lemlist to Make automates repetitive tasks and integrates lemlist with hundreds of other tools. Instead of manually moving data between systems or triggering actions, create workflows that automatically add leads to campaigns, update CRM records, send notifications, and more—saving hours every week and streamlining your outreach process.

Prerequisites

Before you start:

  • Active lemlist account

  • Admin access to lemlist

  • Make (Integromat) account (or ready to create one)

  • Basic understanding of automation workflows (helpful but not required)

What Make (Integromat) Does

Make (formerly Integromat) is an automation platform that connects apps and automates workflows.

With lemlist + Make, you can:

  • Automatically add leads - Import leads from Google Sheets, Airtable, CRM when conditions met

  • Trigger actions from campaigns - Create tasks in Asana when lead replies, send Slack notifications when lead interested

  • Update multiple systems - When lead added to lemlist, create contact in HubSpot and add to email sequence

  • Build custom workflows - Design complex multi-step automations tailored to your sales process

Step 1: Create Make Account

Access Make

  1. Go to Make lemlist integration page

  2. Click Sign Up or Get Started

  3. Create account with email and password

  4. Verify email address

  5. Log in to Make

Step 2: Obtain lemlist API Key

Access API settings

  1. In lemlist, click your profile picture or name (bottom-left), then go to Settings

    Screenshot

  2. In the left-side menu, click Integrations

    Screenshot

Generate and copy your API key

  1. In the API overview section, click Generate

  2. In API keys, copy the generated API key (a long string of characters)

Screenshot

⚠️ Keep secure: API key provides access to your lemlist account. Don't share publicly or commit to code repositories.

💡 Multiple keys: You may see multiple API keys if you have different access levels or team settings. Use the appropriate key for your automation.

Step 3: Connect lemlist to Make

Create new scenario

  1. In Make dashboard, click Create a new scenario

  2. Search for lemlist in apps list

  3. Click lemlist to add it to scenario

Add lemlist module

  1. Click the + button to add module

  2. Search and select lemlist

  3. Choose action (e.g., "Add Lead to Campaign," "Get Campaign," "Update Lead")

  4. Click Add

Authorize connection

  1. Module prompts for connection

  2. Click Add or Create a connection

  3. Name connection (e.g., "lemlist - Main Account")

  4. Paste API key in API Key field

  5. Click Save

✅ Result: Make now connected to lemlist and can access your campaigns and leads.

Step 4: Build Automation Workflow

Choose trigger app

Decide what starts the workflow:

  • Google Sheets - When new row added

  • Webhook - When form submitted

  • Schedule - Every day at specific time

  • CRM - When deal status changes

  • Another tool - Hundreds of options

Example: Google Sheets trigger → When new row added with lead data → Add lead to lemlist campaign

Configure lemlist action

After trigger set up:

  1. Add lemlist module to scenario

  2. Choose action:

    • Add Lead to Campaign

    • Update Lead

    • Delete Lead

    • Get Campaign Stats

    • Unsubscribe Lead

  3. Configure action:

    • Select campaign (dropdown populated from your lemlist account)

    • Map fields from trigger (email, firstName, lastName, etc.)

    • Add custom variables if needed

  4. Save module

Test workflow

  1. Click Run once at bottom of scenario

  2. Trigger test event (e.g., add test row to Google Sheet)

  3. Watch workflow execute

  4. Verify lead added to lemlist campaign

  5. Check for errors in Make execution log

💡 Debugging: Make shows detailed execution logs. If workflow fails, check logs for error messages and field mapping issues.

Activate scenario

  1. Toggle scenario to ON

  2. Workflow now runs automatically when trigger conditions met

  3. Monitor executions in Make dashboard

✅ Result: Automation active and running.

Explore Pre-Built Templates

Use Make templates

Make offers pre-built workflow templates for common use cases:

  1. In Make, go to Templates section

  2. Search for lemlist

  3. Browse available templates:

    • "Add new Google Sheets rows to lemlist campaign"

    • "Create lemlist leads from new Typeform entries"

    • "Send Slack notification when lemlist lead replies"

  4. Click template to preview

  5. Click Use template

  6. Connect your accounts and customize as needed

💡 Fast start: Templates provide starting point, modify to fit your workflow.

Common Automation Ideas

Lead generation workflows:

  • Google Sheets → lemlist: New row added → Add to campaign

  • Typeform → lemlist: Form submitted → Add to campaign with custom variables

  • LinkedIn Sales Navigator → lemlist: Export leads → Import via CSV

CRM synchronization:

  • lemlist → HubSpot: Lead replies → Create deal

  • lemlist → Salesforce: Lead interested → Update lead status

  • Pipedrive → lemlist: Deal reaches stage → Add to follow-up campaign

Notification workflows:

  • lemlist → Slack: Lead replies → Send message to #sales channel

  • lemlist → Email: Lead clicks link → Notify account manager

  • lemlist → Asana: Lead interested → Create task for sales rep

Data enrichment:

  • lemlist → Clearbit: New lead added → Enrich with company data

  • lemlist → Hunter: Missing email → Find and verify email

  • CSV upload → lemlist: Enrich with LinkedIn data → Add to campaign

Best Practices

Start simple - Build basic trigger → action workflow first. Add complexity after confirming it works.

Test with real data - Use actual lead data during testing to catch field mapping issues early.

Map fields carefully - Ensure trigger data maps to correct lemlist fields (email, firstName, lastName, custom variables).

Use error handling - Add error handlers in Make to catch failures and prevent workflow from breaking.

Monitor executions - Check Make execution logs regularly to catch errors and optimize workflows.

Keep API key secure - Don't share API key publicly. Regenerate if compromised.

Document workflows - Add notes in Make scenario describing what workflow does and why fields mapped specific way.

Use filters - Add Make filters to prevent unwanted leads from entering campaigns (e.g., only add if email valid).

Set execution limits - Configure how often workflow runs to avoid hitting API rate limits.

Troubleshooting

Connection failed when adding API key

Fix: Verify API key copied correctly (no extra spaces). Check API key is from correct lemlist account. Try generating a new API key in lemlist Settings → Integrations.

Campaign not appearing in dropdown

Fix: Verify Make connection authorized successfully. Refresh Make scenario page. Check campaign exists and is active in lemlist. Reconnect lemlist in Make if needed.

Lead not added to campaign

Fix: Check Make execution log for error messages. Verify email field mapped correctly from trigger. Ensure email is valid format. Check campaign not paused or at lead limit. Verify API key has appropriate permissions.

Field mapping errors

Fix: Ensure trigger provides data in expected format. Map exact field names from trigger to lemlist variables. Test with sample data first. Check custom variables exist in lemlist before mapping.

Workflow runs but no action in lemlist

Fix: Check Make execution log shows successful completion. Verify correct campaign selected in lemlist module. Check lead might already exist in campaign (won't add duplicates). Refresh lemlist campaign to see if lead appeared with delay.

API rate limit errors

Fix: Reduce frequency of workflow executions. Add delay between actions if processing multiple leads. Contact lemlist support if hitting limits regularly with legitimate use.

Trigger not firing

Cause: Trigger app not configured correctly, not Make/lemlist issue.

Fix: Test trigger independently of lemlist action. Verify trigger app connection working. Check trigger conditions met. Review trigger app documentation for setup requirements.

Important Notes

⚠️ API key security: Keep API key private. Anyone with your API key can access your lemlist account. Regenerate immediately if compromised.

⚠️ Duplicate prevention: lemlist won't add duplicate leads to same campaign. If workflow tries to add existing lead, action silently skips (no error).

⚠️ Field mapping critical: Incorrect field mapping causes errors or incomplete data. Always test with real data before activating workflow.

⚠️ Execution limits: Make free plan has execution limits. Upgrade if building high-volume automations.

⚠️ API rate limits: lemlist API has rate limits. Design workflows to stay within limits, especially for bulk

Related Articles
Integrate lemlist with Zapier
Integrate Typeform with lemlist
Import leads from Pipedrive to lemlist
Integrate Clay with lemlist
Use Launchpad by lemlist
Did this answer your question?