Skip to main content

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.

images/healthie.svg

​
Parameters

​
Action
Parameters
{
  "$result_object_key": {
    "client_id": "789012",
    "created_at": "2024-01-15T10:30:00Z",
    "created_by_id": "123456",
    "due_date": "2024-01-20T10:30:00Z",
    "id": "678901",
    "note_content": "Follow up with patient regarding lab results",
    "priority": 0
  }
}

{
  "$result_object_key": {
    "client_id": "The identifier of the client associated with this task",
    "created_at": "The date and time this task was created",
    "created_by_id": "The identifier of the user who created this task",
    "due_date": "The date and time this task is due to be completed",
    "id": "Unique identifier for the task",
    "note_content": "The note content associated with the task",
    "priority": "Level of urgency for this task (0 = standard priority, 1 = high priority)"
  }
}

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