> ## 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.

# Level

> Connect Level RMM to Triggr with a Level API key.

Triggr works with Level devices (with their hardware and network details) and groups, including creating groups for new clients.

## Set up Level

You need administrator access in Level, or a role with access to Settings.

<Steps>
  <Step title="Create an API key">
    Go to **Settings > API keys**, click **+ Create API key** and enter `Triggr` as the Description.
  </Step>

  <Step title="Choose the access">
    Choose Read-only if workflows only list devices and groups, or Read and write if they create groups or change anything. You can change this later without changing the key.
  </Step>

  <Step title="Copy the key">
    Click Create key and copy the key.
  </Step>
</Steps>

See Level's [API keys settings](https://docs.level.io/en/articles/13909289-api-keys-settings).

## Connect it in Triggr

<Steps>
  <Step title="Open the integration">
    Go to **Integrations > Level** 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="Enter the key">
    Paste the key into API Key, without a `Bearer` prefix, and click Save Configuration.

    <Frame>
      <img src="https://mintcdn.com/triggr/nyuVXZ1rouDTTEvu/images/level/configure.png?fit=max&auto=format&n=nyuVXZ1rouDTTEvu&q=85&s=32d59850b95418483a407cd420210859" alt="The Level 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/level/configure.png" />
    </Frame>
  </Step>
</Steps>

One key covers all your clients. For endpoints without a built-in action, use a Generic Integration Action step with URL Type set to Relative to base URL and a path such as `/v2/tags`. See Level's [API reference](https://developers.level.io).

## Troubleshooting

<AccordionGroup>
  <Accordion title="Every action fails with 401">
    Check the key was pasted in full with no `Bearer` prefix, and still exists under Settings > API keys. Deleting a key in Level revokes it straight away.
  </Accordion>

  <Accordion title="Creating a group fails with 403">
    The key is Read-only. Click Edit on the key in Level and change it to Read and write. Nothing changes in Triggr.
  </Accordion>

  <Accordion title="Lists stop at 20 records">
    Set the action's `limit` to up to 100. When `has_more` is `true`, pass the last record's ID in `startingAfter` to get the next page.
  </Accordion>

  <Accordion title="Requests fail with 429">
    Level's rate limit was reached. Spread large workflows out or run them in smaller batches.
  </Accordion>
</AccordionGroup>


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