> ## Documentation Index
> Fetch the complete documentation index at: https://university.triggr-app.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cisco Meraki

> Connect your Cisco Meraki dashboard to Triggr with a Meraki administrator's dashboard API key.

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.

<Steps>
  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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](/security/ip-allowlist) to its API ranges, and to its dashboard ranges too if you've set both.
  </Step>
</Steps>

See Meraki's [Cisco Meraki Dashboard API](https://documentation.meraki.com/General_Administration/Other_Topics/Cisco_Meraki_Dashboard_API) guide.

## Connect it in Triggr

<Steps>
  <Step title="Open the integration">
    Go to **Integrations > Cisco Meraki** and click **Configure** on the Base Configuration card.

    <Frame>
      <img src="https://mintcdn.com/triggr/nyuVXZ1rouDTTEvu/images/integrations-common/base-configuration.png?fit=max&auto=format&n=nyuVXZ1rouDTTEvu&q=85&s=bb81acb082055015f91beda7b4876f35" alt="The Base Configuration card with Status Not Configured, Admin Consent Not Required and a Configure button." width="2272" height="330" data-path="images/integrations-common/base-configuration.png" />
    </Frame>
  </Step>

  <Step title="Paste the key">
    Paste it into API Key, without `Bearer` in front, and click **Save Configuration**.

    <Frame>
      <img src="https://mintcdn.com/triggr/MwzXHG3UWzFixdSz/images/cisco-meraki/configure.png?fit=max&auto=format&n=MwzXHG3UWzFixdSz&q=85&s=ec5b9dd934338aa2431e3cdb9afc90cc" alt="The Cisco Meraki configuration window with an API Key field, an Allow insecure TLS switch under Advanced, and a Save Configuration button." width="1344" height="898" data-path="images/cisco-meraki/configure.png" />
    </Frame>
  </Step>
</Steps>

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

<AccordionGroup>
  <Accordion title="404 Not Found on every request">
    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.
  </Accordion>

  <Accordion title="403 Forbidden when making changes">
    The administrator has Read-only access in that organisation. Change its Organization Access to Full.
  </Accordion>

  <Accordion title="Requests to one organisation are refused">
    Add the Triggr administrator to that organisation, and check its Login IP ranges include [Triggr's IP addresses](/security/ip-allowlist). List Organizations ignores those ranges, so the organisation can appear there while other requests to it fail.
  </Accordion>

  <Accordion title="No API access section on My Profile">
    The account signs in through SAML. Use an administrator that signs in with a Meraki password.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.