> ## Documentation Index
> Fetch the complete documentation index at: https://docs.morf.health/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Track

> Documentation for the Track action for Mixpanel

![images/mixpanel.svg](https://mintcdn.com/morfhealth/EU2WCxuXGIUQcziR/images/mixpanel.svg?fit=max\&auto=format\&n=EU2WCxuXGIUQcziR\&q=85\&s=c248ead83d12ab28ba87536b49b4936f)

# Parameters

**Action** `Parameters`

**parameters**

**Event Name** `string` *required*

This field maps to the destination API `name` field.

**Distinct ID** `string`

`ID` `PII`
This field maps to the destination API `distinct_id (defaults to profile ID)` field.

**Properties** `Map\<string,dynamic (any)\>`

This field maps to the destination API `properties` field.

```json Result Object Example theme={null}
{
  "$result_object_key": {
    "event_id": "3d86967c-ec0e-4369-9a5d-9664ce6eabdd"
  }
}
```

```json Result Object Description theme={null}
{
  "$result_object_key": {
    "event_id": "The track event ID registered in the call to Mixpanel's track endpoint"
  }
}
```

### Result Object Field Details

You can use the result of the action's data as inputs to downstream workflow actions.

Each fetch action requires an object name, which nests the action's result data inside the downstream data context in the workflow. See [Passing Data Between Actions](https://docs.morf.health/docs/knowledge_base/passing_data_between_actions.md) for how to set it and reference the result from downstream nodes.

Here we demonstrate how to refer to this data using the prefix `$result_object_key`.

**TrackEventResult** `Fetch Action Response Object`

**fields**

**event\_id** `string` *required*

The track event ID registered in the call to Mixpanel's track endpoint

```json CEL theme={null}
$result_object_key.event_id
```

```json Example theme={null}
"3d86967c-ec0e-4369-9a5d-9664ce6eabdd"
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.