{
  "$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"
  }
}

Parameters

Action

Parameters

Hide parameters

Metric Entry ID

string

required

This field maps to the destination API id field.

Metric Entry Value

float64 (double)

required

This field maps to the destination API metric_stat field.

{
  "$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

Hide fields

string

required

The unique identifier of the entry

CEL

$result_object_key.id

Example

"890123"

type

string

The type for this entry, options are - FoodEntry, WorkoutEntry, MirrorEntry, SleepEntry, NoteEntry, WaterIntakeEntry, PoopEntry’, null: false

CEL

$result_object_key.type

Example

"FoodEntry"

added_by_user

string

ID of user that added the entry

CEL

$result_object_key.added_by_user

Example

"901234"

category

string

The category of this entry

CEL

$result_object_key.category

Example

"Breakfast"

emotions

string

The users emotions towards the meal

CEL

$result_object_key.emotions

Example

"Happy"

name

string

The name for this entry

CEL

$result_object_key.name

Example

"Morning Smoothie"

description

string

The description for the entry

CEL

$result_object_key.description

Example

"Banana and protein smoothie after workout"

created_at

timing.v1.Timestamp

required

The time at which this entry was created

CEL

$result_object_key.created_at

Example

"2023-04-01T14:30:00Z"

value

float64 (double)

The metric_stat value of the metric entry

CEL

$result_object_key.value

Example

{
  "$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_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"
  }
}

Parameters

Action

Parameters

Hide parameters

Metric Entry ID

string

required

This field maps to the destination API id field.

Metric Entry Value

float64 (double)

required

This field maps to the destination API metric_stat field.

{
  "$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

Hide fields

string

required

The unique identifier of the entry

CEL

$result_object_key.id

Example

"890123"

type

string

The type for this entry, options are - FoodEntry, WorkoutEntry, MirrorEntry, SleepEntry, NoteEntry, WaterIntakeEntry, PoopEntry’, null: false

CEL

$result_object_key.type

Example

"FoodEntry"

added_by_user

string

ID of user that added the entry

CEL

$result_object_key.added_by_user

Example

"901234"

Update Metric Entry

Parameters

Result Object Field Details

Update Metric Entry

Parameters

Result Object Field Details

​Parameters

​Result Object Field Details

​Parameters

​Result Object Field Details

Parameters

Result Object Field Details

Parameters

Result Object Field Details