Cisco Meraki Integration

Create a single source of truth for IT assets and mobile devices using the Asset Panda and Cisco Meraki integration. Sync device information from Cisco Meraki to Asset Panda’s centralized platform for full transparency into the state of asset inventory. With a 360° view of IT assets, identify which items are currently deployed, in need of repair, or ready for replacement. Real-time tracking supports operational efficiency and cost control. Sync device data by type or configuration (such as company-owned versus company-managed), and manage devices directly in Asset Panda. The integration imports network device data from Cisco Meraki into Asset Panda to improve visibility into deployed infrastructure.

Prerequisites

  • Active Asset Panda subscription

  • Cisco Meraki deployment in your organization

  • Admin access to both Cisco Meraki and Asset Panda

Generating a Cisco Meraki API Key

  1. Log in to the Cisco Meraki dashboard.

  2. Click your username in the top-right corner to open your profile.

  3. Scroll to the API access section.

  4. Click Generate new API key.

  5. Copy and securely store the API key. This key is used in Asset Panda to authenticate the connection.

Note: API access must be enabled under Organization > Settings > Dashboard API access.

Adding the Cisco Meraki Integration in Asset Panda

  1. Log in to Asset Panda as an administrator.

  2. Go to Settings > Account Management.

  3. Under the appropriate module, click Manage under Integrations.

  4. Open the Integration Store.

  5. Find the Cisco Meraki tile and click Add.

  6. Switch to the Integrations in this module tab.

  7. Locate the Cisco Meraki tile and click Configure.

  8. Once verified, click Continue with mapping to proceed.

Note: If the connection is valid, you should see a success message and a green checkmark above the Authentication tab.

Authenticating the Cisco Meraki Connection

Authorize data access between Cisco Meraki and Asset Panda by entering your API credentials. This establishes a secure connection that enables Asset Panda to retrieve device data from your Meraki environment and proceed with mapping configuration.

  1. On the authentication screen, enter the Meraki API Key.

  2. Provide the Organization ID.

  3. Click Test and save connection.

  4. If the test is successful, click Continue with Mapping to proceed to the field mapping configuration.

Creating a Mapping

Set up a mapping to define which type of Meraki data syncs with a specific collection in Asset Panda. Use the external entity selection to determine what kind of Meraki data to bring into Asset Panda:

  • Administrators: Import admin profiles for visibility into who manages network settings.

  • Network Clients: Sync connected client devices to track endpoints on the network.

  • Network Devices: Import Meraki-managed hardware such as routers, switches, and access points.

  • Networks: Bring in metadata and details about configured networks.

  • Organization Devices: Pull all devices associated with the Meraki organization for comprehensive inventory coverage.

  1. Click Add Mapping.

  2. Enter a Mapping Name (e.g., "Meraki Devices Import").

  3. Sync direction is set to one-way from Meraki to Asset Panda by default.

  4. Select External Entity: Devices.

  5. Choose the Collection in Asset Panda where the Meraki data is stored.

Configuring Field Mapping

Map specific data fields from Cisco Meraki to fields in the selected Asset Panda collection to ensure accurate and reliable data import.

  1. In the mapping configuration, select a Unique Identifier from the available Meraki fields. Only fields with guaranteed uniqueness should be used as identifiers. The following options are supported:

    • Network ID: A unique ID representing each Meraki network. Recommended unique identifier when syncing network-level records.

    • Name: The name assigned to a network or device. Use only if naming conventions ensure uniqueness.

    • Organization ID: The identifier of the Meraki organization. Not suitable as a record-level unique identifier.

    • Product types: General device categories (e.g., wireless, switch). Not unique.

    • Tags: Custom metadata labels. Use only if standardized and uniquely applied.

    • Time zone: Network’s configured time zone. Not appropriate for uniqueness.

  2. Map the selected Meraki field to a unique field in the Asset Panda collection.

  3. Add additional fields from Meraki to sync into Asset Panda, such as model, status, IP address, or assigned configuration. Only fields marked as unique in Asset Panda collections are available for use as unique identifiers.

  4. Click Save to complete the integration mapping.

PreviousApple Business Manager IntegrationNextJamf Pro Integration

Last updated