Skip to content
For LLMsView as Markdown·

Amplitude

Track events, analyze product usage, and query cohorts with Amplitude.

DetailValue
CategoryAnalytics
Base URLhttps://api2.amplitude.com
AuthenticationAPI Key
Endpoints5
Connector keyamplitude

Using Amplitude in a workflow

  1. Go to Connections and click New Connection.
  2. Pick Amplitude from the marketplace.
  3. Enter your credentials (see Authentication above for what's expected).
  4. In a workflow, drop an API Call node and select this connection.
  5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

EndpointSummary
POST /2/httpapiTrack events
POST /identifyIdentify a user
GET /2/events/segmentationQuery event segmentation
GET /2/users/{amplitude_id}/eventsGet events for a user
GET /2/funnelsQuery funnel analysis

Each endpoint is documented in full below. Use the outline on the right to jump to one.

POST /2/httpapi

Track events

DetailValue
Operation IDanalytics.trackEvents
MethodPOST
Path/2/httpapi

Parameters

No parameters.

Request Body

FieldType
api_keystring
eventsarray

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Amplitude connection from the Connection dropdown.
  3. In the Operation dropdown, select analytics.trackEvents.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Amplitude API reference.

POST /identify

Identify a user

DetailValue
Operation IDanalytics.identify
MethodPOST
Path/identify

Parameters

No parameters.

Request Body

FieldType
api_keystring
identificationarray

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Amplitude connection from the Connection dropdown.
  3. In the Operation dropdown, select analytics.identify.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Amplitude API reference.

GET /2/events/segmentation

Query event segmentation

DetailValue
Operation IDanalytics.queryEvents
MethodGET
Path/2/events/segmentation

Parameters

NameLocationTypeRequired
equerystringYes
startquerystringYes
endquerystringYes

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Amplitude connection from the Connection dropdown.
  3. In the Operation dropdown, select analytics.queryEvents.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Amplitude API reference.

GET /2/users/{amplitude_id}/events

Get events for a user

DetailValue
Operation IDanalytics.getUserEvents
MethodGET
Path/2/users/{amplitude_id}/events

Parameters

NameLocationTypeRequired
amplitude_idpathstringYes

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Amplitude connection from the Connection dropdown.
  3. In the Operation dropdown, select analytics.getUserEvents.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Amplitude API reference.

GET /2/funnels

Query funnel analysis

DetailValue
Operation IDanalytics.queryFunnels
MethodGET
Path/2/funnels

Parameters

NameLocationTypeRequired
equerystringYes
startquerystringYes
endquerystringYes

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Amplitude connection from the Connection dropdown.
  3. In the Operation dropdown, select analytics.queryFunnels.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Amplitude API reference.