{
  "$result_object_key": {
    "email_address": "john.doe@example.com",
    "first_name": "John",
    "id": "212012",
    "is_emergency_contact": true,
    "last_name": "Doe",
    "phone_number": "+15551234123",
    "relationship": "Caregiver"
  }
}
{
  "$result_object_key": {
    "email_address": "Email address of the notification contact",
    "first_name": "First name of the notification contact",
    "id": "ID for the notification contact",
    "is_emergency_contact": "Whether the notification contact is an emergency contact",
    "last_name": "Last name of the notification contact",
    "phone_number": "Phone number of the notification contact",
    "relationship": "Relationship between the notification contact and the user"
  }
}

Parameters

Action
Parameters
{
  "$result_object_key": {
    "email_address": "john.doe@example.com",
    "first_name": "John",
    "id": "212012",
    "is_emergency_contact": true,
    "last_name": "Doe",
    "phone_number": "+15551234123",
    "relationship": "Caregiver"
  }
}
{
  "$result_object_key": {
    "email_address": "Email address of the notification contact",
    "first_name": "First name of the notification contact",
    "id": "ID for the notification contact",
    "is_emergency_contact": "Whether the notification contact is an emergency contact",
    "last_name": "Last name of the notification contact",
    "phone_number": "Phone number of the notification contact",
    "relationship": "Relationship between the notification contact and the user"
  }
}

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.

NotificationContact
Fetch Action Response Object