Cisco Meraki Integration
You can integrate with Cisco Meraki to create a single source of truth for IT assets and mobile devices. The integration imports network device data from Cisco Meraki into Asset Panda Pro to improve visibility into the deployed infrastructure.
You can sync device data by type or configuration (such as company-owned versus company-managed), and manage devices directly in Asset Panda Pro. You can then identify the items that are currently deployed, in need of repair, or ready for replacement. Real-time tracking supports operational efficiency and cost control.
Prerequisites
Active Asset Panda subscription
Cisco Meraki deployment in your organization
Admin access to both Cisco Meraki and Asset Panda
Generate a Cisco Meraki API Key
You authorize data access between Cisco Meraki and Asset Panda by entering your API credentials via a key generated from Meraki. The key establishes a secure connection that enables Asset Panda Pro to retrieve device data from your Meraki environment.
API access must be enabled under Organization > Settings > Dashboard API access.
Log into the Cisco Meraki dashboard.
Click your username in the upper-right corner to open your profile.
Under API access, click Generate new API key.
Copy and securely store the API key. This key is used in Asset Panda Pro to authenticate the connection.
Add the Cisco Meraki Integration in Asset Panda
Log into Asset Panda Pro with an administrator account
Navigate to
Settings > Account Management.Expand the appropriate account and module.
Click Manage in the Integrations card.
Select Integrations Store.
In the Cisco Meraki tile, click Add. The Integrations in this module tab is displayed.
In the Cisco Meraki tile, click Configure.
Enter the Meraki API Key
Click Test and save connection. If the connection is valid, a success message is displayed and a green check is displayed above the Authentication tab.
If the test is successful, click Continue with Mapping.
Create a mapping to define the Meraki data to sync with the Asset Panda Pro collection:
Click Add Mapping.
Enter a Mapping Name (for example,
Meraki Devices Import).
Sync direction is set to one-way from Meraki to Asset Panda Pro by default.
Select the External Entity to specify the 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.
Choose the Collection in Asset Panda where the Meraki data will be stored.
Configure field mapping to map Meraki fields to collection fields:
In the mapping configuration, select a Unique Identifier from the available Meraki fields. Only fields with guaranteed uniqueness should be used. The following options are supported:
Network ID: Unique ID representing each Meraki network. This is the recommended unique identifier when syncing network-level records.
Name: Name assigned to a network or device. Use only if naming conventions ensure uniqueness.
Organization ID: Identifier of the Meraki organization. This is not suitable as a record-level unique identifier.
Product types: General device categories (for example, wireless or switch). This value is not unique.
Tags: Custom metadata labels. Use only if standardized and uniquely applied.
Time zone: Network’s configured time zone. This value is not appropriate for uniqueness.
Map the selected Meraki field to a unique field in the Asset Panda Pro collection.
Add additional fields from Meraki to sync into Asset Panda Pro, 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.
Click Save to complete the integration mapping.
Last updated