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.

In order to set up an integration with Meraki, you will need:

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

    At any time, you can come back to your Hudu admin area >> Integrations >> Cisco Meraki to make changes to the integration.


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 device information from Meraki, sorted into asset layouts based on set sort rules and your primary sync location(s).

What Hudu needs from Cisco Meraki

  • API Key



Enabling Integrations

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.


Obtaining the Cisco Meraki information

  • Navigate to your Cisco Meraki portal.
  • Navigate to Organization > Settings > API Access and make sure the option is set to "Enable access to the Cisco Meraki Dashboard API".
  • Once this is enabled, proceed to the avatar icon (on the top-right of the green ribbon) > My profile page to generate an API key.




  • Copy you Meraki API key into Hudu.
  • Save the settings.

    Make sure to test the integration for a successful connection before continuing; do not continue on until you see a connection successful message display.

  • 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).


Matching Organizations

Before your organizations (and their corresponding data) from Meraki can be brought into Hudu, they must first be matched to companies that either already exist within your Hudu environment; OR to companies that you create now. 


    Hudu recommends matching one company first, for testing purposes, to ensure that your information comes over correctly.

  • The first time your integration connection runs successfully, it will attempt to bring in organizations from Meraki; these are then added to the Matched Companies List of that integration.
    • Navigate to Hudu admin area >> Integrations >> and find Meraki from the list. Click into it.
    • It should now have a button that says Match Companies.
    • Go through the list of organizations and either bulk create/match all OR decide to:
      • Match the organization to an existing (already created) client in Hudu;
      • Create a matched client within Hudu from a Meraki organization;
      • Leave unmatched, organization (and corresponding data) will not be created/brought into Hudu.
  • Once you have matched your organizations, you must re-run the integration import to fill in all the data for the newly matched/created companies.



Select Primary Sync Location

The Meraki integration requires you to select a Primary Sync Location for Configurations that serves as your "junk drawer" asset layout; storing the information that is being pulled in, but not otherwise told where to be placed. 


  • Navigate back to your Hudu admin area >> Integrations >> Meraki ((Edit Settings)).
  • Choose asset layouts (must be active asset layouts) from the list to designate as the primary sync locations.

    If you don't see/have not created any asset layouts yet, you’ll need to create these. Visit Asset Layouts for additional information!


Skip Asset Types

  • Choose to skip importing devices

Additional Options

  • Choose whether you would like the following additional option to be automatically applied: 
    • Auto-update names of Assets. If name is changed in Meraki, the name will automatically be updated in Hudu.
    • Auto-archive deleted devices. If a device is deleted in Meraki, the device will automatically be moved to the Museum 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.

meraki_additional options.png


Sort Rules

Sort rules allow you to select which data types (from Cisco Meraki) will be mapped into which asset layouts (within Hudu). They allow you to specify certain "rules" for asset types as to where they get placed; any asset types that are brought in, but are not told where to be placed via sort rules, will be placed into the corresponding primary sync location.

The asset layouts that you're choosing to sort into can be created beforehand (Hudu admin area >> Asset Layouts; ensure that they're marked active) OR you can create new asset layouts here.


  • Save your settings and stop/start your integration sync again to reflect your changes.



How often do integrations sync?

Answer: Native integrations will automatically re-sync (update) every 3 hours.
You can also use either the global or the card-specific re-sync features to refresh native integration syncs at any point.

Why is my integration taking a long time to finish?

Answer: If the Meraki sync has been loading for a significant amount of time (it can take up to 10 minutes), follow the steps below:

    • Test the connection to ensure Hudu and Meraki are communicating correctly.
    • Verify your Meraki credentials.
    • Refresh the page (while a sync is actively running).
    • Stop the sync and restart the sync.
Accidentally deleted an integration card; how do I get this back?

Answer: It should appear on subsequent re-syncs. If it is still not appearing, ensure that it has not been archived; and still exists in your sort rules.

Notes: Active integrations sync automatically every 3 hours; manual re-syncs can be performed either within an integrations’ settings page or by clicking the top right re-sync button.

Was this article helpful?
0 out of 0 found this helpful