Microsoft Teams alerts

Send conversion and saved-contact alerts from Nimriz to Microsoft Teams through a Workflows webhook.

Availability: Microsoft Teams setup is available on Growth, Professional, and Enterprise plans.

Requirements

• A Growth plan or higher.
• A Microsoft 365 account that can create Workflows for the destination team, channel, or chat.
• A current Microsoft Workflows webhook URL.

Legacy Office 365 connectors are not used. Create the webhook with the Workflows app in Teams.

Create the Teams workflow

1. Open the destination channel or chat in Teams.
2. Select its options menu, then Workflows.
3. Choose a webhook alert template, or create a blank workflow with the trigger When a Teams webhook request is received.
4. Add the Teams action that posts a card to the intended channel or chat.
5. Save the workflow and copy its HTTP POST URL.

Microsoft's Workflows webhook guide shows both the template and blank-workflow paths.

Connect Teams in Nimriz

1. Go to Integrations›Destinations›Browse catalog and choose Microsoft Teams.
2. Paste the Workflow URL.
3. Keep the default Conversion and Contact saved triggers, or add other events.
4. On Review, confirm the disclosed Teams side effect, then select Save, test, and enable.
5. Nimriz saves the destination disabled, posts a real sample Adaptive Card through the workflow, and enables delivery only when that test succeeds.

If the provider test fails, the saved destination stays disabled. Correct the workflow, then select Retry test and enable.

Changing the workflow URL invalidates the previous test and requires a new successful test.

Alert behavior

Conversion and contact-save alerts are immediate. Click, scan, and card-view alerts are opt-in digests. Messages use Adaptive Card 1.4 and omit raw IP addresses, complete User-Agent strings, ip_hash, credentials, and provider response text.

Troubleshooting

• URL rejected: copy the URL from the saved Workflows trigger. Nimriz requires the approved Power Platform host, Workflows path, and signature value.
• Workflow does not run: confirm the flow is enabled and its connection owner can still post to the destination.
• Card does not appear: inspect the flow run history in Teams or Power Automate and confirm the post-card action targets the intended location.
• Revoke access: disable or delete the workflow, then disable or delete the Nimriz destination.