Best Practices

Recommended setup

Start with Organization devices

This entity gives you the most actionable snapshot of your infrastructure. Use it as the foundation for your first report, then layer in networks and admins as needed.

Use a read-only API key

Generate a dedicated API key with read-only access specifically for Coupler.io. This limits exposure if the key is ever compromised and makes it easy to revoke without affecting other integrations.

Join devices with networks

The Organization devices entity contains a network_id field. Use Coupler.io's Join transformation to enrich it with network names and types from Organization networks — much more useful for reporting than raw IDs.

Append across multiple organizations

If you manage more than one Meraki organization, add multiple sources in a single data flow and use Append to build a unified device or admin inventory across all orgs.

Data refresh and scheduling

Sync API request logs daily

Meraki has limited log retention for API requests. A daily refresh ensures you capture logs before they age out and disappear from the API response window.

Sync device status hourly for uptime monitoring

Device online/offline status is a point-in-time snapshot. If uptime tracking matters, schedule the Organization devices sync to run every hour so you catch outages before they go unnoticed.

Sync admin and SAML data weekly

Admin accounts and SAML configurations change infrequently. A weekly sync is usually enough for compliance reporting without putting unnecessary load on the Meraki API.

Performance optimization

Set a tight start date for API request logs

The Organization API requests entity can return enormous volumes of data if the start date is set too far back. Start with a 7–30 day window and expand only if you need historical analysis.

Split large orgs into separate data flows

If you have organizations with thousands of devices, consider putting each org's entities in its own data flow. This avoids hitting Meraki's 5 requests/second rate limit mid-sync and makes failures easier to debug.

Common pitfalls

Don't use your personal admin API key in production. If that account is ever removed from the organization, all syncs will immediately break. Always use a dedicated service account or a shared admin key.

Do

• Enable API access at the org level before setting up your data flow

• Use a dedicated read-only API key for Coupler.io

• Join devices and networks by network_id for richer reports

• Set a specific start date to limit data volume on first sync

Don't

• Use your personal Meraki admin key for automated syncs

• Set the start date years back on the API requests entity

• Expect device status to reflect real-time changes between syncs

• Assume a single API key has access to all orgs if you manage multiple