IT OPS

Real-time noncompliant-device webhook to Teams

Receives a webhook from your MDM the moment a laptop checks in as out-of-date, enriches it with owner data.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMDM compliance webhook receivedHTTP webhook
  • LogicFilter to truly noncompliant check-ins
  • ActionEnrich device with owner dataPostgreSQLPostgres
  • ActionFormat Teams card with fix link
  • OutputPost card to IT Teams channelMicrosoft Teams

What it does

Listens for device-status webhooks from your MDM or endpoint agent. When a laptop reports a noncompliant OS patch level, the workflow looks up the owner and posts a structured card to a Microsoft Teams channel showing the device, owner, OS version, and a self-service update link the owner can be pointed to immediately.

When to use it

Use this when you want noncompliance surfaced the instant it happens rather than batched overnight. Best for security-sensitive fleets where a freshly out-of-date endpoint should be visible to the IT channel in real time.

How it works

  1. 1An incoming HTTP webhook from the MDM triggers the workflow with the device's compliance payload.
  2. 2A logic step checks whether the reported patch level is actually below the required baseline, ignoring compliant check-ins.
  3. 3A Postgres lookup enriches the device ID with owner name, email, and Slack handle.
  4. 4An action formats a Teams card with device details and the self-service fix URL.
  5. 5The output step posts the card to the IT operations Teams channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  3. 3
    Connect Microsoft TeamsChannels, chats, files.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.