> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/astera-data-stack-v6/dataflows/sources/excel-file-source.md).

# Excel File Source

Astera Excel File Source provides a high-speed reader for Excel files. Excel File Source supports both .xls and .xlsx files. You can start reading from any location within an Excel workbook. Excel File Source provides the following key features:

## **Layout Discrepancies**

In many instances, file formats are inconsistent with agreed upon layout. Astera provides the functionality to handle these inconsistencies. Inconsistencies include extra fields, out of sequence fields, inconsistent field headers.

## **Automatic Layout Building**

Astera provides the ability to build file layout automatically by reading the sample data file. This feature correctly determines data types most of the time. You can manually change data types in the layout grid.

## **Steps**

Adding an *Excel File Source* object allows you to transfer data from an Excel file. An example of what an Excel file source object looks like is shown below:

![](https://3768133094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH4WCHHphSt0ALtMJlqot%2Fuploads%2F9D6QMHlxB9VutaCml8HB%2F0.jpeg?alt=media)

To configure the properties of an *Excel File Source* object after it was added to the dataflow, right-click on it and select *Properties* from the context menu.


---

# 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://documentation.astera.com/astera-data-stack-v6/dataflows/sources/excel-file-source.md?ask=<question>&goal=<user_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.