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

# Create Task

> Documentation for the Create Task 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**

**Patient ID** `string`

`ID`
This field maps to the destination API `client_id, overrides profile ID if specified` field.

**Assigner ID** `string`

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

**Content** `string` *required*

`HI`
This field maps to the destination API `content` field.

**Due Date** `string` *required*

`HI`
This field maps to the destination API `due_date` field.

**Created By ID** `string`

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

**Priority** `int64`

This field maps to the destination API `priority - 0 is standard (default if not set), 1 is high` field.

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

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

**Task** `Fetch Action Response Object`

**fields**

**id** `string` *required*

Unique identifier for the task

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

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

**created\_by\_id** `string`

`ID` The identifier of the user who created this task

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

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

**client\_id** `string`

`ID` The identifier of the client associated with this task

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

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

**note\_content** `string`

The note content associated with the task

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

```json Example theme={null}
"Follow up with patient regarding lab results"
```

**due\_date** `timing.v1.Timestamp`

The date and time this task is due to be completed

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

```json Example theme={null}
"2024-01-20T10:30:00Z"
```

**created\_at** `timing.v1.Timestamp` *required*

The date and time this task was created

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

```json Example theme={null}
"2024-01-15T10:30:00Z"
```

**priority** `int64` *required*

Level of urgency for this task (0 = standard priority, 1 = high priority)

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

```json Example theme={null}
0
```


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