Skip to main content

💼 Teams

Chipper can send real-time alerts to your Microsoft Teams channels using webhooks.

🔗 Webhook Setup​

Teams integration requires setting up a webhook for each channel you want Chipper to notify. You can set a default webhook on the integration page and then choose specific webhooks in each alert configuration.

Step 1: Create a Teams Webhook​

Using Power Automate Workflows (Recommended)

  1. In Microsoft Teams, click on Workflows in the left sidebar
  2. Click Send webhook alerts to a channel to make a new workflow
  3. For the trigger, search for and select "When a Teams webhook request is received"
  4. Choose a name for your flow (i.e. Chipper Integration)
  5. Specify the channel that you want messages to be sent to. If you want alerts to be sent to different channels, then you will need an integration for each channel.
  6. Copy the HTTP POST URL from the trigger - this is your webhook URL

Step 2: Configure in Chipper​

Option A: Set Default Integration (Recommended)

  1. Go to Settings > Integrations in Chipper
  2. Click Add on the Teams Card
  3. Paste your webhook URL in the input box
  4. Save the integration

📝 Managing Multiple Channels​

You can create multiple Teams integrations for different channels:

  1. Critical Alerts: High-priority channel for urgent issues
  2. General Monitoring: Regular updates and status changes
  3. Maintenance: Scheduled maintenance notifications

Each integration can have its own webhook URL pointing to different Teams channels.

🎨 Message Format​

Chipper sends alert messages in this format:

🚨 Chipper Alert
Alert CHIPPER-123: High temperature detected on Incubator A. Current temperature: 45°C, threshold: 37°C.

Messages include:

  • Alert ID: Unique identifier (e.g., CHIPPER-123)
  • Equipment: Which device triggered the alert
  • Condition: What threshold was exceeded
  • Current Values: Real-time measurements

🔐 Security Notes​

  • Webhook URLs are sensitive: Treat them like passwords - anyone with the URL can send messages
  • HTTPS Only: All webhook URLs use HTTPS encryption
  • No Authentication: The URL itself serves as the authentication token
  • Rotation: If a webhook URL is compromised, delete the old workflow and create a new one