> For the complete documentation index, see [llms.txt](https://docs.influxtechnology.com/support_guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.influxtechnology.com/support_guides/dialog-user-guide/quick-start-guide/extracting-data-around-specific-triggers-using-batch-processing.md).
# Extracting data around specific triggers using Batch Processing
Select 'Batch Processing' to open the 'Export data' window'.
1. In the 'General' tab
* Enable Convert files
* Select the desired format for conversion, e.g., CSV
* Enable 'Convert each input file to separate output file.'
* Enable 'Extract only data around specific triggers.'
* Click 'Browse' and specify the location to store the output file(s) (select 'Make New Folder' to save the file(s) in a completely 'new folder').
* Click 'OK'
2. In the 'Input files' tab
* Click on the ‘Add file(s) for conversion’ icon.
* Select the desired IVD file.
* Click 'Open'.
This inputs the file to the Export data.
3. In the 'Trigger data filters' tab
* Set/define the 'Pre-Trigger time (sec)' and 'Post-Trigger time' (sec).
* Click 'Process'.
Wait whilst the processing is complete.
Click 'Close' once the processing is complete.
Click 'OK' to proceed.
The output files for each trigger event are saved at the specified location.
---
# 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://docs.influxtechnology.com/support_guides/dialog-user-guide/quick-start-guide/extracting-data-around-specific-triggers-using-batch-processing.md?ask=&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.
