Creating an extended integration for Cisco Meraki assets

Sync Meraki with Oomnitza to gain visibility of your assets and to manage asset information.

The following extended integrations are available:

Cisco Meraki Inventory Asset Load

Returns the device inventory of an organization. See Meraki API Documentation: Get Organization Inventory Devices.

Cisco Meraki Network Devices Asset Load

Returns the devices in a network. See Meraki API Documentation: Get Network Devices.

Cisco Meraki SM Devices Asset Load

Returns the devices enrolled in Systems Manager (SM) network. An SM network is a cloud-based Enterprise Mobility Management (EMM) platform which is used to manage mobile and desktop devices. See Meraki API Documentation: Get Network SM Devices.

Cisco Meraki Asset Load

Returns all devices in an organization that have been assigned to a network. See Get Organization Devices.

Note
Replaces the Cisco Meraki basic integration.

Cisco Meraki Network Clients Asset Load

Returns the client devices that have used this network in a specified timespan. See Get Network Clients.

Before you start
Get organization and network ID
Adding credentials
Get API token
Creating the integration
Mappable fields

Before you start

To easily find the records that are uploaded to Oomnitza, it's best practice to create a dedicated user account for each integration. This will make it easier for you to retrieve the records that are uploaded to Oomnitza from the vendor application.

Creating integration users

Make life easy! Before you create the integration, retrieve the information from Meraki that you need to connect and authenticate with Cisco Meraki.

Integration

Connection information

Credentials

Inventory Asset Load

Asset Load

Network Clients Asset Load

Meraki Organization ID. See Get organization networks.

API token. See Authorization: Get your Meraki API Key.

Network Devices Asset Load

SM Devices Asset Load

Meraki Network ID. See Find your Meraki network ID.

API token. Authorization: Get your Meraki API Key

Get your Cisco Meraki Organization ID and Network ID

To get started with Cisco Meraki and Oomnitza, you need your Meraki Organization ID and Network ID. To retrieve this:

Log into Meraki.
Go to https://dashboard.meraki.com/api/v0/organizations and get the Organization ID. Your ID is returned in the id, for example [{"id":"1234567"}].
Go to https://dashboard.meraki.com/api/v0/organizations/{organization_id}/networks, enter the Organization ID you retrieved, and get the Network ID.

Add the value as a global variable so that when you create workflows that use presets the variable is automatically added. See Adding global settings.

The name of the variable is Meraki.Organization Id and you enter the Organization ID as the value.

Adding credentials

Get your Cisco Meraki API key

The Cisco Meraki API uses API Key authentication and requires your API key to be added to Oomnitza.

To obtain your API key, complete the following steps:

Log in to your Meraki account.
Go to Organization>Settings > Dashboard API access
Select the Enable access to the Cisco Meraki Dashboard API.
Select My Profile.
In the API access section, click Generate new API key
Copy your API key.

Best practice
Create a dedicated user account with its own credentials.

To authorize the connection, complete these steps:

In Oomnitza, click Configuration > Security > Credentials.
Click Add new credential (+).
Search for the integration, and then click the forward button > to select the integration.
Add your API key.
Click Create.

Integration not in the list? Click Advanced Mode and complete these steps:

Add the information details.
Click the AUTHORIZATION tab.
Ensure that API Key is selected as the Authorization type.
Ensure that the Token Name is X-Cisco-Meraki-API-Key
Enter the API Key.
In the Add to field, ensure that Header is selected.
Click Authenticate.
Click CREATE.

Creating the integration

In Oomnitza, click Configuration> Integrations> Overview.
Click Block view
Scroll down to the Extended section for asset integrations.
Click NEW INTEGRATION.
Select the integration in the sidebar.
Click ADD.

Integration details overview

More information is provided about the following fields to help you complete the integration:

Software data

Depending on the asset integration, an option might be available to ingest desktop software information such as the name and version of the software installed on an asset. To view the software information in Oomnitza, you must have the software module.

Installation types

Cloud. Store credentials in the Oomnitza cloud.
Local. Store credentials locally. If you want to sync Oomnitza with vendor applications that require AWS or OAUTH authentication, select cloud as the type of installation. Local installations don't support AWS and OAuth authentication.

Integration preferences

Create & Update. Add and update records.
Create only. Add records.
Update only. Update records.

Integration details

To review or update the integrations details, click Edit .

When you edit the Integration details section, you can select the name or names of integration contacts. Integration contacts will receive an in-app notification and an email, when the integration fails, when the integration fails to complete within 24 hours, or when the scheduled integration fails to run.

Update the integration name.
Select an installation type.
For integration preferences, select an option.
Enter the name of the integration user.

Credential details

If you selected Cloud as the installation type, choose one of the following options:

Select the credentials that were created for the integration.
Edit the credentials that were created for the integration.
Create new credentials

Scheduling the integration

By default, data is synced once every day. Change the interval or the time so that the data is streamed when your system isn't busy.

Click Edit .
Make and save your changes.

Mapping fields to Oomnitza

To map the fields to Oomnitza, click Edit .

Select Edit integration to add rules for syncing data. Filtering integration results.

Click SMART MAPPING.

You can add new fields to your integration by selecting Add new field on the mapping page.
Creating custom API fields.

Create custom mappings

Map Meraki fields to Oomnitza fields to get the asset information that you need. For the field mapping, it is recommended to follow these steps:

Click Smart Mapping to automatically add Meraki fields to Oomnitza. Values from the integration can also be dragged to the appropriate field on the Oomnitza side, or selected from the integration field dropdown.
Create a custom mapping for the Network ID field. To create a custom mapping, do the following:
1. Click the down arrow on the Network Id field.
2. Select Add new Oomnitza assets field.
3. Change the name of the field to Meraki Network ID.
4. Click CREATE.
Assign a sync key such as the serial number.
Click UPDATE.

Mappable fields

Cisco Meraki Inventory to Oomnitza mappings

Claimed At
Connector Sync Time
Device Name
License Expiration Date
MAC Address
Model
Network Id
Order Number
Product Type
Serial Number
Tags List

Cisco Meraki SM Devices to Oomnitza mappings

Connector Sync Time
IMEI
Last User
Location
MEID
Name
OS
Owner Email
Phone Number
Public IP Address
SSID
Serial Number
System Model
System Type
Wifi MAC Address

Cisco Meraki Asset Load to Oomnitza mappings

Address
Beacon Id Params Major
Beacon Id Params Minor
Beacon Id Params Uuid
Connect: Credentials
Connect: Organization Id
Connector Sync Time
Firmware
Floor Plan Id
Lan Ip
Lat
Lng
Mac
Model
Name
Network Id
Notes
Serial Number
Tags List
Url
Wan1 Ip
Wan2 Ip

Cisco Meraki Network Clients Asset Load to Oomnitza mappings

Adaptative Policy Group
Connector Sync Time
Description
Device Type Prediction
ID
First Seen
Group Policy 8021x
IP Address
IP Address v6
Last Seen
Local IP Address v6
Mac Address
Manufacturer
MCG Network ID
MCG Node MAC
MCG Node Name
MCG Serial
Named VLAN
Network ID
Network Name
Notes
Operating System
PSK Group
Recent Device Connection
Recent Device MAC Address
Recent Device Name
Recent Device Serial Number
SM Installed?
SSID
Status
Switch Port
User
VLAN
Wireless Capabilities

Did you know?
You can define rules for your integration by selecting Edit integration on the mapping page. For example, you may only want to run the integration if a certain contact or region exists. See Filtering integration results.

You can add new fields to your integration by selecting Add new field on the mapping page. All you need to do is specify the property name. See Creating custom API fields.

Launching the integration

Your integration is in Draft mode until the required mandatory fields are added. When added, click Launch to activate your integration.

If you selected Cloud as the installation type when creating the integration, see Running an extended integration

If you selected Local as the installation type when creating the integration, see Running an extended integration locally.

Viewing data ingested by Oomnitza

Viewing ingested asset data

For asset integrations, click Hardware. If the asset integration also ingests software data, click Software.

Viewing ingested user data

For user integrations, click People. If you chose the option to ingest User and SaaS user data, click Software > SaaS, click the SaaS app, and then click the Users tab.

Contents