Resources · Make integration

Amplitude Make integrationAutomate Amplitude with Make.

Can Make feed Amplitude and read it back without code? Yes. The Amplitude Make integration gives you 23 modules: one scheduled trigger, 19 actions and 3 searches. This page is for product and growth teams, and it takes you from the connection to a first working scenario.

Try the Amplitude integration on MakeSee the 23 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can you automate with the Amplitude Make integration?

The Amplitude Make integration links your Amplitude project to the other tools you use, without writing code. Make can push data in (events, cohorts, releases, annotations) and pull analysis out (user counts, retention, funnels, chart results), then hand the result to a sheet, a CRM or a chat. You build it once, and it keeps running.

Charts that travel on their own. Watch New Annotations picks up each annotation your product team adds, and Get Results of a Chart fetches the numbers of a chart you already built, so the context and the figures reach people who never open Amplitude.

Cohorts that follow your CRM. Upload a Cohort turns a customer list into a cohort, and Modify Cohort's Memberships moves one account in or out when a deal closes. Sales and product then look at the same group of users.

Events from outside the product. Upload Event Data sends a payment, a ticket or an offline sale into Amplitude, and Create a Release marks each version you ship, so the analysis covers what happens beyond the app itself.

What the integration does not do: it has a single trigger, and it watches annotations only. New events, users or cohorts never start a scenario by themselves, so you query them with a Get or List module on the scenario's schedule. For anything the modules leave out, Make an API Call reaches the rest of the Amplitude API. The same app often has an n8n node too; the n8n vs Make comparison lays out the criteria. To learn the editor step by step, the Make training walks you through it, and check Make pricing before you size your plan.

Connect

How do you connect Amplitude to Make?

  1. 01

    Add an Amplitude module

    In a scenario, click the +, search for Amplitude and pick any module, then click Create a connection. A connection is your Amplitude account linked to Make once; every Amplitude module reuses it afterwards.

  2. 02

    Copy your project keys

    In Amplitude, open Organization Settings at the top right, then Projects, and click the project you want to automate. The project details pane shows the API key and the API secret key. Copy both.

  3. 03

    Name and save the connection

    Back in Make, the Connection name field is optional, but naming it after the project helps once you have several. Paste the two keys and save. Every Amplitude module in your scenarios can now use that project.

First scenario

Your first scenario: send new sign-ups to Amplitude

GoalWhen a new sign-up lands in another tool, Make sends it to Amplitude as event data.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. A scenario is the automation you build: a chain of modules, each one a brick such as a trigger, an action or a search.

  2. 02

    Start from the tool that holds sign-ups

    Add the trigger of the app where sign-ups arrive, a CRM or a form tool for example, and connect it. Each new sign-up becomes a bundle: one item handed to the next module.

  3. 03

    Add Upload Event Data

    Click the + on the right of that first module, search for Amplitude and pick Upload Event Data. Choose your Amplitude connection, then map the sign-up's data from the previous module into the fields Make shows.

  4. 04

    Test with Run once

    Click Run once, then create a test sign-up. Open the bundles each module received to see exactly what reached Amplitude. One module run on one bundle counts as one operation on your plan.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module: a new scenario runs every 15 minutes by default, and the Free plan does not go below 15 minutes. Then switch the scenario on.

Triggers

What starts an Amplitude scenario?

1 module starts a scenario when something happens in Amplitude. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Amplitude as soon as it happens.

Amplitude1Watch New Annotations

Watch New Annotations

Scheduled trigger

In Make“Triggers when a new annotation has been added.”

Each annotation someone adds to your Amplitude project starts the scenario, and Make hands it over as a bundle you can pass to the next module.

How it fires
scheduled. Make checks Amplitude on the scenario's schedule, every 15 minutes by default, so a new annotation shows up at the next check rather than the second it is saved.
When to use it
your product team marks launches and incidents as annotations, and you want each one posted where the rest of the company reads, or paired with Get Results of a Chart.
Watch out
it is the only trigger of the app, so events, users and cohorts are never watched. To start from those, schedule the scenario and query them with a Get or List module.
Modules

What can Make do in Amplitude?

Amplitude gives you 22 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Amplitude1

Create an Annotation

Action

In Make“Creates an annotation.”

You get the context of a change written right next to your numbers, without anyone typing it: this module adds a new annotation to your Amplitude project from the scenario.

When to use it
a campaign goes live in your marketing tool, or a price changes in your store, and the date should be marked in Amplitude on its own.
Watch out
every run creates a fresh annotation, so make sure the trigger before it passes each change only once.
Amplitude2

Create a Release

Action

In Make“Creates a new release.”

A clear record of what shipped, stored in Amplitude as a new release each time the module runs, so anyone reading the data can match a curve to a version.

When to use it
your deployment or project tool marks a version as done, and the release should appear in Amplitude without a manual step.
Watch out
start from a trigger that fires once per version; a module that returns the whole version list would create one release per item.
Amplitude3

Get Active and New User Counts

Action

In Make“Returns the number of active or new users.”

How many people used the product, or how many were new: this module returns that count so the scenario can drop it wherever your team already looks.

When to use it
a founder wants the figure in a spreadsheet row or a chat message right after a launch, without logging into Amplitude.
Watch out
you receive numbers, not the users behind them. To see what one person did, Get User Activity is the brick to pick.
Amplitude4

Get an Annotation

Action

In Make“Retrieves an annotation specified by ID.”

The full record of one annotation, fetched by its ID, ready for a later module to reuse its text or its date.

When to use it
you stored an annotation ID in a sheet, or received it from Watch New Annotations earlier in the flow, and need the complete details at a later step.
Watch out
the ID is required. If you do not have it yet, List Annotations returns every annotation of the project and lets you pick the right one.
Amplitude5

Get Average Session Length

Action

In Make“Gets the average session length (in seconds) for each day in the specified date range.”

Day by day, the average time a session lasts over the date range you set. The value comes back in seconds, one figure per day.

When to use it
a redesign has just shipped, and the product manager wants to see whether people stay longer on each day that follows.
Watch out
divide by 60 before showing minutes to a non-technical reader, and plan where a list of daily values will go in the next module.
Amplitude6

Get Average Sessions per User

Action

In Make“Gets the average number of sessions per user on each day in the specified date range.”

A habit signal: for each day of your range, how many sessions one user opened on average. It answers how often people come, not how long they stay.

When to use it
you launched a feature meant to bring people back, and want a daily sign that it works, sent to the team that built it.
Watch out
pair it with Get Average Session Length only if you need both angles, since every extra module adds one operation per run.
Amplitude7

Get Event Segmentation

Action

In Make“Gets metrics for an event with segmentation.”

The metrics of one event, split by segment, so you learn who performs an action and not only how often it happens.

When to use it
a sales lead asks how many trial accounts, compared with paying ones, clicked the upgrade button, and the answer should land in the CRM next to the account list.
Watch out
the module looks at one event at a time. For a sequence of steps, List Funnel Analysis fits the question better.
Amplitude8

Get Real-Time Active Users

Action

In Make“Gets active user numbers with minute granularity for the last two days.”

Active user numbers minute by minute across the last two days: the closest view Make gives you of what is happening in the product right now.

When to use it
a launch or an email send has just gone out, and the team wants the minute-level figures posted in their chat shortly after.
Watch out
the window stops two days back. For older periods, Get Active and New User Counts is the module to use.
Amplitude9

Get Results of a Chart

Action

In Make“Retrieves the results of an existing chart.”

The analysis you already built in Amplitude, reused anywhere: this module reads the results of an existing chart and passes them to the next step.

When to use it
your team maintains a key chart, and a leader wants its numbers pasted into a sheet or a slide whenever a new annotation appears.
Watch out
the chart has to exist first. Make reads it, it does not build it, so set the chart up in Amplitude before wiring the module.
Amplitude10

Get Retention Analysis

Action

In Make“Gets user retentions for specific starting and returning actions.”

Proof of whether users come back, measured between a starting action and a returning action that you choose.

When to use it
after an onboarding change, a growth lead wants to know whether people who signed up return to use the core feature, with the result stored next to the change log.
Watch out
the number only means something with its two actions. Name them clearly in the scenario so the next reader interprets it the same way.
Amplitude11

Get Revenue LTV

Action

In Make“Gets the lifetime value of new users.”

A revenue figure tied to product data: the lifetime value of your new users, returned to the scenario so finance can use it outside Amplitude.

When to use it
the finance lead is preparing a board pack and wants LTV placed in the sheet beside acquisition spend.
Watch out
the module covers new users. It does not give you the value of your whole existing base, so label the figure accordingly.
Amplitude12

Get Session Length Distribution

Action

In Make“Gets the number of sessions for each pre-defined length ("bucket") period during a specified date range.”

The spread behind the average: the number of sessions in each predefined length bucket over your date range.

When to use it
the average looks healthy, yet you suspect many people leave within seconds while a few stay a very long time, and you want the split in a report.
Watch out
Amplitude defines the buckets, so you read its groups as they come. For one simple figure, Get Average Session Length is easier.
Amplitude13

Get User Activity

Action

In Make“Gets a user summary and their most recent 1000 events plus all of the events from their most recent session.”

One user's story at a glance: a summary with their most recent 1000 events, plus every event from their latest session.

When to use it
a support ticket comes in, and the agent needs to see what the customer did just before writing, attached to the ticket automatically.
Watch out
anything older than those 1000 events is left out, so for a long-term view rely on charts instead of this module.
Amplitude14

Get User Composition

Action

In Make“Gets the distribution of users across values of a user property in the specified date range.”

How your users split across the values of one user property during the date range, returned as a distribution you can drop into a sheet.

When to use it
marketing is planning a campaign and wants the share of users per value of a property, such as country or plan, before choosing a target.
Watch out
one run reads one property. Comparing two means a second module, and one more operation on your plan.
Amplitude15

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Access to any endpoint of the Amplitude API, through the connection you already set up, for everything the other modules do not cover.

When to use it
you need an Amplitude feature that none of the listed modules reaches, and you would rather stay in the same scenario than switch tools.
Watch out
you write the request yourself from Amplitude's API reference. It is the one module here that asks you to read developer docs.
Amplitude16

Modify Cohort's Memberships

Action

In Make“Modifies the memberships of a cohort specified by ID.”

An existing cohort kept up to date without rebuilding it: this module changes who belongs to a cohort you identify by its ID.

When to use it
a deal closes in your CRM, and that account must join the cohort your team uses to follow customers.
Watch out
the cohort ID is required. Fetch it once with List Cohorts, note it in the module, and the scenario can reuse it on every run.
Amplitude17

Send an Attribution Campaign Event

Action

In Make“Sends an attribution campaign event.”

Campaign attribution data delivered to Amplitude as an event, so the source of a user is recorded alongside the rest of their activity.

When to use it
your ad or partner platform reports a conversion, and you want Amplitude to hold the campaign information too.
Watch out
each bundle sends one event. If your trigger can pass the same conversion twice, Amplitude receives it twice.
Amplitude18

Upload a Cohort

Action

In Make“Generates a new cohort or updates an existing one.”

A list from another tool turned into an Amplitude cohort: the module creates a new cohort, or updates one that already exists.

When to use it
your VIP customers live in a CRM or a spreadsheet, and you want them as a cohort ready for analysis in Amplitude.
Watch out
aiming it at an existing cohort updates that cohort, so check which one is selected before your first Run once.
Amplitude19

Upload Event Data

Action

In Make“Uploads event data.”

Events from any tool Make connects, sent into Amplitude, so actions outside your product still count in your analysis.

When to use it
a payment, a support ticket or an offline sale should appear in Amplitude like any in-app event, next to the rest of the user's journey.
Watch out
the module runs once per bundle, and each run is one operation, so a batch of rows costs as many operations as it has rows.
Amplitude20

List Annotations

Search

In Make“Lists all annotations.”

Your whole annotation timeline in one go: every annotation of the project comes back, each one as its own bundle.

When to use it
you want to copy the history of launches and incidents into a sheet or a wiki page, for example when a new team member joins.
Watch out
as a search, it can return zero, one or many bundles, and every module placed after it runs once per bundle, which multiplies operations.
Amplitude21

List Cohorts

Search

In Make“Lists all cohorts.”

All the cohorts of your project, listed, which is also the simplest way to find the ID that other cohort modules ask for.

When to use it
you are setting up Modify Cohort's Memberships and need to know which cohort to target before mapping anything.
Watch out
a project with many cohorts returns many bundles. Run it once to read the IDs rather than leaving it in front of modules that act on each bundle.
Amplitude22

List Funnel Analysis

Search

In Make“Lists a funnel drop-off and conversion rates.”

Where people drop off, and how many convert, across the steps of a funnel: this search returns both rates for your scenario to share.

When to use it
the checkout team changed the payment page and wants to know at which step buyers now quit.
Watch out
as a search, it can return several bundles. Read what Run once shows before you map the values into the next module.
Need help

Need help automating Amplitude with Make?

A person reads every message.

FAQ

Amplitude and Make: common questions

01Is the Amplitude Make integration free?
Yes, Amplitude is a standard app, so it works from the Make Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the minimum interval to 1 minute, remove the cap on active scenarios and count usage in credits per month. Your Amplitude subscription is separate and depends on Amplitude.
02What do you need to connect Amplitude to Make?
An active Amplitude account and a project API key. In Amplitude, open Organization Settings, then Projects, click the target project and copy the API key and the API secret key from the details pane. In Make, add any Amplitude module, click Create a connection, give it a name if you like and paste both keys. That single connection then serves all 23 Amplitude modules, including Make an API Call, so you set it up only once per project.
03Does the Amplitude trigger in Make react instantly?
No. Watch New Annotations is a scheduled trigger, the only one the app offers, and there is no instant trigger. Make checks Amplitude on the scenario's schedule: every 15 minutes by default, 15 minutes at the shortest on the Free plan and down to 1 minute on paid plans. A new annotation is therefore picked up at the next check. For other data, the scenario runs on its schedule and asks Amplitude with a Get or List module.
04What if an Amplitude module is missing in Make?
Use Make an API Call. It calls any endpoint of the Amplitude API with the connection you already created, so you stay in the same scenario instead of adding another tool. The trade-off is that you build the request yourself from Amplitude's API reference. Before going that far, check the 19 actions and 3 searches: retention, funnels, chart results, cohorts and event uploads are already covered by dedicated modules, each with its own note on this page.
05Make or n8n for Amplitude?
It depends on the criteria that matter to your team, not on a winner. On Make, Amplitude comes with 23 ready modules, one scheduled trigger and Make an API Call for the rest, all usable from the Free plan. The same app often has an n8n node as well, so compare the modules each tool offers for your exact use case, and the way each one fits the tools you already run, before choosing.
Same platform

Other docs you might need on this stack.

Browse all integrations