Linking Cisco Meraki as a source
This source is currently in alpha. The interface and available tables may change.
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
Contents
The Cisco Meraki connector syncs network infrastructure data – networks, devices, device inventory, uplink statuses, and assurance alerts – into PostHog, so you can analyze network health alongside your product data.
Each connection imports one Meraki organization. All tables use full refresh sync.
Prerequisites
- A Cisco Meraki account with API access enabled
- An API key with administrator read permissions for the data you want to sync
- Your Meraki organization ID
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
When linking Cisco Meraki, you'll need:
- In the Meraki Dashboard, go to Organization > API & Webhooks > API keys and access. Create an API key and enable API access for your organization.
- Note your organization ID from Organization > Configure > Info in the Meraki Dashboard.
- Back in PostHog, select your region, enter the API key and Organization ID, then click Next.
- Select the tables you want to sync, set the sync frequency, then click Import.
Region selection
Choose the region that matches your Meraki organization:
| Region | Description |
|---|---|
| Global | Americas, Europe, Asia-Pacific (default) |
| Canada | Canada |
| China | China |
| India | India |
| US Government | US Government |
Changing the region requires re-entering your API key.
Available tables
| Table | Description | Sync method |
|---|---|---|
networks | Networks that the API key can access in the selected Meraki organization | Full refresh |
devices | Devices assigned to networks in the selected Meraki organization | Full refresh |
inventory_devices | Device inventory for the selected Meraki organization, including devices without an assigned network | Full refresh |
uplink_statuses | Current uplink status for MX, MG, and Z series devices in the selected Meraki organization | Full refresh |
assurance_alerts | Active health alerts for the selected Meraki organization. Resolved and dismissed alerts are excluded | Full refresh |
Full refresh tables reload all data on each sync.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Organization ID | text | Yes |
Region | select | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
networks | Networks that the API key can access in the selected Meraki organization. | Full refresh | — | — |
devices | Devices assigned to networks in the selected Meraki organization. | Full refresh | — | — |
inventory_devices | Device inventory for the selected Meraki organization, including devices without an assigned network. | Full refresh | — | — |
uplink_statuses | Current uplink status for MX, MG, and Z series devices in the selected Meraki organization. | Full refresh | — | — |
assurance_alerts | Active health alerts for the selected Meraki organization. Resolved and dismissed alerts are excluded. | Full refresh | — | — |
Troubleshooting
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.