Integrations
Plays well with what you’ve already got. Works with the kit already on site.
Nobody buys everything from one vendor. Here’s what Bolt connects to: cameras, readers, intercoms and the plumbing behind them. Each one says whether it works today or is still on the list. Cameras, readers, intercoms and plumbing: the kit you’ll find when you walk in. Each one says whether it works today or is still on the list, so nothing gets quoted that isn’t ready.
The list.
Available means it works today. Microsoft 365, Google Workspace, Slack, Zapier, Home Assistant and n8n are planned: listed so you know where we’re heading, not ready to buy.
Showing all 20: 8 available, 12 early access or planned
ONVIF
AvailableVideo
Profile S and T cameras connect to Bolt.Vision through the local recorder.
Good for: Axis, Hanwha, Bosch and the rest: if it speaks ONVIF, Bolt.Vision can read it.
Axis
AvailableVideo
Axis cameras connect over ONVIF Profile S and T.
Good for: New builds that want a sharp picture in low light.
Hanwha ANPR
AvailableVideo
Number-plate reads over TCP feed a Bolt rule, which decides whether the barrier lifts.
Good for: Barriers and gates where the plate is the credential.
Akuvox
AvailableDoors & credentials
Video intercoms paired with Bolt doors. A visitor calls from the lobby panel; the host lets them in.
Good for: Buildings that want a face on the screen before the door opens.
HID Signo
AvailableDoors & credentials
Signo readers over OSDP, with secure channel and supervised wiring.
Good for: HID estates that aren’t ready to replace the readers.
MQTT
AvailableAutomation
Native. Bolt events are published over MQTT with TLS.
Good for: If it speaks MQTT, it can subscribe to Bolt directly.
Webhooks
AvailableMessages
Send any Bolt event to any HTTPS endpoint, HMAC-signed and retried with backoff.
Good for: When none of the above is quite right: you write the other end, Bolt calls it.
Email
AvailableMessages
Visitor invites and notifications by email, sent through Resend.
Good for: Visitors get a link, not an app to install.
Apple Wallet
Early accessDoors & credentials
Add-to-Wallet passes with Express Mode, so the phone works even when it’s locked.
Good for: Staff who’d rather carry a phone than a card. In pilot.
Google Wallet
Early accessDoors & credentials
Wallet passes on Android with the same credential model as Apple.
Good for: The same pass on both platforms. In pilot.
Microsoft 365
PlannedIdentity
Sync staff and groups from Entra ID, sign in with OIDC, and let off-boarding follow the directory.
Good for: HR removes someone; their access goes with them.
Google Workspace
PlannedIdentity
Directory sync and SAML single sign-on, with group-to-role mapping.
Good for: Engineers get the rear entrance because they’re in the Engineering group.
Okta
PlannedIdentity
SCIM provisioning and SAML sign-in.
Good for: Identity stacks that aren’t Microsoft 365 or Google.
Auth0
PlannedIdentity
OIDC provider, planned alongside Okta.
Good for: Customers who bring their own identity provider.
Network Optix
PlannedVideo
A two-way bridge: Bolt events on NX timelines, NX clips opened from Bolt events.
Good for: Security teams who already live in NX Meta or Witness.
Zapier
PlannedAutomation
Triggers on unlock, denial and motion; actions to grant access and send invites.
Good for: Glue Bolt into the tools you already use, without code.
n8n
PlannedAutomation
A packaged n8n node over the Bolt API and event stream.
Good for: When Zapier is too simple and custom code is too much.
Home Assistant
PlannedAutomation
An integration over the Bolt MQTT event stream.
Good for: Small buildings where commercial and home blur together.
Twilio SMS
PlannedMessages
SMS visitor passes and one-time codes.
Good for: Visitors who don’t have email on them (a surprising number).
Slack
PlannedMessages
Host notifications when a visitor checks in; denial alerts to a security channel.
Good for: Offices that already live in Slack.
Three ways in. Pick one. Three ways in for the IT team.
If it speaks HTTP or MQTT, it can speak to Bolt. API access is set up with you during onboarding. If it speaks HTTP or MQTT, it can speak to Bolt. API access is set up during onboarding, so the customer’s developers don’t need you on site.
-
REST API
HTTPS · scoped keys
Every button in the dashboard maps to an API call. Keys are scoped, so a script only gets what it needs.
-
MQTT
v5 · TLS
Subscribe to events as they happen. No polling.
-
Webhooks
HMAC-signed
Bolt calls your endpoint, retries with backoff, and signs every call so you know it’s really us.
Can’t find the one you need?
Tell us what’s missing. If we hear it twice, it goes on the list. Either way, you’ll get a straight answer about how far off it is. Tell us what the site runs. If we hear it twice, it goes on the list. Either way, you’ll get a straight answer before you quote.
Request received.
Thanks. We read every one, and we’ll reply within one working day with an honest answer.