---
title: Automatic import
description: Automatic Import helps you quickly parse, ingest, and create ECS mappings for data from sources that don’t yet have prebuilt Elastic integrations. This...
url: https://www.elastic.co/elastic/docs-builder/docs/2422/solutions/security/get-started/automatic-import
products:
  - Elastic Cloud Serverless
  - Elastic Security
---

# Automatic import
Automatic Import helps you quickly parse, ingest, and create [ECS mappings](https://www.elastic.co/elasticsearch/common-schema) for data from sources that don’t yet have prebuilt Elastic integrations. This can accelerate your migration to Elastic Security, and help you quickly add new data sources to an existing SIEM solution in Elastic Security. Automatic Import uses a large language model (LLM) with specialized instructions to quickly analyze your source data and create a custom integration.
While Elastic has 400+ [prebuilt data integrations](https://docs.elastic.co/en/integrations), Automatic Import helps you extend data coverage to other security-relevant technologies and applications. Elastic integrations (including those created by Automatic Import) normalize data to [the Elastic Common Schema (ECS)](https://docs-v3-preview.elastic.dev/elastic/docs-builder/docs/2422/reference/ecs), which creates uniformity across dashboards, search, alerts, machine learning, and more.
<tip>
  Click [here](https://elastic.navattic.com/automatic-import) to access an interactive demo that shows the feature in action, before setting it up yourself.
</tip>

<admonition title="Requirements">
  - A working [LLM connector](https://www.elastic.co/elastic/docs-builder/docs/2422/explore-analyze/ai-features/llm-guides/llm-connectors).
  - Elastic Stack users: An [Enterprise](https://www.elastic.co/pricing) subscription.
  - Serverless users: a project with the [Security Analytics Complete](https://www.elastic.co/elastic/docs-builder/docs/2422/deploy-manage/deploy/elastic-cloud/project-settings) feature tier.
  - A sample of the data you want to import.
</admonition>

<admonition title="Notes on sample data">
  To use Automatic Import, you must provide a sample of the data you wish to import. An LLM will process that sample and automatically create an integration suitable for processing the data represented by the sample. **Automatic Import supports the following sample formats: JSON, NDJSON, CSV, and syslog (structured and unstructured).**
  - You can upload a sample of arbitrary size. The LLM will detect its format and select up to 100 documents for detailed analysis.
  - The more variety in your sample, the more accurate the pipeline will be. For best results, include a wide range of unique log entries in your sample instead of repeating similar logs.
  - When uploading a CSV, a header with column names will be automatically recognized. However if the header is not present, the LLM will still attempt to create descriptive field names based on field formats and values.
  - For JSON and NDJSON samples, each object in your sample should represent an event, and you should avoid deeply nested object structures.
  - When you select `API (CEL input)` as one of the sources, you will be prompted to provide the associated OpenAPI specification (OAS) file to generate a CEL program that consumes this API.

  <warning>
    Note that CEL generation in Automatic Import is in beta and is subject to change. The design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features.
  </warning>
</admonition>

<admonition title="Recommended models">
  You can use Automatic Import with any LLM, however model performance varies. Model performance for Automatic Import is similar to model performance for Attack Discovery; models that perform well for Attack Discovery perform well for Automatic Import. Refer to the [large language model performance matrix](https://www.elastic.co/elastic/docs-builder/docs/2422/solutions/security/ai/large-language-model-performance-matrix).
</admonition>

<important>
  Using Automatic Import allows users to create new third-party data integrations through the use of third-party generative AI models (“GAI models”). Any third-party GAI models that you choose to use are owned and operated by their respective providers. Elastic does not own or control these third-party GAI models, nor does it influence their design, training, or data-handling practices. Using third-party GAI models with Elastic solutions, and using your data with third-party GAI models is at your discretion. Elastic bears no responsibility or liability for the content, operation, or use of these third-party GAI models, nor for any potential loss or damage arising from their use. Users are advised to exercise caution when using GAI models with personal, sensitive, or confidential information, as data submitted may be used to train the models or for other purposes. Elastic recommends familiarizing yourself with the development practices and terms of use of any third-party GAI models before use. You are responsible for ensuring that your use of Automatic Import complies with the terms and conditions of any third-party platform you connect with.
</important>


## Create a new custom integration

1. In Elastic Security, click **Add integrations**.
2. Under **Can’t find an integration?** click **Create new integration**.
   ![The Integrations page with the Create new integration button highlighted](https://www.elastic.co/elastic/docs-builder/docs/2422/solutions/images/security-auto-import-create-new-integration-button.png)
3. Click **Create integration**.
4. Select an [LLM connector](https://www.elastic.co/elastic/docs-builder/docs/2422/explore-analyze/ai-features/llm-guides/llm-connectors).
5. Define how your new integration will appear on the Integrations page by providing a **Title**, **Description**, and **Logo**.  Click **Next**.
6. Define your integration’s package name, which will prefix the imported event fields.
7. Define your **Data stream title**, **Data stream description**, and **Data stream name**. These fields appear on the integration’s configuration page to help identify the data stream it writes to.
8. Select your [**Data collection method**](https://docs-v3-preview.elastic.dev/elastic/docs-builder/docs/2422/reference/beats/filebeat/configuration-filebeat-options). This determines how your new integration will ingest the data (for example, from an S3 bucket, an HTTP endpoint, or a file stream).
   <admonition title="Importing CEL data">
   If you select **API (CEL input)**, you’ll have the additional option to upload the API’s OAS file here. After you do, the LLM will use it to determine which API endpoints (GET only), query parameters, and data structures to use in the new custom integration. You will then select which API endpoints to consume and your authentication method before uploading your sample data.
   </admonition>
9. Upload a sample of your data. Make sure to include all the types of events that you want the new integration to handle.
10. Click **Analyze logs**, then wait for processing to complete. This may take several minutes.
11. After processing is complete, the pipeline’s field mappings appear, including ECS and custom fields.
   ![The Automatic Import Review page showing proposed field mappings](https://www.elastic.co/elastic/docs-builder/docs/2422/solutions/images/security-auto-import-review-integration-page.png)
12. (Optional) After reviewing the proposed pipeline, you can fine-tune it by clicking **Edit pipeline**. Refer to the [Elastic Security ECS reference](https://www.elastic.co/elastic/docs-builder/docs/2422/reference/security/fields-and-object-schemas/siem-field-reference) to learn more about formatting field mappings. When you’re satisfied with your changes, click **Save**.
   <admonition title="How to edit a CEL program">
   If your new integration collects data from an API, you can update the CEL input configuration (program and API authentication information) from the new integration’s integration policy.
   </admonition>
   ![A gif showing the user clicking the edit pipeline button and viewing the ingest pipeline flyout](https://www.elastic.co/elastic/docs-builder/docs/2422/solutions/images/security-auto-import-edit-pipeline.gif)
13. Click **Add to Elastic**. After the **Success** message appears, your new integration will be available on the Integrations page.
   ![The automatic import success message](https://www.elastic.co/elastic/docs-builder/docs/2422/solutions/images/security-auto-import-success-message.png)
14. Click **Add to an agent** to deploy your new integration and start collecting data, or click **View integration** to view detailed information about your new integration.
15. (Optional) Once you’ve added an integration, you can edit the ingest pipeline by going to the **Ingest Pipelines** page using the navigation menu or the [global search field](https://www.elastic.co/elastic/docs-builder/docs/2422/explore-analyze/find-and-organize/find-apps-and-objects).

<tip>
  You can use the [Data Quality dashboard](https://www.elastic.co/elastic/docs-builder/docs/2422/solutions/security/dashboards/data-quality-dashboard) to check the health of your data ingest pipelines and field mappings.
</tip>