Cisco Meraki: network devices, WAN uplinks, and licence expiry

Cisco Meraki is where your network lives: the MX appliances at the edge of each site, the MS switches behind them, and the MR access points on top. This connector reads four things out of it — your organizations and their networks, every device and whether it is online, the WAN uplink state at each site, and how your licences are tracking — and hangs each one off the matching Current company so it feeds your business reviews and the company posture panel. Current reads Meraki and can never change anything in it.

1. 1
   1 · Sign in as a read-only administrator

   In the Meraki dashboard, sign in as an administrator whose access is read-only across the organizations you want Current to see. If you do not have one, create it under Organization → Configure → Administrators first — it takes a minute and it is the safest way to run this.
2. 2
   2 · Open Organization ▸ Configure ▸ API & Webhooks

   Go to the API keys and access tab. You can also reach the same place from your avatar in the top right → My profile → API access.
3. 3
   3 · Generate the key

   Press Generate API key. Meraki allows two keys per person, so if the button is greyed out this administrator already has two and you will need to revoke one first — check with whoever owns the other integration before you do.
4. 4
   4 · Copy it before you leave the page

   Meraki shows the key once, at the moment you generate it. Copy it now — if you close the page you will have to generate another, and that counts against the two-key limit.

1. 1
   Open the Meraki card

   In Current's left sidebar open Integrations (it sits under Admin, so Tenant Admins have the link) and find Cisco Meraki in the Monitoring & security section.
2. 2
   Pick your Meraki cloud

   Meraki runs five separate clouds and a key only works against the one your organizations live on: Global (the default, covering North America, Europe, and Asia-Pacific), Canada, China, India, and US Government (FedRAMP). If your organizations are Canadian-hosted, pick Canada — a Canadian organization queried against the global address fails exactly like a wrong key.
3. 3
   Paste the API key, then press Test connection

   Current reads a short organization list back to prove the key works and that the administrator it belongs to can actually see organizations, before it stores anything. If Meraki refuses, the card shows Meraki's own reason rather than a generic failure. On success the key is stored server-side only — the browser never sees it again.

Meraki supports two ways of running an MSP estate, and both are normal. Meraki calls them the Tailored Service model — one organization per partner — and the Standard Service model, where you run a small number of organizations and each partner is a network inside one. Meraki recommends the second for service providers and says it is the more common of the two.

Current supports both. The connection maps by organization out of the box; if your partners are networks inside one or two organizations, switch the card to map by network instead. After the first sync, the card tells you what it found — for example, one organization containing thirty-four networks — so you can confirm which shape you are on rather than guessing.

1. 1
   Let the auto-matcher run first

   Every sync links each organization (or network) to the one Current company whose normalized name matches — lowercased, with punctuation and Inc/LLC/Ltd-style suffixes stripped — and only when exactly one company matches. Two companies that both fit stay unmapped for you to decide.
2. 2
   Open the mapping panel

   Integrations → Cisco Meraki → Manage → Customer mapping. It opens on the Unmapped tab. Expect more manual work here than with some other connectors: Meraki knows nothing about your PSA, so there is no customer id the two systems already share and names are all Current has to go on.
3. 3
   Map a row to its company

   On an unmapped row press Map, type a few letters of the Current company, and pick it. That organization's devices and uplinks attach to the company right away, rather than waiting for the next 6-hour sync.
4. 4
   Ignore internal or lab organizations

   For anything that should never map to a partner — your own office, a lab, a demo network — press Ignore. It moves to the Ignored tab and stops counting against the card's unmapped badge.
5. 5
   Fix a wrong match later

   The Mapped tab lists every linked row; Unmap corrects a bad auto-match, and the Ignored tab's Un-ignore brings a dismissed one back. A mapping you set by hand is never overwritten by a later auto-match, and neither is a manual unlink.

Meraki syncs every 6 hours on a schedule, plus whenever you press Sync now on the card. Each run walks your organizations one at a time — not all at once — reads their networks, devices, uplinks, and licence posture, and replaces the device and uplink sets. Meraki allows ten requests a second per organization; Current deliberately runs at under half that, because your PSA integration and your own scripts are drawing on the same allowance.

Every request Current makes to Meraki passes through a read-only guard that permits five specific read endpoints and nothing else. Meraki's API is a full network management API — it can reboot a device, power-cycle a switch port, move licences between organizations, create administrators, and delete an entire organization — and none of those paths exist anywhere in the connector's code, so a bug cannot reach them either. Generating the key from a read-only Meraki administrator adds a second, independent layer on Meraki's own side. Meraki stays the source of truth; Current only reads.

• ＋The company's network panel: device counts by product type, the four device states kept apart, and how many sites have their WAN up.
• ＋WAN uplink detail per site: which interface, its state, the internet provider, and cellular signal where a site is running on mobile backup.
• ＋Licence posture: how many licences are expiring and expired, or the co-termination date, depending on the organization's licensing model. This is your renewal list.
• ＋The Fleet & Network chapter of a Strategic Business Review, alongside your other network feeds.
• ＋Dashboard network metrics — device counts and site connectivity read from Meraki once it is connected and mapped.