---
title: AI Ingestion (AI)
slug: solutions/ai-ingestion-ai
docTags: 
createdAt: 2026-03-04T10:38:36.675Z
---

**AI Ingestion** stores records of ingestion configurations used to build vendor connectors and alert ingestion pipelines. Each record (for example, AI-1, AI-2) represents one ingestion setup.

1\) Open **AI Ingestion**

- Navigate to **Application Records** → **AI Ingestion** (in the AI Ingestion Workspace).
- Each record has a **Tracking Id** (prefix AI-), **Vendor Product**, **API Specification Uploaded**, **Asset Created/Used**, and **Name of component(s) generated**.

2\) What the application is for

- **Custom widget:** The application includes a custom widget with two modes: **Create Connector Actions as Components** (build Turbine components from an OpenAPI spec) and **Run the Ingestion Process** (build a full ingestion component with Hero AI–assisted TEDS mapping). Use the widget to add new records as you configure ingestion for each vendor or source.
- **Records:** Each record stores the outcome of a widget run (vendor, spec, asset, component names). Open a record to see details of that ingestion configuration.
- **Audit tab:** Use the **Audit** tab in the application to view ingestion activity and key fields (Vendor Product, API Specification Uploaded, Name of component(s) generated) without configuring reports.

3\) When to use it

- When you need to onboard a new alert source (SIEM, EDR, XDR, etc.) and build connector and ingestion components.
- When you want to review which ingestion configurations exist or which components were generated.
- For full step-by-step instructions, see [AI SOC Ingestion](docId:0p9Qwz3o-0J5DNkPJUGmq).