> ## 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.

# Add Internal Note To Conversation

> Documentation for the Add Internal Note To Conversation action for Spruce

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

# Parameters

**Action** `Parameters`

**parameters**

**Conversation ID** `string` *required*

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

**Note** `string` *required*

`HI` `ID` `PII`
This field maps to the destination API `body.value` field.

```json Result Object Example theme={null}
{
  "$result_object_key": {
    "request_id": "asyncRequest_0D4QABCC06000"
  }
}
```

```json Result Object Description theme={null}
{
  "$result_object_key": {
    "request_id": "Asynchronous request ID for the message sent."
  }
}
```

### 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`.

**MessageSent** `Fetch Action Response Object`

**fields**

**request\_id** `string` *required*

Asynchronous request ID for the message sent.

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

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


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