LinkedIn Lead Gen to HubSpot and Slack: An Advanced Make.com Workflow

Introduction

If your sales cycle hinges on fast follow up after a LinkedIn lead gen form submission, you know the pain: leads arrive in a spreadsheet or inbox, data is inconsistent, and reps spend precious minutes cleaning and assigning records. This automation wires LinkedIn Lead Gen directly into HubSpot as new or updated contacts, enriches the data, and sends a real time Slack alert to the right channel. No more manual data wrangling, no more missed follow ups. By the end you’ll have an end to end Make.com scenario that captures, deduplicates, enriches, and notifies your team.

This post walks you through a concrete, production ready setup. You’ll learn the trigger from LinkedIn Lead Gen, how to map fields to HubSpot properties, how to deduplicate based on email, how to enrich with company data, and how to push a Slack notification that includes a lead details and a CTA to follow up.

Pro tip: if you already run HubSpot and Slack, this pattern scales to multiple teams. You can reuse the same Make scenario with different HubSpot pipelines and Slack channels.

What You'll Need

• LinkedIn Ads or LinkedIn Lead Gen Forms with the Form URL and permission to access submissions (via LinkedIn Ads account).
• HubSpot account with a contact property set that can store lead data (email, first name, last name, company, job title, website).
• Slack workspace with a channel for new leads and a Slack app with an incoming webhook or Slack Bot token.
• Make.com account with access to at least standard features or higher (to use webhooks and data stores).
• Basic ownership of the HubSpot CRM pipeline and a Slack channel for alerts.

How It Works (The Logic)

When a new LinkedIn Lead Gen form submission occurs (trigger), Make.com reads the form data, maps it into HubSpot contact properties, checks for duplicates by email, enriches the data if possible, creates or updates the contact in HubSpot, and finally posts a structured notification to Slack with the lead details and a CTA to follow up. If a duplicate is found, you can update the existing contact instead of creating a new one, and still trigger the Slack notification if desired.

Step-by-Step Setup

1. Create a new Scenario in Make.com and add the LinkedIn Lead Gen form trigger. Choose the correct form from your LinkedIn Ads account. Ensure you have access to the form submissions.
2. Add a HubSpot module to create or update a contact. Map fields as follows:
   • Email: email (HubSpot property)
   • First Name: firstname
   • Last Name: lastname
   • Company: company
   • Job Title: jobtitle
   • Website: website
   • Any custom properties you track in HubSpot (e.g., Lead Source, LinkedIn Campaign).
3. Add a router to handle duplication logic. Use a search module in HubSpot by email to see if a contact already exists. If exists, use Update Contact; if not, use Create Contact.
4. Optional enrichment step. If you want to pull company data, add a modules that query a public or paid company enrichment service, then map fields back to HubSpot company or contact associations.
5. Add a Slack module to post a message in a designated channel. Include lead name, company, job title, form name, and a link to the HubSpot contact. Example fields to include:
   • Channel: #sales-leads
   • Message: New lead from LinkedIn Lead Gen: {{firstname}} {{lastname}} at {{company}} ({{website}}). Lead email: {{email}}. HubSpot: {{hubspot_contact_link}}
6. Test the scenario with a real or test LinkedIn Lead Gen submission. Check HubSpot for the new or updated contact and verify Slack notification arrives promptly.
7. Add error handling. Route errors to a dedicated Slack channel or email, and consider a fallback path that logs failed submissions to a Google Sheet or Airtable table for auditing.
8. Turn on the scenario and set up a re-run policy for failed runs if needed.
9. Review field mappings and permissions. Ensure Make.com has the right scopes to read LinkedIn Lead Gen submissions and write to HubSpot.
10. Document data flow. Maintain a simple diagram in your knowledge base so teammates understand where data travels from LinkedIn to HubSpot to Slack.

Real-World Business Scenario

A B2B software agency uses LinkedIn Lead Gen forms to capture demos. With this setup, every new demo request is created as a HubSpot contact, deduplicated by email, enriched with company size and industry, and a Slack alert is posted to the sales channel with a direct link to the contact. This eliminated 20 minutes per lead and reduced follow up time by 40 minutes per day. The team can move to a personalized outreach sequence in HubSpot within minutes of submission.

If you want to see how we’ve implemented similar flows for clients, you can read related work in our case studies section here.

Common Variations

• Add a step to create a task in HubSpot for the assigned rep when a lead is new.
• Extend the Slack notification with a dynamic CTA button linked to the HubSpot contact to start a workflow or schedule a call.
• Add a condition to only notify Slack for leads from certain LinkedIn campaigns or with a minimum lead score after enrichment.

A Practical End to End Pattern

This pattern reduces manual data entry, improves data quality, and accelerates first contact with a new lead. It is especially useful for teams running LinkedIn Lead Gen campaigns and using HubSpot as the central CRM with Slack as the notification channel. Olmec Dynamics has built and optimized these automations for multiple clients across industries. See how we can tailor this pattern to your stack at our case study page.