Skip to content

Connect HubSpot and Slack

Qualify inbound leads, post to #sales the moment one scores hot, and keep every lead’s HubSpot contact current, from one request.

34 actions combinedHubSpot: OAuth or Bearer token authSlack: OAuth or Bearer token auth

New Lead
Web form submission
Qualify Lead

Score buying intent

gpt-5.5
Hot lead?

Score > 70

Paths
IF

score > 70

ELSE

Default path

Slack

Notify #sales

post_message
HubSpot

Sync the contact

create_contact

TL;DR

Connect HubSpot and Slack once and one ModuleX agent runs your lead desk: it scores each inbound lead, posts the hot ones to #sales with post_message, and keeps the CRM current with search_contacts, create_contact, and update_contact. One plain-English request; the composer makes it repeatable on every new lead.

The two tools. What each one is, before they meet.

What is HubSpot?

The ModuleX HubSpot integration lets a ModuleX agent operate HubSpot on your behalf, running create, update and find actions across recent contacts, contact by ids and contacts, directly from a plain-English request, using your organization's own HubSpot credentials. No pre-built workflow is required: the agent picks the right HubSpot action for the task.

HubSpot in ModuleX

What is Slack?

The ModuleX Slack integration lets a ModuleX agent operate Slack on your behalf, running list actions across channels, messages and reactions, directly from a plain-English request, using your organization's own Slack credentials. No pre-built workflow is required: the agent picks the right Slack action for the task.

Slack in ModuleX

One workflow across HubSpot and Slack

  1. 01Connect HubSpotConnect HubSpot once with OAuth or a Bearer token, using your organization’s own credentials. ModuleX encrypts them and scopes them to your org.
  2. 02Connect SlackConnect Slack once with OAuth or a Bearer token, then pick the channel that should hear about hot leads.
  3. 03Describe the workflowAsk ModuleX to qualify inbound leads, post an alert to #sales when a lead scores hot, and create or update the HubSpot contact. It maps to real actions like Slack post_message and HubSpot create_contact.
  4. 04Review the planModuleX streams the plan onto the canvas: the lead trigger, the scoring step, a hot-lead branch to Slack, and the HubSpot sync. Check it before it runs.
  5. 05Run itRun it on every inbound lead so #sales hears about the hot ones and HubSpot stays current, or send the same request by hand.

Drive HubSpot and Slack in plain English

Type what you want. A ModuleX agent picks the right HubSpot and Slack actions, chains them, and runs it. No workflow to build.

  • When a lead scores hot, post an alert to #sales
    resolves topost_message
  • Create or update the HubSpot contact for this lead
    resolves tocreate_contactupdate_contact
  • Find the HubSpot contact for this email and post their status to #sales
    resolves tosearch_contactspost_message

HubSpot and Slack at a glance

HubSpot categoryCRM
Slack categoryCommunication
Actions available34 (26 + 8)
HubSpot authenticationOAuth or Bearer token
Slack authenticationOAuth or Bearer token
Runs on your own credentialsYes
Works in the composerYes
Multi-step / tool-chainingYes
HubSpot docsView docs
Slack docsView docs
Last updatedJul 2026

Connect HubSpot and Slack

HubSpotOAuth or Bearer token auth

HubSpot uses OAuth. You connect your HubSpot account once; ModuleX stores the access token encrypted and scoped to your organization, so your team shares a single secure connection.

Connect HubSpot
SlackOAuth or Bearer token auth

Slack uses OAuth. You connect your Slack account once; ModuleX stores the access token encrypted and scoped to your organization, so your team shares a single secure connection.

Connect Slack

Recipes that use HubSpot or Slack

Inbound Lead RoutingNew leads get scored the moment they arrive and the hot ones land in #sales while your reps are still at their desks. A ModuleX agent rates buying intent, posts the strong leads to Slack, and files every contact in HubSpot.5 steps · on every new leadBuild a one-pager on a company before you meet themA one-pager combining public background with your own record, reusable by whoever meets them next. Built for anyone walking into a meeting knowing only the company name.4 steps · on demandSee which accounts went quiet this weekOne weekly digest naming the accounts that have gone quiet, with what each signal was. Built for a customer success manager who finds out about churn after it happens.5 steps · weeklyImport a contact list into your CRM without the cleanupContacts in the CRM with the fields mapped, and a list of the rows that needed a human decision. Built for whoever inherits the spreadsheet after a conference.5 steps · on demandFailed Payment Follow-upA failed invoice stops being a silent number on a dashboard and becomes a tracked case your team can act on. When Stripe reports a payment failure, a ModuleX agent pulls the details, re-sends the invoice, and posts the case to Slack.6 steps · on payment failureSupport Ticket TriageNew tickets get read, prioritized, and routed the moment they land, and the urgent ones surface in Slack instead of sitting in a queue. A ModuleX agent classifies each Freshdesk ticket, sets its priority and tags, assigns it, and posts the ones that cannot wait.6 steps · on every new ticketBrief yourself on a candidate before the callA brief covering the role, the application, and what earlier rounds already established. Built for an interviewer who opens the CV two minutes before the interview.4 steps · before each meetingCatch up on a channel you stopped readingA summary of decisions and open questions, with the items waiting on you called out. Built for anyone returning to a busy channel after two days away.4 steps · on demandCheck database health without opening the dashboardA short, regular status that tells you when something moved out of range, and stays quiet otherwise. Built for a small team with no dedicated operations engineer.4 steps · on demandPut an external MCP server to workA tool that was not in the catalog, usable in the same place as the 175+ that are. Built for teams with internal tools that no catalog will ever cover.4 steps · on demandStart the day with one brief instead of five tabsOne brief covering the meetings, the messages that need a reply, and the work that is due. Built for anyone who begins the morning reconstructing the day from four apps.5 steps · weekdays 8amStart the day knowing what moved in the repoA short brief showing what shipped and what is waiting on a person. Built for an engineering manager reconstructing yesterday from notifications.4 steps · weekdays 8amInvestigate an error spike while it is still spikingAn investigation note that starts with a timeline instead of a blank page. Built for an on-call engineer who gets an alert and a blank page to start from.5 steps · on alertDraft the next sprint from the backlog you haveA candidate list that people can argue with, ready before the meeting rather than during it. Built for a team that spends the first hour of planning finding the candidates.4 steps · weeklyPrepare everything a new joiner needs on day oneA per-role onboarding checklist with real owners and dates, created before the start date. Built for an operations lead who assembles the same onboarding list every time, from memory.4 steps · on demandPrepare for the next meeting in the gap before itA short brief on who you are meeting, what was last agreed, and what is still open. Built for anyone with back-to-back calls and no preparation time between them.5 steps · before each meetingRequest the access a new joiner needs, with a person approvingAn access request with an explicit approver and a written record of the decision. Built for an IT lead who grants access by message and remembers it later, if at all.4 steps · on demandRoute a purchase request to the right approverA request that reached the right person, with a record of who approved what. Built for an operations manager who is the bottleneck on every small purchase.5 steps · on demandShip the latest commit and watch the buildA deploy that was confirmed by a person, watched to completion, and reported where the team reads. Built for a small team where deploying means remembering four steps in order.5 steps · on demandTurn an overnight inbox into a short listA short digest that names the messages needing a reply and compresses everything else. Built for anyone who opens the laptop to fifty unread messages.4 steps · weekdays 8amTriage the support queue before your shift startsA queue that is grouped and ordered, with repeated issues visible as one cluster. Built for a support lead who opens the queue to sixty tickets and no order to them.4 steps · on every new ticketNotice a ranking drop in the same week it happensA weekly digest that names the pages and queries that moved, while it is still recent. Built for an SEO owner who finds out about a drop from the quarterly review.4 steps · weeklyGet told before you sell out of somethingAn alert naming the items that are running low, before the storefront says sold out. Built for a store operator who discovers a stockout from a customer complaint.4 steps · on alertGet the ad numbers without opening the ads managerA weekly digest with the movement per campaign, without opening the ads manager. Built for a growth marketer who checks campaigns daily out of anxiety, not insight.4 steps · weeklyWatch the funnel without building a dashboardA weekly stage-by-stage view of the funnel, assembled from the tools you already run. Built for a founder who wants the funnel numbers without another BI project.5 steps · weekly

HubSpot and Slack: frequently asked

  • HubSpot connects with OAuth or a Bearer token, and Slack with OAuth or a Bearer token. You connect each once; ModuleX stores the credentials encrypted and scoped to your organization.

Put HubSpot and Slack to work together.

Connect HubSpot and Slack once and let one agent run the workflow across both from a single plain-English request.

Last updated: Jul 2026HubSpotSlackAll 179 integrations