In Brief: We set up HubSpot lead alerts in Microsoft Teams for a client, so every alert lands in the right channel shortly after a form is submitted. One HubSpot workflow checks whether the contact has submitted a specific earlier form, then sends its own Teams notification for each path, with details such as the contact's name, company and the page they converted on. The setup needs an admin-level Teams installation, connected teams in HubSpot, and a Professional or Enterprise HubSpot subscription.
A lead fills in a form on your website. HubSpot records it, may send someone an internal email, and moves on. Meanwhile, your sales team is in Microsoft Teams all day and sees the email hours later, if at all.
That gap is exactly what one of our clients asked us to close. Their marketing team runs lead campaigns, including LinkedIn Ads, and they wanted new submissions to appear in Teams, in a channel that matched where the lead came from. They also wanted sales to see straight away whether the person had downloaded something before. Here is how we built it with the native HubSpot and Microsoft Teams integration, and what you need to check before you try it yourself.
- Form submitted
- Email lands in an inbox
- Lead goes cold
- Next lead comes in
Why Form Submissions Get Lost Between HubSpot and Teams
HubSpot already notifies people about new leads. The problem is where those notifications go. Standard HubSpot notifications are personal: each user decides which ones they receive, in the bell, by email, or in Teams. Nobody owns the shared view, so a lead from a paid campaign can sit unassigned while everyone assumes someone else saw it.
The second problem is context. An email that says a form was submitted rarely tells sales which campaign drove it, or whether this person already downloaded something last month. Reps then open HubSpot, search for the contact and piece the story together. The same visibility gap shows up when HubSpot permissions hide leads from the people they are assigned to: the data exists, but not where the team is looking.
The fix is to stop relying on personal settings and send the alert from a workflow, to a shared Teams channel, with the context already in the message.
Want one view of every lead, not just a channel alert?
Explore HubSpot CRM DashboardsBefore You Build: Admin-Level Install and Connected Teams
Teams alerts often fail for reasons that have nothing to do with the workflow. The cause is often in the setup, decided on the install screen long before anyone opens the workflow editor. We made the same point about the setup decisions behind a monday.com and HubSpot two-way sync, and it applies here too. Check these four things first.
- Workflows need a Professional or Enterprise subscription. The Teams integration itself works on every HubSpot plan, but the workflow actions do not.
- Choose the admin-level install. HubSpot offers two install types. A user-level install does not need a Microsoft admin, but it only covers personal notifications, creating tasks and tickets from Teams, and Teams meeting links. The admin-level install, approved by a Microsoft Teams Global Admin, unlocks every feature.
- Map every user. HubSpot links HubSpot users to Teams users automatically when the email addresses match. When they don't, each user has to connect and verify their Teams account manually, or they will not receive notifications sent to users from a workflow.
- Connect the team. This is a step many setup guides leave out. In HubSpot, go to Settings > Integrations > Connected Apps > Microsoft Teams > Settings > Global Settings, and click Connect next to each team you want to use. A team that isn't connected won't appear in the workflow's Team dropdown.
The Connected Teams list in HubSpot. Every team used in a lead alert workflow must show as Connected.
If a team is missing from that list, either the HubSpot bot isn't installed in it, or its visibility is turned off. Only the user who completed the admin-level install can connect a team or make it visible to everyone else. HubSpot's guide to connecting HubSpot and Microsoft Teams explains how to add the bot to a team manually.
How We Built HubSpot Lead Alerts in Microsoft Teams
The whole setup is one contact-based workflow with a single branch and two Teams actions. Here is how it fits together.
The lead alert workflow: a form trigger, a branch for returning leads, and a separate Teams notification on each path.
The trigger. The workflow enrols a contact when a form submission has been completed, any number of times, and the form is one of the lead forms we picked. Re-enrolment is on, so a contact who submits again goes through the workflow again. Without re-enrolment, a returning lead would never trigger a second alert.
The branch. The first action checks whether the contact has submitted a specific earlier form. If yes, they go down the "Has Submitted Previously" path. If not, they go down "None met": they haven't submitted that earlier form, so the workflow treats them as a new lead.
The Teams actions. Each path ends in its own Send Microsoft Teams Notifications action. In the returning lead action shown above, Send to is set to Channel, the Team is the client's connected team, and the Channel is dedicated to LinkedIn Ads leads. Giving each lead source its own channel means sales can mute what isn't theirs and act on what is.
The same action works in every workflow type, including deals, tickets and HubSpot custom objects, so this pattern isn't limited to contacts.
"The integration itself takes minutes. What makes it work is the setup around it: the right install type, mapped users and one channel per lead source, so every alert lands where someone is actually watching," says Antonio Karneluti, CTO of Loncom Consulting.
New Lead or Returning Lead? Why the Branch Matters
A new lead and a returning lead need different responses. Someone who downloads their first ebook is starting to research. Someone who already downloaded an earlier asset and comes back for another is showing repeat interest, and that is often the better moment for sales to reach out.
Without the branch, both look identical in Teams. With it, each path sends its own message, so the channel itself tells sales which leads to prioritise. You can also route the two paths to different channels or people, for example returning leads straight to the account owner.
One warning: the branch is only as reliable as your contact data. If the same person exists as two contact records, HubSpot treats the second submission as a brand new lead. Duplicates are one of the first things we check in any CRM data audit, and they matter just as much here.
Writing Alerts Sales Can Act On
An alert that only says "new form submission" sends people back into HubSpot. The message should answer who, from where and what they did, without a click.
In the returning lead action, the message combines personalisation tokens with plain text: the contact's first name, last name and company name, followed by "has downloaded our Ebook", and then the URL path of the form submission. The URL path shows exactly which page the person converted on, which is usually enough to tell which campaign or asset brought them in.
A few more options in the same action are worth knowing, all covered in HubSpot's guide to managing records and notifications in Microsoft Teams:
- Formatting: asterisks make text bold, underscores make it italic, and square brackets followed by a URL in parentheses create a link.
- Mentions: type @ followed by a person's Microsoft Teams email address to tag them in the alert.
- Record owner: the "Send notification to record owner" checkbox sends a copy to the contact owner as well as the channel.
- Action buttons: "Select actions to include with message" adds buttons to the alert, so the person receiving it can act on the record straight from Teams.
Common Issues and How to Fix Them
Most of these come down to one thing: both systems have to agree on who and where. HubSpot matches users by email and teams by connection, the same matching problem we unpacked in our guide to a two-way Sanity and HubSpot sync without duplicates.
In Short
HubSpot lead alerts in Microsoft Teams work best when they come from a workflow, not from personal notification settings. Install the integration at admin level, connect each team, map your users, then build one workflow that branches new and returning leads and sends each to the channel that matches its source. Put the name, company and conversion page in the message, and sales can act without opening HubSpot.
Want lead alerts your sales team actually acts on?
Book a Free ConsultationFAQ
How do I send HubSpot lead alerts to a Microsoft Teams channel?
Connect Microsoft Teams to HubSpot with the admin-level install and connect the team you want to use. Then build a workflow triggered by a form submission and add the Send Microsoft Teams Notifications action, with Send to set to Channel. Choose the team and channel, write the message with personalisation tokens, and turn the workflow on.
Why doesn't my Microsoft Teams team appear in a HubSpot workflow?
Because it hasn't been connected in HubSpot yet. A team only shows up in the workflow's Team dropdown after it's connected in the Microsoft Teams integration's Global Settings. If it's missing from that settings list as well, the HubSpot app needs adding to the team in Teams, or its visibility needs switching on.
Do I need an admin-level installation to use Teams workflow actions?
Yes. Without the admin-level install, HubSpot unlocks only a small set of Teams features, and workflow alerts to channels aren't among them. A Microsoft Teams Global Admin has to approve the install, and the HubSpot account needs a Professional or Enterprise subscription for workflows.
Can HubSpot send different Teams alerts for new and returning leads?
Yes. Add a branch to the workflow that checks whether the contact has submitted a form before, then add a separate Teams notification action to each path. Turn on re-enrolment so returning leads go through the workflow again.
How does Loncom set up HubSpot and Microsoft Teams integrations?
As a HubSpot Diamond Solutions Partner with 150+ CRM implementations behind us, we start with the setup that decides whether alerts work at all: install type, user mapping and connected teams. Then we design the workflows around how your sales team actually works, which channels they watch, which leads need a different response, and what each alert must say. Learn more about our integration services.
Share:
Leave a comment