---
title: "lemlist"
description: "lemlist on looot as of 2026-09-28: 5 jobs through 5 endpoints, how you reach it, what it costs, and how to run it."
---

{/* Generated by scripts/generate-providers.mjs from data/providers.json. Do not edit. */}

<ProviderHeader id="lemlist" />

## What it's good for

lemlist is in Workspace & CRM. Reach for it to analytics outreach campaign; list outreach campaign; add outreach lead.

As of 2026-09-28 (catalog revision 85280) it serves 5 jobs through 5 endpoints.

## Jobs

| Job id | What it does | Endpoints |
| --- | --- | --- |
| `outreach.campaign.analytics` | Analytics outreach campaign | 1 |
| `outreach.campaign.list` | List outreach campaign | 1 |
| `outreach.campaign.pause` | Pause outreach campaign | 1 |
| `outreach.lead.add` | Add outreach lead | 1 |
| `outreach.lead.update` | Update outreach lead | 1 |

## Access

- **Needs your own key** for 5 endpoints: looot has no key of its own for them yet. See [Bring your own key](/guides/bring-your-own-key).

## Price basis

5 free. A call that fails at the provider costs $0; see [What's free](/money/free-and-failures).

## Free first in fallback

Yes. 5 endpoints cost $0, and a $0 row is tried ahead of the paid rows in its bucket. See [Free first](/concepts/free-first).

## Run it

A job run takes shared input names, not lemlist's own field names; looot maps them for each provider. For `job:outreach.lead.update`, `company` is taken by 1 of its 1 providers, `first_name` is taken by 1 of its 1 providers, `last_name` is taken by 1 of its 1 providers. See [Job inputs](/concepts/job-inputs).

Example input for `looot run` or the MCP [`run`](/mcp-tools/run) tool, with placeholder values:

<CodeGroup>

```bash CLI
looot run job:outreach.lead.update --input '{"company":"Example Inc","first_name":"Jane","last_name":"Doe"}'
```

```json MCP
{
  "endpointId": "job:outreach.lead.update",
  "input": {
    "company": "Example Inc",
    "first_name": "Jane",
    "last_name": "Doe"
  },
  "idempotencyKey": "<new unique key>"
}
```

</CodeGroup>

A job run picks among all the job's providers. To run lemlist itself, name one of its endpoints (MCP [`search`](/mcp-tools/search) with `{"filters": {"provider": "lemlist"}}` lists them), for example `lemlist-update-lead`: `looot inspect lemlist-update-lead` prints its exact input fields and price.

## In the live catalog

- Browse: [looot.ai/public-catalog/lemlist-campaign-stats](https://looot.ai/public-catalog/lemlist-campaign-stats), or search [looot.ai/public-catalog](https://looot.ai/public-catalog?text=lemlist) for lemlist.
- Every endpoint, no account needed: `curl "https://api.looot.ai/v1/public-catalog?provider=lemlist"`

lemlist's name and logo are trademarks of their owner, shown to identify the provider.

<Related />