Skip to main content
Triggr manages Meraki organisations, networks, devices, wireless SSIDs, MX security appliances, switch ports and clients.

​
Set up Cisco Meraki

The key has exactly the access of the administrator who generates it, and that administrator must sign in with a Meraki password, not SAML single sign-on.
1

Add an administrator for Triggr

In each organisation Triggr should work with, go to Organization > Configure > Administrators and click Add admin. Enter a Name such as Triggr and a mailbox you control, set Organization Access to Full (or Read-only if workflows only read data), click Create admin, then Save changes.
2

Generate an API key

Set the administrator’s password from Meraki’s email and sign in as them. Click the avatar in the top right to open My Profile, click Generate API key under API access and copy the key. Meraki shows it only once.
3

Allow Triggr's IP addresses, if you restrict API access

If an organisation uses Login IP ranges (Organization > Configure > Settings), add Triggr’s IP addresses to its API ranges, and to its dashboard ranges too if you’ve set both.
See Meraki’s Cisco Meraki Dashboard API guide.

​
Connect it in Triggr

1

Open the integration

Go to Integrations > Cisco Meraki and click Configure on the Base Configuration card.
The Base Configuration card with Status Not Configured, Admin Consent Not Required and a Configure button.
2

Paste the key

Paste it into API Key, without Bearer in front, and click Save Configuration.
The Cisco Meraki configuration window with an API Key field, an Allow insecure TLS switch under Advanced, and a Save Configuration button.
One key covers every organisation its administrator can access, with no client mapping. Each step takes the organizationId, networkId or device serial it acts on; List Organizations returns the organisations the key can reach. To replace the key, generate a new one in My Profile, paste it in via Edit on the Base Configuration card, then revoke the old one. Each administrator can have two keys at a time.

​
Troubleshooting

Meraki returns 404 for a missing or wrong key. Check it was pasted in full, without Bearer, and hasn’t been revoked. If only some actions fail, check the step’s IDs.
The administrator has Read-only access in that organisation. Change its Organization Access to Full.
Add the Triggr administrator to that organisation, and check its Login IP ranges include Triggr’s IP addresses. List Organizations ignores those ranges, so the organisation can appear there while other requests to it fail.
The account signs in through SAML. Use an administrator that signs in with a Meraki password.