{
  "$result_object_key":  {
    "external_id":  "f3b87a2e09d514c6c2e79b9a",
    "id":  "5ba682d23d7cf92bef87bfd4"
  }
}

{
  "$result_object_key":  {
    "external_id":  "The unique identifier for the contact which is provided by the Client.",
    "id":  "The unique identifier for the contact which is given by Intercom."
  }
}

​
Parameters

​
Action
Parameters
​
ID
string

This field maps to the destination API id field.

{
  "$result_object_key":  {
    "external_id":  "f3b87a2e09d514c6c2e79b9a",
    "id":  "5ba682d23d7cf92bef87bfd4"
  }
}

{
  "$result_object_key":  {
    "external_id":  "The unique identifier for the contact which is provided by the Client.",
    "id":  "The unique identifier for the contact which is given by Intercom."
  }
}

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

​
ArchivedContact
Fetch Action Response Object
​
id
string
required

The unique identifier for the contact which is given by Intercom.

CEL
$result_object_key.id
Example
"5ba682d23d7cf92bef87bfd4"
​
external_id
string

The unique identifier for the contact which is provided by the Client.

CEL
$result_object_key.external_id
Example
"f3b87a2e09d514c6c2e79b9a"