IT OPS

Zoom Rooms offline-device watcher to facilities ticket

Polls Zoom Rooms health on a schedule, and when a room or its controller goes offline, opens a ClickUp facilities ticket tagged with the building, floor, and room name.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerEvery 10 minutes (schedule)
  • ActionFetch Zoom Rooms device healthZoomZoom
  • LogicKeep only offline / stale-heartbeat rooms
  • LogicSkip rooms with an existing open ticketClickUpClickUp
  • OutputCreate ClickUp facilities task with locationClickUpClickUp

What it does

This workflow keeps a continuous eye on every Zoom Room in your fleet and turns an offline device into an actionable facilities ticket — with the physical location baked in so a technician knows exactly where to go.

When to use it

Run this when your IT or workplace team manages more than a handful of conference rooms and gets blindsided by "the room is dead" complaints minutes before a meeting. It catches outages before users do.

How it works

  1. 1A schedule fires every 10 minutes and pulls the live Zoom Rooms dashboard for device status.
  2. 2A filter keeps only rooms whose status is `offline` or whose controller has stopped checking in past the heartbeat threshold.
  3. 3For each flagged room it checks ClickUp for an existing open ticket on that room ID to prevent duplicates.
  4. 4New offline rooms get a ClickUp task created in the Facilities list, titled with the room name and pre-filled with building, floor, and last-seen timestamp from the room's location metadata.
  5. 5The task is assigned to the on-site tech for that building and tagged `zoom-room` and `hardware-offline`.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ZoomMeetings, recordings, transcripts.
  2. 2
    Connect ClickUpDocs + tasks + chats in one workspace.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.