Appearance
Amplitude
Track events, analyze product usage, and query cohorts with Amplitude.
| Detail | Value |
|---|---|
| Category | Analytics |
| Base URL | https://api2.amplitude.com |
| Authentication | API Key |
| Endpoints | 5 |
| Connector key | amplitude |
Using Amplitude in a workflow
- Go to Connections and click New Connection.
- Pick Amplitude from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
POST /2/httpapi | Track events |
POST /identify | Identify a user |
GET /2/events/segmentation | Query event segmentation |
GET /2/users/{amplitude_id}/events | Get events for a user |
GET /2/funnels | Query funnel analysis |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
POST /2/httpapi
Track events
| Detail | Value |
|---|---|
| Operation ID | analytics.trackEvents |
| Method | POST |
| Path | /2/httpapi |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
api_key | string |
events | array |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Amplitude connection from the Connection dropdown.
- In the Operation dropdown, select
analytics.trackEvents. - 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
| Detail | Value |
|---|---|
| Operation ID | analytics.identify |
| Method | POST |
| Path | /identify |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
api_key | string |
identification | array |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Amplitude connection from the Connection dropdown.
- In the Operation dropdown, select
analytics.identify. - 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
| Detail | Value |
|---|---|
| Operation ID | analytics.queryEvents |
| Method | GET |
| Path | /2/events/segmentation |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
e | query | string | Yes |
start | query | string | Yes |
end | query | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Amplitude connection from the Connection dropdown.
- In the Operation dropdown, select
analytics.queryEvents. - 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
| Detail | Value |
|---|---|
| Operation ID | analytics.getUserEvents |
| Method | GET |
| Path | /2/users/{amplitude_id}/events |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
amplitude_id | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Amplitude connection from the Connection dropdown.
- In the Operation dropdown, select
analytics.getUserEvents. - 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
| Detail | Value |
|---|---|
| Operation ID | analytics.queryFunnels |
| Method | GET |
| Path | /2/funnels |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
e | query | string | Yes |
start | query | string | Yes |
end | query | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Amplitude connection from the Connection dropdown.
- In the Operation dropdown, select
analytics.queryFunnels. - 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.