> ## Documentation Index
> Fetch the complete documentation index at: https://docs.morf.health/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Update Client Source

> Documentation for the Update Client Source action for Healthie

![images/healthie.svg](https://mintcdn.com/morfhealth/EU2WCxuXGIUQcziR/images/healthie.svg?fit=max\&auto=format\&n=EU2WCxuXGIUQcziR\&q=85\&s=d168a24dbae69f2202ca63dd7aa2e1f3)

# Parameters

**Action** `Parameters`

**parameters**

**Reference Source** `string`

`ID`
This field maps to the destination API `ref_source` field.

**Reference Source Other** `string`

`ID`
This field maps to the destination API `ref_source_other` field.

**Reference Type** `string`

This field maps to the destination API `ref_type` field.

**Patient ID** `string`

`ID`
This field maps to the destination API `user_id` field.

```json Result Object Example theme={null}
{
  "$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"
  }
}
```

```json Result Object Description theme={null}
{
  "$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 an object name, which nests the action's result data inside the downstream data context in the workflow. See [Passing Data Between Actions](https://docs.morf.health/docs/knowledge_base/passing_data_between_actions.md) for how to set it and reference the result from downstream nodes.

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

**ClientSource** `Fetch Action Response Object`

**fields**

**id** `string` *required*

ID of the client source

```json CEL theme={null}
$result_object_key.id
```

```json Example theme={null}
"3265"
```

**readable\_source** `string`

Get readable source based on ref\_type

```json CEL theme={null}
$result_object_key.readable_source
```

```json Example theme={null}
"John Doe MS, LMFT"
```

**ref\_source** `string`

The source of how a client was acquired: contain ID or a Other string

```json CEL theme={null}
$result_object_key.ref_source
```

```json Example theme={null}
"12345"
```

**ref\_source\_other** `string`

If ref\_source eq 'Other', than it may contain custom string or NULL

```json CEL theme={null}
$result_object_key.ref_source_other
```

```json Example theme={null}
"Instagram"
```

**ref\_type** `string`

The type of the source of how a client was acquired

```json CEL theme={null}
$result_object_key.ref_type
```

```json Example theme={null}
"referring_provider"
```

**related\_insurance\_id** `string`

ID of the related insurance

```json CEL theme={null}
$result_object_key.related_insurance_id
```

```json Example theme={null}
"12345"
```

**related\_object\_id** `string`

ID of the related object, or 'Other'

```json CEL theme={null}
$result_object_key.related_object_id
```

```json Example theme={null}
"12345"
```

**related\_object\_name** `string`

Name of the related object

```json CEL theme={null}
$result_object_key.related_object_name
```

```json Example theme={null}
"Other"
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.