> 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/a-c-integrations/abnormal-ai-setup-for-workbench.md).
# Abnormal AI Setup for Workbench
The Abnormal AI integration allows Expel to apply our detection strategy to your Abnormal AI alerts and pull them into the Workbench queue for investigation and remediation.
## Prerequisites
1. You must have the [Organization Admin role](/workbench-setup/get-started/add-and-manage-users/user-role-rights.md) in Workbench to set up this integration.
2. You must have admin access in Abnormal AI to create an API token.
## Step 1: Create an Access Token
1. [Log in to Abnormal AI](https://portal.abnormalsecurity.com/) using an account with admin access.
2. Navigate to [**Settings > Integrations**](https://portal.abnormalsecurity.com/home/settings/integrations).
3. Select **Abnormal REST API**.
4. An integration page for your organization displays, showing a unique API access token. **Copy and paste the token to a safe place** as you will need to enter this into Workbench later.
5. In the **IP Safelist field**, enter the list of IP addresses provided in [Configure an IP Allow List](/workbench-setup/configure-an-ip-allow-list.md) in a comma-separated list.
6. Select **Save**.
## Step 2: Add Abnormal AI as a Security Device in Workbench
Now that you have an access token, you can configure the integration in Workbench.
1. [Log in to Workbench](https://workbench.expel.io/auth/login?orig=%2F).
2. In the side menu, navigate to **Organization Settings > Security Devices**.
3. Select **Add Security Device**.
4. In the search box, type “Abnormal” and then select the **Abnormal AI** integration.
5. 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 Abnormal AI”; 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.
* **Abnormal Security API** endpoint URL - enter `https://api.abnormalplatform.com`. For EU-based tenants enter `https://eu.rest.abnormalsecurity.com` .
* **Abnormal Security API authentication token** - enter the API token you saved in [Step 1](#step-1-create-an-access-token).
6. Select **Save**.
7. On the console access screen, select **No thanks, I will not provide console access** from the dropdown.
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 and receiving data.
* To check on the status, select the downward arrow for your device in the first column and choose **View details**.
* Polling will happen first; data will be received after that. **You must refresh the page to see updates.**
* If your device does not begin polling within 15 minutes, and does not begin receiving data within 30 minutes, [contact our support team for help](/support/how-to-reach-us.md).
* To check if alerts are coming through, navigate to **Dashboards > Alert Analysis**. Scroll to the device you want to check, and select the **Expel Alerts** tab to reveal more alert information. It can take 36 to 72 hours for alerts to appear after setup, as we [tune your device](/workbench-reference/alerts/how-expel-alerts-work.md#device-tuning).
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.expel.io/connect-your-technology/a-c-integrations/abnormal-ai-setup-for-workbench.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.