Prefer env vars at build time (GOOGLE_SITE_VERIFICATION, BING_SITE_VERIFICATION, YANDEX_VERIFICATION, BAIDU_SITE_VERIFICATION, NAVER_SITE_VERIFICATION). Optionally paste meta tags below this comment for a one-off deploy. DNS TXT alternatives: see docs/indexing-playbook.md --> Microsoft Teams integration | Robomap Docs
Robomap Docs
Open app

Robomap Docs

Microsoft Teams integration

Post Robomap device, agriculture, and support-chat alerts to a Microsoft Teams channel via webhook.

What it does

Robomap posts device alerts, agriculture threshold alerts, and support-chat notifications to a Microsoft Teams channel using an Incoming Webhook or Workflows URL that accepts Adaptive Card JSON.

Get a Teams webhook URL

  1. In Microsoft Teams, open the target channel.
  2. Choose Connectors / Workflows and add an Incoming Webhook (or a Workflow that accepts Adaptive Card JSON).
  3. Copy the webhook URL.

See Microsoft’s guide: Add an Incoming Webhook.

Connect in Robomap

  1. Go to Account → Integrations → Microsoft Teams.
  2. Paste the webhook URL (optional channel name) and click Connect. Robomap sends a confirmation Adaptive Card, then stores the URL encrypted.
  3. Enable toggles for device alerts, agriculture thresholds, and/or support chat.
  4. Click Send test message to verify delivery.

Alert routing

When toggles are enabled:

  • Device incidences → Teams Adaptive Card
  • Agriculture threshold breaches (deduped about 15 minutes) → Teams
  • Support chat messages / replies → Teams

Troubleshooting

  • Connect succeeds but no cards — confirm Workflows still accept the Adaptive Card payload; regenerate the webhook if the connector was removed.
  • Only some alert types arrive — check each toggle on the integration settings page.
  • Too many agriculture posts — thresholds are evaluated on the farm dashboard; widen limits or rely on the built-in dedupe window.