Amplitude
Analytics & DataConnect AI agents to Amplitude. Agents track events and identify users through the ingestion APIs, query segmentation, funnels, retention, and revenue LTV, manage cohorts including uploads and downloads, and govern the event taxonomy.
What This Integration Enables
Amplitude is where product teams decide what is working. The problem is that the answer usually stays in the dashboard. This integration puts agents on both sides of that gap: they feed Amplitude clean data through the ingestion APIs (Track Event, Identify User, Group Identify, batch and historical backfills) and they pull answers back out through segmentation, funnel, retention, and revenue LTV queries so the numbers can start a workflow instead of ending one. Agents also carry the unglamorous work that keeps an analytics instance trustworthy: syncing the tracking-plan taxonomy, uploading and downloading cohorts, annotating charts when a release or campaign ships, and running privacy deletion jobs. That last group is why this connector needs [human-in-the-loop](/concepts/human-in-the-loop/) built in rather than bolted on. Querying a funnel is free to get wrong. Scheduling a GDPR deletion job is not. FlowRunner's position is that agents should run the entire loop from metric to action, and stop exactly at the steps a person should own. Connector capabilities here are built and verified against Amplitude's official APIs.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Funnel drop detection with a staged response
Every Monday, an agent runs Get Funnel Analysis on the activation funnel and Get Retention Analysis on the same population. When step conversion falls against the prior four weeks and retention confirms it is a real shift rather than noise, the agent queries the affected users, stages them with Upload Cohort, and posts the numbers to the growth channel in [Slack](/integrations/slack). The growth lead approves before that cohort feeds a win-back campaign. The metric found the problem; the humans decide what the response costs.
A revenue and engagement digest that writes itself
An agent runs Get Revenue LTV, Get Event Segmentation, and Get Realtime Active Users on a schedule and appends the results to a running dashboard with [Google Sheets](/integrations/google-sheets). When a release ships, the same agent calls Create Chart Annotation so every chart in Amplitude carries the context of what changed and when. Nobody rebuilds the Monday deck. The deck maintains itself, and the annotations mean next quarter's analysis does not require archaeology.
Right-to-be-forgotten requests, verified and gated
A deletion request arrives through the support queue. The agent calls Search Users to resolve the requester's email to Amplitude IDs, pulls Get User Activity to confirm the match is the right person and not a namesake, and checks List User Deletion Jobs for an existing job. It then presents the case to the privacy owner: the matched IDs, the activity summary, the request source. Only after approval does the agent call Create User Deletion Job. Amplitude executes these jobs permanently, so the workflow treats scheduling one as a decision, not a task.
Human-in-Loop Highlight
Create User Deletion Job permanently removes all data for the listed users, and Amplitude only allows a user to be pulled back out with Remove User From Deletion Job until three days before the job runs. After that window, there is no undo. So the deletion agent never schedules a job on its own authority. It resolves identity with Search Users, gathers the evidence with Get User Activity, and asks the privacy owner in Slack: "Deletion requested for [email protected]. I matched 2 Amplitude IDs with activity ending 14 March. Approve scheduling the deletion job, or flag for manual review?" The agent does the lookup work in seconds. The irreversible click belongs to a person.
Agent Capabilities
49 actionsEvent Ingestion
5- Track Event Sends a single event through the HTTP V2 API with event properties, user properties, groups, and revenue fields. Used to record workflow outcomes as first-class product events.
- Track Multiple Events Sends up to 2000 events in one request. Used when a workflow produces a batch of events at once.
- Batch Upload Events Uploads events through the Batch Event Upload API, built for high-volume and historical backfills. Used to bring past activity from another system into Amplitude.
- Identify User Updates a user's properties without sending an event, including set, set-once, add, append, and unset operations. Used to keep profile attributes current as workflows learn things.
- Group Identify Sets or updates properties on a group such as a company or account. Used for account-level analytics in B2B setups.
Analytics Queries
9- List Events Retrieves all event types visible in the project with weekly totals and unique user counts. Used to discover what is actually being tracked before querying.
- Get Event Segmentation Runs an Event Segmentation query for one or two events over a date range, segmented and grouped by properties. Used for scheduled metric pulls and threshold checks.
- Get Funnel Analysis Runs a funnel query with step-by-step and cumulative conversion rates. Used to detect conversion drops that should open a workflow.
- Get Retention Analysis Measures how many users return and perform an event after a starting event. Used to confirm whether a funnel movement is a real behavioral shift.
- Get Realtime Active Users Retrieves realtime active user counts at 5-minute granularity for today and yesterday. Used for launch-day monitoring.
- Get Average Session Length Retrieves average session length per day over a date range. Used in engagement digests.
- Get Average Sessions Per User Retrieves average sessions per user per day. Used alongside session length for engagement reporting.
- Get Session Length Distribution Retrieves the histogram of session lengths over a date range. Used to spot shifts in how deeply users engage.
- Get Revenue LTV Runs a Revenue Lifetime Value query returning ARPU, ARPPU, revenue, or paying user counts grouped by start date. Used for cohort revenue reporting.
Users
3- Search Users Searches by Amplitude ID, User ID, Device ID, or prefix and returns matching users with their Amplitude IDs. Used to resolve identity before activity lookups and deletion jobs.
- Get User Activity Retrieves a user's device, location, and usage summary plus a paginated event stream. Used to verify identity matches and investigate individual behavior.
- Get User Profile Retrieves a user's profile including properties, cohort memberships, and recommendations. Used to enrich decisions in other workflows with what Amplitude knows about the user.
Chart Annotations
5- List Chart Annotations Retrieves all chart annotations in the project. Used to audit what context already exists on the charts.
- Get Chart Annotation Retrieves a single annotation by ID.
- Create Chart Annotation Marks a moment in time such as a release or campaign launch on Amplitude charts. Used so every deploy leaves a visible mark on the metrics it may have moved.
- Update Chart Annotation Updates an annotation's label, timestamps, category, or chart association.
- Delete Chart Annotation Permanently deletes an annotation by ID. Used in cleanup workflows.
Cohorts
7- List Cohorts Retrieves all behavioral cohorts with IDs, names, sizes, and definitions. Used to find the right cohort before downloads or membership updates.
- Request Cohort Download Starts an asynchronous export of a cohort's members and returns a request ID to poll.
- Get Cohort Download Status Checks an export job and reports when the file is ready.
- Download Cohort Downloads the member list of a completed export. Used to hand a cohort to an outreach or suppression workflow.
- Get Cohort Download Usage Retrieves the current month's cohort download usage against the plan quota. Used so workflows budget the quota instead of burning it.
- Upload Cohort Creates or replaces a static cohort from a list of user IDs. Used to stage a churn-risk or campaign population directly from a workflow.
- Update Cohort Membership Incrementally adds or removes cohort members without re-uploading the full list. Used to keep long-lived cohorts current.
Taxonomy
16- List Event Categories Retrieves all event categories in the tracking plan.
- Create Event Category Creates a new event category. Used when the tracking plan gains a new area.
- Update Event Category Renames an existing event category.
- Delete Event Category Deletes an event category from the taxonomy.
- List Event Types Retrieves all event types with category, description, visibility, and owner. Used to audit the tracking plan against the internal spec.
- Create Event Type Creates a new event type in the taxonomy.
- Update Event Type Renames an event type or changes its category, description, tags, or owner.
- Delete Event Type Deletes an event type from the taxonomy. Historical event data is not removed.
- List Event Properties Retrieves event property definitions, optionally for a single event type.
- Create Event Property Creates an event property definition with data type and validation rules.
- Update Event Property Updates an event property definition.
- Delete Event Property Deletes an event property definition. Historical data is not removed.
- List User Properties Retrieves user property definitions in the taxonomy.
- Create User Property Creates a custom user property definition.
- Update User Property Updates a custom user property definition.
- Delete User Property Deletes a custom user property definition. Historical data is not removed.
Privacy
3- Create User Deletion Job Schedules a permanent privacy deletion for the specified users under GDPR and CCPA. The gated action in this connector: workflows require human approval before calling it.
- List User Deletion Jobs Retrieves scheduled deletion jobs in a date range with status and affected users. Used to track deletion progress for compliance reporting.
- Remove User From Deletion Job Cancels a user's deletion, possible only until three days before the job runs. Used when a request is withdrawn or was approved in error.
Export
1- Export Raw Events Exports raw event data for an hour range and stores the ZIP archive in FlowRunner file storage. Used for warehousing, backups, and downstream processing.
Frequently Asked Questions
What can FlowRunner do with Amplitude?
FlowRunner agents can run Track Event, Track Multiple Events, and Batch Upload Events in Amplitude, plus 46 more actions.
Does connecting Amplitude to FlowRunner require OAuth?
No. Amplitude connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can Amplitude trigger a FlowRunner workflow automatically?
Amplitude doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Amplitude
$100 in credits. No card required. Connect in minutes.