Cisco Meraki

One native integration that can be set up within Hudu is Cisco Meraki.

Before setting up your Cisco Meraki integration, please read over our Understanding Integrations article to learn basic concepts and useful tips.

What You'll Need

• Access to retrieve Meraki API credentials.
• Admin or Super-Admin user role within Hudu.

Integration Features

Hudu's integration with Cisco Meraki allows you to sync over:

• Organizations
  • Create client spaces within Hudu directly from Meraki organizations, or seamlessly merge them into existing (already-created) client spaces.
• Devices
  • Pull in Meraki device information into an asset layout based on your primary sync location.

What Hudu needs from Cisco Meraki

• API Key

Obtaining the Cisco Meraki information

• Navigate to your Cisco Meraki Dashboard.
• To generate an API key, go the My Profile page accessed via the avatar icon in the top right-hand corner of the dashboard. 
  • This API key will be associated with the dashboard administrator account which generates it and will inherit the same permissions as that account. You can generate, revoke and regenerate your API key on your profile.
    • Note: The Meraki API is enabled by default for the entire organization, however, if there are any Meraki clients with unlicensed devices, the API will be disabled. You will need to make sure to disable API access for any clients with unlicensed devices for the integration to work. 

• Copy you Meraki API key into Hudu.
• Save the settings.
• To limit API access to IP ranges, navigate to Organization > Settings > Security and list the IP ranges to allow and select "Allow Dashboard API access to these ranges".

• Start the sync. After inputting all settings and ensuring the connection was successful; start the sync to push initial data to Hudu from Meraki (this is required before moving on).

Enabling the Integration

Integrations can be enabled at any point during your Hudu environment testing and/or during production. Integrations can be merged into your existing documentation based on set rules; providing the ability to start with integration setup, or easily connect them at a later date. To enable the Meraki integration:

• Navigate to Hudu admin area → Integrations.
• Select Cisco Meraki from the list.

Setting up the Integration in Hudu

Step 1. Connect to Meraki

• Enter your Meraki API Key
• Select asset types to skip (optional)
• Select any additional options (optional):
  • Auto-update names of Assets - If name is changed in Meraki, the name will automatically be updated in Hudu
  • Do not update basic company details - This will prevent the company details from being changed in Hudu if they are changed in Meraki
  • Match assets on primary serial - This option tells Meraki to match devices using their primary serial number. It helps ensure that assets are correctly identified and reduces the chance of duplicates when device names or other attributes change.

Step 2. Test connection and run an initial sync

• Navigate to the Integration Overview page

• Click Test Connection

• If the test is successful, start an initial sync

Step 3. Match Meraki Organizations

• Stop and restart the sync to pull in Meraki Organizations

• Organizations are added to the Matched Companies List for the integration

  • Before Meraki Organizations (and their associated data) can be imported into Hudu, they must be matched to:

    • Existing companies already in Hudu, or

    • New companies created during the matching process

    • Hudu recommends matching one company first to verify data imports correctly

• To access company matching:

• Navigate to Hudu Admin → Integrations

• Locate Meraki

• Click into the integration

• Click Match Companies

• For each company, choose one of the following options:

  • Match the company to an existing Hudu client

  • Create a new Hudu client from the Meraki company

  • Leave the company unmatched (the company and associated data will not be imported)

• Save the Settings

Step 4. Run another sync

• This sync will bring in the Meraki device types

Step 5. Choose where Meraki data will fill to

• Select Default Asset Layout for configurations

  • Choose asset layout (must be an active asset layout) from the list to designate as the primary sync location

• Add Sort Rules

  • Sort Rules determine how data types from Meraki are mapped to asset layouts in Hudu

  • They let you define specific rules that control where each asset type is placed

  • Any asset types imported without an assigned Sort Rule will automatically be placed into the default asset layout

  • Asset layouts used for Sort Rules can be created ahead of time in the Hudu admin area (Admin → Asset Layouts) and must be marked as Active

  • You can also create new asset layouts directly from this section if needed

• Save the Settings

Step 6. Run a final sync

• Stop and restart the sync to pull in Meraki devices

FAQ