Skip to main content
images/google.svg

​
Parameters

​
Action
Parameters
{
  "$result_object_key": {
    "estimated_row_count": 1000,
    "partition": "2025-03-17",
    "schema_differences": [
      {
        "description": "Number of visits of this patient",
        "field": "number_of_visits",
        "field_addition": {},
        "field_type": "INTEGER",
        "field_update": {
          "new_description": "Number of visits of this patient",
          "new_field_type": "STRING",
          "new_repeated": true,
          "new_required": false
        },
        "nested_field_changes": null,
        "repeated": false,
        "required": true
      }
    ],
    "table_name": "healthie_patient_updated",
    "table_schema": [
      {
        "description": "Number of visits of this patient",
        "fields": null,
        "name": "number_of_visits",
        "repeated": false,
        "required": true,
        "type": "INTEGER"
      }
    ]
  }
}

{
  "$result_object_key": {
    "estimated_row_count": "Estimated total number of rows including the data just inserted",
    "partition": "Date partition the data was saved to",
    "schema_differences": {
      "description": "Field description",
      "field": "Field name",
      "field_addition": {},
      "field_type": "Field type",
      "field_update": {
        "new_description": "New description",
        "new_field_type": "New field type",
        "new_repeated": "New value for whether the field is a list",
        "new_required": "New value for whether the field is required"
      },
      "nested_field_changes": null,
      "repeated": "If the field is a list",
      "required": "If the field is required"
    },
    "table_name": "Table name used to save the data",
    "table_schema": {
      "description": "Field description",
      "fields": null,
      "name": "Field name",
      "repeated": "If the field is a list",
      "required": "If the field is required",
      "type": "Field type"
    }
  }
}

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