{
  "$result_object_key":  {
    "event_id":  "3d86967c-ec0e-4369-9a5d-9664ce6eabdd"
  }
}

{
  "$result_object_key":  {
    "event_id":  "The track event ID registered in the call to Mixpanel's track endpoint"
  }
}

​
Parameters

​
Action
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)>
required

This field maps to the destination API properties field.

{
  "$result_object_key":  {
    "event_id":  "3d86967c-ec0e-4369-9a5d-9664ce6eabdd"
  }
}

{
  "$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 a result object key to be specified which will nest the action’s result data inside the downstream data context in the Workflow.

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

​
TrackEventResult
Fetch Action Response Object
​
event_id
string
required

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

CEL
$result_object_key.event_id
Example
"3d86967c-ec0e-4369-9a5d-9664ce6eabdd"