{
  "$result_object_key": [
    {
      "archived": false,
      "archived_at": "2024-07-04T10:32:12+00:00",
      "created_at": "2024-07-04T10:32:12+00:00",
      "id": "39580875173",
      "properties": {
        "hs_createdate": "2024-07-19T11:58:57.046Z",
        "hs_lastmodifieddate": "2024-07-19T14:29:14.882Z",
        "hs_object_id": 12345789
      },
      "updated_at": "2024-07-04T10:32:12+00:00"
    }
  ]
}

{
  "$result_object_key": [
    {
      "archived": "Whether the user was archived",
      "archived_at": "When the user was archived",
      "created_at": "When the user was created",
      "id": "ID",
      "properties": {
        "key": null,
        "value": null
      },
      "updated_at": "When the user was updated"
    }
  ]
}

​
Parameters

​
Action
Parameters
{
  "$result_object_key": [
    {
      "archived": false,
      "archived_at": "2024-07-04T10:32:12+00:00",
      "created_at": "2024-07-04T10:32:12+00:00",
      "id": "39580875173",
      "properties": {
        "hs_createdate": "2024-07-19T11:58:57.046Z",
        "hs_lastmodifieddate": "2024-07-19T14:29:14.882Z",
        "hs_object_id": 12345789
      },
      "updated_at": "2024-07-04T10:32:12+00:00"
    }
  ]
}

{
  "$result_object_key": [
    {
      "archived": "Whether the user was archived",
      "archived_at": "When the user was archived",
      "created_at": "When the user was created",
      "id": "ID",
      "properties": {
        "key": null,
        "value": null
      },
      "updated_at": "When the user was updated"
    }
  ]
}

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

​
[]User
Fetch Action Response Object