Network integration
Meraki (Cisco)
Read-onlyCisco Meraki organizations, networks, devices, and uplink health on every customer's account hub. One Dashboard API key covers every org you can see.
What Vectis syncs
The read side of the adapter. Pulled on a schedule and available everywhere the customer account surface lives. Every row below is a method this connector exposes today.
| Capability | Synced |
|---|---|
| Organizations the API key has access to | |
| Networks per organization with device count and product types | |
| Devices per network — MX firewalls, MS switches, MR access points, MV cameras — with model, serial, status, last-reported, firmware | |
| Uplink statuses (primary + cellular failover) per device | |
| Uplink loss + latency samples for ISP performance trending |
Read-only today
This adapter pulls data into Vectis but doesn't write back into Meraki (Cisco). Rules can still react to the synced data — for example, a Pax8 subscription change can open a ConnectWise ticket. The write-back lands in the PSA, not in Meraki (Cisco).
Meraki (Cisco) is one of the read-only systems Vectis correlates against — synced data lands on the customer hub, drives rules, and shows up on the timeline; the vendor’s lifecycle stays inside its own console.
How it correlates
One customer, every tool.
Vectis is about Meraki (Cisco) joining your other systems around the customer account — not a standalone dashboard. Two concrete examples:
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) can override the API base URL in the same form. The first sync auto-discovers every (org, 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. The Dashboard API is read-only here.
Full setup guideavailable after signup
Try Vectis with Meraki (Cisco).
14-day free trial. Connect Meraki (Cisco) at signup. See every customer with their full context on day one. Cancel anytime during the trial at no charge.