> For the complete documentation index, see [llms.txt](https://www.center.daxium-air.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.center.daxium-air.com/user-documentation/build/building-the-reporting/report-types.md).

# Report Types

Overview of the different ways to generate and deliver reports automatically in Daxium-Air.

Instead of generating reports manually, you can configure Daxium-Air to produce and deliver them automatically. There are two types of automated reports.

## Automatic reports

Automatic reports generate your template as soon as a trigger condition is met. They are typically used when you want to generate one separate file per submission — for example, every time a submission is created or updated.

## Scheduled reports

Scheduled reports generate periodically (daily, weekly, monthly) and use **Listing mode** to compile data from multiple submissions into a single file. They are typically used for summary or aggregation reports sent to a team on a regular basis.

***

## Common setup

Both report types share the same initial configuration. Open the report template configuration, then complete the following steps.

1. **Rename** the output file.
2. **Select a format** (Word, Excel, PowerPoint).
3. **Set a time zone.**
4. Optionally **choose a** [**condition**](/user-documentation/build/building-forms/conditions.md) to limit which submissions are included. By default, generation runs on all submissions in the configured period.
5. To **send the generated report by email**, fill in the **Email** and **Recipient** fields.

![](https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2Fgit-blob-5e87d5a5e6decf0d1e6ba0543162418e325e5c4b%2Fdda3d7_45f95c65de6c426c919a57905e70182a~mv2.png?alt=media)

The **\</> Edit** button lets you insert form field values into the email subject or body.

![](https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2Fgit-blob-a5332c92ffb463fb867154c360ea8daf7b54cb40%2Fdda3d7_7287c092310d4547b4222b56152e6fa5~mv2.png?alt=media)

![](https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2Fgit-blob-0aa6395b4e4b8a85160a10f67a7e4a3c6224e8b1%2Fdda3d7_95dc41226d6c462ea27f159caece91d6~mv2.png?alt=media)

![](https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2Fgit-blob-b1a8a3b5dfed6f4fe6a8728a3d4a99a4bc7c4512%2Fdda3d7_3a52e9800da54ebfa83581c9a97dcacd~mv2.png?alt=media)

Once the common setup is complete, configure the type-specific settings on the child page:

* [Scheduled Reports](/user-documentation/build/building-the-reporting/report-types/scheduled-reports.md) — define the period and frequency
* [Automatic Reports](/user-documentation/build/building-the-reporting/report-types/automatic-reports.md) — define the trigger event


---

# 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://www.center.daxium-air.com/user-documentation/build/building-the-reporting/report-types.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.