Data & Storage · Integration
Amplitude
Add Amplitude to your product for your customers, and give your AI agents governed access to it.
Embed an Amplitude integration so your customers can stream product events from your app into their own Amplitude project and read cohorts and chart results back inside your product, with governed agent access to the same analytics. Because every project has its own event taxonomy, event and property mapping is configuration per customer rather than code. fastn handles each customer's API credentials and upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Send product events and user properties into each customer's own Amplitude project, mapped to their taxonomy.
Read cohorts so your product can segment users using the definitions the customer already maintains.
Read chart and query results so usage insight appears inside your product instead of another tab.
Identify and update user and group properties as records change in your product.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads a cohort and chart results before answering a question about usage.
An agent sends a corrective event or property update within governed permissions.
An agent reacts to a drop in a tracked event and gathers the supporting breakdown.
Example prompt
Which events did this account trigger least in the last 30 days compared with the month before?
Set up Amplitude in 4 steps
- 01Open the Amplitude connector from your fastn dashboard.
- 02Have each customer authenticate their Amplitude project with its API credentials.
- 03Map the events and user properties your product sends and reads, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Amplitude integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Amplitude integration without building it. Your customers connect their own Amplitude account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Amplitude update is not your on-call problem.
- One integration serves your product and your agents. The same governed Amplitude connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Works well with
Appcues
HubSpot
SlackOften used alongside
Tools the same teams tend to run next to Amplitude, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceAmplitude integration FAQ
How do I add an Amplitude integration to my product?
Enable the Amplitude connector in your fastn dashboard, then let each customer authenticate their own Amplitude account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Amplitude client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Amplitude account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Amplitude account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Amplitude integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads a cohort and chart results before answering a question about usage.
Who maintains the Amplitude integration?
fastn does. When Amplitude changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the Amplitude integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large Amplitude reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the Amplitude integration?
A common starting point: send product events and user properties into each customer's own Amplitude project, mapped to their taxonomy. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Amplitude integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Amplitude does not change your per-connector cost. You can start free with 3 connected accounts.
Add Amplitude to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.