Skip to main content
images/healthie.svg

​
Parameters

​
Action
Parameters
{
  "$result_object_key": {
    "added_by_user": "901234",
    "category": "Breakfast",
    "created_at": "2023-04-01T14:30:00Z",
    "description": "Banana and protein smoothie after workout",
    "emotions": "Happy",
    "id": "890123",
    "name": "Morning Smoothie",
    "type": "FoodEntry",
    "value": 450
  }
}

{
  "$result_object_key": {
    "added_by_user": "ID of user that added the entry",
    "category": "The category of this entry",
    "created_at": "The time at which this entry was created",
    "description": "The description for the entry",
    "emotions": "The users emotions towards the meal",
    "id": "The unique identifier of the entry",
    "name": "The name for this entry",
    "type": "The type for this entry, options are - FoodEntry, WorkoutEntry, MirrorEntry, SleepEntry, NoteEntry, WaterIntakeEntry, PoopEntry', null: false",
    "value": "The `metric_stat` value of the metric entry"
  }
}

​
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.
​
MetricEntry
Fetch Action Response Object