SMARTTILE · DEVICEAUTOMATE™ · WATCHGUARD FIREBOX · BETABETA

WatchGuard Fireboxes, read from WatchGuard Cloud

BETA — built and unit-tested, switched off until proven on a real WatchGuard Cloud account. One read-only Access ID gives SmartTile every Firebox's model, serial, Fireware version, cloud status, restarts and licence expiry — and, for cloud-managed Fireboxes, BOVPN configuration, the policy base with a change history and deployment history.

SmartTile integrates with
WatchGuard Firebox appliances (incl. FireboxV and FireCluster) connected to WatchGuard Cloud — through the WatchGuard Cloud public API (USA, Europe or Japan region), signed in with a READ-ONLY Access ID, its password and the account's API Key.
How SmartTile automates it
Once switched on, SmartTile's agent reads every Firebox in the account every 5 minutes (status, identity, uptime) and hourly reads licences and, for cloud-managed Fireboxes, BOVPN configuration, policies into a change ledger and deployments; each new problem becomes one Workflow event.
Category
DeviceDeviceAutomate™

WatchGuard Cloud already knows every Firebox an account owns. SmartTile connects to it once per account — or once for a whole WatchGuard Service Provider, with each managed account mapped to its own SmartTile company — and only reads: the only requests it posts are sign-in token requests. WatchGuard Cloud's “offline” means the Firebox lost its cloud connection, so up/down stays with SmartTile's own ping and SNMP checks. Beta: every switch ships off.

What is built today

Identity onto the device

Model, serial, Fireware version and MAC written to the linked SmartTile device through the shared identity writer — blanks filled, a manual value never overwritten.

Automatic linking

Each Firebox links to the device in the same company with the same serial (else the same public IP), only when exactly one matches. A person can link or unlink; an unlink is respected.

Cloud status + restarts

Online, offline (and since when) or no longer listed in the account. An uptime counter going backwards is recorded as a restart.

Licence expiry

The Firebox licence expiry date, read hourly. Expired, or expiring within 30 days, becomes a problem a Workflow can act on.

Policies + change ledger

Cloud-managed Fireboxes: firewall policies read hourly; each added, removed, changed (which fields) or moved policy is logged. The first read is the baseline.

BOVPN configuration

Cloud-managed Fireboxes: Branch Office VPN tunnels with endpoints and networks, as configured. The pre-shared key is dropped before anything is stored.

Deployment history

Cloud-managed Fireboxes: the last 25 configuration deployments with status and author; a failed deployment in the last 7 days is flagged.

One Workflow per problem

“A WatchGuard Firebox reports a problem” fires once when it opens — offline in WatchGuard Cloud, restarted, missing, licence expired or expiring, deployment failed.

What it takes in WatchGuard Cloud

  1. Sign in to WatchGuard Cloud as an Owner or Administrator (a Service Provider uses its own Service Provider account).
  2. Administration → My Account: copy the Account ID (WGC-1-… or ACC-…).
  3. Administration → Managed Access → Enable API Access: set the read-only password (WatchGuard also asks for a read-write one — SmartTile never uses it), accept the licence, Save.
  4. Copy the Access ID (Read-only) and the API Key; the API URL shows the region (api.usa…, api.deu…, api.jpn…).
  5. In SmartTile: DeviceAutomate → WatchGuard Firebox → Configure → Add connection, Test, Save; switch WatchGuard on for the company and map managed accounts.
Nothing to install on the Firebox and no inbound rule — SmartTile calls WatchGuard Cloud, not the box.
FireboxWhat works
Cloud-managed (Fireware 12.5.3+)Everything on this page; BOVPN needs Fireware 12.5.7+.
Locally managed, connected to WatchGuard CloudIdentity, cloud status, restarts and licence — no policies, BOVPN or deployments.
Not in WatchGuard CloudNothing over the API — monitor with SmartTile's ping and SNMP.
Service ProviderOne connection; each managed account mapped to its SmartTile company. Unmapped accounts are listed, never read.
SmartChoice · SmartTile DeviceAutomate™ — WatchGuard FireboxPage 1 of 2
SMARTTILE · DEVICEAUTOMATE™ · WATCHGUARD FIREBOX — EXACTLY WHAT SMARTTILE ASKS, AND HOW IT IS KEPT SAFE

Exactly what SmartTile calls on the WatchGuard Cloud API

POST/oauth/tokensign in with the read-only Access ID (token, 1 h)
POST/rest/platform/authorization/v1/audiencestoken audience for a managed account (Service Provider)
GET/rest/platform/accounts/v2/accounts/{acct} · …/childrenaccount name; managed accounts
GET/rest/firebox/management/v1/info/{acct}/devices?device_type=FBFireboxes: model, serial, version, state, uptime
GET/rest/platform/allocation/v2/{acct}/assets/licenses/fireboxlicence expiry, MAC (hourly)
GET/rest/firebox/management/v1/configuration/{acct}/bovpn/ipsec/tunnelsBOVPN configuration (hourly)
GET/rest/firebox/management/v1/configuration/{acct}/firewall/policiespolicy base → change ledger (hourly)
GET/rest/firebox/management/v1/commands/{acct}/transactions?tx_type=deploymentdeployment history (hourly)

Security and control

Read-only

The client has no write method; its only POSTs request sign-in tokens. Use the read-only Access ID — SmartTile never deploys, changes or reboots anything.

Encrypted, never shown

The read-only password and API Key are sealed with AES-256-GCM on save and never returned — only “set”. Tokens live in memory only; audit rows name fields, never values.

The company is the tenant

A connection belongs to one company; a managed account is read only once mapped to a company the admin also manages. A Firebox links only to a device in its own company.

Off until switched on

Scheduled poll, policy inventory and Workflow events are platform switches; each company has its own switch. All default off, plus a global kill switch.

Built today vs. what WatchGuard's API does not give

AreaToday (beta)Not available
ProofUnit-tested against WatchGuard's published OpenAPI specs.Proven on a real account — then the switches go on.
Up / downCloud status shown and offered to Workflows.Marking a Firebox DOWN — stays with ping / SNMP.
VPNBOVPN tunnel configuration.Live tunnel state, so no VPNAutomate watching.
Backups / firmwareRunning Fireware version; deployment history.Config export (Config Backups); available releases (FirmwareAutomate).
Access / health—Administrator logins; interfaces, bandwidth, FireCluster HA — use SNMP.

Common objections

ObjectionAnswer
“Will it flood our IT Service Management (ITSM) system?”This integration opens no ticket and sends no e-mail. A Workflow you build fires once per problem.
“We are a WatchGuard Service Provider.”One connection covers every managed account; map each to its customer's SmartTile company.
One read-only Access ID — and every Firebox in WatchGuard Cloud joins the pane your NOC already watches.
SmartChoice · smarttile.smartchoiceus.com · (800) 217-3096, 24×7 · verified 2026-10-06Page 2 of 2