🔓 Unlock all 10,000+ workflows & prompts free Join Newsletter →
✅ Full access unlocked — explore all 10,000 AI workflow and prompt templates Browse Templates →
Home › n8n › Workflow
January 22, 2026

HubSpot + Slack: turn job posts into sales leads

HubSpot + Slack: turn job posts into sales leads - n8n workflow automation template
Lisa Granqvist Partner Workflow Automation Expert
HubSpot + Slack: turn job posts into sales leads - n8n workflow automation template
Get a free AI assessment → Get a free AI assessment → ⬇️ Use template

Job posts keep showing up in your market, and you know they mean something. But unless someone manually spots them, researches the company, and logs the lead, that “intent signal” just disappears into the scroll.

HubSpot users in sales and growth feel this first. A marketing manager sees the same missed window from the other side. And if you run an agency, you’re probably tired of explaining why “timing” matters when nobody has time to track it. This HubSpot Slack leads automation turns hiring activity into contacts, tasks, and alerts you can act on.

You’ll see how the workflow captures job intent, enriches and de-duplicates the record, updates HubSpot, and pings the right people in Slack so follow-up actually happens.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: HubSpot + Slack: turn job posts into sales leads

The Problem: Job Intent Data Gets Lost (Or Never Logged)

Hiring is a buying signal. A company posts for “RevOps,” “Paid Search,” or “Sales Development” because something is changing, and budgets usually follow. The frustrating part is how easy it is to waste that signal: someone sees the post, bookmarks it, then forgets. Or a rep creates a half-baked HubSpot record, skips enrichment, and you end up with duplicates and no clear next step. Multiply that by a week of job posts and you’re not “missing a few leads.” You’re training your team to ignore a reliable trigger.

It adds up fast. Here’s where it breaks down in real life.

  • Job posts get captured in random places (a Slack message, a note, a spreadsheet), so nothing is routed to sales consistently.
  • Without enrichment, reps spend about 10–20 minutes hunting for a domain, a decision-maker, and a usable email.
  • Duplicate companies and contacts quietly pile up, which means reporting gets messy and sequences hit the wrong record.
  • Follow-up depends on memory, not a task, so “great timing” turns into “we’ll reach out next month.”

The Solution: Job Intent → Enriched HubSpot Lead + Slack Routing

This workflow starts when a job intent signal hits your system through a webhook (for example, from a scraper, a job-post monitoring tool, or a form you use internally). n8n then enriches the company and contact details via Dropcontact, so you’re not working from a vague company name and a role title. Next, it looks up the company in HubSpot and decides whether to update an existing account or create a new one. In the same pass, it searches for the contact, upserts the contact record, and checks key conditions like customer status, open deals, and whether an email was detected. Finally, it routes the outcome: sales gets a Slack notification when the signal is actionable, customer success gets alerted if it’s an existing customer, and HubSpot tasks are created so the lead doesn’t die in Slack.

The flow is simple to reason about. Webhook in, enrichment and HubSpot matching in the middle, then Slack + tasks + optional outreach enrollment as the finish. You get clean CRM data and immediate visibility, without asking someone to do “quick admin” all day.

What You Get: Automation vs. Results

Example: What This Looks Like

Say you track 25 new job posts a week. Manually, a rep might spend about 15 minutes researching each company, 10 minutes finding a contact, and 5 minutes logging everything in HubSpot (roughly 12 hours weekly). With this automation, you send the job intent into the webhook, wait a couple minutes for enrichment and HubSpot updates, and Slack gets the right alert automatically. You still choose the message, but the lead is already clean, enriched, and assigned.

What You’ll Need

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • HubSpot to store companies, contacts, and tasks
  • Slack to notify sales or customer success
  • Dropcontact API key (get it from your Dropcontact dashboard)

Skill level: Intermediate. You’ll connect accounts, map a few HubSpot fields, and test the webhook payload end-to-end.

Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).

How It Works

A job intent signal hits your webhook. Your monitoring tool (or internal process) sends details like company name, job title, and source URL into n8n’s Webhook node.

Enrichment fills in the blanks. n8n calls Dropcontact to enrich the data, which helps turn “Company X is hiring” into something you can actually use in HubSpot, like a matched domain and contact identity details.

HubSpot gets updated, not cluttered. The workflow looks up the company first, then chooses between creating a new account or updating an existing one. It searches for the contact, upserts the contact record, and runs a few checks (customer status, contact attempts, and open deals) so you don’t spam existing opportunities or step on CS toes.

Slack and follow-up tasks get routed. Sales receives a Slack notification for net-new, actionable signals, and HubSpot tasks are created for outreach. If the account is already a customer, CS can be alerted instead, so the conversation stays coordinated.

You can easily modify the routing logic to notify different channels or assign tasks to specific owners based on territory. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Webhook Trigger

Set up the inbound trigger that receives hiring intent signals and kicks off the workflow.

  1. Add the Job Intent Webhook node as your trigger.
  2. Set HTTP Method to POST.
  3. Set Path to fe426a62-eee5-4fed-bc74-45d4ac09b338-lonescale.
  4. Send a sample POST payload to the webhook URL to generate test data.

Step 2: Enrich and Identify the Company

Enrich the inbound data and locate the company record in HubSpot before deciding how to proceed.

  1. Add Dropcontact Enrichment and map Company to {{ $json["body"]["people_company_name"] }}, Website to {{ $json["body"]["people_company_domain"] }}, Last Name to {{ $json["body"]["people_last_name"] }}, and First Name to {{ $json["body"]["people_first_name"] }}.
  2. Credential Required: Connect your dropcontactApi credentials in Dropcontact Enrichment.
  3. Add HubSpot Company Lookup with Operation set to searchByDomain, Domain set to {{ $node["Job Intent Webhook"].json["body"]["people_company_domain"] }}, and Limit set to 1.
  4. Include Properties array values hs_lead_status, numberofemployees, description, and linkedin_company_page.
  5. Credential Required: Connect your hubspotOAuth2Api credentials in HubSpot Company Lookup.
  6. Confirm Dropcontact Enrichment connects to HubSpot Company Lookup in the canvas.

Step 3: Create or Update the HubSpot Company and Find the Contact

Branch based on whether a company exists, then update or create the company and search for the contact.

  1. Add Account Exists Check with condition {{ $json["companyId"] }} is isNotEmpty.
  2. Connect the true output of Account Exists Check to Update HubSpot Account and the false output to Create HubSpot Account.
  3. In Update HubSpot Account, set Company ID to {{ $json["companyId"] }} and map Description, Number Of Employees, and LinkedIn Company Page using the expressions in the node.
  4. In Create HubSpot Account, set Name to {{ $node["Job Intent Webhook"].json["body"]["company_name"] }} and map Website URL, Description, Year Founded, and LinkedIn Company Page from the webhook payload.
  5. Add HubSpot Contact Search with Operation set to search, and filter on Email using {{ $node["Dropcontact Enrichment"].json["email"][0]["email"] }}.
  6. Credential Required: Connect your hubspotOAuth2Api credentials in Update HubSpot Account, Create HubSpot Account, and HubSpot Contact Search.

Step 4: Upsert the Contact and Run Parallel Checks

Upsert the contact in HubSpot, then evaluate multiple lead status conditions in parallel.

  1. Add Upsert HubSpot Contact and set Email to {{ $node["Dropcontact Enrichment"].json["email"][0]["email"] }}.
  2. Map Job Title, Last Name, First Name, and Company Name with the expressions from the node parameters, and map the custom property linkedin_url to {{ $json["properties"]["lemlistlinkedinurl"] || $node["Job Intent Webhook"].json["body"]["people_linkedin_url"] }}.
  3. Credential Required: Connect your hubspotOAuth2Api credentials in Upsert HubSpot Contact.
  4. Connect HubSpot Contact Search to Upsert HubSpot Contact.
  5. Upsert HubSpot Contact outputs to both New Account Check, Customer Status Check, Contact Attempt Check, and Open Deal Check in parallel.

Tip: Parallel checks let you trigger multiple actions based on lead status without waiting for sequential evaluation.

Step 5: Configure Outreach and Notification Actions

Send Slack alerts, create HubSpot tasks, and enroll leads in Lemlist based on lead status and email availability.

  1. From New Account Check, route to Email Detected. This node then outputs to both Lemlist Lead Enrollment and LinkedIn Outreach Task in parallel.
  2. In Lemlist Lead Enrollment, set Email to {{ $json["properties"]["email"]["value"] }} and Campaign ID to Hiring Signal Lonescale. Map Last Name, First Name, Company Name, and LinkedIn URL using the provided expressions.
  3. Credential Required: Connect your lemlistApi credentials in Lemlist Lead Enrollment.
  4. In LinkedIn Outreach Task, keep Type as task, set Subject to Hiring Signal - New lead to contact, and associate company/contact IDs using {{ $node["Update HubSpot Account"].json["companyId"] || $node["Create HubSpot Account"].json["companyId"] }} and {{ $json["vid"] }}.
  5. Credential Required: Connect your hubspotOAuth2Api credentials in LinkedIn Outreach Task.
  6. From Contact Attempt Check, connect to HubSpot Follow-up Task with its metadata body expression intact and associations set to {{ $node["Update HubSpot Account"].json["companyId"] || $node["Create HubSpot Account"].json["companyId"] }} and {{ $json["vid"] }}.
  7. Credential Required: Connect your hubspotOAuth2Api credentials in HubSpot Follow-up Task.
  8. From Customer Status Check, connect to CS Slack Alert and set Channel to Customer Success - Customer News with the provided message expression.
  9. From Open Deal Check, connect to Sales Slack Notification and keep the HubSpot record URL expression intact.
  10. Credential Required: Connect your slackOAuth2Api credentials in CS Slack Alert and Sales Slack Notification.

⚠️ Common Pitfall: Ensure Email Detected is correctly configured to only pass records with a valid email; otherwise, Lemlist Lead Enrollment may fail or enroll incomplete leads.

Step 6: Test and Activate Your Workflow

Validate the end-to-end flow and then enable the workflow for production use.

  1. Click Execute Workflow and send a test POST request to the Job Intent Webhook URL.
  2. Verify that Dropcontact Enrichment returns email data and that HubSpot Company Lookup returns or creates a company record.
  3. Confirm that Upsert HubSpot Contact creates/updates the contact and that parallel checks fire as expected.
  4. Check for outreach actions: Lemlist Lead Enrollment enrollment, LinkedIn Outreach Task creation, and Slack messages from CS Slack Alert or Sales Slack Notification.
  5. Once verified, toggle the workflow to Active to process real hiring signals.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

  • HubSpot credentials can expire or need specific permissions. If things break, check your HubSpot private app scopes and the connection status inside n8n first.
  • If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
  • Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.

Related Workflows

If your team also needs to keep inbound interest from slipping through the cracks, HubSpot to Slack, never miss high value leads pairs well with job-intent routing so every “hot moment” lands in the right channel.

For teams doing both enrichment and outreach logging, Hunter + HubSpot: qualify leads and log outreach is a strong companion, especially when you want to verify emails before sequences start.

When a spreadsheet still drives your lead list (it happens), Google Sheets + HubSpot: leads logged and followed up helps you keep HubSpot in sync so reps stop copying rows into the CRM.

Need cleaner cold outreach inputs too? Airtable to Lemlist, clean leads added and verified is useful when job intent becomes one of several sources feeding a single outbound engine.

Finally, if you want your whole team to actually see replies, Lemlist to Mattermost, reply alerts your team sees closes the loop after the HubSpot task gets completed and outreach starts.


Quick reference:

Frequently Asked Questions

How long does it take to set up this HubSpot Slack leads automation?

About an hour if your HubSpot, Slack, and Dropcontact accounts are ready.

Do I need coding skills to automate HubSpot Slack leads?

No. You’ll connect accounts, map fields, and paste in a webhook URL.

Is n8n free to use for this HubSpot Slack leads workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Dropcontact API costs based on how many enrichments you run.

Where can I host n8n to run this HubSpot Slack leads automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I customize this HubSpot Slack leads workflow for different routing (like territories or channels)?

Yes, and it’s one of the best reasons to use n8n. You’ll adjust the “Customer Status Check,” “Open Deal Check,” and “New Account Check” decision points to match your rules, then point the Slack nodes to different channels. Common customizations include routing by country, routing by deal stage, and creating different HubSpot tasks for email vs. LinkedIn follow-up.

Why is my HubSpot connection failing in this workflow?

Usually it’s expired credentials or missing scopes on your HubSpot private app. Reconnect HubSpot in n8n, then confirm the app has permission to read and write companies, contacts, and tasks. If the workflow creates records but can’t update them, it’s often a permissions mismatch. And if you’re pushing a lot of job posts at once, HubSpot rate limiting can show up as intermittent failures.

How many job posts can this HubSpot Slack leads automation handle?

For most small teams, hundreds per month is fine, and the real limit is your n8n plan and enrichment budget. On n8n Cloud, your monthly execution limit depends on your plan. If you self-host, there’s no fixed execution cap, but your server resources and API rate limits will still matter. If you plan to ingest job posts in bulk, use batching (Split in Batches) and pace the enrichment calls.

Is this HubSpot Slack leads automation better than using Zapier or Make?

Often, yes, because this workflow relies on multiple checks (customer status, open deals, contact attempts) and careful upserts, which get awkward and expensive in simpler automation tools. n8n is also easier to extend when you want to add logic like batching, merges, or multi-channel routing. Zapier or Make can still be fine if your process is just “job post in → Slack message out,” and you don’t care about CRM cleanliness. Honestly, CRM cleanliness is where most automations fall apart. Talk to an automation expert if you want help choosing.

Once it’s running, job intent stops being “interesting” and starts being actionable. The workflow handles the repetitive cleanup and routing so your team can focus on the conversation.

Need Help Setting This Up?

Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.

Talk to Automation Expert →

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

×

Use template

Get instant access to this n8n workflow Json file

Copy and import json workflow into your n8n workflow

💬
Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.