> ## Documentation Index
> Fetch the complete documentation index at: https://docs.msportal.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure Cisco Meraki Integration

> Connect your Cisco Meraki Dashboard to MSPortal.ai to sync network devices across all your companies

This guide walks you through connecting your Cisco Meraki Dashboard to MSPortal.ai so network devices sync automatically into your device inventory.

## Overview

Cisco Meraki is a cloud-managed networking platform for access points, switches, security appliances, cameras, and sensors. By integrating Meraki with MSPortal.ai, you can:

* Sync network devices from all your Meraki organizations into MSPortal's device inventory
* Map Meraki organizations to the correct MSPortal companies
* Assign Meraki networks to company locations so devices land in the right place
* Keep device details like model, serial number, firmware version, and IP address current
* Classify Meraki hardware into your own device types (firewalls, switches, access points, and more)

## Prerequisites

* Cisco Meraki Dashboard account with organization admin access
* Dashboard API access enabled for your Meraki organization
* MSPortal.ai account with integration management permissions

## Part 1: Generate a Meraki API Key

Before connecting to MSPortal.ai, you need a Meraki Dashboard API key.

<Steps>
  <Step title="Log into the Meraki Dashboard">
    Access your dashboard at [dashboard.meraki.com](https://dashboard.meraki.com).
  </Step>

  <Step title="Enable Dashboard API Access">
    Go to **Organization > Settings** and scroll to the **Dashboard API access** section.

    Check **Enable access to the Cisco Meraki Dashboard API** and save.

    <Note>
      If you manage multiple Meraki organizations, enable API access in each organization you want to sync.
    </Note>
  </Step>

  <Step title="Generate the API Key">
    Open your profile by clicking your account name in the top-right corner, then select **My profile**.

    In the **API access** section, click **Generate new API key**.

    <Info>
      Newer Meraki dashboards also offer API key management under **Organization > Configure > API & webhooks**. Either location produces a valid key.
    </Info>
  </Step>

  <Step title="Copy the API Key">
    Copy the key immediately.

    <Warning>
      **Store the API key securely!** Meraki only shows the key once. If you lose it, generate a new one.
    </Warning>

    <Tip>
      The key inherits the permissions of your Meraki account. Devices sync from every organization the key can access, so a dedicated read-only Meraki admin account is a good choice for generating the key.
    </Tip>
  </Step>
</Steps>

***

## Part 2: MSPortal Setup

Meraki is configured through a settings panel rather than a multi-step wizard. You connect the API key once for your whole tenant, then map organizations and device types.

### Connect the API Key

<Steps>
  <Step title="Navigate to Integrations">
    In MSPortal.ai, go to **Settings > Integrations**.
  </Step>

  <Step title="Find Cisco Meraki">
    Locate the **Cisco Meraki** integration card and click **Connect** to open the Meraki settings panel.
  </Step>

  <Step title="Configure the API Key">
    Click **Configure API Key**.

    In the **Configure Meraki API Key** dialog, paste your key into the **API Key** field and click **Connect**.

    <Note>
      Your API key is encrypted and stored securely. It is used to sync device information from all organizations accessible with the key.
    </Note>
  </Step>

  <Step title="Review the Configuration">
    After connecting, the panel shows your configuration:

    | Field                   | Description                                             |
    | ----------------------- | ------------------------------------------------------- |
    | **Auth Method**         | Confirms the API key is configured                      |
    | **Organizations**       | Meraki organizations discovered with your key           |
    | **Mapped to Companies** | How many organizations are linked to MSPortal companies |
    | **Last Device Sync**    | Timestamp of the most recent device sync                |
  </Step>
</Steps>

### Map Organizations

Map each Meraki organization to an MSPortal company. Only devices from mapped organizations are imported.

<Steps>
  <Step title="Open Organization Mappings">
    In the Meraki settings panel, click **Map Organizations**.
  </Step>

  <Step title="Use Quick Match">
    Click **Quick Match** to automatically match Meraki organizations to MSPortal companies based on name similarity. Review the results and adjust as needed.
  </Step>

  <Step title="Map Manually">
    For organizations that were not matched automatically:

    1. Find the organization in the list
    2. Click the **Select company** dropdown in the "Mapped To" column
    3. Search for and select the correct MSPortal company

    Use the filter to view **All Organizations**, **Mapped Only**, or **Unmapped Only**. The **View in Meraki** link opens the organization in the Meraki Dashboard.
  </Step>
</Steps>

### Device Type Mappings

Control how Meraki product types are classified in your device inventory.

<Steps>
  <Step title="Open Device Type Mappings">
    In the Meraki settings panel, click **Device Type Mappings**.
  </Step>

  <Step title="Review and Adjust Mappings">
    Each Meraki product type (wireless, appliance, switch, camera, cellular gateway, sensor, and others) can be mapped to one of your MSPortal device types.

    Sensible defaults are applied automatically, for example: appliances map to Firewalls, switches to Switches, and wireless devices to Access Points. Adjust any mapping to fit your own device type structure.
  </Step>
</Steps>

### Run the First Sync

<Steps>
  <Step title="Sync All Companies">
    Back in the Meraki settings panel, click **Sync All Companies** to pull devices from every mapped organization.
  </Step>

  <Step title="Verify Devices">
    Once the sync completes, open the **Devices** page for a mapped company and confirm the Meraki hardware appears with the expected device types.
  </Step>
</Steps>

***

## Company-Level Setup (Optional)

In addition to the tenant-wide API key, individual companies can connect their own Meraki access and choose exactly which networks sync.

<Steps>
  <Step title="Open the Company">
    Go to **Settings > Companies** and select a company.
  </Step>

  <Step title="Connect Meraki for the Company">
    Find the **Device Integrations** section and locate the **Cisco Meraki** card.

    Click **Connect** to authorize through Meraki's sign-in popup, or choose **Use API Key** to enter a Meraki API key for this company.
  </Step>

  <Step title="Select the Organization and Networks">
    Choose which Meraki organization belongs to this company, then select the specific networks to sync.
  </Step>

  <Step title="Map Networks to Locations">
    Click **Map Networks to Locations** to assign each Meraki network to a company location. Devices are automatically associated with these locations when synced.

    <Note>
      Locations must already exist in the company's settings before they can be assigned to networks.
    </Note>
  </Step>

  <Step title="Manage the Company Integration">
    From the company's Meraki card you can also use **Sync Now**, **Pause Sync** / **Resume Sync**, and **Remove Integration**.
  </Step>
</Steps>

***

## What Gets Synced

The Meraki integration syncs the following data to MSPortal:

### Organizations and Networks

* Organization names and dashboard links
* Networks within each organization, including their product types

### Devices

Network hardware from mapped organizations:

* Device name
* Serial number
* MAC address
* Model
* Firmware version
* IP address
* Product type, classified into your MSPortal device types

***

## Synchronization Schedule

After initial setup, data syncs automatically:

| Data Type                                     | Sync Frequency       |
| --------------------------------------------- | -------------------- |
| Devices (organizations and networks included) | Daily at 3:00 AM UTC |

Each integration syncs at most once every 24 hours on the schedule. Manual syncs are not limited by this interval.

<Note>
  You can trigger a manual sync at any time with **Sync All Companies** in the tenant-wide settings, or **Sync Now** on a company's Meraki card.
</Note>

***

## Managing Your Integration

After setup, manage the integration from **Settings > Integrations** by opening the **Cisco Meraki** card:

| Action                             | Description                                                         |
| ---------------------------------- | ------------------------------------------------------------------- |
| **Map Organizations**              | Add or change organization-to-company mappings                      |
| **Device Type Mappings**           | Adjust how Meraki product types classify into device types          |
| **Sync All Companies**             | Trigger an immediate device sync for all mapped organizations       |
| **Disable Sync** / **Enable Sync** | Pause or resume scheduled syncing without removing the integration  |
| **Update API Key**                 | Replace the stored Meraki API key                                   |
| **Remove**                         | Delete the integration, all synced data, and company configurations |

***

## Troubleshooting

| Issue                          | Solution                                                                                                   |
| ------------------------------ | ---------------------------------------------------------------------------------------------------------- |
| API key rejected               | Verify the key was copied fully and that Dashboard API access is enabled in Meraki                         |
| No organizations listed        | Confirm the Meraki account that generated the key has access to the expected organizations                 |
| No devices syncing             | Check that organizations are mapped to companies; only mapped organizations import devices                 |
| Devices classified incorrectly | Adjust the mappings under **Device Type Mappings**                                                         |
| Data looks stale               | Scheduled syncs run once per day; use **Sync All Companies** to force an immediate refresh                 |
| Devices missing a location     | Use **Map Networks to Locations** on the company's Meraki card and confirm locations exist for the company |

***

## Security & Privacy

* **API Key Storage**: Your Meraki API key is encrypted and never exposed in logs or responses
* **Data Isolation**: All synced data is tenant-isolated and only visible to your organization
* **Read-Only Usage**: MSPortal only reads device and network information; it never changes your Meraki configuration

***

## Next Steps

After setting up the Meraki integration:

<CardGroup cols={2}>
  <Card title="View Devices" icon="laptop" href="/user-guides/devices/index">
    Browse the synced network hardware in your device inventory
  </Card>

  <Card title="Import Devices" icon="download" href="/user-guides/integrations/import-devices">
    Learn how device imports work across integrations
  </Card>

  <Card title="Sync Schedules" icon="clock" href="/user-guides/integrations/sync-schedules">
    See when each integration refreshes its data
  </Card>

  <Card title="Other Integrations" icon="plug" href="/user-guides/integrations/index">
    Explore additional integration options
  </Card>
</CardGroup>

## Need Help?

For assistance with the Cisco Meraki integration, contact [support@msportal.ai](mailto:support@msportal.ai).