--- title: "Samsung SmartThings Integration" description: "Control your smart home from AI agents through Samsung SmartThings. Agents list devices, read live device status, send control commands, browse locations and rooms, and execute saved scenes." url: https://flowrunner.ai/integrations/smartthings date_modified: 2026-08-01T02:40:32-07:00 --- # Samsung SmartThings [Utilities & Personal](https://flowrunner.ai/integrations/category/utilities-personal) Control your smart home from AI agents through Samsung SmartThings. Agents list devices, read live device status, send control commands, browse locations and rooms, and execute saved scenes. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 9 actions · API key · available [Samsung SmartThings website](https://smartthings.com/) · [Platform Documentation](https://developer.smartthings.com/docs/api/public) · Capability data verified 2026-07-28 1. A monitoring schedule polls the office environment every few minutes 2. Get Device Status reads the server-room temperature sensor's current value and last-update timestamp 3. The reading is compared against the alert threshold and the trailing baseline 4. When the threshold trips, Send Device Command switches the auxiliary cooling on 5. The facilities channel gets the reading, the action taken, and the device's response 6. Before the workflow escalates to the lock-and-shutdown scene, a person confirms, because Execute Scene on "Close Building" locks physical doors that people may still be behind 7. On confirmation, Execute Scene runs the saved shutdown sequence in one call ## What This Integration Enables SmartThings is where the physical environment becomes queryable and commandable: switches, thermostats, locks, and sensors, grouped into locations and rooms, with saved scenes that bundle actions. This connector hands that surface to FlowRunner agents, and the interesting work happens where device state meets business context. An agent that knows the calendar, the ticket queue, and the temperature sensor can do what no single-platform automation can: respond to the whole situation. - Read live device status and branch flows on switch state, temperature, and sensor readings - Send commands: switch devices, dim lights, set colors, adjust thermostats, lock doors - Execute saved scenes so multi-device sequences run as one workflow step - Inventory devices, locations, and rooms across an account - Discover each device's capabilities and commands before controlling it Commands here move things in physical space, including locks that stand between people and rooms. That is why FlowRunner's [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) gate sits on the commands with physical consequences. ### Without FlowRunner **Device state is checked by walking over**: Whether the door locked or the temperature spiked is known only when someone looks **Smart devices and business systems ignore each other**: The calendar knows the office is closed; the thermostat and locks do not **Responses to alerts are manual sequences**: An after-hours alarm means someone drives in to flip switches and check doors ### With FlowRunner **Live state feeds workflow decisions**: Sensor readings, switch states, and lock status branch flows the moment they change **External events drive the physical space**: Calendar events, alerts, and business hours trigger scenes and device commands **Escalations act with human sign-off**: Routine adjustments run autonomously; door locks and shutdowns wait for a person ## Use Case Scenarios ### The environment alert that acts before it pages The agent polls Get Device Status on the server-room temperature sensor. A crossed threshold first triggers Send Device Command to start auxiliary cooling, then posts the reading and the action to [Slack](https://flowrunner.ai/integrations/slack). If the next poll shows the temperature still climbing, the escalation goes to a human with the trend attached. Most incidents end at the first step, handled before anyone was interrupted. ### The building that follows the calendar A [Google Calendar](https://flowrunner.ai/integrations/google-calendar) event marks the office closed for a holiday. The agent runs Execute Scene on the closing sequence, verifies the result with Get Device Status on the locks and thermostat, and logs the run to [Google Sheets](https://flowrunner.ai/integrations/google-sheets). On the first workday morning, the reverse scene warms the space before the earliest badge-in. Nobody remembers the thermostat again, which is the point. ### The device inventory that stays true Quarterly, the agent walks List Locations, List Rooms, and List Devices, capturing each device's capabilities and room assignment into an asset sheet. Get Device fills in manufacturer and type detail. Devices that stopped reporting, their status timestamps gone stale, surface as a maintenance list for facilities. The smart-device estate becomes an audited inventory instead of a drawer of forgotten installs. ## Human-in-Loop Highlight Send Device Command with the lock capability is the line this connector draws: commanding a door lock changes who can physically enter or exit a space, and a wrong lock command is not a data error, it is a person standing outside at night or sealed in a server room during an incident. Scenes concentrate the same risk, one Execute Scene call on a "Good Night" or "Close Building" sequence locks every door and kills every light it was configured with. So the workflow tiers its autonomy by consequence. Lights, thermostats, and cooling run on the agent's judgment, because the worst case is comfort. Lock commands and shutdown scenes present their intent first: which devices, current state from Get Device Status, and what will change. A person who can account for who is in the building answers, and the agent executes and verifies. The same command surface, two very different levels of trust, assigned by what the command touches. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 9 actions ### Devices 4 - **List Devices** Lists all devices the token can access, filterable by location or capability such as switch, temperatureMeasurement, or motionSensor. Returns each device's ID, label, capabilities, location, and room, with pagination. - **Get Device** Retrieves a device's full details: label, manufacturer, type, components, and every capability each component exposes. The discovery step before sending any command. - **Get Device Status** Retrieves a device's live status grouped by component and capability, with current attribute values and last-update timestamps. The read that turns physical state into workflow branches. - **Send Device Command** Sends a control command: capability, command, and arguments, targeting the main component by default. Switches on, thermostat setpoints, light colors, door locks. The action this page's tiered gate governs. ### Locations and Rooms 3 - **List Locations** Lists the account's locations with ID and name, the top of the physical hierarchy. - **Get Location** Retrieves one location's details: name, country, time zone, coordinates, and temperature scale. The context read behind schedule-aware flows. - **List Rooms** Lists the rooms within a location with ID and name, the grouping that maps devices to physical space. ### Scenes 2 - **List Scenes** Lists the saved scenes, optionally filtered by location, with the IDs Execute Scene needs. - **Execute Scene** Runs a scene by ID, firing all its saved device actions at once and returning the execution status. Routine scenes run autonomously; lock-and-shutdown sequences run after human confirmation. ## Frequently Asked Questions ### What can FlowRunner do with Samsung SmartThings? FlowRunner agents can run List Devices, Get Device, and Get Device Status in Samsung SmartThings, plus 6 more actions. ### Does connecting Samsung SmartThings to FlowRunner require OAuth? No. Samsung SmartThings connects to FlowRunner with an API key, no OAuth flow required. ### Can Samsung SmartThings trigger a FlowRunner workflow automatically? Samsung SmartThings doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Samsung SmartThings?** This integration exposes Samsung SmartThings to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/smartthings. Site index: https://flowrunner.ai/llms.txt