Databases

InfluxDB Cloud, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your InfluxDB Cloud account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Databases
  • Connects with a key
  • 9 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What InfluxDB Cloud is

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

You paste in a key from your own InfluxDB Cloud account. It is kept encrypted, and you can withdraw it from inside InfluxDB Cloud whenever you like.

How a run works

One message in, the work done in InfluxDB Cloud.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in InfluxDB Cloud. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own InfluxDB Cloud account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

9 tools it already has

What it can do in InfluxDB Cloud

These are the ready-made tools your AI employee already has in InfluxDB Cloud. It is not limited to them, but it never has to be taught these.

  • Add Dashboard CellTool 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.
  • Delete UserTool to delete a user by ID. Use when you need to remove a user in InfluxDB Cloud; requires an operator token.
  • Generate Flux Query ASTTool to generate a Flux query Abstract Syntax Tree (AST). Use when you need to inspect the structure of a Flux script. Use after composing your Flux query; this validates syntax an
  • Get DBRP MappingTool to retrieve a DBRP mapping by ID. Use when you need to fetch details of a specific DBRP mapping in InfluxDB Cloud.
  • List RoutesTool to list top-level API routes. Use when you need to discover all available API endpoints for an instance. Call after setting a valid authorization token.
  • Sign InTool to create a user session by authenticating credentials. Use when initiating a user session after collecting credentials.
  • Sign OutTool to expire a user session using a session cookie. Use when ending an authenticated session after signin.
  • Update DBRPTool to update a DBRP mapping's default and retention policy. Use when modifying an existing DBRP mapping after initial creation.
  • Write Line Protocol DataTool to write line protocol data to a bucket. Use when ingesting asynchronous line protocol points after formatting the payload.
Access, and who is in charge of it

You stay the boss of your InfluxDB Cloud account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own InfluxDB Cloud account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in InfluxDB Cloud is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in InfluxDB Cloud and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

Questions people ask about InfluxDB Cloud

Can an AI employee really work inside InfluxDB Cloud?
Yes. It signs in to your own InfluxDB Cloud account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of InfluxDB Cloud?
No. Nothing moves and nothing is replaced. Your records stay in InfluxDB Cloud, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my InfluxDB Cloud account?
You paste in a key from your own InfluxDB Cloud account. It is kept encrypted, and you can withdraw it from inside InfluxDB Cloud whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in InfluxDB Cloud?
It has 9 ready-made tools in InfluxDB Cloud today, among them Add Dashboard Cell, Delete User and Generate Flux Query AST. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use InfluxDB Cloud and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in InfluxDB Cloud and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in InfluxDB Cloud?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in InfluxDB Cloud is written down with what it did and when.