{
  "$result_object_key":  {
    "id":  "678901"
  }
}

{
  "$result_object_key":  {
    "id":  "Unique identifier for the task"
  }
}

​
Parameters

​
Action
Parameters
​
Patient ID
string

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

​
Assigner ID
string
required

ID This field maps to the destination API user_id 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.

{
  "$result_object_key":  {
    "id":  "678901"
  }
}

{
  "$result_object_key":  {
    "id":  "Unique identifier for the task"
  }
}

​
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
​
id
string
required

Unique identifier for the task

CEL
$result_object_key.id
Example
"678901"