Amplitude

Amplitude API · Live

Ask Amplitude what the dashboard can't.

Paste your Amplitude project's API key and secret key. The agent can run Event Segmentation queries, pull active-user counts, fetch saved chart data, and trace individual user journeys — all read-only, admin-only.

Connect AmplitudeHow it worksLive
Auth
Amplitude API key + Secret key
Access
Read-only · Admin-only
Plan
Every plan
Freshness
Live — every call hits Amplitude's API
Available on
Every plan

Examples

Questions teams actually ask.

The tools it pulls from are shown inline — every answer in Lumen cites the underlying records it read.

Product

Daily active users for the last 30 days, grouped by plan tier.

pullsactiveUserseventSegmentation
Growth

How many signups happened in the last 7 days, segmented by acquisition channel?

pullseventSegmentation
Analytics

Pull the data behind our retention chart (chart id `abc-123`) and tell me what shifted week-over-week.

pullschartData
Support

Find the Amplitude user for email `[email protected]` and give me their last 100 events.

pullsuserSearchuserActivity
Leadership

Percent of DAU that triggered the `viewed_report` event yesterday.

pullseventSegmentation

Preview

See what the answer looks like.

Toggle the tools Lumen is allowed to use. The plan, answer, and cited sources update to match.

Tools
Read-only (admin)
You

Is `viewed_report` usage up week-over-week, and which plan tier drove the move?

Plan
  1. amplitude.eventSegmentation — event=viewed_report, 7 days, interval=1 (daily)
  2. amplitude.eventSegmentation — same event, grouped by `plan_tier` user property
  3. compare this week vs last week totals
Answer

`viewed_report` is up 18% week-on-week (14,210 → 16,780 uniques). The entire lift is on Growth-tier accounts (+41%); Starter and Enterprise are flat. Full daily series and grouped breakdown inlined.

Sources
  • [1]amplitude.eventSegmentation — 7 daily buckets, metric=uniques
  • [2]amplitude.eventSegmentation — same window, groupBy=plan_tier, 3 tiers

Scope

What Lumen sees. What it can change.

Read is on by default. Every write is a separate toggle, capped per user, and logged.

Read

What Lumen reads

Lumen calls Amplitude's REST API using the API-key/secret-key pair you supplied. Admin-only — org members without admin role can't reach these operations.

  • Event Segmentation

    Event counts / uniques / totals / %-of-DAU / averages over time, optionally grouped by a user property

  • Active users

    DAU/WAU/MAU-style counts with daily / weekly / monthly interval

  • Saved chart data

    Fetch the raw numbers behind any saved chart by chart ID

  • User search

    Find a user by Amplitude ID, user ID, device ID, or user-property value

  • User activity

    Fetch a specific user's session + event history (up to 1,000 events)

Write · opt-in

What Lumen can write

Lumen does not write to Amplitude. No event ingestion, no cohort mutation, no user-property writes. Use the Amplitude SDK for ingestion.

    Every query is logged with user, operation, event name (or chart ID), date range, and row count. Exportable as CSV.

    Install

    Connect in under a minute.

    No keys, no call, no app marketplace fine print.

    1. Grab keys
      01

      Copy the project keys

      In Amplitude, go to Settings → Projects → your project → General. Copy the API Key and Secret Key (both from the same project — they must be paired).

    2. Connect
      02

      Paste them into Lumen

      In Settings → Integrations → Amplitude, paste the keys. If you're on the EU data residency plan, set `region` to `eu`. Both keys are stored encrypted.

    3. Ask
      03

      Try a warm-up query

      Start with "How many DAU did we have yesterday?" — the agent will call `activeUsers` with the right date format and return the number plus the supporting series.

    Questions

    Frequently asked.

    Why admin-only?
    Amplitude data can contain PII in user properties (emails, names, IDs) and identifies individual users in `userActivity`. Admin-gating is a deliberate guardrail.
    Does Lumen write events?
    No. Event ingestion is out of scope — use Amplitude's standard SDK or HTTP ingestion endpoint.
    What date format do I need to use?
    None — you just write the question. The agent formats dates as `YYYYMMDD` behind the scenes (what Amplitude's API expects) and validates before hitting the API.
    Can I use this with cohorts?
    Cohort reads (who's in a cohort, cohort size) are on the roadmap. Today, use `eventSegmentation` with a `groupBy` on a user property that distinguishes the cohort.
    What about EU data residency?
    Set `region: eu` at install — Lumen will route requests to Amplitude's EU endpoint.
    Does Lumen cache chart data?
    No. Every `chartData` call hits Amplitude fresh. The agent cites the chart ID alongside the numbers so you can cross-reference in the dashboard.
    Can I restrict which events the agent can query?
    Not yet in Lumen itself. The Amplitude project key scope is whatever Amplitude exposes — per-event allowlisting is a roadmap item.

    Pairs with

    Better together.

    Connect Amplitude. Ask a hard product question.

    API key + Secret key. Read-only. Admin-only.

    Connect AmplitudeBack to all integrations