Network integration

Vectis + Meraki (Cisco).

Cisco Meraki organizations, networks, devices, and uplink health on every customer's account hub. One Dashboard API key covers every org you can see.

Read-onlyVectis syncs from this tool. Inline write-back is not supported by the vendor's documented API surface.

Start 30-day free trial Read the setup guide

Vectis customer hub network tab for a Cisco Meraki-connected customer — per-site device count, ISP uptime, latency, devices-online ratio, and device-level inventory with status badges.

What Vectis syncs

The read side of the adapter.

Vectis enumerates every organization the Dashboard API key has access to, then pulls networks per organization with device count and product types. Per-network devices sync with their model, serial, status, last-reported, and firmware — MX firewalls, MS switches, MR access points, MV cameras. Uplink status (primary plus cellular failover) syncs per device, alongside uplink loss and latency samples for ISP performance trending.

What you can do

The write side of the adapter.

Meraki is a read-only adapter here — Vectis surfaces network and device state and feeds it into rules, but Dashboard configuration changes stay inside the Meraki console. The cross-vendor pattern is what matters: a firmware-drift rule that watches for versions outside an approved set works the same way across Meraki, UniFi, and Aruba Central because all three vendors land in the same network_devices table, source-tagged.

Honest about the limits

What we don’t do, and why.

The Dashboard API is read-only in Vectis by deliberate scope — configuration changes happen inside the Meraki console with proper change-management. Meraki runs regional clusters (api.meraki.ca, api.meraki.cn, api.meraki.in, api.gov-meraki.com), so operators on those clusters override the API base URL in the same admin form; the default api.meraki.com handles every other tenant. Mapping is the deliberate gate: only mapped networks surface to customer pages, and unmapped networks on the same Dashboard account (internal lab networks, for example) stay hidden by default.

How it correlates

One customer, every tool.

Meraki (Cisco) on the customer account hub alongside every other system you run — not a standalone dashboard. A few of the most common shapes this takes:

ISP loss in the same view as the ticket spike

Meraki uplink loss climbing on a network correlates against tickets opened by users at that site. The customer hub shows both, in chronological order — no jumping between Dashboard and the PSA to confirm "yes, the ISP was flaky when they called."

Firmware drift, source-tagged, audit-clean

Devices land in the same network_devices table as UniFi and Aruba Central, source-tagged by vendor. A rule that watches for firmware versions outside an approved set works the same way across all three vendors.

Setup snapshot

What connecting looks like.

Generate a Dashboard API key at dashboard.meraki.com → My profile → API access. Paste it into Vectis admin → Integrations → Meraki. Operators on Meraki regional clusters (api.meraki.ca, api.meraki.cn, api.meraki.in, api.gov-meraki.com) override the API base URL in the same admin form. The first sync auto-discovers every (organization, network) pair the key can see; map each network to a Vectis customer in the admin screen. Only mapped networks surface to customer pages — internal lab networks on the same Dashboard account stay hidden by default.

# In the Vectis hub, add the connector:
category  Network
vendor    Meraki (Cisco)
status    Read-only

Read the full setup guide

Other Network integrations

Evaluating Meraki (Cisco) against the alternatives?

UniFi (Ubiquiti)

Aruba Central (HPE)

Pricing

Meraki (Cisco) is available on every Vectis tier — $299/mo and up. See pricing

Also reachable over MCP — bring your own client → /mcp

Try Vectis with Meraki (Cisco).

30-day free trial. Connect Meraki (Cisco) at signup. See every customer with their full context on day one. Month-to-month, cancel anytime.

Start 30-day free trial All integrations