Get a real-time alert in your Teams channel every time a high-intent visitor lands on your site, an account matches your ICP, or a workflow you built pushes a contact to your team.
This guide walks you through connecting a Teams channel, customizing what gets sent there, and using it as a destination in your workflows.
What you'll need: edit access to a Microsoft Teams channel, and an admin or owner role on your Knock2 account. The whole setup takes about three minutes.
How it works
Knock2 posts notifications to your Teams channel by sending data to a Workflow URL that Microsoft Teams gives you. There's no app to install in Teams, no IT review, and no admin consent — you create a small workflow inside your Teams channel that listens for incoming messages from Knock2, and Teams hands you a unique URL to paste into Knock2.
Once it's connected, you can use Teams the same way you use Slack today:
Get standard notifications every time a qualified contact or account is identified by Knock2.
Use Teams as a workflow output when you build automations in the Workflow Builder.
Connect multiple channels — for example, a high-intent channel for your sales team and a broader channel for your marketing team — each with its own filters.
Step 1: Create the Workflow in Microsoft Teams
Do this once per channel you want to receive notifications in.
Open the Teams channel you want notifications to land in.
Click the ⋯ (More options) button next to the channel name.
Choose Workflows.
💡 If you don't see Workflows, your tenant admin may need to enable Power Automate for your team. Most Microsoft 365 plans include it by default.
Search for and select the template "Post to a channel when a webhook request is received."
Microsoft Teams will walk you through a short setup wizard:
Confirm the team and channel where messages should post.
Sign in if Teams asks (this is just confirming your identity, not granting Knock2 access).
When the wizard finishes, Teams gives you a long HTTPS URL that starts with
https://prod-XX.region.logic.azure.com/.... Copy this URL. You'll paste it into Knock2 in the next step.
⚠️ Treat this URL like a password. Anyone who has it can post messages to your channel. Don't share it in screenshots, email, or other channels.
Step 2: Connect Microsoft Teams in Knock2
In the Knock2 dashboard, go to Settings → Microsoft Teams.
Click Connect Microsoft Teams.
In the modal:
Enter a Channel name (e.g.
#sales-alerts). This is just a label — it doesn't need to match the exact name in Teams. It's used in your Knock2 dashboard so you can recognize this connection later.Paste the Workflow URL you copied from Teams.
Click Send test message. Knock2 will post a small confirmation card to your Teams channel within a couple of seconds. If it lands, you're connected.
💡 If the test fails, you'll see an inline error. You can still save the connection and try again later — Workflows webhooks occasionally return transient errors during initial setup.
Click Save connection.
You'll be taken to the connection detail page, where you can configure exactly what this channel receives.
Step 3: Choose what gets sent to this channel
On the connection detail page, you control three things:
Active toggle
Found in the top right. Use this to pause or resume notifications for this channel without deleting the connection.
Notification rules
Two switches:
Send contact notifications — fires when an individual visitor is identified (e.g., "Sarah Chen, VP Marketing at Acme just visited your pricing page").
Send account notifications — fires when a target company is identified, even if no individual person is matched yet (e.g., "Acme Corp had three sessions today").
Both default to on when you first connect a channel.
Filters
Two dropdowns:
Contact filter set — only send contact notifications that match this saved filter. For example, "Lead score > 80" or "Title contains VP, Director, or CMO."
Account filter set — only send account notifications that match this saved filter.
If you leave them as All contacts (no filter) and All accounts (no filter), everything Knock2 identifies will land in this channel.
These filter sets are the same ones you use elsewhere in Knock2 — you can create or edit them in the Contacts and Accounts pages.
Click Save changes when you're done.
Use Teams as a workflow output
Beyond standard notifications, you can route specific workflow outputs to a Teams channel.
Go to Workflows and open or create a workflow.
Drag a new Microsoft Teams node from the Outputs section in the left sidebar onto the canvas.
Connect it downstream of any filter, condition, or enrichment node.
In the right panel, pick the channel you want this workflow to post to from the dropdown.
Each prospect that flows through the workflow gets posted to the chosen Teams channel as an Adaptive Card.
💡 The "Don't repeat leads" toggle (on by default) prevents the same lead from being posted twice within 60 minutes, even across multiple workflow runs.
Some patterns customers find useful:
Hot leads channel: trigger on
lead_score > 80→ post to#sales-alerts.Enterprise pipeline: filter on
employee_count > 1000andindustry in (Finance, Healthcare)→ post to#enterprise-teamand add the company to HubSpot.Marketing attribution: filter on
utm_source = paid_search→ post to#paid-attributionfor the marketing team to see.
What the notification looks like
Every notification posts as an Adaptive Card with:
Header: contact name and title (or company name for account notifications).
Subhead: company name (linked to their website) and industry.
Photo or logo when available, with a Google favicon as a fallback.
Description of the company (truncated to 200 characters).
Facts grid with employees, revenue, funding, location, last page visited, CRM deal stage, deal owner, and account owner — populated based on what Knock2 has on file.
Website and LinkedIn quick links.
"Open Knock2" button that deep-links you straight to the contact or account in your dashboard.
The notification is posted by Flow Bot (Microsoft's automation account) — that's normal for any workflow-based webhook in Teams.
Connecting multiple channels
You can connect as many Teams channels as you'd like. Each connection is independent, so you can:
Send hot leads to one channel and broader visitor activity to another.
Connect both a sales channel and a marketing channel with completely different filter sets.
Use one channel as a workflow output (e.g., post-enrichment alerts) and another as a standard notification channel (e.g., daily visitor stream).
To add another channel, repeat Steps 1 and 2 with a different channel and Workflow URL. Each connection appears as its own row in Settings → Microsoft Teams.
Managing your connections
From Settings → Microsoft Teams, click any row to open its detail page, where you can:
Pause notifications with the active toggle.
Edit notification rules and filters.
Send a test message any time to confirm the channel is still live.
Rotate the Workflow URL if you ever need to replace it (typically only when the underlying workflow in Teams gets deleted and recreated). Click Rotate Workflow URL, paste the new URL, and save.
Disconnect the channel entirely — choose ⋯ → Disconnect from the row in the list. This stops all notifications and workflow outputs targeting that channel.
Slack and Teams together
If you're already using the Slack integration, you don't need to choose. Both run independently — connect Teams alongside Slack and notifications fire to both. Each has its own filter sets, its own dedup window, and its own settings, so you can fine-tune them separately.
Troubleshooting
The test message didn't appear in my Teams channel.
A few common causes:
The Workflow URL was copied incorrectly. Make sure you copied the entire URL, including the
?sig=...portion at the end.The Workflow in Teams got disabled or deleted. Open Teams → channel → ⋯ → Workflows and confirm your workflow is still listed and turned on. If not, recreate it and use the new URL via Rotate Workflow URL in Knock2.
The Microsoft Teams service had a transient error. Wait a minute and click Send test message again from the connection detail page.
I'm not seeing notifications even though the test message worked.
Check the Active toggle is on.
Check that Send contact notifications and/or Send account notifications are enabled.
If you have a filter set attached, make sure your visitors are actually matching it. Open the Contacts or Accounts page and apply the same filter — if no rows appear, the filter is too restrictive.
Notifications are deduplicated per channel for 60 minutes — a returning visitor won't re-trigger if they were already posted within that window.
I want to change the filter for an existing connection.
Go to Settings → Microsoft Teams, click the connection, change the Contact filter set or Account filter set dropdown, and click Save changes. The new filter takes effect immediately for the next visitor.
Can I delete the Workflow URL from Knock2 without disconnecting?
The Workflow URL is what powers the connection — without it, notifications can't be posted. If you want to pause without losing your settings, use the Active toggle instead. To replace the URL with a new one, use Rotate Workflow URL.
Where can I see what was sent?
The same notifications also appear in your Knock2 contact and account history. We log each successful send internally for support purposes, but the channel itself is your source of truth — anything that lands there is what your team saw.
Permissions
Anyone in your Knock2 organization with admin or owner access can connect, edit, or disconnect Teams channels.
Reps can view the channels their organization has connected but can't add or remove them.
The Workflow URL is stored securely on Knock2's servers and is never displayed back in the dashboard once saved.