> ## Documentation Index > Fetch the complete documentation index at: https://docs.letsflow.ai/llms.txt > Use this file to discover all available pages before exploring further. # Cisco Meraki > Manage Meraki networks, devices, clients, and operational alerts. export const flowWebUrl = "https://app.letsflow.ai"; Connect Cisco Meraki to manage networks, devices, clients, and alerts from Flow automations. Choose which teams can use the connection. Enable Automation for each team before it can run Cisco Meraki actions. ### Prepare in Cisco Meraki Enable Dashboard API access for each Meraki organization your automations need. In Meraki Dashboard, open **Organization > API & Webhooks > API keys and access** to create your personal API key. See [Meraki API-key setup](https://developer.cisco.com/meraki/api-v1/authorization/) and [Dashboard API access](https://documentation.meraki.com/Platform_Management/Dashboard_Administration/Operate_and_Maintain/How-Tos/How_to_Use_the_Cisco_Meraki_Dashboard_API). The API key inherits your administrator permissions in each organization. Read actions need read access. Write actions need permission to change the target resource. This connection uses the global Meraki API at `https://api.meraki.com/api/v1`. Regional API hosts, including Canada, China, India, and US Government, require a separate connection setup. See [Meraki API regions](https://developer.cisco.com/meraki/api-v1/schema/). If verification rejects the key, replace it and reconnect. If Meraki denies access, check Dashboard API access and the key owner's organization permissions. If verification is temporarily unavailable, try again. ### Connect in Flow 1. Open **Integrations**. 2. Choose **Add connection**. 3. Search for **Cisco Meraki**. 4. Select the **Cisco Meraki** card. Open Flow 1. Choose who can use the connection. 2. Select **Continue** through the setup steps. 3. Give the connection a name. 4. Select **Connect** to open the credential form. 5. Enter your Meraki Dashboard API key. 6. Submit the form. 7. Wait for Flow to verify the key. 8. Open the new connection's **Automations** tab. 9. Choose **Enable** for the intended team or teams. 10. Select the Cisco Meraki actions automations can run. 11. Choose **Save** if you changed the selection. ## Permissions and scopes This integration does not define provider scopes. ## Supported actions | Action | Description | Risk | | - | - | - | | Claim devices into a network. (Note: for recently claimed devices, it may take a few minutes for API requests against that device to succeed) | Claim devices into a network as a core deployment action. | high | | Create a network | Create a Meraki network for a new site or service deployment. | high | | Create a new dashboard administrator | Create a Dashboard administrator for approved access provisioning. | high | | Cycle a set of switch ports on non-Catalyst MS devices | Power-cycle selected switch ports to recover attached devices; approval is required because the action is disruptive. | high | | Get firmware upgrade information for a network | Read network firmware upgrade state before scheduling changes or diagnosing upgrade incidents. | low | | List the availability information for devices in an organization | List device availability details across the organization to identify unreachable assets. | low | | List the dashboard administrators in this organization | List Dashboard administrators for access reviews and offboarding checks. | low | | List the devices in a network | List devices assigned to a specific network for site-scoped administration. | low | | List the devices in an organization that have been assigned to a network. | List organization devices already assigned to networks for fleet-wide lookup. | low | | List the events for the network | List network events for troubleshooting and attaching relevant evidence to incidents. | low | | List the networks that the user has privileges on in an organization | List networks in an organization for site lookup and downstream network-scoped actions. | low | | List the organizations that the user has privileges on | List Meraki organizations available to the connected administrator so workflows can select the correct tenant. | low | | List the status of every Meraki device in the organization | List current status of every Meraki device to support outage detection and incident triage. | low | | List the switch ports for a switch | List switch ports to locate the interface that needs verification or remediation. | low | | Remove a single device | Remove a device from a network during reassignment or retirement; approval is required. | high | | Return a network | Retrieve a network to verify identity, product types, tags, and current configuration before changes. | low | | Return a ping job | Retrieve the asynchronous Meraki ping job status and results. | low | | Return a single device | Retrieve a single Meraki device by serial before diagnosis or configuration changes. | low | | Return a single device from the inventory of an organization | Retrieve one inventory device by serial to verify claim and assignment state. | low | | Return the alert configuration for this network | Read a network's alert configuration before validating or changing notification behavior. | low | | Return the alert history for this network | Retrieve network alert history for incident correlation and ITSM ticket enrichment. | low | | Return the client associated with the given identifier | Retrieve a specific network client to verify identity, status, and attachment details. | low | | Return the client details in an organization | Search organization-wide for a client by identifying details without first knowing its network. | low | | Return the device inventory for an organization | List organization inventory, including devices not yet assigned to a network, for provisioning workflows. | low | | Return the policy assigned to a client on the network | Read the policy currently assigned to a client before remediation. | low | | Revoke all access for a dashboard administrator within this organization | Revoke all organization access for a Dashboard administrator; approval is required. | high | | Rollback a Firmware Upgrade For A Network | Rollback a failed network firmware upgrade; incident/change approval is required. | high | | Update a network | Update core network metadata and settings used in site administration workflows. | high | | Update a switch port | Update an individual switch port configuration; change approval is required because service may be interrupted. | high | | Update an administrator | Update administrator privileges and organization or network access scopes. | high | | Update firmware upgrade information for a network | Schedule or modify a network firmware upgrade; maintenance approval is required. | high | | Update the alert configuration for this network | Update network alerting and notification configuration; change approval is required. | high | | Update the attributes of a device | Update canonical device attributes such as name, tags, address, and notes. | high | | Update the policy assigned to a client on the network | Assign or change a client's Meraki policy for access remediation; approval is required because connectivity may be affected. | high | | View the Change Log for your organization | Read the Meraki organization change log for incident investigation and change verification. | low | This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.