Connect HubSpot to Microsoft Teams in two minutes.
Real-time triggers from HubSpot, ready-made actions in Microsoft Teams. Filter, transform, and route without writing a line of code.
Workflows fire when something happens in HubSpot.
- New CompanyWebhook
- Company DeletedWebhook
- Company Property ChangedWebhook
- New ContactWebhook
- Contact DeletedWebhook
Workflows do something in Microsoft Teams, instantly.
- Create Teams ChannelAPI
- Delete Teams MessageAPI
- Get Teams MessageAPI
- List Teams ChannelsAPI
- List Teams MembersAPI
- List TeamsAPI
Pick the way that fits your stack.
Pair pages are mirrored. Each direction gets its own dedicated page.
When something happens in HubSpot, do it in Microsoft Teams.
18 HubSpot triggers wired to 9 Microsoft Teams actions. Most-used pairing: New Company → Create Teams Channel.
Or fire it the other way around.
2 Microsoft Teams triggers wired to 23 HubSpot actions downstream.
See Microsoft Teams → HubSpot →Common HubSpot → Microsoft Teams workflows.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Fires when a new company is created in HubSpot. Use to enrich the company with firmographic data, mirror to your data warehouse, or run account-matching against parent records.
Fires when a new company is created in HubSpot. Use to enrich the company with firmographic data, mirror to your data warehouse, or run account-matching against parent records.
Fires when a new company is created in HubSpot. Use to enrich the company with firmographic data, mirror to your data warehouse, or run account-matching against parent records.
Fires when a new company is created in HubSpot. Use to enrich the company with firmographic data, mirror to your data warehouse, or run account-matching against parent records.
Fires when a company is deleted in HubSpot. Useful for audit logs or for tearing down related records in other systems.
Fires when a company is deleted in HubSpot. Useful for audit logs or for tearing down related records in other systems.
Fires when a company is deleted in HubSpot. Useful for audit logs or for tearing down related records in other systems.
Fires when a company is deleted in HubSpot. Useful for audit logs or for tearing down related records in other systems.
Fires when a specific company property changes in HubSpot. Use a property filter to react only on changes you care about (e.g. lifecycle stage).
Connect HubSpot and Microsoft Teams in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize HubSpot and Microsoft Teams
Open Tiny Command, authorize HubSpot and Microsoft Teams once each. Both connections are available to every workflow on your account.
- 2TriggerPick a HubSpot trigger
Drop the HubSpot → New Company trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/hubspot.trigger-company-created - 3TransformAdd a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
- 4ActionAdd the Microsoft Teams action
Drop the Microsoft Teams → Create Teams Channel action below it. Map fields from the HubSpot payload into the Microsoft Teams inputs.
microsoft-teams.create-channel - 5PublishPublish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.
Questions about HubSpot + Microsoft Teams.
How long does it take to connect HubSpot and Microsoft Teams on Tiny Command?
Is the HubSpot ↔ Microsoft Teams integration real-time?
Can I filter or transform data between HubSpot and Microsoft Teams?
What HubSpot events can trigger a Microsoft Teams workflow?
Do I need a paid plan to use HubSpot with Microsoft Teams?
What if I want Microsoft Teams → HubSpot instead?
Other apps that pair well with HubSpot.
Wire HubSpot to Microsoft Teams in 2 minutes.
Free tier available. No credit card. No onboarding call.
