--- title: "Cisco Meraki Integration" description: "Connect AI agents to your Cisco Meraki cloud-managed network. Agents enumerate organizations, networks, and devices, monitor device availability, audit connected clients and data usage, and update device metadata across the deployment." url: https://flowrunner.ai/integrations/meraki date_modified: 2026-08-01T02:40:32-07:00 --- # Cisco Meraki [Developer Tools](https://flowrunner.ai/integrations/category/developer-infrastructure) Connect AI agents to your Cisco Meraki cloud-managed network. Agents enumerate organizations, networks, and devices, monitor device availability, audit connected clients and data usage, and update device metadata across the deployment. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 10 actions · API key · available [Cisco Meraki website](https://cisco.com/) · [Platform Documentation](https://developer.cisco.com/meraki/api-v1/) · Capability data verified 2026-07-28 1. The availability sweep runs on its five-minute schedule 2. List Device Statuses pulls every device in the organization, filtered to offline and alerting 3. The agent compares against the maintenance calendar and the previous sweep, separating momentary flaps from confirmed outages 4. Get Device hydrates each confirmed-down serial with its model, network, and street address 5. An incident pages the on-call engineer with the serial, the site, and the last-reported timestamp 6. The engineer decides whether this is a remote fix, a truck roll, or a carrier escalation 7. The outage record lands in the operations log with timestamps, ready for the postmortem ## What This Integration Enables For a business running Meraki across many sites, retail locations, clinics, branch offices, the network is invisible until it fails, and the failure is always discovered at the worst end: by the people trying to take payments or see patients. The Meraki Dashboard already knows the truth of the whole deployment. This connector makes that truth ambient. FlowRunner agents walk the natural Meraki hierarchy, organization to network to device, and turn a dashboard someone has to check into a reporter that speaks up. - Enumerate organizations, networks, and every device across the deployment, with product-type filters - Monitor availability fleet-wide and distinguish online, offline, alerting, and dormant states - Audit which clients used a network, on which SSID and VLAN, with per-client data usage over a window of up to 31 days - Keep device names, tags, and street addresses in sync with an external source of truth The connector is deliberately read-heavy: most of its value is telemetry. Its one write, Update Device, is exactly where FlowRunner applies [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) review, because device metadata is what the rest of the tooling keys on. ### Without FlowRunner **Outages discovered by phone call**: A site's network is down when the site manager calls to say so, and the clock started an hour ago **Inventory as an export**: The hardware list was accurate on the day someone last downloaded it **Dashboard-shaped knowledge**: Everything about the network is known, but only to whoever is logged in ### With FlowRunner **Outages detected in minutes**: Status sweeps run continuously and page a person only for confirmed, unplanned downtime **Inventory as a living record**: Every device's serial, model, firmware, and location append to the sheet as the fleet changes **Network events reach the stack**: Statuses, clients, and usage flow into Slack, incident tools, and reports on their own ## Use Case Scenarios ### The multi-site availability watch Every five minutes, an agent runs List Device Statuses across the organization. A security appliance offline at one store is checked against the previous sweep and the maintenance window list; confirmed outages page the on-call engineer through [PagerDuty](https://flowrunner.ai/integrations/pagerduty) with the device details from Get Device, while a summary posts to [Slack](https://flowrunner.ai/integrations/slack) for visibility. Dormant devices accumulate into a weekly report instead of paging anyone, because a spare in a drawer is not an incident. ### The inventory that maintains itself Weekly, List Organization Devices enumerates the fleet and reconciles it against the asset sheet in [Google Sheets](https://flowrunner.ai/integrations/google-sheets): new serials append with model, network, and location; devices that vanished from the organization get flagged rather than silently dropped. Finance gets a defensible hardware count at refresh-planning time, and nobody spends an afternoon exporting CSVs from the dashboard. ### The client audit nobody had time to run Monthly, List Network Clients pulls every client seen on the guest and corporate networks within the timespan cap. The agent sorts by data usage and flags the anomalies: a manufacturer string nobody recognizes on the corporate SSID, a guest client moving significant data at night. The shortlist goes to the security channel with MAC, IP, SSID, VLAN, and last-seen time, and a person decides which entries deserve investigation. The network was always recording this; now someone actually reads it. ## Human-in-Loop Highlight Update Device carries a sharp edge documented in Meraki's own API: supplying tags replaces the device's entire tag list, not appends to it. In a Meraki deployment, tags are rarely decoration; they drive site groupings, alert scoping, and the automation other tools hang off. A bulk metadata sync that writes a fresh tag list can silently detach fifty access points from the groupings that determine who gets paged when they fail. So when a FlowRunner agent reconciles device metadata from an external source of truth, it computes the before-and-after per serial and presents the diff: which names change, which addresses update, and, highlighted separately, every device whose tag list would shrink. A network engineer approves the batch, or excludes the surprises, before Update Device writes anything. Reading the fleet is free. Rewriting what the fleet's automation keys on gets a second pair of eyes. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 10 actions ### Organizations 2 - **List Organizations** Lists all organizations the API key can access, each with its ID, name, dashboard URL, API access status, licensing model, and cloud region. The starting point of the hierarchy. - **Get Organization** Retrieves a single organization by ID with its name, dashboard URL, API access status, licensing model, and cloud region. ### Networks 2 - **List Networks** Lists all networks in an organization, each with its ID, name, product types, time zone, tags, and enrollment URL. - **Get Network** Retrieves a single network by ID, including its name, product types, time zone, tags, and notes. ### Devices 4 - **List Organization Devices** Lists every device across all networks in an organization, with serial, name, model, MAC address, product type, network ID, tags, and location. Optionally filtered by product type. The fleet-wide inventory action. - **List Network Devices** Lists the devices in a specific network, including firmware alongside the standard attributes. - **Get Device** Retrieves a single device by serial number: name, model, MAC address, product type, network ID, tags, firmware, LAN IP, and physical location. - **Update Device** Updates a device's name, tags, and street address by serial. Only supplied fields change, but a supplied tag list replaces the existing one entirely, which is why this action sits behind this page's human gate. ### Monitoring 2 - **List Network Clients** Lists clients that used a network within a timespan of up to 31 days: MAC and IP addresses, description, user, VLAN, manufacturer, OS, connecting SSID, online status, last-seen time, and data usage. - **List Device Statuses** Lists the availability of every device in an organization: online, offline, alerting, or dormant, with the last-reported time. Optionally filtered by status. The heartbeat behind the availability watch. ## Frequently Asked Questions ### What can FlowRunner do with Cisco Meraki? FlowRunner agents can run List Organizations, Get Organization, and List Networks in Cisco Meraki, plus 7 more actions. ### Does connecting Cisco Meraki to FlowRunner require OAuth? No. Cisco Meraki connects to FlowRunner with an API key, no OAuth flow required. ### Can Cisco Meraki trigger a FlowRunner workflow automatically? Cisco Meraki doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Cisco Meraki?** This integration exposes Cisco Meraki to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/meraki. Site index: https://flowrunner.ai/llms.txt