Keen.io is an embedded analytics API that enables developers to collect, analyze, and visualize event data seamlessly.
Keen.io is an embedded analytics API that enables developers to collect, analyze, and visualize event data seamlessly. On Nagent, Keen.io is exposed as a fully-configurable analytics integration that any agent can call — 6 actions, and API key authentication. No code is required to wire Keen.io into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Keen.io to automate the kinds of tasks analytics teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Keen.io into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Keen.io, with input parameters and output schema. Drop these into any step of an agent built in Helix.
KEEN_IO_INSPECT_ALL_EVENT_COLLECTIONSRetrieve schema information for all event collections in a Keen.io project. Use this tool to: - List all event collection names in a project - Discover the schema (property names and types) for each collection - Explore available data before running queries Returns up to 5000 event collections with their names, URLs, and optional property schemas.
Input parameters
If true, include inferred property schema in response
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
KEEN_IO_INSPECT_COLLECTION_PROPERTYTool to return details for a specific property in an event collection. Use when you need to inspect a property's inferred type and resource URL.
Input parameters
The property name within the event collection to retrieve details for (e.g., 'keen.id', 'user.email', 'item.price'). Use dot notation for nested properties.
The name of the event collection to inspect (e.g., 'purchases', 'pageviews', 'signups'). Must be an existing collection in your project.
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
KEEN_IO_INSPECT_SINGLE_EVENT_COLLECTIONRetrieve schema information for a single Keen.io event collection. Returns the inferred property types for all fields in the specified collection, useful for understanding data structure before running queries. Property types include 'num' (numbers), 'string' (text), 'bool' (booleans), and 'datetime' (timestamps). Use this tool when you need to: - Understand the structure of a specific event collection - Verify property names and types before building queries - Debug data type mismatches in analytics queries
Input parameters
The name of the event collection to inspect (e.g., 'purchases', 'pageviews', 'signups'). Must be an existing collection in your project.
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
KEEN_IO_LIST_CACHED_DATASETSList all cached dataset definitions for a Keen.io project. Returns paginated results of pre-computed dataset definitions including their query configuration, status, and timing information. Use limit and after_name parameters to page through large result sets. Cached datasets allow pre-computing analytics for hundreds or thousands of entities at once, enabling instant retrieval of results for any indexed entity.
Input parameters
Maximum number of dataset definitions to return per page (1-100). If not specified, defaults to the API default.
Pagination cursor; use the last dataset_name from previous page.
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
KEEN_IO_SELECT_UNIQUETool to return unique values for a target property. Use when distinct property values are required for matching events with optional filters and timeframe constraints.
Input parameters
Optional array of filter objects to refine which events are analyzed.
Property or list of properties to group results by. Returns unique values for each group.
Time interval for bucketing results (e.g., 'hourly', 'daily', 'weekly', 'monthly', 'yearly').
Timezone for interpreting relative timeframes. Either an offset in seconds (e.g., -28800 for PST) or IANA timezone name (e.g., 'US/Pacific').
Time range to analyze. Use either a relative timeframe string (e.g., 'this_7_days', 'previous_30_days', 'this_month') or an absolute timeframe object with 'start' and 'end' keys containing ISO-8601 timestamps.
The property name whose unique (distinct) values will be returned. Supports nested properties using dot notation (e.g., 'user.id', 'item.category').
Name of the event collection to query for unique values (e.g., 'purchases', 'page_views').
If true, include execution metadata in the response
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
KEEN_IO_UNREVOKE_ACCESS_KEYReactivate a previously revoked Keen.io access key. Use this tool when you need to restore access for a key that was previously revoked but not deleted. A revoked key has its 'active' flag set to false; this operation sets it back to true, allowing the key to be used for API authentication again. Note: This operation requires a Master API Key for authentication. The key must have been previously revoked (not deleted) to be unrevoked.
Input parameters
The Access Key string to reactivate
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
No publicly available marketplace agent is found using this tool yet. There are 58 agents privately built on Nagent that already use Keen.io.
Build on Nagent
Connect Keen.io to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Keen.io, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Keen.io is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Keen.io is connected, you configure its 6 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Keen.io steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Keen.io event fires, the agent kicks off automatically.
Every Keen.io action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Keen.io ships with 6 pre-built analytics actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Keen.io together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Keen.io-based workflows tailored to your business.