Skip to main content
images/hubspot.svg

​
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": "2970281109",
    "properties": {
      "content": "Ticket description",
      "createdate": "2024-07-16T10:41:02.266Z",
      "hs_lastmodifieddate": "2024-07-16T14:27:29.505Z",
      "hs_object_id": "2970281109",
      "hs_pipeline": "0",
      "hs_pipeline_stage": "1",
      "subject": "My Subject"
    },
    "updated_at": "2024-07-04T10:32:12+00:00"
  }
}

{
  "$result_object_key": {
    "archived": "Whether the ticket was archived",
    "archived_at": "When the ticket was archived",
    "created_at": "When the ticket was created",
    "id": "ID",
    "properties": {
      "key": null,
      "value": null
    },
    "updated_at": "When the ticket 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.
​
Ticket
Fetch Action Response Object