Skip to main content
images/healthie.svg

​
Parameters

​
Action
Parameters
{
  "$result_object_key": {
    "id": "3265",
    "readable_source": "John Doe MS, LMFT",
    "ref_source": "12345",
    "ref_source_other": "Instagram",
    "ref_type": "referring_provider",
    "related_insurance_id": "12345",
    "related_object_id": "12345",
    "related_object_name": "Other"
  }
}

{
  "$result_object_key": {
    "id": "ID of the client source",
    "readable_source": "Get readable source based on ref_type",
    "ref_source": "The source of how a client was acquired: contain ID or a Other string",
    "ref_source_other": "If ref_source eq 'Other', than it may contain custom string or NULL",
    "ref_type": "The type of the source of how a client was acquired",
    "related_insurance_id": "ID of the related insurance",
    "related_object_id": "ID of the related object, or 'Other'",
    "related_object_name": "Name of the related object"
  }
}

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