Skip to main content
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.
1

Create an API key

Go to Settings > API keys, click + Create API key and enter Triggr as the Description.
2

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

Copy the key

Click Create key and copy the key.
See Level’s API keys settings.

​
Connect it in Triggr

1

Open the integration

Go to Integrations > Level 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

Enter the key

Paste the key into API Key, without a Bearer prefix, and click Save Configuration.
The Level configuration window with an API Key field, an Allow insecure TLS switch under Advanced, and a Save Configuration button.
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.

​
Troubleshooting

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.
The key is Read-only. Click Edit on the key in Level and change it to Read and write. Nothing changes in Triggr.
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.
Level’s rate limit was reached. Spread large workflows out or run them in smaller batches.