Appearance
Segment
Collect, unify, and route customer data with the Segment Tracking API.
| Detail | Value |
|---|---|
| Category | Analytics |
| Base URL | https://api.segment.io/v1 |
| Authentication | Bearer Token |
| Endpoints | 5 |
| Connector key | segment |
Using Segment in a workflow
- Go to Connections and click New Connection.
- Pick Segment 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 /identify | Identify a user |
POST /track | Track an event |
POST /page | Record a pageview |
POST /group | Associate a user with a group |
POST /batch | Send a batch of events |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
POST /identify
Identify a user
| Detail | Value |
|---|---|
| Operation ID | analytics.identify |
| Method | POST |
| Path | /identify |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
userId | string |
traits | object |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Segment 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 Segment API reference.
POST /track
Track an event
| Detail | Value |
|---|---|
| Operation ID | analytics.track |
| Method | POST |
| Path | /track |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
userId | string |
event | string |
properties | object |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Segment connection from the Connection dropdown.
- In the Operation dropdown, select
analytics.track. - 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 Segment API reference.
POST /page
Record a pageview
| Detail | Value |
|---|---|
| Operation ID | analytics.page |
| Method | POST |
| Path | /page |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
userId | string |
name | string |
properties | object |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Segment connection from the Connection dropdown.
- In the Operation dropdown, select
analytics.page. - 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 Segment API reference.
POST /group
Associate a user with a group
| Detail | Value |
|---|---|
| Operation ID | analytics.group |
| Method | POST |
| Path | /group |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
userId | string |
groupId | string |
traits | object |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Segment connection from the Connection dropdown.
- In the Operation dropdown, select
analytics.group. - 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 Segment API reference.
POST /batch
Send a batch of events
| Detail | Value |
|---|---|
| Operation ID | analytics.batch |
| Method | POST |
| Path | /batch |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
batch | array |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Segment connection from the Connection dropdown.
- In the Operation dropdown, select
analytics.batch. - 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 Segment API reference.