> For the complete documentation index, see [llms.txt](https://docs.expel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expel.io/connect-your-technology/l-p-integrations/logz.io-setup-for-workbench.md).
# Logz.io Setup for Workbench
## Prerequisites
1. A Logz.io account with Enterprise or Pro plan subscription.
{% hint style="info" %}
[Logz.io Community plans don't currently include API tokens.](https://docs.logz.io/docs/user-guide/admin/authentication-tokens/api-tokens/)
{% endhint %}
2. Admin permissions for the Logz.io account to view the Manage Tokens page. *If you’re not an admin user for the account, consult with an account admin to get the token information.*
## Step 1: Create an API token
1. In Logz.io, navigate to  **> Settings > Tools > Manage Tokens > API tokens**.
2. To create an API token, select **+ New API token**.
3. Enter a brief token **name** and click **Add**.
4. **Save the token value** in a safe place for later use.
## Step 2: Add Logz.io as a Security Device in Workbench
Now that you have the API token, you can integrate your Logz.io installation with the Expel Workbench.
1. [Log in to Workbench](https://workbench.expel.io/).
2. In the side menu, navigate to **Organization Settings > Security Devices**.
3. In the search box, search for and select the **Logz.io** integration.
4. A configuration pane displays. Complete the fields as follows:
* **Name** - enter a name that might help you more easily identify this integration, such as “CompanyName Logz.io”; this name will display in Workbench under the Name column, and is a text string that you can filter on.
* **Location** - enter the location of your integration, for example “cloud;” this is also a text string that you can filter on, so we recommend being consistent with location naming across your Expel integrations.
* API token - enter the token you created in [Step 1](#h_01hye5xawm0jyqxar2tptqem7k).
5. Click **Save**.
Your device should be created successfully within a few seconds. A few reminders:
* After your connection is healthy, it will take some time for your device to begin polling.
* To check on the status, select the downward arrow for your device in the first column and choose **View details**.
* If your device does not begin polling within 15 minutes, [contact our support team](/support/how-to-reach-us.md) for help. You must refresh the page to see updates.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.expel.io/connect-your-technology/l-p-integrations/logz.io-setup-for-workbench.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.