> ## Documentation Index
> Fetch the complete documentation index at: https://docs.morf.health/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Search Users

> Documentation for the Search Users action for Hubspot

![images/hubspot.svg](https://mintcdn.com/morfhealth/EU2WCxuXGIUQcziR/images/hubspot.svg?fit=max\&auto=format\&n=EU2WCxuXGIUQcziR\&q=85\&s=2c859a5e64b7620515d906bc05e45339)

# Parameters

**Action** `Parameters`

**parameters**

**Search Properties** `Map\<string,string\>` *required*

`HI` `ID` `PII`
This field maps to the destination API `search_properties` field.

**Properties to Return** `[]User Property`

`HI` `ID` `PII`
This field maps to the destination API `properties_to_return` field.

```json Result Object Example theme={null}
{
  "$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"
    }
  ]
}
```

```json Result Object Description theme={null}
{
  "$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 an object name, which nests the action's result data inside the downstream data context in the workflow. See [Passing Data Between Actions](https://docs.morf.health/docs/knowledge_base/passing_data_between_actions.md) for how to set it and reference the result from downstream nodes.

Here we demonstrate how to refer to this data using the prefix `$result_object_key`.

**\[]User** `Fetch Action Response Object`

**fields**

**id** `string` *required*

ID

```json CEL theme={null}
$result_object_key[*].id
```

```json Example theme={null}
"39580875173"
```

**properties** `Map\<string,string\>` *required*

User properties

```json CEL theme={null}
$result_object_key[*].properties
```

```json Example theme={null}
{
"hs_createdate": "2024-07-19T11:58:57.046Z",
"hs_lastmodifieddate": "2024-07-19T14:29:14.882Z",
"hs_object_id": 12345789
}
```

**archived** `bool` *required*

Whether the user was archived

```json CEL theme={null}
$result_object_key[*].archived
```

```json Example theme={null}
false
```

**archived\_at** `timing.v1.Timestamp`

When the user was archived

```json CEL theme={null}
$result_object_key[*].archived_at
```

```json Example theme={null}
"2024-07-04T10:32:12+00:00"
```

**created\_at** `timing.v1.Timestamp` *required*

When the user was created

```json CEL theme={null}
$result_object_key[*].created_at
```

```json Example theme={null}
"2024-07-04T10:32:12+00:00"
```

**updated\_at** `timing.v1.Timestamp` *required*

When the user was updated

```json CEL theme={null}
$result_object_key[*].updated_at
```

```json Example theme={null}
"2024-07-04T10:32:12+00:00"
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.