IcyPeas on TexAu
Drive IcyPeas from your code, your CRM, or directly from Claude and Cursor. Every action is exposed as REST and as an MCP tool — no glue code, no Zapier middleman.
Top actions
Most-used IcyPeas actions
Quick links into the 1-action catalog. Each action page has the full input/output schema and a try-it widget.
What teams build
Common IcyPeas workflows on TexAu
Enrich on the way in
Trigger on a new IcyPeas record, run the 32-integration waterfall, write verified fields back.
Sync to a TexAu Table
Pull on a schedule, enrich in a Table, push the deltas back. Custom field mapping, conflict resolution, observable trace.
Call from Claude
Every action above is also an MCP tool. Wire IcyPeas into Claude, Cursor, or any MCP client with one config block.
Related other apps
Other Other integrations
FAQ
IcyPeas on TexAu — common questions
How many IcyPeas actions does TexAu support?
TexAu supports 1 public IcyPeas action. Every action is callable as REST and as an MCP tool.
Can I call IcyPeas from Claude or Cursor?
Yes. Every IcyPeas action on TexAu is exposed as an MCP tool, so Claude, Cursor, and any MCP client can invoke it directly.
Is IcyPeas sync bidirectional on TexAu?
TexAu can both pull from and push to IcyPeas via REST. For full bidirectional CRM-style sync, see the CRM apps in the directory.