{
  "$result_object_key":  {
    "id":  "789012"
  }
}

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

​
Parameters

​
Action
Parameters
​
Simple Added Users
[]string
required

PII This field maps to the destination API simple_added_users field.

​
Owner ID
string
required

ID This field maps to the destination API owner_id field.

​
Name
string
required

PII This field maps to the destination API name field.

​
Note
string
required

This field maps to the destination API note.content field.

​
Appointment ID
string

This field maps to the destination API appointment_id field.

{
  "$result_object_key":  {
    "id":  "789012"
  }
}

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

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

​
Conversation
Fetch Action Response Object
​
id
string
required

Unique identifier for the conversation

CEL
$result_object_key.id
Example
"789012"