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

# Cisco Meraki

Cisco Meraki is a cloud-managed IT platform for networking, security, and device management. It gives IT teams centralized visibility and control over their network infrastructure — from switches and access points to security appliances — all through a single dashboard.

Connecting Cisco Meraki to Coupler.io lets you pull your network and device data into any reporting or analytics tool without writing a single line of code.

## Why connect Cisco Meraki to Coupler.io?

* **Centralize network reporting** — combine device, network, and admin data in one place for easier oversight
* **Monitor API usage** — track API request logs to spot unusual activity or quota issues
* **Audit admin access** — export admin and SAML configurations for compliance and security reviews
* **Automate refreshes** — keep your dashboards and reports up to date on a schedule

## Prerequisites

Before you connect, make sure you have:

* A Cisco Meraki account with at least **read-only** API access
* A Meraki **API key** — you can generate one in your Meraki Dashboard under **My Profile → API access**
* API access enabled for your organization (an org admin must turn this on under **Organization → Settings**)

{% hint style="success" %}
If you're new to Coupler.io, start with the **Organization devices** entity — it gives you the broadest view of your infrastructure right away.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Create a new data flow.** In Coupler.io, click **Add data flow**, then search for and select **Cisco Meraki** as your source.
{% endstep %}

{% step %}
**Enter your API key.** Paste your Meraki API key into the API key field. If you haven't generated one yet, go to your Meraki Dashboard → **My Profile** → **API access** → **Generate new API key**.
{% endstep %}

{% step %}
**Select an entity.** Choose the data entity you want to import — for example, Organization devices or Organization networks. You can add more sources to the same data flow later.
{% endstep %}

{% step %}
**Set a start date.** Use the date picker to define how far back you want Coupler.io to pull historical data.
{% endstep %}

{% step %}
**Choose a destination.** Select where you want your data to land — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT, Claude, or Gemini.
{% endstep %}

{% step %}
**Run the data flow.** Click **Run** to execute your first manual sync and confirm everything is working.
{% endstep %}
{% endstepper %}

## Available entities

| Entity                        | Description                                          |
| ----------------------------- | ---------------------------------------------------- |
| Organizations                 | Organization details and configuration               |
| Datacenters                   | Datacenter locations and infrastructure info         |
| Organization networks         | Network configurations and settings                  |
| Organization devices          | Managed devices (switches, APs, security appliances) |
| Organization API requests     | API request logs and usage statistics                |
| Organization admins           | Admin accounts and permission levels                 |
| Organization SAMLs            | SAML authentication configurations                   |
| Organization network settings | Network-level policies and settings                  |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coupler.io/sources/category/other/cisco-meraki.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.