# Abnormal Security

> Act on what Abnormal Security, the AI email security platform, finds: read and remediate threats, acknowledge account takeover cases, review emails employees report, check vendors and employees, and report emails it got wrong. Start a workflow when a threat, case, reported campaign or vendor case arrives.

App · 25 actions. Web page: https://docs.lodol.com/docs/integrations/abnormal-security

## Actions

### Get AI Security Mailbox campaign

Get a campaign employees reported: its subject, sender, who received it, when it was reported and Abnormal's judgement.

**Inputs**

- Campaign ID (`campaign`, text, required): The reported campaign's ID, such as fff51768-c446-34e1-97a8-9802c29c3ebd, from 'List AI Security Mailbox campaigns' or a trigger.

**Outputs**

- `attack_type` (text): The kind of attack, for malicious or spam ones
- `campaign_id` (text): The campaign's ID
- `first_reported` (text): When it was first reported (ISO 8601)
- `from_address` (text): The sender's email address
- `from_name` (text): The sender's display name
- `judgement` (text): Abnormal's judgement, such as Malicious
- `last_reported` (text): When it was last reported (ISO 8601)
- `message_id` (text): Its first message's ID in Abnormal
- `recipient_address` (text): The recipient's email address
- `recipient_name` (text): The recipient's display name
- `subject` (text): Its first email's subject
- `threat_id` (text): The threat it matches in the threat log; empty if none

**Example output**

```json
{
  "attack_type": "Malicious: Phishing",
  "campaign_id": "fff51768-c446-34e1-97a8-9802c29c3ebd",
  "first_reported": "2020-11-11T13:11:40-08:00",
  "from_address": "support@secure-reply.org",
  "from_name": "Support",
  "judgement": "Malicious",
  "last_reported": "2020-11-11T13:11:40-08:00",
  "message_id": "-1234567891011121314",
  "recipient_address": "example@example.com",
  "recipient_name": "Tom",
  "subject": "Fwd: This is spam",
  "threat_id": "184712ab-6d8b-47b3-89d3-a314efef79e2"
}
```

### Get case

Get an account takeover case: its status, severity, the employee it's about, its threats and Abnormal's summary.

**Inputs**

- Case ID (`case`, text, required): The case's ID, such as 1234, from 'List cases' or a trigger.

**Outputs**

- `affected_employee` (text): The employee it's about
- `ai_summary` (list): Abnormal's AI-written summary, point by point
- `analysis` (text): Abnormal's analysis
- `case_id` (text): The case's ID
- `confidence` (text): How sure Abnormal is: LOW, MEDIUM or HIGH
- `customer_visible_time` (text): When the case was shown to you (ISO 8601)
- `first_observed` (text): When the behaviour was first seen (ISO 8601)
- `remediation_status` (text): Not remediated, remediated or Remediation attempted
- `severity` (text): What kind of case it is, such as Potential Account Takeover
- `severity_level` (text): NONE, LOW, MEDIUM or HIGH
- `status` (text): Its status, such as Action Required
- `tenant` (text): The tenant it's in
- `threat_ids` (list): The threats tied to it

**Example output**

```json
{
  "affected_employee": "FirstName LastName",
  "ai_summary": [
    "Sign-in from a new country followed by a new mail rule."
  ],
  "analysis": "Signs in from an unusual location.",
  "case_id": "1234",
  "confidence": "HIGH",
  "customer_visible_time": "2020-06-09T17:42:59Z",
  "first_observed": "2020-06-09T17:42:59Z",
  "remediation_status": "Not remediated",
  "severity": "Potential Account Takeover",
  "severity_level": "HIGH",
  "status": "Action Required",
  "tenant": "my-tenant",
  "threat_ids": [
    "184712ab-6d8b-47b3-89d3-a314efef79e2"
  ]
}
```

### Get case action status

Check whether a change to a case is done, still running, or failed.

**Inputs**

- Case ID (`case`, text, required): The case's ID, such as 1234, from 'List cases' or a trigger.
- Request ID (`action_id`, text, required): The request's action_id, from 'Update case status'.

**Outputs**

- `action_id` (text): The request's ID
- `case_id` (text): The case
- `description` (text): What Abnormal says about it
- `done` (true/false): True once the request has finished
- `status` (text): acknowledged, in_progress, done or error

**Example output**

```json
{
  "action_id": "61e76395-40d3-4d78-b6a8-8b17634d0f5b",
  "case_id": "1234",
  "description": "The request was completed successfully",
  "done": true,
  "status": "done"
}
```

### Get case analysis

Get what Abnormal noticed about a case, such as impossible travel, and its timeline of sign-ins, mail rules and emails sent.

**Inputs**

- Case ID (`case`, text, required): The case's ID, such as 1234, from 'List cases' or a trigger.

**Outputs**

- `case_id` (text): The case
- `events` (list): The flagged events, as Abnormal's timeline lists them
- `insights` (list): What Abnormal noticed

**Example output**

```json
{
  "case_id": "1234",
  "events": [
    {
      "category": "Sign In Event",
      "description": "Suspicious Failed Sign In Attempt for foo@bar.com",
      "details": {
        "browser": "Chrome",
        "operating_system": "Windows 10"
      },
      "ip_address": "123.456.78.900",
      "location": "Aldie, Virginia, US",
      "timestamp": "2020-05-19T17:47:30Z",
      "title": "Suspicious Failed Sign In Attempt"
    }
  ],
  "insights": [
    {
      "description": "Signed in from two countries an hour apart.",
      "signal": "Impossible Travel"
    }
  ]
}
```

### Get employee

Get an employee's name, job title and manager, as Abnormal knows them.

**Inputs**

- Employee email (`email`, text, required): The employee's email address, such as tom@example.com.

**Outputs**

- `email` (text): Their email address
- `manager` (text): Their manager's email address
- `name` (text): Their name
- `title` (text): Their job title

**Example output**

```json
{
  "email": "example@example.com",
  "manager": "manager_email@example.com",
  "name": "Tom",
  "title": "General Manager"
}
```

### Get employee identity analysis

Get what's usual for an employee, such as the IP addresses, devices and places they sign in from, to compare a suspicious sign-in with.

**Inputs**

- Employee email (`email`, text, required): The employee's email address, such as tom@example.com.

**Outputs**

- `count` (number): How many traits
- `email` (text): The employee
- `traits` (list): What's usual for them, trait by trait

**Example output**

```json
{
  "count": 1,
  "email": "example@example.com",
  "traits": [
    {
      "description": "Common IP Addresses for user logins",
      "key": "ip_address",
      "name": "Common IP Addresses",
      "values": [
        {
          "count": 9,
          "share": 0.9,
          "value": "203.12.172.182"
        }
      ]
    }
  ]
}
```

### Get employee sign-ins

Get an employee's sign-ins over the last 30 days: when, from where, with which app and device, and whether each worked.

**Inputs**

- Employee email (`email`, text, required): The employee's email address, such as tom@example.com.

**Outputs**

- `count` (number): How many sign-ins
- `email` (text): The employee
- `logins` (list): Their sign-ins in the last 30 days

**Example output**

```json
{
  "count": 1,
  "email": "example@example.com",
  "logins": [
    {
      "app_display_name": "Office 365 Exchange Online",
      "app_id": "00000002-0000-0ff1-ce00-000000000000",
      "browser": "Chrome",
      "city": "Sydney",
      "client_app_used": "Browser",
      "country_or_region": "AU",
      "device_id": "",
      "ip_address": "203.12.172.182",
      "latitude": "-33.86",
      "longitude": "151.20",
      "operating_system": "Windows 10",
      "resource_display_name": "Office 365 Exchange Online",
      "state": "New South Wales",
      "status": "Success",
      "timestamp": "2026-11-04T08:15:02Z",
      "user_display_name": "Tom",
      "user_principal_name": "example@example.com"
    }
  ]
}
```

### Get message remediation history

Get each remediation status one email has had, such as Auto-Remediated, and the folder it's in now.

**Inputs**

- Message ID (`message_id`, text, required): The email's message_id, from 'Get threat', or its page in the Abnormal portal.

**Outputs**

- `folder_locations` (list): The mailbox folders it's in now, such as Junk
- `history` (list): Each remediation status it has had, oldest first
- `latest_status` (text): Its most recent remediation status
- `message_id` (text): The message

**Example output**

```json
{
  "folder_locations": [
    "Junk"
  ],
  "history": [
    {
      "at": "2023-04-11T20:54:56.244716+00:00",
      "status": "Auto-Remediated"
    }
  ],
  "latest_status": "Auto-Remediated",
  "message_id": "4551618356913732076"
}
```

### Get threat

Get a threat (an email campaign): its subject, sender, kind of attack, and each recipient's copy with its remediation status.

**Inputs**

- Threat ID (`threat`, text, required): The threat's ID, such as 184712ab-6d8b-47b3-89d3-a314efef79e2, from 'List threats' or a trigger.

**Outputs**

- `attack_strategy` (text): How it attacks, such as Name Impersonation
- `attack_type` (text): The kind of attack, such as Phishing: Credential
- `attack_vector` (text): What carries the attack, such as Link
- `from_address` (text): The sender's address, from its first message
- `from_name` (text): The sender's name, from its first message
- `impersonated_party` (text): Who it pretends to be, if anyone
- `message_count` (number): How many of its messages are listed
- `messages` (list): Its messages, one per recipient
- `portal_url` (text): Its first message's page in the Abnormal portal
- `received_time` (text): When its first message arrived (ISO 8601)
- `recipient_count` (number): How many people received it
- `remediation_status` (text): Its first message's remediation status
- `subject` (text): Its subject, from its first message
- `tenant_name` (text): The tenant it was found in
- `threat_id` (text): The threat's ID

**Example output**

```json
{
  "attack_strategy": "Name Impersonation",
  "attack_type": "Extortion",
  "attack_vector": "Text",
  "from_address": "support@secure-reply.org",
  "from_name": "Support",
  "impersonated_party": "None / Others",
  "message_count": 1,
  "messages": [
    {
      "attachment_count": 1,
      "attachment_names": [
        "attachment.pdf"
      ],
      "attack_score": 0.97,
      "attack_strategy": "Name Impersonation",
      "attack_type": "Extortion",
      "attack_vector": "Text",
      "attacked_party": "VIP",
      "auto_remediated": true,
      "cc_emails": [
        "cc@example.com"
      ],
      "from_address": "support@secure-reply.org",
      "from_name": "Support",
      "impersonated_party": "None / Others",
      "internet_message_id": "<5edfca1c.1c69fb81.4b055.8fd5@mx.google.com>",
      "is_read": true,
      "judgement": "Attack",
      "message_id": "4551618356913732076",
      "portal_url": "https://portal.abnormalsecurity.com/home/threat-center/remediation-history/4551618356913732076",
      "post_remediated": false,
      "received_time": "2020-06-09T17:42:59Z",
      "recipient_address": "example@example.com",
      "remediation_status": "Auto Remediated",
      "remediation_time": "2020-06-09T17:42:59Z",
      "reply_to_emails": [
        "reply-to@example.com"
      ],
      "return_path": "support@secure-reply.org",
      "sender_domain": "secure-reply.org",
      "sender_ip_address": "100.101.102.103",
      "sent_time": "2020-06-09T17:42:59Z",
      "subject": "Phishing Email",
      "summary_insights": [
        "Bitcoin Topics",
        "Personal Information Theft"
      ],
      "threat_id": "184712ab-6d8b-47b3-89d3-a314efef79e2",
      "to_addresses": "example@example.com, another@example.com",
      "url_count": 1,
      "urls": [
        "https://www.google.com/"
      ]
    }
  ],
  "portal_url": "https://portal.abnormalsecurity.com/home/threat-center/remediation-history/4551618356913732076",
  "received_time": "2020-06-09T17:42:59Z",
  "recipient_count": 2,
  "remediation_status": "Auto Remediated",
  "subject": "Phishing Email",
  "tenant_name": "example-tenant",
  "threat_id": "184712ab-6d8b-47b3-89d3-a314efef79e2"
}
```

### Get threat action status

Check whether a remediation request on a threat is done, still running, or failed.

**Inputs**

- Threat ID (`threat`, text, required): The threat's ID, such as 184712ab-6d8b-47b3-89d3-a314efef79e2, from 'List threats' or a trigger.
- Request ID (`action_id`, text, required): The request's action_id, from 'Remediate threat'.

**Outputs**

- `action_id` (text): The request's ID
- `description` (text): What Abnormal says about it
- `done` (true/false): True once the request has finished
- `status` (text): acknowledged, in_progress, done or error
- `threat_id` (text): The threat

**Example output**

```json
{
  "action_id": "a33a212a-89ff-461f-be34-ea52aff44a67",
  "description": "The request was completed successfully",
  "done": true,
  "status": "done",
  "threat_id": "184712ab-6d8b-47b3-89d3-a314efef79e2"
}
```

### Get threat links

List the links in a threat's emails, with their domains, such as to block them in a web filter.

**Inputs**

- Threat ID (`threat`, text, required): The threat's ID, such as 184712ab-6d8b-47b3-89d3-a314efef79e2, from 'List threats' or a trigger.

**Outputs**

- `count` (number): How many links
- `links` (list): The links in its messages
- `threat_id` (text): The threat

**Example output**

```json
{
  "count": 1,
  "links": [
    {
      "display_text": "This is not a spoof!",
      "domain": "lamronba.com",
      "link_type": "html href",
      "message_id": "4551618356913732076",
      "source": "body",
      "url": "http://spoof.lamronba.com"
    }
  ],
  "threat_id": "184712ab-6d8b-47b3-89d3-a314efef79e2"
}
```

### Get vendor

Get a vendor's risk level, the people on each side who email, where its email comes from and Abnormal's analysis.

**Inputs**

- Vendor (`vendor`, text, required): The vendor's domain, such as vendor.com.

**Outputs**

- `analysis` (list): Abnormal's analysis of the vendor
- `company_contacts` (list): Your mailboxes that deal with the vendor
- `countries` (list): Where the vendor's emails come from
- `domain` (text): The vendor's domain
- `ip_addresses` (list): The IP addresses the vendor's emails come from
- `risk_level` (text): Its risk level, such as High; empty unless details asked
- `tenant_name` (text): The tenant it's in
- `vendor_contacts` (list): The vendor's mailboxes your people deal with

**Example output**

```json
{
  "analysis": [
    "Vendor compromise observed in Abnormal Community"
  ],
  "company_contacts": [
    "bob@company.com"
  ],
  "countries": [
    "United States"
  ],
  "domain": "vendor.com",
  "ip_addresses": [
    "127.0.0.1"
  ],
  "risk_level": "High",
  "tenant_name": "example-tenant",
  "vendor_contacts": [
    "alice@vendor.com"
  ]
}
```

### Get vendor activity

Get what Abnormal has seen from a vendor: attacks from its domain, signals from other customers, and what Abnormal did.

**Inputs**

- Vendor (`vendor`, text, required): The vendor's domain, such as vendor.com.

**Outputs**

- `count` (number): How many events
- `domain` (text): The vendor's domain
- `events` (list): The vendor's activity, as Abnormal's timeline lists it

**Example output**

```json
{
  "count": 1,
  "domain": "vendor.com",
  "events": [
    {
      "action_taken": "Post Remediated",
      "attack_goal": "malware and ransom",
      "domain_ip": "",
      "event_type": "Targeted Attack",
      "has_engagement": false,
      "ip_country": "",
      "recipient": "bob@company.com",
      "suspicious_domain": "alice@vendor.com",
      "threat_id": "184712ab-6d8b-47b3-89d3-a314efef79e2",
      "timestamp": "2021-01-01T00:00:00Z"
    }
  ]
}
```

### Get vendor case

Get a vendor case: the vendor, what Abnormal noticed, and the emails involved.

**Inputs**

- Vendor case ID (`vendor_case`, text, required): The vendor case's ID, such as 42, from 'List vendor cases' or a trigger.

**Outputs**

- `domain` (text): The vendor's domain
- `first_observed` (text): When its first message arrived (ISO 8601)
- `insights` (list): What Abnormal noticed
- `last_modified` (text): When the case last changed (ISO 8601)
- `timeline` (list): The emails involved
- `vendor_case_id` (text): The vendor case's ID

**Example output**

```json
{
  "domain": "vendor.com",
  "first_observed": "2020-06-09T17:42:59Z",
  "insights": [
    {
      "description": "The sender's domain imitates the vendor's.",
      "highlight": "Look-alike domain"
    }
  ],
  "last_modified": "2020-06-09T17:42:59Z",
  "timeline": [
    {
      "marked_as": "Malicious",
      "recipient": "bob@company.com",
      "sender": "alice@vendor.com",
      "subject": "Click Me!",
      "threat_id": "184712ab-6d8b-47b3-89d3-a314efef79e2",
      "timestamp": "2021-01-01T00:00:00Z"
    }
  ],
  "vendor_case_id": "42"
}
```

### List AI Security Mailbox campaigns

List the IDs of campaigns employees reported to AI Security Mailbox (formerly Abuse Mailbox). Without dates, the last 24 hours.

**Inputs**

- From (`since`, date and time): Only campaigns on or after this date and time.
- To (`until`, date and time): Only campaigns on or before this date and time.
- Dates are (`date_field`, text): Which date From and To are about. Defaults to when it was last reported. One of: `lastReportedTime` (When it was last reported), `receivedTime` (When its first email was received).
- Sender (`sender`, text): Words in the sender's name or address.
- Recipient (`recipient`, text): Words in the recipient's name or address.
- Subject (`subject`, text): Words in the email's subject.
- Reporter (`reporter`, text): Words in the reporter's name or address.
- Attack type (`attack_type`, text): The kind of attack Abnormal judged it. One of: `Internal-to-Internal Attacks (Email Account Takeover)`, `Spam`, `Reconnaissance`, `Scam`, `Social Engineering (BEC)`, `Phishing: Credential`, `Invoice/Payment Fraud (BEC)`, `Malware`, `Extortion`, `Phishing: Sensitive Data`, `Other`.
- Judgement (`judgement`, text): What Abnormal judged it. One of: `All` (Any), `Malicious`, `Spam`, `Safe`.
- Sort by (`sort_by`, text): Defaults to when it was last reported. One of: `lastReportedTime` (When it was last reported), `receivedTime` (When its first email was received).
- Order (`sort_order`, text): Defaults to newest first. One of: `desc` (Newest first), `asc` (Oldest first).
- How many (`limit`, number): The most to list on a page, up to 500. Defaults to 100. From 1 to 500.
- Page (`page`, number): Which page to list, from 1. A list's next page is in its next_page. At least 1.

**Outputs**

- `campaigns` (list): The reported campaigns found, by ID
- `count` (number): How many are listed
- `next_page` (number): The next page to ask for; 0 when this is the last
- `page` (number): The page listed

**Example output**

```json
{
  "campaigns": [
    {
      "campaign_id": "fff51768-c446-34e1-97a8-9802c29c3ebd"
    }
  ],
  "count": 1,
  "next_page": 0,
  "page": 1
}
```

### List audit logs

List who did what in the Abnormal portal, such as viewing an email or remediating a threat. Abnormal keeps 90 days.

**Inputs**

- From (`since`, date and time): Only entries on or after this date and time.
- To (`until`, date and time): Only entries on or before this date and time.
- Category (`category`, text): Only these areas of the portal, separated by spaces, such as threat_log abuse_mailbox.
- Action (`action_name`, text): Only these actions, separated by spaces, such as view_message_content.
- Result (`status`, text): Only what succeeded, or what failed. One of: `SUCCESS` (Succeeded), `FAILURE` (Failed).
- Source IP (`source_ip`, text): Only what was done from this address.
- How many (`limit`, number): The most to list on a page, up to 100. Defaults to 100. From 1 to 100.
- Page (`page`, number): Which page to list, from 1. A list's next page is in its next_page. At least 1.

**Outputs**

- `audit_logs` (list): The audit log entries
- `count` (number): How many are listed
- `next_page` (number): The next page to ask for; 0 when this is the last
- `page` (number): The page listed

**Example output**

```json
{
  "audit_logs": [
    {
      "action": "view_message_content",
      "category": "threat_log",
      "message_id": "4551618356913732076",
      "reason": "Investigating a reported email",
      "recipient": "example@example.com",
      "request_url": "",
      "sender": "support@secure-reply.org",
      "source_ip": "203.0.113.7",
      "status": "SUCCESS",
      "subject": "Phishing Email",
      "tenant_name": "example-tenant",
      "timestamp": "2026-11-05T10:02:11Z",
      "user_email": "analyst@example.com"
    }
  ],
  "count": 1,
  "next_page": 0,
  "page": 1
}
```

### List cases

List account takeover cases, by when they last changed. Needs Abnormal's Account Takeover product.

**Inputs**

- From (`since`, date and time): Only cases changed on or after this date and time.
- To (`until`, date and time): Only cases changed on or before this date and time.
- How many (`limit`, number): The most to list on a page, up to 500. Defaults to 100. Counts only when a date is given. From 1 to 500.
- Page (`page`, number): Which page to list, from 1. A list's next page is in its next_page. At least 1.

**Outputs**

- `cases` (list): The cases found
- `count` (number): How many are listed
- `next_page` (number): The next page to ask for; 0 when this is the last
- `page` (number): The page listed

**Example output**

```json
{
  "cases": [
    {
      "case_id": "1234",
      "confidence": "HIGH",
      "created": "2020-06-09T17:42:59Z",
      "description": "Potential Account Takeover",
      "first_observed": "2020-06-09T17:42:59Z",
      "last_modified": "2020-06-09T18:02:00Z",
      "severity_level": "HIGH",
      "tenant": "my-tenant"
    }
  ],
  "count": 1,
  "next_page": 0,
  "page": 1
}
```

### List misclassification reports

List the false positives or missed attacks your organization reported (Detection 360), with where Abnormal is with each and its analysis. Without dates, the last 30 days.

**Inputs**

- Reports of (`inquiry_type`, text, required): False positives or missed attacks. One of: `FALSE_POSITIVE` (False positives), `MISSED_ATTACK` (Missed attacks).
- From (`since`, date and time): Only reports sent on or after this date and time.
- To (`until`, date and time): Only reports sent on or before this date and time.
- Statuses (`statuses`, list): Only reports in these statuses. Leave empty for all. One or more of: `UNREVIEWED`, `CONTAINING_ATTACK` (Containing the attack), `IMPROVING_PLATFORM` (Improving detection), `CORRECTING_JUDGEMENT` (Correcting the judgement), `RESOLVED`.

**Outputs**

- `count` (number): How many are listed
- `reports` (list): Your misclassification reports

**Example output**

```json
{
  "count": 1,
  "reports": [
    {
      "analysis": "The sender's new mail server looked unfamiliar.",
      "id": "5021",
      "inquiry_type": "FALSE_POSITIVE",
      "message_ids": [
        "4551618356913732076"
      ],
      "root_causes": [
        {
          "description": "The vendor moved to a new mail provider.",
          "name": "Unusual sender infrastructure"
        }
      ],
      "status": "RESOLVED",
      "submitted_at": "2026-11-02T15:20:00Z",
      "submitted_by_email": "lhching@bigcompany.com",
      "submitted_by_name": "Ching Li-Hsieh"
    }
  ]
}
```

### List reported emails not analyzed

List emails employees reported to AI Security Mailbox that Abnormal did not analyze, such as phishing simulations, and why. Without dates, the last 90 days.

**Inputs**

- From (`since`, date and time): Only reports on or after this date and time.
- To (`until`, date and time): Only reports on or before this date and time.
- Sort by (`sort_by`, text): Defaults to the date reported. One of: `dateReported` (Date reported), `subject`.
- Order (`sort_order`, text): Defaults to newest first. One of: `desc` (Newest first), `asc` (Oldest first).

**Outputs**

- `count` (number): How many are listed
- `reports` (list): The reported messages Abnormal did not analyze

**Example output**

```json
{
  "count": 1,
  "reports": [
    {
      "message_id": "7362810024012345678",
      "reason": "PHISHING_SIMULATION",
      "recipient_email": "lhching@bigcompany.com",
      "recipient_name": "Ching Li-Hsieh",
      "reported_at": "2026-11-05T09:12:00Z",
      "reporter_email": "lhching@bigcompany.com",
      "reporter_name": "Ching Li-Hsieh",
      "subject": "Read me"
    }
  ]
}
```

### List threats

List the IDs of threats in Abnormal's threat log, by when they were received or remediated, the kind of attack, sender, recipient or subject. Use 'Get threat' for each one's details.

**Inputs**

- From (`since`, date and time): Only threats on or after this date and time.
- To (`until`, date and time): Only threats on or before this date and time.
- Dates are (`date_field`, text): Which date From and To are about. Defaults to when it was received. One of: `receivedTime` (When it was received), `latestTimeRemediated` (When it was last remediated).
- Kind (`source`, text): Attacks, borderline emails, spam, or everything. Defaults to everything. One of: `all` (Everything), `attacks`, `borderline`, `spam`.
- Sender (`sender`, text): Words in the sender's name or address.
- Recipient (`recipient`, text): Words in the recipient's name or address.
- Subject (`subject`, text): Words in the email's subject.
- Topic (`topic`, text): What the email is about. One of: `Billing Account Update`, `Covid-19 Related Attack`, `Cryptocurrency`, `Invoice`, `Invoice Inquiry`.
- Attack type (`attack_type`, text): The kind of attack. One of: `Internal-to-Internal Attacks (Email Account Takeover)`, `Spam`, `Spam Bomb`, `Reconnaissance`, `Scam`, `Social Engineering (BEC)`, `Phishing: Credential`, `Invoice/Payment Fraud (BEC)`, `Malware`, `Extortion`, `Phishing: Sensitive Data`, `Other`.
- Attack vector (`attack_vector`, text): What carries the attack. One of: `Link`, `Attachment`, `Text`, `Others`, `Attachment with Zipped File`, `QR Code`, `Calendar Invite`.
- Attack strategy (`attack_strategy`, text): How the attack works. One of: `Name Impersonation`, `Internal Compromised Email Account`, `External Compromised Email Account`, `Spoofed Email`, `Unknown Sender`, `Covid 19 Related Attack`.
- Impersonated party (`impersonated_party`, text): Who the email pretends to be. One of: `VIP`, `Assistants`, `Employee (other)`, `Brand`, `Known Partners`, `Automated System (Internal)`, `Automated System (External)`, `Unknown Partner`, `None / Others`.
- Flagged by your own rules (`customer_override`, list): Only threats your own custom AI model, custom rules or blocklist flagged. One or more of: `Custom AI Model`, `Custom Rule`, `Customer Blocklist`.
- How many (`limit`, number): The most to list on a page, up to 500. Defaults to 100. Counts only when a date is given. From 1 to 500.
- Page (`page`, number): Which page to list, from 1. A list's next page is in its next_page. At least 1.

**Outputs**

- `count` (number): How many are listed
- `next_page` (number): The next page to ask for; 0 when this is the last
- `page` (number): The page listed
- `threats` (list): The threats found, by ID

**Example output**

```json
{
  "count": 1,
  "next_page": 0,
  "page": 1,
  "threats": [
    {
      "threat_id": "184712ab-6d8b-47b3-89d3-a314efef79e2"
    }
  ]
}
```

### List vendor cases

List the IDs of vendor cases: vendors whose email looks compromised. Use 'Get vendor case' for each one's details.

**Inputs**

- From (`since`, date and time): Only vendor cases on or after this date and time.
- To (`until`, date and time): Only vendor cases on or before this date and time.
- Dates are (`date_field`, text): Which date From and To are about. Defaults to when it last changed. One of: `lastModifiedTime` (When it last changed), `firstObservedTime` (When its first email arrived).
- How many (`limit`, number): The most to list on a page, up to 100. Defaults to 100. Counts only when a date is given. From 1 to 100.
- Page (`page`, number): Which page to list, from 1. A list's next page is in its next_page. At least 1.

**Outputs**

- `count` (number): How many are listed
- `next_page` (number): The next page to ask for; 0 when this is the last
- `page` (number): The page listed
- `vendor_cases` (list): The vendor cases found, by ID

**Example output**

```json
{
  "count": 1,
  "next_page": 0,
  "page": 1,
  "vendor_cases": [
    {
      "vendor_case_id": "42"
    }
  ]
}
```

### List vendors

List the vendors your organization emails with, riskiest first.

**Inputs**

- Include details (`include_details`, true/false): Add each vendor's risk level, contacts, countries and analysis. The token needs access to vendor details.
- How many (`limit`, number): The most to list on a page, up to 1,000. Defaults to 100. From 1 to 1000.
- Page (`page`, number): Which page to list, from 1. A list's next page is in its next_page. At least 1.

**Outputs**

- `count` (number): How many are listed
- `next_page` (number): The next page to ask for; 0 when this is the last
- `page` (number): The page listed
- `vendors` (list): The vendors, riskiest first

**Example output**

```json
{
  "count": 1,
  "next_page": 0,
  "page": 1,
  "vendors": [
    {
      "analysis": [
        "Vendor compromise observed in Abnormal Community"
      ],
      "company_contacts": [
        "bob@company.com"
      ],
      "countries": [
        "United States"
      ],
      "domain": "vendor.com",
      "ip_addresses": [
        "127.0.0.1"
      ],
      "risk_level": "High",
      "tenant_name": "example-tenant",
      "vendor_contacts": [
        "alice@vendor.com"
      ]
    }
  ]
}
```

### Remediate threat

Take a threat's emails out of every inbox, or put them back. Abnormal does it in the background: 'Get threat action status' says when it's done.

**Inputs**

- Threat ID (`threat`, text, required): The threat's ID, such as 184712ab-6d8b-47b3-89d3-a314efef79e2, from 'List threats' or a trigger.
- Remediation (`remediation`, text, required): Take the emails out of inboxes, or put them back. One of: `remediate` (Remediate: take it out of inboxes), `unremediate` (Unremediate: put it back in inboxes).

**Outputs**

- `action_id` (text): The request's ID, for 'Get threat action status'
- `remediation` (text): What was asked: remediate or unremediate
- `status_url` (text): Where Abnormal reports the request's progress
- `threat_id` (text): The threat

**Example output**

```json
{
  "action_id": "a33a212a-89ff-461f-be34-ea52aff44a67",
  "remediation": "remediate",
  "status_url": "https://api.abnormalplatform.com/v1/threats/184712ab-6d8b-47b3-89d3-a314efef79e2/actions/a33a212a-89ff-461f-be34-ea52aff44a67",
  "threat_id": "184712ab-6d8b-47b3-89d3-a314efef79e2"
}
```

### Report misclassified email

Tell Abnormal it flagged a safe email (a false positive), or missed an attack, spam or graymail, so it can review it. Abnormal's answer shows in 'List misclassification reports'.

**Inputs**

- What happened (`report_type`, text, required): A safe email was flagged, or an unwanted one was missed. One of: `false-positive` (False positive: a safe email was flagged), `missed-attack` (Missed attack), `missed-spam` (Missed spam), `missed-graymail` (Missed graymail (unwanted bulk email)).
- Portal link (`portal_link`, text): The flagged email's page in the Abnormal portal, such as the portal_url from 'Get threat'. Only when What happened is False positive: a safe email was flagged.
- Sender email (`sender_email`, text): Who sent the missed email. Only when What happened is Missed attack, Missed spam or Missed graymail (unwanted bulk email).
- Recipient email (`recipient_email`, text): Who received it. Only when What happened is Missed attack, Missed spam or Missed graymail (unwanted bulk email).
- Subject (`subject`, text): Its subject. Only when What happened is Missed attack, Missed spam or Missed graymail (unwanted bulk email).
- Received on (`received_date`, date): The day the email arrived.
- Details (`details`, text): Anything that helps Abnormal, such as who noticed and why.

**Outputs**

- `report_type` (text): What was reported, such as false-positive
- `submitted` (true/false): True once Abnormal accepted the report

**Example output**

```json
{
  "report_type": "false-positive",
  "submitted": true
}
```

### Update case status

Acknowledge a case (in progress, attack resolved or not an attack), mark it as needing action, or record that you remediated it yourself. 'Get case action status' says when it's done.

**Inputs**

- Case ID (`case`, text, required): The case's ID, such as 1234, from 'List cases' or a trigger.
- New status (`new_status`, text, required): What to set the case to. One of: `action_required` (Action required), `acknowledge_in_progress` (Acknowledged: in progress), `acknowledge_resolved` (Acknowledged: attack resolved), `acknowledge_not_an_attack` (Acknowledged: not an attack), `remediated_externally` (Remediated outside Abnormal).
- Resolution (`resolution`, text): Whether it was a real attack. Only when New status is Acknowledged: attack resolved. One of: `TRUE_POSITIVE` (True positive: it was an attack), `FALSE_POSITIVE` (False positive: it was not an attack), `TRUE_FALSE_POSITIVE` (True false positive), `UNKNOWN`.
- Comment (`comment`, text): How it was resolved, up to 4,000 characters. Only when New status is Acknowledged: attack resolved.

**Outputs**

- `action_id` (text): The request's ID, for 'Get case action status'
- `case_id` (text): The case
- `new_status` (text): What was asked, such as acknowledge_resolved
- `status_url` (text): Where Abnormal reports the request's progress

**Example output**

```json
{
  "action_id": "61e76395-40d3-4d78-b6a8-8b17634d0f5b",
  "case_id": "1234",
  "new_status": "acknowledge_resolved",
  "status_url": "https://api.abnormalplatform.com/v1/cases/1234/actions/61e76395-40d3-4d78-b6a8-8b17634d0f5b"
}
```
