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

# ContactFindInput

> Request body for the find contact inbound webhook endpoint.

Used in: [Find Contact](/inbound-find)

***

## Fields

| Field           | Type              | Required | Description                                                                                                                             |
| --------------- | ----------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| `full_name`     | string            | No\*     | Contact name to search                                                                                                                  |
| `phone_number`  | string            | No\*     | Phone number to search                                                                                                                  |
| `contact_email` | string            | No\*     | Email address to search                                                                                                                 |
| `match_any`     | boolean or string | No       | If `true`, falls back to individual field searches when strict matching returns no results. Accepts string `"true"` (case-insensitive). |

\*At least one of `full_name`, `phone_number`, or `contact_email` is required.

## Example

```json theme={null}
{
  "full_name": "John Doe",
  "phone_number": "5550000001",
  "match_any": false
}
```

## Notes

<Note>
  By default, all provided fields must match the same contact (strict mode). Set `match_any: true` to fall back to individual field lookups if no strict match is found.
</Note>

<Note>
  `match_any` accepts the string `"true"` for integrations that serialize booleans as strings (e.g. some Zapier steps).
</Note>