NagentArtefacts
Dev & Technology
Enterprise and White Glove
Company
InfluxDB Cloud connects to a Nagent workspace with an API key. Once it is connected, agents can call 9 InfluxDB Cloud actions, such as "Add Dashboard Cell", "Get DBRP Mapping" and "List Routes". Nothing is enabled on connect: each action is allowed one at a time, and an action with side effects runs or waits for a person according to the agent's level.
Every operation an agent can call against InfluxDB Cloud, with input parameters and output schema.
INFLUXDB_CLOUD_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.
Input parameters
Cell height in grid units
Cell width in grid units
X position of the cell in the dashboard grid
Y position of the cell in the dashboard grid
Human-readable name for the cell
ID of an existing view to copy into the new cell
ID of the dashboard to which the cell will be added
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INFLUXDB_CLOUD_DELETE_USERDelete 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.
Input parameters
The unique identifier (ID) of the user to delete from InfluxDB Cloud. Must be a valid 16-character hexadecimal user ID.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INFLUXDB_CLOUD_GENERATE_QUERY_ASTGenerates 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).
Input parameters
The Flux query script to analyze. Must be valid Flux syntax.
Optional OpenTracing span context for distributed tracing.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INFLUXDB_CLOUD_GET_DBRPRetrieve 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).
Input parameters
Organization name. Optional. Specify either 'org' or 'orgID' to filter by organization (not both).
Organization ID (16-character hexadecimal). Optional. Specify either 'org' or 'orgID' to filter by organization (not both).
Unique identifier of the DBRP mapping to retrieve (16-character hexadecimal string).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INFLUXDB_CLOUD_LIST_ROUTESLists 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.
Input parameters
OpenTracing span context for distributed tracing. When provided, this value is sent as the 'Zap-Trace-Span' HTTP header to correlate requests across services.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INFLUXDB_CLOUD_SIGNINAuthenticates 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.
Input parameters
Override the base URL for the sign-in request. If not provided, the connection's base_url is used.
User account password for authentication
Username for login (typically the account email)
OpenTracing span context for request tracing.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INFLUXDB_CLOUD_SIGNOUTTool to expire a user session using a session cookie. Use when ending an authenticated session after signin.
Input parameters
Session cookie from POST /api/v2/signin to be sent in the Cookie header.
OpenTracing span context for request tracing.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INFLUXDB_CLOUD_UPDATE_DBRPTool to update a DBRP mapping's default and retention policy. Use when modifying an existing DBRP mapping after initial creation.
Input parameters
Query parameter. Organization name that owns the DBRP mapping.
Query parameter. Organization ID that owns the DBRP mapping.
Path parameter. The ID of the DBRP mapping to update.
Set true to make this mapping the default retention policy for the specified database; set false to remove the default mapping.
Retention policy name (InfluxDB v1) for the mapping.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
INFLUXDB_CLOUD_WRITE_DATAWrites 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.
Input parameters
Organization name. Specify either this or orgID (not both). Use org when you know the organization name.
Line protocol formatted data. Format: 'measurement\[,tag=value...\] field=value\[,field=value...\] \[timestamp\]'. Multiple lines can be separated by newlines.
Organization ID (16-character hexadecimal). Specify either this or org (not both). Use orgID for programmatic access.
The target bucket name where data will be written. Buckets are named containers for time-series data in InfluxDB.
Timestamp precision for the data points. Options: ns (nanoseconds), us (microseconds), ms (milliseconds), s (seconds), m (minutes), h (hours). Default is ns.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
Agents can call 9 InfluxDB Cloud actions on Nagent, including "Add Dashboard Cell", "Get DBRP Mapping" and "List Routes". Add Dashboard Cell: Add a cell to a dashboard. Each action is listed on this page with its input parameters and its output.
InfluxDB Cloud connects with an API key, under your workspace's own connection. Nothing is enabled on connect: each action is allowed one at a time and can be scoped to the agents that need it.
Add Dashboard Cell takes 1 required input: dashboardID. It also takes 6 optional inputs: h, w, x, y, name and usingView. It returns data, error and successful.