Skip to main content

Use Launchpad by lemlist

Learn how to make the most of this app that allows you to seamlessly integrate automation tools with your HubSpot in real time

Updated over a week ago

Learning Objective

By the end of this tutorial, you’ll know how to install Launchpad in HubSpot, add it to your CRM records (company/contact/deal), create custom workflow trigger buttons, and push leads into a lemlist campaign from HubSpot.

Why This Matters

Launchpad connects HubSpot to your automation tools and APIs so you can enrich records and trigger workflows directly from the CRM, without switching tools. That means cleaner data, faster follow-up, and repeatable processes your team can run from inside HubSpot.

Prerequisites

  • You have admin access (or the required permissions) in HubSpot to install apps and customize record layouts.

  • If you plan to push leads to lemlist, you have access to your lemlist workspace and can generate an API key.


Core Lesson — Step-by-Step Workflow

This workflow is organized into 4 phases: install Launchpad, explore what it can do, add it to your record layouts, then create buttons that trigger workflows (including sending leads to lemlist).

Phase 1: Install Launchpad in HubSpot

  1. Go to the HubSpot Marketplace: Head to the HubSpot Marketplace and search for Launchpad by lemlist.

  2. Install the app: Click Install, and follow the on-screen steps to connect Launchpad to your HubSpot account.

  3. Authorize permissions: Accept the required permissions so Launchpad can read/write the data needed to enrich records and run automations.

  4. Connect your automation tools or API(s): Link the tools/API endpoints you want Launchpad to use so it can send data and trigger workflows.


Phase 2: Choose the right Launchpad workflow for your use case

Launchpad can run multiple workflows depending on what you want to automate. Below are common “ready-to-use” examples and what inputs they require, so you can pick the right one before you build buttons in HubSpot.

Find Verified Emails and Phone Numbers

Use this to enrich contact records with verified contact details so your outreach and routing rules always rely on up-to-date data.

  • How to use: Trigger a Launchpad workflow to search for verified emails and phone numbers from your CRM data.

  • Properties you need to send: linkedIn URL

  • Email enrichment:

  • Phone enrichment:

Use AI to get an offering from a company

Use this to quickly generate a structured summary of a company’s products/pricing so reps don’t have to research from scratch before outreach.

  • What it does: This workflow scrapes a company's landing page and uses AI to summarize the different products it offers.

  • What property you need to send: company domain

What property you need to create: company product (multi-line text)

Find Social Media Pages

Use this to enrich company records with social profiles (LinkedIn, X, YouTube, TikTok, etc.) so your team has quick context and can engage faster.

  • How to use: Trigger a workflow to find a company’s social media pages directly from their profile in HubSpot.

  • What properties you need to send: domain

Push Leads to lemlist Campaigns

Use this to send leads from HubSpot straight into lemlist campaigns so outreach can start immediately—without exports, imports, or manual copy/paste.

  • How to use: Push new leads from your HubSpot CRM into a lemlist campaign with a few clicks.

  • What properties you need to send: LinkedIn URL or Email

  • How it works: You only to connect a lemlist API key

  • How to get a lemlist API key


Phase 3: Add Launchpad to company, contact, and deal records

Adding Launchpad to your record layouts makes it available in the right sidebar so your team can run actions (like enrichment or lead-push) directly from a record.

  1. In your HubSpot settings, go to the Connected Apps tab and click Go to settings.

From here, select Add to X and drag and drop the Launchpad card where you want it to appear in HubSpot.

To company:

To contact:


Phase 4: Create buttons that trigger workflows

Custom triggers are what turn Launchpad into a “one-click” action inside HubSpot. You define what to send (properties), where to send it (webhook URL), and how it should run (method).

  1. On your Launchpad card inside a record, click More, then select Add custom trigger.

  2. Enter a name, your trigger workflow URL, and the properties you would like to send to your webhook, then save.

  3. Your new button appears on the right panel, ready to use on that record type.


Practical Application / Real-Life Example

A common setup is: (1) enrich a lead, then (2) push qualified leads into a lemlist campaign. This keeps HubSpot as the source of truth while lemlist runs outbound automatically.

How to push a lead into a lemlist campaign

This example uses the built-in “Add lead to lemlist campaign” action in the Launchpad card.

1. Click Add lead to lemlist campaign.

2. In lemlist, go to Settings > Integrations and generate a new API key.

3. Back in the HubSpot app modal, add your lemlist API key.

4. In the dropdown, select the campaign you want to send the lead to.


Troubleshooting & Pitfalls

  • Issue: The Launchpad card doesn’t appear on records.
    Root cause: It hasn’t been added to the record layout (or you’re viewing a different object/layout).
    Fix: Repeat Phase 3 and ensure you added Launchpad to the correct object (Company/Contact/Deal) and the correct view.

  • Issue: Custom trigger button appears but does nothing / fails.
    Root cause: Webhook URL, method, or required properties are missing/incorrect.
    Fix: Edit the trigger and confirm the URL, method (GET/POST), and selected properties match what your workflow expects.

  • Issue: Can’t push a lead to lemlist.
    Root cause: Invalid API key or missing identifier (LinkedIn URL or Email).
    Fix: Generate a new API key in lemlist and confirm the HubSpot record contains a valid Email or LinkedIn URL.


Knowledge Check

  • Which HubSpot record types did you add Launchpad to (company, contact, deal), and why?

  • What properties does your workflow need (e.g., domain, LinkedIn URL, email) to run successfully?

  • If a trigger fails, what are the first 3 settings you would verify (URL, method, properties)?

Did this answer your question?