Microsoft Teams

The Microsoft Teams integration sends OpsGrip notifications directly to your Teams channels using webhooks and Adaptive Cards.

What It Does

When connected, OpsGrip can post notifications to a Teams channel for events like: - New task assignments - Task status changes - On-call alerts and escalations - Inventory warranty alerts - OGI insights - Team member changes - Project milestones

Notifications arrive as Adaptive Cards — rich, formatted messages with actionable information right in Teams.

Setting Up the Integration

Step 1: Create a Webhook in Teams

  1. Open Microsoft Teams
  2. Go to the channel where you want OpsGrip notifications
  3. Click the three-dot menu (⋯) on the channel
  4. Select Connectors (or Workflows depending on your Teams version)
  5. Find Incoming Webhook and click Configure
  6. Name it "OpsGrip" and optionally upload the OpsGrip icon
  7. Click Create and copy the webhook URL

Step 2: Connect in OpsGrip

  1. Go to Settings → Integrations
  2. Find the Microsoft Teams card
  3. Click Connect
  4. Paste the webhook URL
  5. Test the connection
  6. Save

Step 3: Configure Notifications

Choose which OpsGrip events trigger Teams notifications. You probably don't want every single event going to Teams — pick the ones that matter most for real-time awareness.

High priority (always send to Teams): - On-call alerts and escalations - Critical inventory alerts - New team member joined

Medium priority (your choice): - Task assignments - Project status changes - OGI insights

Skip for Teams (keep in-app only): - Routine task updates - Minor status changes - System announcements

Tips

  • Create a dedicated #opsgrip channel in Teams to keep notifications organized
  • Test the webhook immediately after setup — send a test notification to confirm it's working
  • If your team gets notification fatigue, reduce the event types rather than disconnecting entirely
  • Webhook URLs are sensitive — treat them like passwords and don't share them publicly
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us