> For the complete documentation index, see [llms.txt](https://docs.harmony.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.harmony.io/integrations/networking/cisco-meraki.md).

# Cisco Meraki

The Cisco Meraki integration connects Harmony to your Meraki network environment using the Meraki Dashboard API. Once connected, Harmony can pull network data from your Meraki organization to support visibility, monitoring, and workflow automation across your infrastructure.

This integration is available under the **Networking** category on the Integrations settings page. If you manage more than one Meraki environment, you can add multiple instances of this integration to cover each organization separately.

### Prerequisites

Before you set up the integration, make sure you have the following:

* A Cisco Meraki account with access to the organization you want to connect.
* A Meraki Dashboard API key. You can generate one from your Meraki Dashboard under **My Profile > API access** (or **Organization > Configure > API & Webhooks**, on the **API keys and access** tab). Copy the key right away: it is shown only once. Generate it with an account that does not sign in to the dashboard with SAML/SSO, because SAML users cannot generate API keys.
* Sufficient permissions in Harmony to manage integrations.

### Connect Cisco Meraki to Harmony

1. In Harmony, go to **Settings** > **Integrations**.
2. Find **Cisco Meraki** under **Networking** (or search for it by name) and click its card.
3. If this is your first Meraki connection, the connection form opens. If you are adding a subsequent Meraki environment, click **+ Create instance**.
4. Enter an **Instance name** that identifies this environment (required).
5. Paste your Meraki Dashboard API key into the **API Key** field.
6. Click **Connect**.

Harmony establishes the connection. Once the integration is active, it will appear in your list of configured integrations under the Networking category.

### Multiple Instances

If your organization manages more than one Cisco Meraki environment, you can add a separate instance for each one. Repeat the connection steps above for each environment, using the appropriate API key for each. Each instance is managed and named independently, making it straightforward to distinguish between environments at a glance.

### Removing the Integration

To disconnect Cisco Meraki from Harmony:

1. Go to **Settings** > **Integrations**.
2. Click the **Cisco Meraki** card under **Networking**.
3. Click the delete (trash) icon next to the instance you want to remove, and confirm.

Removing an instance disconnects Harmony from that Meraki environment and stops any data collection associated with it. Other instances, if you have added more than one, are not affected.

### Related Integrations

* Juniper Mist - another Networking integration available on the same Integrations settings page, using an API endpoint and API key for authentication.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.harmony.io/integrations/networking/cisco-meraki.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
