> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/connectors-and-triggers/connectors/structured-data/influxdb.md).

# InfluxDB

Discover more about the InfluxDB connector and how to use it on the Digibee Integration Platform.

{% hint style="info" %}
The content of this documentation is under revision and may change. We appreciate your understanding as we work to improve it.
{% endhint %}

**InfluxDB** interacts with InfluxDB v1, a time series database.

## **Parameters**

Take a look at the configuration options for the component. Parameters supported by [Double Braces expressions](/documentation/connectors-and-triggers/double-braces/overview.md) are marked with `(DB)`.

### **General tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Connection Bean</strong> <code>(DB)</code></td><td>Connection to the Influx database. The class should be InfluxDB.class.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Fail On Error</strong></td><td>If the option is activated, the pipeline's execution with an error will be interrupted. Otherwise, the pipeline execution proceeds, but the result will show a false value for the <code>"success"</code> property.</td><td>False</td><td>Boolean</td></tr></tbody></table>

### **Optional tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Auto Create Database</strong></td><td>Define if the database should be created automatically if it doesn’t exist.</td><td>False</td><td>Boolean</td></tr><tr><td><strong>Batch</strong></td><td>Define whether this operation is a batch operation or not.</td><td>False</td><td>Boolean</td></tr><tr><td><strong>Check Database Existence</strong></td><td>Define whether to verify the existence of the database when starting the endpoint.</td><td>False</td><td>Boolean</td></tr><tr><td><strong>Database Name</strong> <code>(DB)</code></td><td>The name of the database where the time series will be stored.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Operation</strong> <code>(DB)</code></td><td>Define whether this operation is an insert or a query.</td><td>insert</td><td>String</td></tr><tr><td><strong>Query</strong> <code>(DB)</code></td><td>Define the query to be executed when the operation is “query”.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Retention Policy</strong> <code>(DB)</code></td><td>The string that specifies the retention policy for data created by the endpoint.</td><td>default</td><td>String</td></tr></tbody></table>

### **Headers tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Retention Policy</strong> <code>(DB)</code></td><td>The string that specifies the retention policy for data created by the endpoint.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Database Name</strong> <code>(DB)</code></td><td>The name of the database where the time series will be stored.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Query</strong> <code>(DB)</code></td><td>Define the query to be executed when the operation is “query”.</td><td>N/A</td><td>String</td></tr></tbody></table>

### **Documentation tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Documentation</strong></td><td>Section for documenting any necessary information about the connector configuration and business rules.</td><td>N/A</td><td>String</td></tr></tbody></table>


---

# 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.digibee.com/documentation/connectors-and-triggers/connectors/structured-data/influxdb.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.