The Keys
Utilities & PersonalConnect AI agents to The Keys, a French smart lock system. Agents lock and unlock doors, create an accessory share, and read lock status, existing shares, and access logs. The connector exposes no share expiry and no revoke.
What This Integration Enables
The Keys is a French smart lock system, and it is the rare connector where the agent's write does not stay inside software. Unlocking a door is a physical event at a physical address, and a digital key handed out by a flow opens that door for whoever holds it. FlowRunner treats that asymmetry as the design point rather than an afterthought. Agents read the account side freely: List Locks returns every lock with its state, battery level, paired accessories and recent activity, Get Access Logs returns the open and close history for one lock with the user who performed each action, Get Accessory resolves a gateway, keypad or remote by ID, and List Lock Shares returns the user shares, accessory shares and pending share requests on a lock. Those reads cost nothing and can run on any schedule.
The write side is deliberately narrow. Create Accessory Share provisions a digital key for an accessory and returns the code that signs gateway commands. Unlock Door, Lock Door and Get Lock Status are sent to the lock's gateway over HTTP, and the gateway relays them to the lock over Bluetooth, so the gateway host must be reachable from the internet for any of the three to work. Locks that only answer on a private LAN can still be read through the cloud API but cannot be driven remotely. The connector does not configure or administer the gateway itself; it reads gateway details and sends commands through it. There are no triggers on this connector, because The Keys exposes no event subscription, so flows start from a schedule, a booking in another system, or a request that arrives somewhere else.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Contractor Visit Window
A maintenance job is booked for a site at ten on Thursday. The agent runs List Locks to resolve the correct door, runs Get Accessory to confirm the gateway that serves it was seen recently and is still reachable, and runs List Lock Shares to show which digital keys are already live on that lock. It assembles the job, the door, the window, and the existing key list into one message for the facilities owner. Nothing is minted until a person names the door. The provisioning work that used to mean a phone call and a drive becomes a single approval.
After Hours Delivery
A delivery arrives outside staffed hours and the driver reaches a request channel. The agent runs Get Lock Status through the gateway to read the live door position, battery voltage and signal strength, confirms the lock is closed and the gateway is answering, and only then sends Unlock Door. After a set interval it sends Lock Door and reads Get Access Logs to record who opened the door and when. The entry is a logged event with a result status rather than a story reconstructed later.
Access Review
On a schedule, the agent walks every lock with List Locks, pulls List Lock Shares for each, and cross checks the accessory and user shares against the roster of people and contractors who are supposed to hold access. It reads Get Access Logs to show which of those shares have actually been used. Revocation is not something this connector can do, so the agent does not pretend otherwise: it hands the facilities owner a named list of stale shares to remove in The Keys app, with the last use date beside each one.
Human-in-Loop Highlight
Create Accessory Share is where the flow stops. The action mints a digital key that operates a physical lock, and it returns the code used to sign gateway commands for that lock. It takes a lock ID, an accessory ID, a name and an optional description. It takes no expiry, and this connector exposes no action that revokes a share once created. That combination is the whole argument for a human gate: the agent can create access to a real door in one call, and it cannot take that access back. So it does not call the action on its own. It assembles the job, the resolved lock from List Locks, the gateway confirmed reachable by Get Accessory, and the existing key list from List Lock Shares, then routes to the facilities owner in Slack: "Provision a digital key on the Rear Loading Door for the Thursday HVAC visit? Three accessory shares already exist on this lock, two of them unused since March. This share has no expiry and must be removed in the app. Approve, pick a different door, or hold?" A person names the door. The agent then runs Create Accessory Share and records the returned share ID against the job so the review flow can find it later.
Agent Capabilities
8 actionsLocks
1- List Locks Retrieves every smart lock registered to the account, including each lock's name, identifier, state, battery level, paired accessories (gateways, keypads, remotes) and recent activity logs. Use this to discover lock IDs and gateway accessories needed by the other operations.
Access Logs
1- Get Access Logs Returns the recent access and event history for a single lock, such as open and close actions with the user who performed them, timestamps and result status. The log is read from the account record for the specified lock ID.
Accessories
1- Get Accessory Retrieves the details of a single accessory such as a gateway, keypad or remote by its numeric ID, including its type, firmware version and connectivity info (for gateways this includes the last-seen time and local IP address). Use it to locate a gateway's address before sending lock or unlock commands.
Sharing
2- List Lock Shares Lists all access shares for a lock, grouped into user shares (people invited by phone number), accessory shares (digital keys used by gateways or remotes) and pending share requests. Each accessory share includes the code used to authenticate gateway commands for that lock.
- Create Accessory Share Creates an accessory (digital key) share that grants an accessory, such as a gateway, permission to operate a lock and returns the share ID and the code used to sign gateway commands. Use this to provision remote access for a lock through its gateway. Routed for sign-off, because the share carries no expiry and cannot be revoked through this connector.
Gateway Control
3- Unlock Door Sends an open command to a lock through its gateway. The gateway relays the command to the lock over Bluetooth and returns a status. The gateway host must be reachable from FlowRunner (a public IP or port forward), and the code must be the gateway or accessory share code authorized for the lock.
- Lock Door Sends a close command to a lock through its gateway. The gateway relays the command to the lock over Bluetooth and returns a status. The gateway host must be reachable from FlowRunner (a public IP or port forward), and the code must be the gateway or accessory share code authorized for the lock.
- Get Lock Status Queries a lock's live status through its gateway, returning the door position, firmware version, Bluetooth signal strength (RSSI) and battery voltage in millivolts. This performs a Bluetooth query and is slower than reading cached values. The gateway host must be reachable from FlowRunner.
Frequently Asked Questions
What can FlowRunner do with The Keys?
FlowRunner agents can run List Locks, Get Access Logs, and Get Accessory in The Keys, plus 5 more actions.
Does connecting The Keys to FlowRunner require OAuth?
The Keys uses a custom authentication method to connect to FlowRunner.
Can The Keys trigger a FlowRunner workflow automatically?
The Keys doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with The Keys
$100 in credits. No card required. Connect in minutes.