en/ae
Product guideConnect Office Pod Occupancy Sensors to Slack: Setup Guide
Connecting an office pod occupancy sensor to Slack means a battery-powered sensor, a free automation platform, and a Slack channel — no dedicated booking software and no rewiring inside the pod itself.
- Zapier or Make sits between the sensor's own app and Slack, so you can connect office pod occupancy sensors to Slack without new hardware.
- Set the trigger to fire on a status change, not a raw motion event, or the channel floods with repeat alerts.
- A dedicated channel like #pod-status keeps occupancy pings separate from general team chatter.
- Flipping the trigger to 'vacant' turns the same workflow into a free-pod finder instead of a busy-pod warning.
- Free-tier automation plans often check on a delay rather than instantly, so alerts can lag behind the actual state change.
Why this matters
People waste time walking the floor to see which pod is free. An occupancy sensor solves the sensing problem; routing that data into Slack solves the visibility problem, because the team already lives in Slack and won't open a separate app to check a pod's status.
The sensor and the pod don't need to know about each other. Any occupancy sensor with its own manufacturer app or API can sit inside a standalone enclosure like a Quell Office Pod Solo the same way it would sit in any other enclosed room — the automation layer runs entirely outside the pod's own hardware.
This guide covers the standard setup — one sensor, one pod, one Slack channel — plus the reverse workflow for teams who want to know when a pod frees up rather than when it's taken.
Before you start
- Admin access to the Slack workspace you're posting to, so you can authorise a new app or create an incoming webhook.
- An account with an automation platform (Zapier or Make) already linked to the occupancy sensor's own manufacturer app or API — the sensor has to expose its status somewhere before an automation tool can read it.
- The gotcha: many battery-powered occupancy sensors report a fresh "motion detected" event on every re-arm cycle rather than a single continuous "occupied" state. If your trigger fires on every motion event instead of on a status change, Slack repeats the same alert every few minutes while the pod is in use. Set the trigger to "new status" or "state change" before you build anything else.
Set up your occupancy sensor as the trigger
- Open the sensor manufacturer's app and confirm the sensor is already reporting occupied/vacant status correctly — test this before touching Slack at all.
- In your automation platform, click Create Zap (Zapier) or start a new scenario (Make), then search for the sensor's connected app under the Trigger step.
- Choose the event that matches a status change — look for wording like "New Status" or "Sensor State Updated" rather than "Motion Detected."
- Click Continue, then run Test trigger to confirm the platform pulls back a real reading showing whether the pod is currently occupied or vacant.
Expected result: the test step returns sample data with a clear occupied/vacant value, not a stream of raw motion pings.
Configure the Slack alert
- Click the + icon to add an action step and search for Slack.
- Choose Send Channel Message as the action event.
- Connect your Slack workspace when prompted and approve the requested permissions.
- In the Channel field, select or create a channel such as #pod-status.
- In the Message Text field, insert the sensor's pod-name and status fields as variables so the message reads something close to "Study Pod is now occupied."
- Click Continue, run a test send, check the message lands correctly, then click Publish.
Expected result: a message appears in the chosen Slack channel that matches the exact status pulled from the sensor in the trigger test.
Alert when a pod frees up instead of when it's taken
Some teams don't need a warning that a pod is busy — they need to know the second one opens up. That's the same workflow with one field changed.
- Duplicate the published Zap or scenario rather than editing it live.
- In the trigger step, change the status filter from "occupied" to "vacant."
- Point the Slack action at a separate channel, such as #pod-available, so the two alert types don't mix in the same feed.
- Test and publish exactly as before.
This version works well for smaller teams sharing a couple of pods, where a 2-person meeting booth turns over multiple times a day and people would rather get pinged than keep checking.
“Route the occupied alert to an admin-only channel and the vacant alert to the whole team — that split turns Slack into an availability board instead of a monitoring feed.”
Zapier vs Make for pod occupancy alerts
Both platforms do the same core job — read a sensor status and post to Slack — but they fit different setups.
| Platform | Trigger style | Best for | Verdict |
|---|---|---|---|
| Zapier | Simple one-step trigger to one action | A single pod with one sensor and one Slack channel | Use for a straightforward, single-pod setup |
| Make | Visual multi-step scenarios with branching logic | Several sensors across multiple pods feeding different channels | Use if you're scaling past one pod |
| IFTTT | Basic applet-style trigger | Personal, one-off alerts outside a team workflow | Skip for team-wide Slack alerting |
A single-pod team is better off on the simpler Zapier setup; a multi-pod floor is better served by Make's branching scenarios that can route different sensors to different channels from one build.
Troubleshooting the workflow
- Slack posts the same alert repeatedly. The trigger is set to a raw motion event instead of a status change. Go back into the trigger step and switch to the "new status" or equivalent event type.
- No alert appears at all. The automation account has lost its authorisation with the sensor's app — this happens after password resets or token expiry on the sensor manufacturer's side. Reconnect the account in the trigger step and rerun the test.
- Alerts land in the wrong channel. Usually caused by a Slack channel being renamed or archived after the Zap was published. Reselect the channel in the Slack action step and republish.
- Noticeable delay between the motion and the Slack message. Free-tier automation plans typically check for updates on a schedule rather than instantly. Check the platform's task history to see the actual gap between the sensor event and the Slack post.
- One channel gets noisy with multiple pods reporting into it. Split pods across separate channels, or add the pod name as a clear prefix in the message text so people can scan quickly.
Customize your workflow
Once the basic sensor-to-Slack alert is running, the same pattern extends further. If a pod already tracks door-open events through a smart lock system, you can add a second trigger that posts to the same channel when a pod is unlocked but not yet showing as occupied — useful for spotting pods that get opened and left idle.
Teams running more than a handful of pods usually outgrow a single Zap per pod fairly quickly. At that point it's worth looking at how the pods themselves are set up on the network before adding more automations — see the guide on networking multiple office pods for large teams for how that structure supports scaling the Slack workflow across a whole floor.
FAQ
What's the best way to connect office pod occupancy sensors to Slack?
An automation platform like Zapier or Make sits between the sensor's manufacturer app and Slack, reading the sensor status and posting a message through a Slack action step. No custom code or dedicated booking software is required.
Is Zapier or Make better for pod occupancy alerts?
Zapier suits a single pod with one sensor and one Slack channel. Make is built for branching scenarios, which matters once several sensors need to route to different channels from one build.
Can I get a Slack alert when a meeting booth becomes free instead of when it's taken?
Yes — duplicate the occupied-alert automation and change the trigger filter from occupied to vacant, then point it at a separate Slack channel so the two alert types don't mix.
Do I need facilities management software to get Slack alerts from a pod sensor?
No. An automation platform bridges the sensor's app directly to Slack without an extra booking or facilities licence sitting in between.
Why does my Slack channel get flooded with duplicate pod alerts?
The trigger is usually set to a raw motion event instead of a status change. Switching the trigger to fire only on a new status stops the repeat pings.
How much does it cost to connect an occupancy sensor to Slack?
Cost depends on the sensor's own subscription tier and the automation platform's plan, both of which vary by provider — check current plan details directly with each one before committing.
One last thing
The workflow breaks down faster from channel sprawl than from bad automation logic — teams that give every pod its own Slack channel end up with more unread notifications than the wall-mounted status light they were trying to replace. Keep occupied and vacant alerts in exactly two channels, no matter how many pods are on the floor, and let the message text carry the pod name.
