# InfluxDB Cloud AI integration on Definable

> InfluxDB Cloud is a fully managed, scalable, and secure time series database service designed for real-time analytics and monitoring.

## What this connects

InfluxDB Cloud is a fully managed, scalable, and secure time series database service designed for real-time analytics and monitoring.

Vendor: https://cloud2.influxdata.com/signup

## Tools available

**9** tools available. First 9:

- `INFLUXDB_CLOUD_ADD_DASHBOARD_CELL` — Add Dashboard Cell — Tool to add a cell to a dashboard. Use when you want to add or copy a cell to an existing dashboard after verifying the dashboard exists.
- `INFLUXDB_CLOUD_DELETE_USER` — Delete User — Delete a user from InfluxDB Cloud by their user ID. This action permanently removes a user from the InfluxDB Cloud organization. Requires an operator token with write:users permission to execute successfully. Use this when you need to remove a user's access to the InfluxDB Cloud organization.
- `INFLUXDB_CLOUD_GENERATE_QUERY_AST` — Generate Flux Query AST — Generates an Abstract Syntax Tree (AST) from a Flux query script. Use this tool to analyze the structure of a Flux query and validate its syntax. The AST shows the parsed structure but does not validate semantic correctness (e.g., whether buckets or fields exist).
- `INFLUXDB_CLOUD_GET_DBRP` — Get DBRP Mapping — Retrieve a Database and Retention Policy (DBRP) mapping by ID from InfluxDB Cloud. DBRP mappings enable InfluxDB 1.x query compatibility by mapping old database/retention policy names to InfluxDB 2.x buckets. Use this action to: - Verify which bucket a 1.x database/retention policy maps to - Check if a mapping is the default for its database - Inspect mapping configuration before updating or querying data with 1.x APIs Prerequisites: You must have a valid DBRP mapping ID (obtain via listing DBRP mappings or from previous create operations).
- `INFLUXDB_CLOUD_LIST_ROUTES` — List Routes — Lists all available InfluxDB v2 API endpoints and routes. This action queries the root API endpoint (GET /api/v2) to retrieve a comprehensive map of all available API resources and their corresponding URLs. Use this to discover what endpoints are available in your InfluxDB Cloud instance, including resources for data management (buckets, write, delete, query), user management (users, orgs, authorizations), monitoring (checks, tasks, dashboards), and configuration (labels, variables, Telegraf). The response includes both simple route strings (e.g., "/api/v2/buckets") and nested route objects (e.g., query routes with analyze, ast, suggestions endpoints). Authentication: Requires a valid authorization token in the metadata headers.
- `INFLUXDB_CLOUD_SIGNIN` — Sign In — Authenticates a user with username and password to create a session with InfluxDB Cloud. Returns a session cookie that can be used for subsequent API requests instead of token-based authentication. Use this when you need to authenticate with user credentials rather than API tokens, or when establishing a user session for operations that require session-based authentication.
- `INFLUXDB_CLOUD_SIGNOUT` — Sign Out — Tool to expire a user session using a session cookie. Use when ending an authenticated session after signin.
- `INFLUXDB_CLOUD_UPDATE_DBRP` — Update DBRP — Tool to update a DBRP mapping's default and retention policy. Use when modifying an existing DBRP mapping after initial creation.
- `INFLUXDB_CLOUD_WRITE_DATA` — Write Line Protocol Data — Writes time-series data in line protocol format to an InfluxDB Cloud bucket. Use this tool to ingest metrics, sensor data, or any time-series measurements into InfluxDB. The data must be formatted according to InfluxDB line protocol specification.

## Auth

Auth schemes: `API_KEY`.

## How agents use InfluxDB Cloud

Inside a Definable workflow, InfluxDB Cloud is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → InfluxDB Cloud** — the Researcher (GPT-5.5) pulls context from InfluxDB Cloud (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → InfluxDB Cloud** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into InfluxDB Cloud (create record, post message, draft email).
- **Designer / Engineer → Distributor → InfluxDB Cloud** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via InfluxDB Cloud (attach file, open PR comment, post status).

The Verifier checks every InfluxDB Cloud call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- databases — https://definable.ai/apps/category/databases/
- analytics — https://definable.ai/apps/category/analytics/

## Related

- HTML page: https://definable.ai/apps/influxdb_cloud/
- Same category (databases): https://definable.ai/apps/category/databases/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt