Send Nimriz conversion alerts to Microsoft Teams

Deliver conversion and saved-contact alerts through a Teams Workflows webhook, with readable Adaptive Cards and bounded activity digests.

Read setup docs All integrations

Conversions
Contact saves
Optional click and scan digests

Event flow

Async delivery

ConversionContact savedActivity digest

Nimrizredact · filter · map

Microsoft Teams

Bot traffic is excluded by default. Delivery runs off the redirect path with automatic retries.

Why Microsoft Teams with Nimriz

Bring campaign outcomes into Microsoft Teams without relying on retired Office 365 connectors. Nimriz uses a current Workflows endpoint, formats Adaptive Cards, and validates the real flow before enabling delivery.

Alerts for outcomes that matter

Send conversions and saved-contact activity to Microsoft Teams by default, so the channel highlights customer outcomes instead of becoming another click counter.

Digests for busy campaigns

Clicks, QR scans, and card views are opt-in and grouped into bounded digests with an overflow count, keeping higher-volume activity readable.

Tested before live delivery

Nimriz posts a real sample to Microsoft Teams and enables the destination only after the current webhook succeeds.

Under the hood

What Nimriz sends, and how.

Post Adaptive Card 1.4 alerts through a customer-owned Microsoft Workflows endpoint.

Plan note

Microsoft Teams alerts are available on Growth, Professional, and Enterprise plans.

Delivery: Microsoft Workflows webhook with Adaptive Card 1.4
Default alerts: Conversions and saved contacts
Volume control: Bounded opt-in digests for clicks, scans, and card views
Validation: Approved Workflows host, path, signature, and real test card

Guided setup

Connected in four reviewed steps.

01
Create a Workflow
Use the Teams Workflows app to create a webhook-triggered card flow.
02
Choose alert events
Keep outcome-focused defaults or opt into activity digests.
03
Send a real test
Confirm the sample Adaptive Card reaches the selected channel or chat.
04
Enable delivery
Nimriz enables the destination after the current workflow succeeds.

Use cases

Sales outcome alerts
Contact-save notifications
Campaign activity digests

Privacy notes

Alerts omit raw IP, complete User-Agent strings, visitor hashes, credentials, and provider response text.

Nimriz never forwards raw IP addresses or complete User-Agent strings in integration payloads. Strict privacy mode omits visitor hashes and selected granular fields such as city.

Analytics privacy docs

Pair Microsoft Teams with the rest of the catalog.

Live

Generic HTTP

Deliver link, QR, card, and conversion events to any HTTPS endpoint with custom methods, custom headers, and fully templated JSON payloads.

Live

Zapier

Trigger Zaps instantly from link, QR, and click activity, and create or update branded links from any of the apps your team already automates with.

Live

Make

Feed link, click, and QR scan events into Make scenarios over instant webhooks, and manage branded links from modules inside the visual builder.

Live

n8n

Use the Nimriz community node to trigger self-hosted or cloud n8n workflows from link activity, and manage branded links with a dedicated operations node.

Live

Webhooks

Receive signed, replayable lifecycle events from Nimriz in your own backend, with HMAC signatures, retry schedules, and a delivery history you can operate.