{ "$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." }}
v1
Archive Contact
Documentation for the Archive Contact action for Intercom
{ "$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_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." }}
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.