Integrations / IcyPeas

TexAu × IcyPeas

API Key1 actions availableMCP-ready

Used by 1,200+ teams

Connect IcyPeas →Talk to sales
IcyPeas logo

TexAu integrates with IcyPeas. Enrich, sync, and automate every action from one API. Bring it into Claude, Cursor, or any MCP client. Built for sales, RevOps, and growth teams who want a programmable layer on top.

Built for Sales, RevOps, and growth teams running outbound..

1 actionsAPI KeyMCP-readyasync-safeREST + Webhooks

What you can build

Three workflows worth shipping with IcyPeas.

  • Enrich every new record before it hits IcyPeas

    Run the 32-integration waterfall on inbound, write the verified result back.

  • Sync TexAu Tables to IcyPeas on a schedule

    Bidirectional sync, conflict resolution, custom field mapping.

  • Trigger IcyPeas actions from Claude or your API

    Every action exposed as an MCP tool. Call it from any agent.

The catalog

Every IcyPeas action TexAu supports.

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

Enrich · 1

IcyPeas logoFind Email by Name and Domain (Icypeas)

The trace

How a IcyPeas workflow runs.

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

IcyPeas logoIcyPeas
TexAu enrichment
IcyPeas logoIcyPeas

Auth & setup

Connect IcyPeas in four steps.

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

    Generate an API key in IcyPeas

    IcyPeas settings → API → Create new key.

  2. 2

    Open Studio → Connections → IcyPeas

    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 IcyPeas

Bring IcyPeas 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-icypeas": {
      "command": "npx",
      "args": ["-y", "@texau/mcp-server"],
      "env": {
        "TEXAU_API_KEY": "...",
        "TEXAU_PLATFORM": "icypeas"
      },
      "tools": [
        "icypeas-find-email-by-name-and-domain"
      ]
    }
  }
}

Compared

Where TexAu wins vs native IcyPeas 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 Zapier or manual scripts to TexAu.

Most IcyPeas teams land on TexAu after they hit the ceiling of Zapier or manual scripts. 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 Zapier or manual scripts 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 IcyPeas 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 IcyPeas in Studio →

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

Start free →Talk to sales