{ "$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" } ]}
v1
Search Users
Documentation for the Search Users action for Hubspot
{ "$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" } ]}
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.