Lemlist: List Enrichment Providers

List Enrichment Providers.

Tool ID: lemlist_list_enrichment_providers

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.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'lemlist_list_enrichment_providers',
  {
    "type": "email"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute lemlist_list_enrichment_providers --input '{
  "type": "email"
}' --json

Example response

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

{
  "data": {
    "data": [
      {
        "id": "id_123",
        "displayName": "Example",
        "types": [
          "email"
        ],
        "source": "internal"
      }
    ]
  }
}

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

Input reference

Lists the providers your team can place in a waterfall, for one enrichment type. This is the catalog of legal providers[].id values for the waterfall endpoints: read it before creating or updating a waterfall. It includes lemlist internal providers and the external providers lemlist supports through your own API key. An external provider has connected: false until you connect it with your own API key; a waterfall cannot enable a provider that is not connected.

Name	Type	Required	Default	Details
`payload.type`	`"email" \| "phone"`	Yes	—	Enrichment type of the providers to list. Allowed: `email`, `phone`.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.data`	`array`	No	—	Providers available for the requested type, in the lemlist default order
`result.data.data[].id`	`string`	Yes	—	Stable identifier, to use as `providers[].id` in the waterfall endpoints.
`result.data.data[].displayName`	`string`	Yes	—	Name shown in the lemlist app.
`result.data.data[].types`	`array`	Yes	—	Enrichment types this provider supports.
`result.data.data[].source`	`"internal" \| "external"`	Yes	—	`internal`: paid with lemlist credits, always available. `external`: called with your own API key, saved through the connection endpoint. Allowed: `internal`, `external`.
`result.data.data[].connected`	`boolean`	No	—	Only on external providers: `true` once its API key is saved in lemlist. A waterfall can only enable a connected provider.
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

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

Get started

Build and automate

Common workflows

Data and integrations

Reference

Lemlist: List Enrichment Providers

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation