Integrations / Lemlist

TexAu × Lemlist

API Key23 actions availableMCP-ready

Used by 1,200+ teams

Connect Lemlist →Talk to sales
Lemlist logo

TexAu enriches every Lemlist campaign before send (phone, email, intent). Map any TexAu column to a Lemlist variable. Built for outbound SDRs and agency cold-email teams who refuse to send to unverified lists.

Built for outbound SDRs and agency cold-email teams.

23 actionsAPI KeyMCP-readyasync-safeREST + Webhooks

What you can build

Three workflows worth shipping with Lemlist.

  • Enrich before Lemlist sends

    Run the waterfall, only push verified emails, map any column to a Lemlist variable.

  • Personalize at the icebreaker level

    Pull a recent post, write a one-line intro into a custom variable, send.

  • Pull replies back into a TexAu Table

    Reply landed? Surface it next to the original enrichment context.

The catalog

Every Lemlist action TexAu supports.

Grouped by verb. Each row links to the full input/output schema and a try-it widget.

Action catalog is syncing. Check back shortly.

The trace

How a Lemlist workflow runs.

Lemlist → TexAu enrichment → Lemlist writeback. One trace, every step observable.

Lemlist logoLemlist
TexAu enrichment
Lemlist logoLemlist

Auth & setup

Connect Lemlist in four steps.

Screenshots coming soon. The flow below is the live four-step setup.
  1. 1

    Generate an API key in Lemlist

    Lemlist settings → API → Create new key.

  2. 2

    Open Studio → Connections → Lemlist

    Paste the key. We store it encrypted at rest.

  3. 3

    We test the connection on save

    Bad key? You see the error inline before any workflow runs.

  4. 4

    Run your first action

    Pick any action from the catalog above and try it live.

MCP for Lemlist

Bring Lemlist into Claude, Cursor, or any MCP client.

Drop this into your config. Every action above becomes a tool the model can call.

claude_desktop_config.json
{
  "mcpServers": {
    "texau-lemlist": {
      "command": "npx",
      "args": ["-y", "@texau/mcp-server"],
      "env": {
        "TEXAU_API_KEY": "...",
        "TEXAU_PLATFORM": "lemlist"
      },
      "tools": [
        "lemlist-example-action"
      ]
    }
  }
}

Compared

Where TexAu wins vs native Lemlist automation.

Enrichment depth

Native: one provider. TexAu: 32-integration waterfall with attribution.

Branching logic

Native: linear. TexAu: real conditionals, retries, async-safe steps.

AI surface

Native: none. TexAu: every action is also an MCP tool.

Migration

From manual list-building to TexAu.

Most Lemlist teams land on TexAu after they hit the ceiling of manual list-building. The pattern is the same: a workflow worked for the first 10 contacts, then it broke at 1,000. Steps timed out. Branching turned into a Frankenstein. Enrichment was always one provider deep, so half the rows came back empty.

TexAu replaces the brittle middle. The 32-integration waterfall fills the rows that manual list-building left empty. Async-safe steps mean a slow LinkedIn fetch does not block the whole run. Branching is real branching, not nested filters. And every action you build for Lemlist is also an MCP tool. Claude can call it, your API can call it, your Studio operator can run it from a Table.

We import existing workflows. We do not ask you to rebuild from scratch. Most teams are running the same automations on TexAu within a week, with deeper enrichment and observable traces from day one.

Connect Lemlist in Studio →

Free to start. No credit card. Every action above runs in your first session.

Start free →Talk to sales