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

# Upcell: Contact Existence

> Check which contact fields, such as email or phone, are on file for a person before enriching them. Includes SDK V2 examples, schemas, and cost.

Check which contact fields, such as email or phone, are on file for a person before enriching them.

> [!NOTE]
>
> Tool ID: `upcell_contact_existence`

## Run this action

Use the TypeScript SDK for one call. Use `ctx.tools.execute(...)` inside a Play for durable calls, scheduled calls, or CSV processing.

```ts theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'upcell_contact_existence',
  {
    "contact": {
      "linkedinUrl": "https://www.linkedin.com/in/jane-doe",
      "firstName": "Jane",
      "lastName": "Doe"
    },
    "existenceFields": [
      "email"
    ]
  },
);

console.log(result.toolResponse.raw);
```

### CLI

```bash theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
deepline tools execute upcell_contact_existence --input '{
  "contact": {
    "linkedinUrl": "https://www.linkedin.com/in/jane-doe",
    "firstName": "Jane",
    "lastName": "Doe"
  },
  "existenceFields": [
    "email"
  ]
}' --json
```

## Example response

The static output schema lacks the details for a reliable example. Use `deepline describe upcell_contact_existence --json` for the complete live contract.

## Input reference

Check for the existence of specific contact fields for a given contact from **upcell’s** database. This endpoint accepts a Contact object and a list of fields to check. The response contains a map where the key is the field and value is true/false for the existence of that field in upcell's database. ### Request Body | **Field** | **Type** | **Description** | **Required** | | --- | --- | --- | --- | | `contact` | `Contact` | Contact data to match to check for existence of fields. Supports: linkedinUrl, firstName, lastName, title, companyName, companyDomain, companySocialUrl, email, personalEmail | ✅ Yes | | `existenceFields` | `array` | List of fields to check for existence (e.g., `mobile`). | ✅ Yes | ### Possible Existence Field Values - `mobile` --- ### Example Request (JSON) \`\`\` json \{ "contact": \{ "linkedinUrl": "[https://www.linkedin.com/in/marklbedard/](https://www.linkedin.com/in/marklbedard/)" }, "existenceFields": \[ See the live schema below for the complete notes.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `payload.contact` | `object` | Yes | — | Contact data to match. Supports linkedinUrl, firstName, lastName, title, companyName, companyDomain, companySocialUrl, email, personalEmail. |
| `payload.existenceFields` | `array` | Yes | — | List of fields to check for existence (e.g., mobile). |

<details>
  <summary>Show raw input schema</summary>

  ### Input JSON Schema

  ````json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
  {
    "type": "object",
    "description": "Check for the existence of specific contact fields for a given contact from **upcell’s** database. This endpoint accepts a Contact object and a list of fields to check. The response contains a map where the key is the field and value is true/false for the existence of that field in upcell's database. ### Request Body | **Field** | **Type** | **Description** | **Required** | | --- | --- | --- | --- | | `contact` | `Contact` | Contact data to match to check for existence of fields. Supports: linkedinUrl, firstName, lastName, title, companyName, companyDomain, companySocialUrl, email, personalEmail | ✅ Yes | | `existenceFields` | `array` | List of fields to check for existence (e.g., `mobile`). | ✅ Yes | ### Possible Existence Field Values - `mobile` --- ### Example Request (JSON) ``` json { \"contact\": { \"linkedinUrl\": \"https://www.linkedin.com/in/marklbedard/\" }, \"existenceFields\": [ \"mobile\" ] } ``` --- ### Response The response returns a map of fields to a boolean (true/false) if that field exists for the given contact in upcell's database. #### Example Success Response ``` json { \"fieldsExistence\": { \"mobile\": true } } ``` --- ### Error Handling The API returns appropriate error messages with status codes if something goes wrong. | **Error Code** | **Message** | **Description** | | --- | --- | --- | | 400 | Invalid Request | Verify your request is properly formatted | | 401 | Unauthorized | Verify you are using a valid API key | | 500 | Internal Server Error | An unexpected error occurred. | #### Example Error Response ``` json { \"error\": { \"code\": 400, \"message\":\"Contact is required for existence check\" } } ```",
    "properties": {
      "contact": {
        "type": "object",
        "description": "Contact data to match. Supports linkedinUrl, firstName, lastName, title, companyName, companyDomain, companySocialUrl, email, personalEmail.",
        "properties": {
          "linkedinUrl": {
            "type": "string"
          },
          "firstName": {
            "type": "string"
          },
          "lastName": {
            "type": "string"
          },
          "title": {
            "type": "string"
          },
          "companyName": {
            "type": "string"
          },
          "companyDomain": {
            "type": "string"
          },
          "companySocialUrl": {
            "type": "string"
          },
          "email": {
            "type": "string"
          },
          "personalEmail": {
            "type": "string"
          }
        },
        "additionalProperties": false
      },
      "existenceFields": {
        "type": "array",
        "description": "List of fields to check for existence (e.g., mobile).",
        "items": {
          "type": "string"
        }
      }
    },
    "required": [
      "contact",
      "existenceFields"
    ],
    "additionalProperties": false
  }
  ````
</details>

## Output reference

Standard tool result payload.

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `result.data` | `unknown` | Yes | — | Provider response payload. |
| `result.meta` | `object` | No | — | Additional response metadata (status, paging). |

<details>
  <summary>Show raw output schema</summary>

  ### Output JSON Schema

  ```json theme={"languages":{"custom":["/languages/deepline-prompt.json"]}}
  {
    "type": "object",
    "description": "Standard tool result payload.",
    "properties": {
      "data": {
        "description": "Provider response payload."
      },
      "meta": {
        "type": "object",
        "description": "Additional response metadata (status, paging).",
        "additionalProperties": true
      }
    },
    "required": [
      "data"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Deepline cost

* Pricing model: `fixed` (per call).
* Estimated Deepline credits: `0` per pricing unit.
* Provider-native pricing may still exist outside Deepline credit billing.

## Related documentation

* [Upcell provider guide](https://deepline.com/docs/providers/upcell/guide.md)
* [SDK V2 quickstart](https://deepline.com/docs/sdk-v2/quickstart.md)
* [SDK reference](https://deepline.com/docs/sdk-v2/sdk-reference.md)
* [Run tools across a CSV](https://deepline.com/docs/sdk-v2/batch-csv.md)


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