Your team should hear about a qualified outcome while it is still useful, not after someone remembers to open a dashboard. Nimriz can now send conversion and saved-contact alerts directly to Slack and Microsoft Teams. Each destination uses the provider's current message format, requires a real provider test before enablement, and keeps delivery work outside the redirect path.
Alert on outcomes, not every click
A channel becomes noisy quickly when every click creates a new message. The Slack and Microsoft Teams connectors therefore default to conversions and saved contacts. These are the moments that usually justify an interruption: a lead submitted details, a customer completed an outcome, or a campaign produced a result that needs follow-up.
Higher-volume click, QR scan, and card-view activity is available as an opt-in digest. Digests group activity into bounded summaries with an overflow count so teams can monitor campaign movement without turning a working channel into an event log.
Choose Slack or Microsoft Teams
Slack delivery uses a customer-owned incoming webhook on the standard Slack webhook host. Nimriz formats each alert with Block Kit so the message is readable without custom payload work.
Microsoft Teams delivery uses a Power Automate Workflows webhook and Adaptive Card 1.4. This follows the current Workflows path instead of relying on retired Office 365 connectors. Any successful 2xx response, including an asynchronous 202 response, is accepted.
Both destinations are available on Growth, Professional, and Enterprise plans.
Test the real channel before enabling
Saving a webhook is not enough to prove that a team will receive an alert. Nimriz creates the destination in a disabled state, sends a real sample message through the provider, and enables delivery only after the current webhook succeeds. Changing the webhook invalidates that readiness until another provider test passes.
The destination health view then shows recent attempts, success status, safe error information, and replay controls. Provider response bodies and credentials are not stored in delivery history.
Keep alert payloads privacy-aware
Team alerts contain the campaign and outcome context needed for action. They omit raw IP addresses, complete User-Agent strings, visitor hashes, credentials, and provider response text. Filters let you narrow a destination to the events and campaign context that belong in that channel.
Start with one focused channel
Create a Slack incoming webhook or Microsoft Teams Workflow, add it under integration destinations, and send the provider test. Keep the default outcome alerts first. Add activity digests only when a team has a clear operational reason to monitor higher-volume traffic.
For exact setup steps, use the Slack guide or Microsoft Teams guide.