> ## 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.

# Lemlist: Post Leads Leadid Enrich

> Enrich Lead. Lemlist Post Leads Leadid Enrich reference includes SDK V2 and CLI requests, input constraints, response fields, and Deepline cost.

Enrich Lead.

<Info>
  Tool ID: `lemlist_post_leads_leadid_enrich`
</Info>

## Run this action

Use the TypeScript SDK for a single call. Put `ctx.tools.execute(...)` inside a Play when the call should be durable, scheduled, or run across a CSV.

```ts theme={null}
import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'lemlist_post_leads_leadid_enrich',
  {
    "leadId": "lead_123"
  },
);

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

### CLI

```bash theme={null}
deepline tools execute lemlist_post_leads_leadid_enrich --input '{
  "leadId": "lead_123"
}' --json
```

## Example response

The SDK exposes this shape at `result.toolResponse.raw`. Values below are representative.

```json theme={null}
{
  "data": {
    "id": "id_123"
  }
}
```

Use `deepline tools get lemlist_post_leads_leadid_enrich --json` for the latest machine-readable contract.

## Input reference

Enrich Lead

| Name | Type | Required | Default | Details |
| - | - | - | - | - |
| `payload.leadId` | `string` | Yes | — | Unique lead ID |
| `payload.findEmail` | `boolean` | No | — | Search email address in another campaign |
| `payload.verifyEmail` | `boolean` | No | — | Find verified email |
| `payload.linkedinEnrichment` | `boolean` | No | — | Run LinkedIn enrichment |
| `payload.findPhone` | `boolean` | No | — | Find phone number |
| `payload.webhookUrl` | `string` | No | — | Webhook URL for enrichment events |
| `payload.force` | `boolean` | No | — | Re-run an enrichment that would otherwise be skipped. Bypasses skips caused by data already present on the contact: existing email, existing phone, LinkedIn enrichment already done for the same `linkedinUrl` / `linkedinUrlSalesNav`, or email already having a deliverability status. Does **not** bypass: - **Enrichment currently in progress** — if another enrichment is already running for this contact, the request is still skipped (no parallel enrichments, no double billing). - \*\*Previously See the live schema for the complete constraint. |

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

  ### Input JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "description": "Enrich Lead",
    "properties": {
      "leadId": {
        "type": "string",
        "description": "Unique lead ID"
      },
      "findEmail": {
        "type": "boolean",
        "description": "Search email address in another campaign"
      },
      "verifyEmail": {
        "type": "boolean",
        "description": "Find verified email"
      },
      "linkedinEnrichment": {
        "type": "boolean",
        "description": "Run LinkedIn enrichment"
      },
      "findPhone": {
        "type": "boolean",
        "description": "Find phone number"
      },
      "webhookUrl": {
        "type": "string",
        "description": "Webhook URL for enrichment events"
      },
      "force": {
        "type": "boolean",
        "description": "Re-run an enrichment that would otherwise be skipped. Bypasses skips caused by data already present on the contact: existing email, existing phone, LinkedIn enrichment already done for the same `linkedinUrl` / `linkedinUrlSalesNav`, or email already having a deliverability status. Does **not** bypass: - **Enrichment currently in progress** — if another enrichment is already running for this contact, the request is still skipped (no parallel enrichments, no double billing). - **Previously returned not-found** — for `findEmail` and `findPhone`, if a prior enrichment with the same inputs (`linkedinUrl`, `linkedinUrlSalesNav`, first / last name, company name / domain / LinkedIn URL) already returned not-found, the request is still skipped. Changing any of those inputs on the lead lifts the block without needing `force`."
      }
    },
    "required": [
      "leadId"
    ],
    "additionalProperties": false
  }
  ```
</details>

## Output reference

Standard tool result payload.

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

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

  ### Output JSON Schema

  ```json theme={null}
  {
    "type": "object",
    "description": "Standard tool result payload.",
    "properties": {
      "data": {
        "type": "object",
        "description": "Provider response payload.",
        "properties": {
          "id": {
            "type": "string",
            "description": "Enrichment ID"
          }
        },
        "additionalProperties": false
      },
      "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

* [Lemlist provider guide](/docs/providers/lemlist/guide)
* [SDK V2 quickstart](/docs/sdk-v2/quickstart)
* [SDK reference](/docs/sdk-v2/sdk-reference)
* [Run tools across a CSV](/docs/sdk-v2/batch-csv)


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