{ "$result_object_key": { "conversation_id": "conv_12345", "created_at": "2025-01-15T13:12:41Z", "id": "item_12345", "is_internal_note": false, "text": "Hello, how can I help you today?" }}
{ "$result_object_key": { "conversation_id": "ID of the conversation this item belongs to.", "created_at": "Timestamp when the conversation item was created.", "id": "Unique identifier for the conversation item in the Spruce system.", "is_internal_note": "Whether this is an internal note (not visible to patients).", "text": "Text content of the conversation item." }}
v1
Find First Matching Conversation Item
Documentation for the Find First Matching Conversation Item action for Spruce
This field maps to the destination API text field.
{ "$result_object_key": { "conversation_id": "conv_12345", "created_at": "2025-01-15T13:12:41Z", "id": "item_12345", "is_internal_note": false, "text": "Hello, how can I help you today?" }}
{ "$result_object_key": { "conversation_id": "ID of the conversation this item belongs to.", "created_at": "Timestamp when the conversation item was created.", "id": "Unique identifier for the conversation item in the Spruce system.", "is_internal_note": "Whether this is an internal note (not visible to patients).", "text": "Text content of the conversation item." }}
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.